All Shares Gone - Lacie 5Big Network 2

[Jocko]

So definitely, there is no issue on your raid devices.

but several mount points are missing in your last output, you should have these lines

Code: Select all

/dev/md4 /media/internal_1 xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/md4 /lacie/tmp xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/md4 /lacie/var xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/md4 /lacie/torrent_dir xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/md4 /lacie/autoupdate xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/md4 /lacie/afp_db xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/md4 /shares/Share xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/md4 /shares/Public xfs rw,nosuid,nodev,usrquota,prjquota 0 0

that would mean the firmware failed to mount md4 and then there is an issue with the fs (xfs) on it.

As I do not use the Lacie firmware, I don't know if these commands are available, so do

Code: Select all

which file xfs_repair

and try also to do a manual mount:
check if mountpoints exist

Code: Select all

ls -l /shares/Share /shares/Public /lacie/tmp /lacie/var /lacie/autoupdate /lacie/afp_db

and if Yes try to do one (for example with tmp)

Code: Select all

mount /dev/md4 /lacie/tmp

[Glaven Clattuck]

"Jocko"]So definitely, there is no issue on your raid devices.

As I do not use the Lacie firmware, I don't know if these commands are available, so do

Code: Select all

which file xfs_repair

this is the result

Code: Select all

/sbin/xfs_repair

can i proceed with the other two command?

[Jocko]

So no need to use fvdw-sl console if we need to check the file system on md4 :thumbup

Before using xfs_repair, I want to know what is the message when you try to mount /dev/md4.

So first do the other commands in my previous post

[Glaven Clattuck]

So no need to use fvdw-sl console if we need to check the file system on md4 :thumbup

Before using xfs_repair, I want to know what is the message when you try to mount /dev/md4.

So first do the other commands in my previous post

This is the first, can i proceed with mount on the /lacie/afp_db that seem the only available?

Code: Select all

[root@LaCie-5big ~]# ls -l /shares/Share /shares/Public /lacie/tmp /lacie/var /lacie/autoupdate /lacie/afp_db
ls: /shares/Share: No such file or directory
ls: /shares/Public: No such file or directory
ls: /lacie/tmp: No such file or directory
ls: /lacie/var: No such file or directory
ls: /lacie/autoupdate: No such file or directory
/lacie/afp_db:




[Jocko]

Yes try it

[Glaven Clattuck]

the response was:

Code: Select all

mount: mounting /dev/md4 on /lacie/afp_db failed: Structure needs cleaning

[Jocko]

So you have an inconsistent fs on md4.

So do this command to clean it

Code: Select all

/sbin/xfs_repair /dev/md4

Note: you may use the flag '-n' to only make a check without repairing... but at the end you will have to repair it

and post its output (with a 16TB device this will take time...)

[Glaven Clattuck]

So you have an inconsistent fs on md4.

So do this command to clean it

Code: Select all

xfs_repair /dev/md4

Note: you may use the flag '-n' to only make a check without repairing... but at the end you will have to repair it

and post its output (with a 16TB device this will take time...)

i think that i need some more

Code: Select all

[root@LaCie-5big ~]# xfs_repair /dev/md4
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.


[Glaven Clattuck]

So you have an inconsistent fs on md4.


Note: you may use the flag '-n' to only make a check without repairing... but at the end you will have to repair it

and post its output (with a 16TB device this will take time...)

ok i repeat the command with -n option at the end and this is the output

Code: Select all

[root@LaCie-5big ~]# xfs_repair /dev/md4 -n     
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
block (24,49737795-49737795) multiply claimed by cnt space tree, state - 2
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
bad hash ordering in block 8388610 of directory inode 12324
        - agno = 1
        - agno = 2
data fork in ino 2151906679 claims free block 1611137185
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - agno = 32
        - agno = 33
        - agno = 34
        - agno = 35
        - agno = 36
        - agno = 37
        - agno = 38
        - agno = 39
        - agno = 40
        - agno = 41
        - agno = 42
        - agno = 43
        - agno = 44
        - agno = 45
        - agno = 46
        - agno = 47
        - agno = 48
        - agno = 49
        - agno = 50
        - agno = 51
        - agno = 52
        - agno = 53
        - agno = 54
        - agno = 55
        - agno = 56
        - agno = 57
        - agno = 58
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - agno = 32
        - agno = 33
        - agno = 34
        - agno = 35
        - agno = 36
        - agno = 37
        - agno = 38
        - agno = 39
        - agno = 40
        - agno = 41
        - agno = 42
        - agno = 43
        - agno = 44
        - agno = 45
        - agno = 46
        - agno = 47
        - agno = 48
        - agno = 49
        - agno = 50
        - agno = 51
        - agno = 52
        - agno = 53
        - agno = 54
        - agno = 55
        - agno = 56
        - agno = 57
        - agno = 58
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
entry "Eragon (2006).nfo" (ino 51265) in dir 12324 is a duplicate name, would junk entry
entry "X-Men.Conflitto.FInale.2006-fanart.jpg" (ino 14317) in dir 12324 is a duplicate name, would junk entry
entry "Eragon (2006).mkv" (ino 51231) in dir 12324 is a duplicate name, would junk entry
entry "Fargo.mkv" (ino 51264) in dir 12324 is a duplicate name, would junk entry
entry "Il Settimo Sigillo (1957) FullHD 1080p 11.7 GB AC3 ITA (AUDIO MUX DA DVD) AC3 ENG_SWE Subs MKV-4A5S1.mkv" (ino 52545) in dir 12324 is a duplicate name, would junk entry
entry "Crossin Over (2009) - HD 720p - AC3 ITA + DTS-AC3 ENG - Subs - NMY.mkv" (ino 57897) in dir 12324 is a duplicate name, would junk entry
entry "Star Trek IX – Insurrezione (1998) HD 720p 6.32 GB AC3 ITA DTS+AC3 ENG Subs MKV-4A5S1.mkv" (ino 57898) in dir 12324 is a duplicate name, would junk entry
entry "Cloud Atlas (2012).1080p.bluray.x264.it.srt" (ino 57899) in dir 12324 is a duplicate name, would junk entry
entry "Crossin Over (2009) - HD 720p - AC3 ITA + DTS-AC3 ENG - Subs - NMY.jpg" (ino 57900) in dir 12324 is a duplicate name, would junk entry
entry "Inception.nfo" (ino 57901) in dir 12324 is a duplicate name, would junk entry
entry "Crossin Over (2009) - HD 720p - AC3 ITA + DTS-AC3 ENG - Subs - NMY.nfo" (ino 57902) in dir 12324 is a duplicate name, would junk entry
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 10354, would move to lost+found
disconnected inode 14317, would move to lost+found
disconnected inode 51231, would move to lost+found
disconnected inode 51264, would move to lost+found
disconnected inode 51265, would move to lost+found
disconnected inode 52545, would move to lost+found
disconnected inode 57897, would move to lost+found
disconnected inode 57898, would move to lost+found
disconnected inode 57899, would move to lost+found
disconnected inode 57900, would move to lost+found
disconnected inode 57901, would move to lost+found
disconnected inode 57902, would move to lost+found
disconnected inode 1074834458, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 10354 nlinks from -1 to 1
would have reset inode 1074834458 nlinks from 0 to 1
No modify flag set, skipping filesystem flush and exiting.


[Jocko]

So try to mount md4 again and if it succeeded unmount md4

Code: Select all

umount /dev/md4

then run again xfs_repair command.

If you failed again to mount md4, you have no choice: need to use the flag L as reported to repair fs

Code: Select all

/sbin/xfs_repair -L /dev/md4