November 28, 20232 yr My disk 5 reported as unmountable. It's XFS. So I stop the array and start it in maintenance mode. I then go to the GUI and do a check disk (xfs_repair -n). It ran *forever* but didn't finish in a way that I expected. The last few lines of the output are: Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 The check disk button is active again. No options were given for running xfs_repair again. Got lots of output like: imap claims in-use inode 11906112941 is free, would correct imap. Lots and lots of lines like this. Any idea what I should do now?
November 28, 20232 yr Author I got this. should I follow these instructions: 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.
November 28, 20232 yr Author trying to mount the filesystem gives me this: root@Vault:/tmp# mount -t xfs /dev/sdg1 mnt mount: /tmp/mnt: can't read superblock on /dev/sdg1. dmesg(1) may have more information after failed mount system call.
November 28, 20232 yr Author ok, I ran it with -L. it *seemed* to finish even though it never reported being done. here is what is in the UI. After many "correcting imap" lines we see this: found inodes not in the inode allocation tree Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 when trying to mount it now it says structure needs cleaning. ps aux | grep xfs_repair shows xfs_repair is no longer running. Edited November 28, 20232 yr by rykr
November 29, 20232 yr Author xfs_repair just keeps quitting. This is now 3 times it has run for *hours* and then finished with this: found inodes not in the inode allocation tree Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 when. I try to Brin the array back online it still says the drive has no recognizable filesystem. Seems like a bug that is causing xfs_repair to just quit. Trying to mount just gives this: mount: /tmp/mnt: mount(2) system call failed: Structure needs cleaning. dmesg(1) may have more information after failed mount system call. Edited November 29, 20232 yr by rykr
November 29, 20232 yr Community Expert If you're not running the latest Unraid release update and try again, in case there's a newer xfsprogs included, if xfs_repair cannot fix the filesystem not much more you can do, other than restoring from backups or using a file recovery app like UFS explorer.
November 29, 20232 yr Author why is that? If I tell it to rebuild that drive from parity will it just rebuild it corrupted?
November 29, 20232 yr Author yeah, I just don't understand why it doesn't finish with either a success or error. could the xfs_repair program be being killed? I just ran it again like this: xfs_repair -vP /dev/md5p1 it produced this output: Phase 1 - find and verify superblock... - block cache size set to 1402128 entries Phase 2 - using internal log - zero log... zero_log: head block 2 tail block 2 - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata badly aligned inobt rec (starting inode = 10879599959) ir_freecount/free mismatch, inode chunk 5/142181719, freecount 255 nfree 0 invalid inode count, inode chunk 5/142181719, count 255 ninodes 48 agi_count 34401952, counted 34402143 in ag 5 agi_freecount 68, counted 323 in ag 5 sb_icount 266868928, counted 267733823 sb_ifree 244, counted 505 sb_fdblocks 159628764, counted 167451433 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... found inodes not in the inode allocation tree found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 no error, success, or nothing. just stops. I'm on 6.12.4 and I confirmed that 6.12.5 doesn't update the xfs progs
November 29, 20232 yr Author ok, dmesg shows me that xfs_repair is running out of memory going to try again with -m option
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.