Meles Meles Posted August 11, 2021 Share Posted August 11, 2021 (edited) One of my data disks has decided not to mount. UNMOUNTABLE: NOT MOUNTED I've tried 1. Stopping the array. Removing the disk. Start the array. Stop the array. Add the disk back in again. Start the array, rebuild from parity. 24hrs later (once the rebuild has happened), still the same error. grrrrr. 2. xfs_repair (from the GUI so save any potential confusion) with the -L option Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 Metadata CRC error detected at 0x459c09, xfs_dir3_block block 0x280000010/0x1000 bad directory block magic # 0x1e0d0000 in block 0 for directory inode 10737418375 bad bestfree table in block 0 in directory inode 10737418375: repairing table Metadata CRC error detected at 0x459c09, xfs_dir3_block block 0x280000018/0x1000 bad directory block magic # 0xa770470 in block 0 for directory inode 10737418387 bad bestfree table in block 0 in directory inode 10737418387: repairing table - agno = 6 - agno = 7 Metadata CRC error detected at 0x45c929, xfs_dir3_data block 0x40/0x1000 bad directory block magic # 0xa770270 in block 0 for directory inode 15149353946 bad bestfree table in block 0 in directory inode 15149353946: repairing table - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 5 - agno = 2 - agno = 4 - agno = 7 - agno = 0 - agno = 6 bad directory block magic # 0x1e0d0000 in block 0 for directory inode 10737418375 bad bestfree table in block 0 in directory inode 10737418375: repairing table bad directory block magic # 0xa770470 in block 0 for directory inode 10737418387 bad bestfree table in block 0 in directory inode 10737418387: repairing table bad directory block magic # 0xa770270 in block 0 for directory inode 15149353946 - agno = 8 - agno = 9 - agno = 10 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad directory block magic # 0x1e0d0000 for directory inode 10737418375 block 0: fixing magic # to 0x58444233 bad directory block magic # 0xa770470 for directory inode 10737418387 block 0: fixing magic # to 0x58444233 bad directory block magic # 0xa770270 for directory inode 15149353946 block 0: fixing magic # to 0x58444433 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Metadata corruption detected at 0x45c7c0, xfs_dir3_data block 0x40/0x1000 libxfs_bwrite: write verifier failed on xfs_dir3_data bno 0x40/0x1000 Metadata corruption detected at 0x459aa0, xfs_dir3_block block 0x280000010/0x1000 libxfs_bwrite: write verifier failed on xfs_dir3_block bno 0x280000010/0x1000 Metadata corruption detected at 0x459aa0, xfs_dir3_block block 0x280000018/0x1000 libxfs_bwrite: write verifier failed on xfs_dir3_block bno 0x280000018/0x1000 Maximum metadata LSN (8:2325105) is ahead of log (1:2). Format log to cycle 11. xfs_repair: Releasing dirty buffer to free list! xfs_repair: Releasing dirty buffer to free list! 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. Bah.... Any more ideas? This is a brand new (22days Power On) 12TB Ironwolf Pro which is pretty much full. Diagnostics attached....... skynet-diagnostics-20210811-1952.zip Edited August 11, 2021 by Meles Meles Quote Link to comment
Meles Meles Posted August 11, 2021 Author Share Posted August 11, 2021 Oh FFS. now it's mounted OK. 26GB of data in "lost+found" for me to trawl through.... Quote Link to comment
itimpi Posted August 11, 2021 Share Posted August 11, 2021 Just now, Meles Meles said: Oh FFS. now it's mounted OK. 26GB of data in "lost+found" for me to trawl through.... Most of the time it is easier to restore from backups (assuming you have them). if you DO want to sort out a lost+found folder then it is worth mentioning that the Linux ‘file’ command can be used to determine the file type (and thus typically file extension) for files that have lost their names. 1 Quote Link to comment
Meles Meles Posted August 11, 2021 Author Share Posted August 11, 2021 14 minutes ago, itimpi said: Most of the time it is easier to restore from backups (assuming you have them). but surely RAID is a backup? yeah, i'll take a look at the files that are there. if it's all too hard i'll trash them - i'm pretty sure they are all downloaded media files anyway. I "normally" have a backup on a second unRAID server, but as "luck" would have it i've trashed it this week and haven't yet redone my backup of stuff I care about. It's all on Onedrive as well anyway Quote Link to comment
Recommended Posts
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.