September 30, 20232 yr Hello my array has a corrupted disk and i had to chance this i had removed the disk from the array und startet it again he says the disk is now emulated, but on the right side it say Unmountable: Unsupported or no file system and so i cant access the files from the emulated disk i dont know what to do now..... hope anyone can help me, there are many needed data on this tower-diagnostics-20230930-2224.zip
October 1, 20232 yr Author 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 19616, counted 32 sb_ifree 1510, counted 29 sb_fdblocks 202752381, counted 1464608865 - 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 - 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 = 4 - agno = 1 - agno = 3 - agno = 5 - agno = 2 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 0x47c2cb, 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 0x47c2cb, 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. thats the output without -n
October 1, 20232 yr Community Expert There are no disk errors logged, suggesting a xfs_repair problem, so not much more you can do, except maybe waiting for a newer xfsprogs release in case they fix that issue, other option is to post in the xfs mailing list to see if they can help.
October 1, 20232 yr Author That's really a joke i have two parity disks extra for emergencies, but it doesn't help totally stupid.... I still thank you for the help
October 1, 20232 yr Community Expert Parity cannot help with filesystem corruption, another option would be to use a file recovery util like UFS explorer, there's a free tril that should show if it can recover the data.
October 6, 20232 yr Author Hello, I was able to save a large part of the data using data recovery tools. Not all of them, but at least a large part, thanks for the tip. How do I proceed now? because disk1 (from parity) is still unmountable. should I format this now? and then put in a new disk? or create a new config and have the parity completely rebuilt? best regards nowaczuk
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.