kevinsyn Posted February 24, 2023 Share Posted February 24, 2023 Hi there, I accidently mounted the wrong drive on my unassigned drives to replace one of the drives on my main shared drives. I immediately stopped the array and replaced the right drive. My main array is all good, but my unassigned drive XFS is understandably corrupt. I had some files on it is there any way to recover? On running the filesystem check script on unassigned: FS: crypto_LUKS Opening crypto_LUKS device '/dev/sdf1'... Executing file system check: /sbin/xfs_repair -n /dev/mapper/WorkingDrive 2>&1 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... Metadata CRC error detected at 0x46b78d, xfs_inobt block 0xaea80678/0x1000 btree block 3/3 is suspect, error -74 bad magic # 0xbe99d14 in inobt block 3/3 sb_fdblocks 2424336792, counted 2441366498 - 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 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 - agno = 4 - agno = 5 - agno = 8 - agno = 9 - agno = 7 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 6 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting. Closing crypto_LUKS device '/dev/sdf1'... File system corruption detected! RUN WITH CORRECT FLAG DONE When trying to repair it with "Run with correct flag" FS: crypto_LUKS Opening crypto_LUKS device '/dev/sdf1'... Executing file system check: /sbin/xfs_repair -e /dev/mapper/WorkingDrive 2>&1 xfs_repair: cannot open /dev/mapper/WorkingDrive: Device or resource busy Closing crypto_LUKS device '/dev/sdf1'... File system corruption detected! Anyway to recover this or to repair the drive? Quote Link to comment
dlandon Posted February 24, 2023 Share Posted February 24, 2023 Post diagnostics. Quote Link to comment
kevinsyn Posted February 25, 2023 Author Share Posted February 25, 2023 Adding diagnostics blackhole-diagnostics-20230225-1251.zip Quote Link to comment
dlandon Posted February 25, 2023 Share Posted February 25, 2023 I think there may be an issue with Ud when the disk is encrypted. I'll take a look at it later today or tomorrow. Quote Link to comment
dlandon Posted February 26, 2023 Share Posted February 26, 2023 I'm making a change in UD that might be hwlpful with this situation. I'll release a new version later today. Update and then try and see if it works. 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.