November 28, 2025Nov 28 I had an 18tb drive die. I put a 20tb drive in it's place but it says the xfs is unmountable after the parity rebuild? I have dual parity but am unsure how to proceed.Edit: So I think its worse than I thought?Here's diags:homesrv-diagnostics-20251127-2114.zip Edited November 28, 2025Nov 28 by MatthewH12
November 28, 2025Nov 28 Author 4 minutes ago, JorgeB said:Check filesystem on that disk.I ran the command multiple times with and without -L. It always crashes in the same place. Phase 1 - find and verify superblock...Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps...clearing needsrepair flag and regenerating metadatasb_icount 2858656, counted 32sb_ifree 52847, counted 29sb_fdblocks 549504460, counted 4394060152 - found root inode chunkPhase 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - process newly discovered inodes...Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 4 - agno = 5 - agno = 11 - agno = 9 - agno = 7 - agno = 2 - agno = 8 - agno = 12 - agno = 3 - agno = 10 - agno = 13 - agno = 14 - agno = 15 - agno = 6 - agno = 0 - agno = 16Phase 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 failedMetadata corruption detected at 0x49d6d5, xfs_sb block 0x0/0x200libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1SB summary counter sanity check failedMetadata corruption detected at 0x49d6d5, xfs_sb block 0x0/0x200libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1xfs_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.For now I pulled the 20tb just in case. unRAID shows disk 15 as empty but still unmountable. Edited November 28, 2025Nov 28 by MatthewH12
November 28, 2025Nov 28 Community Expert XFS is unable to repair the filesystem, do you still have the old disk intact?
November 28, 2025Nov 28 Author I don't :(. Based on other posts im trying data recovery on the 20tb based on the parity rebuild. Hope it works.
November 28, 2025Nov 28 Community Expert Solution Parity can't help with filesystem corruption; the rebuilt disk will look the same as the current emulated one. If you no longer have the old disk, best bet is to use a file recovery app, like UFS Explorer. The free trial should show if it can recover the data.
November 28, 2025Nov 28 Author Good to know. How do I delete disk 15 from unRAID so I can put a blank drive there and not rebuild on it?
November 28, 2025Nov 28 Community Expert You would need to do a new config, but would then need to rebuild parity, which takes the same time as the disk rebuild.
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.