April 7Apr 7 Author Hey folks, sorry to let the thread go cold. Just here to warm it up a bit.Thanks for all your help so far - I'm incredibly grateful for your time.Just to recap - I'm trying to get my array up and running with an emulated disk to try and recover the data from a dead drive.I didNew ConfigStart array in maintenance mode with disk missing.Check File System - FixZero logFixNow the output says "Fatal error" (see below). Is it just time to cut my losses, accept it lost and move on?Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 38912, counted 32 sb_ifree 178, counted 29 sb_fdblocks 127266174, counted 244071373 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... SB summary counter sanity check failed Metadata corruption detected at 0x49c4e5, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 SB summary counter sanity check failed Metadata corruption detected at 0x49c4e5, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 xfs_repair: Releasing dirty buffer to free list! xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair.
April 7Apr 7 Community Expert Newer versions of Unraid have newer versions of xfsprogs. You might try repair again after upgrading Unraid.
April 7Apr 7 Author Thanks, I have updated to 7.2.4 with same result.Seeing as it's in maintenance mode do i need to add any modifiers? Such as "To repair, remove the -n flag to allow fixes." (mentioned in Unraid Docs)? I can't see anywhere in the GUI to change the modifiers.Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 38912, counted 32 sb_ifree 178, counted 29 sb_fdblocks 127266174, counted 244071373 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 1 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... SB summary counter sanity check failed Metadata corruption detected at 0x49d6d5, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 SB summary counter sanity check failed Metadata corruption detected at 0x49d6d5, xfs_sb block 0x0/0x200 libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1 xfs_repair: Releasing dirty buffer to free list! xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair.
April 8Apr 8 Author I tried to run the xfs repair via the terminal with same results.What will happen if I stick a new drive in now? Is there a way to tell it to attempt rebuild from parity?
April 8Apr 8 Community Expert On 2/20/2026 at 4:50 PM, itimpi said:If the emulated disk is not mountable then the rebuilt disk would not be mountable either.
April 8Apr 8 Community Expert I guess you could rebuild it anyway then see if UFS Explorer could recover anything from it.
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.