March 12, 20188 yr Yesterday all of my user shares were inaccessible and I saw they all went missing. I rebooted and they all came back except the ones on one of my drives which now shows: Unmountable: No file system Attached is the diagnostics file. Not really sure what to do at this point and didn't want to try something that ended up losing the data. diagnostics-20180312-0621.zip
March 12, 20188 yr Community Expert Check filesystem on disk1: https://lime-technology.com/wiki/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
March 12, 20188 yr Author Thanks. I tried running it with with -nv and this is what came back. Phase 1 - find and verify superblock... - block cache size set to 743528 entries Phase 2 - using internal log - zero log... zero_log: head block 180718 tail block 177815 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... bad agbno 4294967295 in agfl, agno 3 freeblk count 5 != flcount 4 in ag 3 agi unlinked bucket 62 is 149374206 in ag 3 (inode=3370599678) sb_ifree 194, counted 2085 sb_fdblocks 352884694, counted 377133049 - 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 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 5 - agno = 3 - agno = 4 - agno = 2 - agno = 1 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 3370599678, would move to lost+found Phase 7 - verify link counts... would have reset inode 3370599678 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Mon Mar 12 06:49:59 2018 Phase Start End Duration Phase 1: 03/12 06:49:52 03/12 06:49:52 Phase 2: 03/12 06:49:52 03/12 06:49:52 Phase 3: 03/12 06:49:52 03/12 06:49:57 5 seconds Phase 4: 03/12 06:49:57 03/12 06:49:57 Phase 5: Skipped Phase 6: 03/12 06:49:57 03/12 06:49:59 2 seconds Phase 7: 03/12 06:49:59 03/12 06:49:59 Total run time: 7 seconds I then tried just -v and this came back. Phase 1 - find and verify superblock... - block cache size set to 743528 entries Phase 2 - using internal log - zero log... zero_log: head block 180718 tail block 177815 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. I'm not sure what to do next.
March 12, 20188 yr Community Expert 6 minutes ago, LimeB said: use the -L option to destroy the log and attempt a repair.
March 12, 20188 yr Author Just now, trurl said: Thanks. Actually just was posting that I say in another thread that is what someone did. Looks like I am good again. Much appreciation!
Archived
This topic is now archived and is closed to further replies.