September 30, 20169 yr Hello, I'm fairly new to unraid and this is the first issue I'm having with the array. Yesterday, services started being unreachable (Sonarr, couchpotato), but the GUI did not show any issues with the array. Then some of my users noted that files were missing and some that were available were unplayable. A bit of googling pointed me to a reboot of the server, which then showed that disk 4 was unmountable. A bit more googling and I've found the "xfs_repair" section of the drive properties. I ran the check and this is what returned: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0x1/0x200 flfirst 118 in agf 0 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan agi unlinked bucket 32 is 56411040 in ag 0 (inode=56411040) sb_icount 80448, counted 80384 sb_ifree 29401, counted 30355 sb_fdblocks 730392170, counted 730413074 - 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 = 1 - agno = 2 - agno = 4 - agno = 3 - agno = 5 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 56411040, would move to lost+found Phase 7 - verify link counts... would have reset inode 56411040 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. Is my next move to run the check without the "-n" to fix the filesystem? I want to check before I do anything irreparable.
September 30, 20169 yr Is my next move to run the check without the "-n" to fix the filesystem? I want to check before I do anything irreparable. Yes, you can use -v for verbose output.
September 30, 20169 yr Author Is my next move to run the check without the "-n" to fix the filesystem? I want to check before I do anything irreparable. Yes, you can use -v for verbose output. Thanks. I attempted this, but seems to something else going on. Not sure what this output means. Phase 1 - find and verify superblock... - block cache size set to 2224560 entries Phase 2 - using internal log - zero log... zero_log: head block 932207 tail block 931542 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.
September 30, 20169 yr Author Thanks. That seems to have done it. Most of what was on that disk appears to be recovered.
Archived
This topic is now archived and is closed to further replies.