August 25, 20232 yr I have been moving everything off my two cache drives. Suddenly my cachetwo drive is not stating its Unmountable: Unsupported or no file system. I need some help to figure this out. It was not done moving everything off. I know the diagnostics may not have much info as I rebooted the system. heimdall-diagnostics-20230824-2230.zip
August 25, 20232 yr Author Ran the GUI file system check and this is what it is showing. Does the blow mean everything is lost? ~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... invalid start block 2829587215 in record 331 of cnt btree block 3/33549 invalid start block 2420771162 in record 343 of cnt btree block 3/33549 agf_freeblks 83920841, counted 83914624 in ag 3 agi unlinked bucket 11 is 37097611 in ag 3 (inode=3258323083) sb_icount 1252096, counted 1177344 sb_ifree 70803, counted 357089 sb_fdblocks 286625134, counted 338414693 - 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 bad CRC for inode 26263971 bad CRC for inode 26263971, would rewrite would have cleared inode 26263971 - agno = 1 - agno = 2 bad CRC for inode 2189826741 bad CRC for inode 2189826741, would rewrite would have cleared inode 2189826741 bad CRC for inode 2254308065 inode identifier 10387980935659847679 mismatch on inode 2254308065 bad CRC for inode 2254308065, would rewrite inode identifier 10387980935659847679 mismatch on inode 2254308065 would have cleared inode 2254308065 - agno = 3 bad CRC for inode 3243741208 inode identifier 7552285953063714815 mismatch on inode 3243741208 bad CRC for inode 3243741208, would rewrite i node identifier 7552285953063714815 mismatch on inode 3243741208 would have cleared inode 3243741208 bad CRC for inode 3280781721 inode identifier 17873957955880681471 mismatch on inode 3280781721 bad CRC for inode 3280781721, would rewrite inode identifier 17873957955880681471 mismatch on inode 3280781721 would have cleared inode 3280781721 bad CRC for inode 3330512564 bad CRC for inode 3330512564, would rewrite would have cleared inode 3330512564 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (3,4642978-4646096) only seen by one free space btree free space (3,38657840-38660937) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 entry "Indexes" in shortform directory 2170818481 references free inode 3243741208 would have junked entry "Indexes" in directory inode 2170818481 bad CRC for inode 3243741208, would rewrite inode identifier 7552285953063714815 mismatch on inode 3243741208 would have cleared inode 3243741208 bad CRC for inode 26263971, would rewrite would have cleared inode 26263971 bad CRC for inode 2189826741, would rewrite would have cleared inode 2189826741 entry "GoP-0.xml" in shortform directory 2201749520 references free inode 2254308065 would have junked entry "GoP-0.xml" in directory inode 2201749520 bad CRC for inode 3280781721, would rewrite inode identifier 17873957955880681471 mismatch on inode 3280781721 would have cleared inode 3280781721 bad CRC for inode 2254308065, would rewrite inode identifier 10387980935659847679 mismatch on inode 2254308065 would have cleared inode 2254308065 bad CRC for inode 3330512564, would rewrite would have cleared inode 3330512564 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... Metadata corruption detected at 0x46f860, inode 0x190c1a3 dinode couldn't map inode 26263971, err = 117 entry "Indexes" in shortform directory inode 2170818481 points to free inode 3243741208 would junk entry Metadata corruption detected at 0x46f860, inode 0x82861ab5 dinode couldn't map inode 2189826741, err = 117 entry "GoP-0.xml" in shortform directory inode 2201749520 points to free inode 2254308065 would junk entry - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 26263975, would move to lost+found disconnected dir inode 86993938, would move to lost+found disconnected dir inode 1137089217, would move to lost+found disconnected dir inode 2209802771, would move to lost+found disconnected inode 2212654973, would move to lost+found disconnected inode 3243741216, would move to lost+found disconnected inode 3258323083, would move to lost+found disconnected dir inode 3306947460, would move to lost+found Phase 7 - verify link counts... would have reset inode 2170818481 nlinks from 3 to 2 Metadata corruption detected at 0x46f860, inode 0x190c1a3 dinode couldn't map inode 26263971, err = 117, can't compare link counts would have reset inode 3258323083 nlinks from 0 to 1 Metadata corruption detected at 0x46f860, inode 0x82861ab5 dinode couldn't map inode 2189826741, err = 117, can't compare link counts No modify flag set, skipping filesystem flush and exiting.
August 25, 20232 yr Author Solution Ok I followed Spaceinvaders One's video on repairing XFS file system and the cache drive is now mounted and data is now available.
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.