August 16, 20241 yr Hello and thanks in advance for any help. I am on Unraid 6.12.10 and have recently had a few system crashes. After the most recent, one of my disks is coming up as unmountable - my drives are all xfs. I ran xfs_repair in maintenance mode, with the following return - any advice on next steps would be much appreciated! Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... 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... invalid start block 811229492 in record 62 of bno btree block 9/6761 agi unlinked bucket 0 is 363776 in ag 9 (inode=19327716608) agi unlinked bucket 1 is 361025 in ag 9 (inode=19327713857) agi unlinked bucket 2 is 368066 in ag 9 (inode=19327720898) agi unlinked bucket 6 is 368070 in ag 9 (inode=19327720902) agi unlinked bucket 7 is 368071 in ag 9 (inode=19327720903) agi unlinked bucket 12 is 368076 in ag 9 (inode=19327720908) agi unlinked bucket 13 is 368077 in ag 9 (inode=19327720909) agi unlinked bucket 27 is 363803 in ag 9 (inode=19327716635) agi unlinked bucket 29 is 363805 in ag 9 (inode=19327716637) agi unlinked bucket 34 is 363554 in ag 9 (inode=19327716386) agi unlinked bucket 40 is 361832 in ag 9 (inode=19327714664) agi unlinked bucket 43 is 363691 in ag 9 (inode=19327716523) agi unlinked bucket 44 is 361836 in ag 9 (inode=19327714668) agi unlinked bucket 45 is 361837 in ag 9 (inode=19327714669) agi unlinked bucket 48 is 361840 in ag 9 (inode=19327714672) agi unlinked bucket 54 is 361014 in ag 9 (inode=19327713846) agi unlinked bucket 56 is 363832 in ag 9 (inode=19327716664) agi unlinked bucket 57 is 361017 in ag 9 (inode=19327713849) sb_ifree 28867, counted 28968 sb_fdblocks 391915494, counted 412540538 - 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 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (9,80274161-80276207) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 6 - agno = 2 - agno = 4 - agno = 5 - agno = 7 - agno = 9 - agno = 8 - agno = 10 - agno = 3 Would clear next_unlinked in inode 19327716386 Would clear next_unlinked in inode 19327716523 Would clear next_unlinked in inode 19327716608 Would clear next_unlinked in inode 19327716637 Would clear next_unlinked in inode 19327716664 Would clear next_unlinked in inode 19327720898 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 19327713846, would move to lost+found disconnected inode 19327713848, would move to lost+found disconnected inode 19327713849, would move to lost+found disconnected inode 19327713856, would move to lost+found disconnected inode 19327713857, would move to lost+found disconnected inode 19327713858, would move to lost+found disconnected inode 19327713899, would move to lost+found disconnected inode 19327714146, would move to lost+found disconnected inode 19327714664, would move to lost+found disconnected inode 19327714668, would move to lost+found disconnected inode 19327714669, would move to lost+found disconnected inode 19327714672, would move to lost+found disconnected inode 19327716381, would move to lost+found disconnected inode 19327716386, would move to lost+found disconnected inode 19327716523, would move to lost+found disconnected inode 19327716608, would move to lost+found disconnected inode 19327716635, would move to lost+found disconnected inode 19327716637, would move to lost+found disconnected inode 19327716664, would move to lost+found disconnected inode 19327720898, would move to lost+found disconnected inode 19327720902, would move to lost+found disconnected inode 19327720903, would move to lost+found disconnected inode 19327720908, would move to lost+found disconnected inode 19327720909, would move to lost+found Phase 7 - verify link counts... would have reset inode 19327713846 nlinks from 0 to 1 would have reset inode 19327713848 nlinks from 0 to 1 would have reset inode 19327713849 nlinks from 0 to 1 would have reset inode 19327713856 nlinks from 0 to 1 would have reset inode 19327713857 nlinks from 0 to 1 would have reset inode 19327713858 nlinks from 0 to 1 would have reset inode 19327713899 nlinks from 0 to 1 would have reset inode 19327714146 nlinks from 0 to 1 would have reset inode 19327714664 nlinks from 0 to 1 would have reset inode 19327714668 nlinks from 0 to 1 would have reset inode 19327714669 nlinks from 0 to 1 would have reset inode 19327714672 nlinks from 0 to 1 would have reset inode 19327716381 nlinks from 0 to 1 would have reset inode 19327716386 nlinks from 0 to 1 would have reset inode 19327716523 nlinks from 0 to 1 would have reset inode 19327716608 nlinks from 0 to 1 would have reset inode 19327716635 nlinks from 0 to 1 would have reset inode 19327716637 nlinks from 0 to 1 would have reset inode 19327716664 nlinks from 0 to 1 would have reset inode 19327720898 nlinks from 0 to 1 would have reset inode 19327720902 nlinks from 0 to 1 would have reset inode 19327720903 nlinks from 0 to 1 would have reset inode 19327720908 nlinks from 0 to 1 would have reset inode 19327720909 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting.
August 16, 20241 yr Solution How aggressive or conservative do you want to be? Do you have backups of irreplaceable stuff if the file system repair doesn't completely work? You can continue with the repair by running the same procedure, remove the -n and replace it with -L, or you can remove the disk and allow parity to emulate and rebuild the filesystem in its current corrupt state on a new drive, and keep the current drive to operate on with more advanced file recovery software. If you want more than one bite at the apple you need to make a copy of the corrupt drive before you attempt more repairs.
August 16, 20241 yr Author 2 hours ago, JonathanM said: How aggressive or conservative do you want to be? Do you have backups of irreplaceable stuff if the file system repair doesn't completely work? You can continue with the repair by running the same procedure, remove the -n and replace it with -L, or you can remove the disk and allow parity to emulate and rebuild the filesystem in its current corrupt state on a new drive, and keep the current drive to operate on with more advanced file recovery software. If you want more than one bite at the apple you need to make a copy of the corrupt drive before you attempt more repairs. Thank you for the reply - I used -L and it successfully repaired the file system.
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.