NIronwolf Posted August 8, 2022 Share Posted August 8, 2022 I've got a disk I had trouble with dropping from the array and now when I start the array it reports "Unmountable: Wrong or no file system" on the Main page. I'm pretty sure the data is lost on this one but I thought I'd send in a diagnostic anyhow. reality-diagnostics-20220808-0954.zip Quote Link to comment
Solution JorgeB Posted August 8, 2022 Solution Share Posted August 8, 2022 Check filesystem on disk5. Quote Link to comment
NIronwolf Posted August 8, 2022 Author Share Posted August 8, 2022 Ran with "-nv" It's not saying exactly what to try next aside from removing "n" so it can better do the repair (and actually perform the repair). Do you see any reason to run anything other than "-v"? Phase 1 - find and verify superblock... - block cache size set to 845784 entries Phase 2 - using internal log - zero log... zero_log: head block 194072 tail block 194068 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... - 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 Metadata corruption detected at 0x436cd3, xfs_inode block 0x80/0x4000 bad CRC for inode 128 bad next_unlinked 0x7ef00fbf on inode 128 bad (negative) size -8990289313340167769 on inode 128 bad CRC for inode 131 bad next_unlinked 0x94474835 on inode 131 Bad flags2 set in inode 131 inode 131 is marked bigtime but file system does not support large timestamps would zero timestamps. bad CRC for inode 132 bad next_unlinked 0x9d2ffbdc on inode 132 Bad flags2 set in inode 132 inode 132 is marked bigtime but file system does not support large timestamps would zero timestamps. bad CRC for inode 133 bad next_unlinked 0x40cbedb0 on inode 133 inode identifier 5872355820447164167 mismatch on inode 133 bad CRC for inode 156 bad next_unlinked 0x97860f4f on inode 156 inode identifier 16625386536039003860 mismatch on inode 156 bad CRC for inode 128, would rewrite bad next_unlinked 0x7ef00fbf on inode 128, would reset next_unlinked bad (negative) size -8990289313340167769 on inode 128 would clear root inode 128 bad CRC for inode 131, would rewrite bad next_unlinked 0x94474835 on inode 131, would reset next_unlinked Bad flags2 set in inode 131 inode 131 is marked bigtime but file system does not support large timestamps would zero timestamps. would fix bad flags2. Bad CoW extent size 0 on inode 131, would reset to zero directory inode 131 has bad size 6155860142751504924 would have cleared inode 131 bad CRC for inode 132, would rewrite bad next_unlinked 0x9d2ffbdc on inode 132, would reset next_unlinked Bad flags2 set in inode 132 inode 132 is marked bigtime but file system does not support large timestamps would zero timestamps. would fix bad flags2. Bad CoW extent size 0 on inode 132, would reset to zero directory inode 132 has bad size 6351474981558740519 would have cleared inode 132 bad CRC for inode 133, would rewrite bad next_unlinked 0x40cbedb0 on inode 133, would reset next_unlinked inode identifier 5872355820447164167 mismatch on inode 133 would have cleared inode 133 bad CRC for inode 156, would rewrite bad next_unlinked 0x97860f4f on inode 156, would reset next_unlinked inode identifier 16625386536039003860 mismatch on inode 156 would have cleared inode 156 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... root inode would be lost - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 bad CRC for inode 128, - agno = 3 - agno = 2 would rewrite bad next_unlinked 0x7ef00fbf on inode 128, would reset next_unlinked bad (negative) size -8990289313340167769 on inode 128 would clear root inode 128 bad CRC for inode 131, would rewrite bad next_unlinked 0x94474835 on inode 131, would reset next_unlinked Bad flags2 set in inode 131 inode 131 is marked bigtime but file system does not support large timestamps would zero timestamps. would fix bad flags2. Would clear next_unlinked in inode 131 Bad CoW extent size 0 on inode 131, would reset to zero directory inode 131 has bad size 6155860142751504924 would have cleared inode 131 bad CRC for inode 132, would rewrite bad next_unlinked 0x9d2ffbdc on inode 132, would reset next_unlinked Bad flags2 set in inode 132 inode 132 is marked bigtime but file system does not support large timestamps would zero timestamps. would fix bad flags2. Would clear next_unlinked in inode 132 Bad CoW extent size 0 on inode 132, would reset to zero directory inode 132 has bad size 6351474981558740519 would have cleared inode 132 bad CRC for inode 133, would rewrite bad next_unlinked 0x40cbedb0 on inode 133, would reset next_unlinked inode identifier 5872355820447164167 mismatch on inode 133 would have cleared inode 133 entry ".." at block 0 offset 80 in directory inode 149 references free inode 131 entry "Rescued.by.Ruby.2022.1080p.NF.WEB-DL.DDP5.1.Atmos.x264-Telly.mkv" in shortform directory 151 references free inode 156 would have junked entry "Rescued.by.Ruby.2022.1080p.NF.WEB-DL.DDP5.1.Atmos.x264-Telly.mkv" in directory inode 151 bad CRC for inode 156, would rewrite bad next_unlinked 0x97860f4f on inode 156, would reset next_unlinked inode identifier 16625386536039003860 mismatch on inode 156 would have cleared inode 156 entry ".." at block 0 offset 80 in directory inode 3263691136 references free inode 131 entry "NCIS" at block 0 offset 96 in directory inode 3263691136 references free inode 133 would clear inode number in entry at offset 96... No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... would reinitialize root directory - traversing filesystem ... - agno = 0 Metadata corruption detected at 0x436cd3, xfs_inode block 0x80/0x4000 entry ".." in directory inode 149 points to free inode 131, would junk entry bad hash table for directory inode 149 (no data entry): would rebuild would rebuild directory inode 149 entry "Rescued.by.Ruby.2022.1080p.NF.WEB-DL.DDP5.1.Atmos.x264-Telly.mkv" in shortform directory inode 151 points to free inode 156 would junk entry - agno = 1 - agno = 2 - agno = 3 entry ".." in directory inode 3263691136 points to free inode 131, would junk entry entry "NCIS" in directory inode 3263691136 points to free inode 133, would junk entry bad hash table for directory inode 3263691136 (no data entry): would rebuild would rebuild directory inode 3263691136 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 149, would move to lost+found disconnected dir inode 170, would move to lost+found disconnected dir inode 174, would move to lost+found disconnected dir inode 1263113345, would move to lost+found disconnected dir inode 1263113396, would move to lost+found disconnected dir inode 3249673023, would move to lost+found disconnected dir inode 3263691136, would move to lost+found Phase 7 - verify link counts... would have reset inode 3263691136 nlinks from 86 to 85 No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Mon Aug 8 10:44:45 2022 Phase Start End Duration Phase 1: 08/08 10:44:44 08/08 10:44:44 Phase 2: 08/08 10:44:44 08/08 10:44:45 1 second Phase 3: 08/08 10:44:45 08/08 10:44:45 Phase 4: 08/08 10:44:45 08/08 10:44:45 Phase 5: Skipped Phase 6: 08/08 10:44:45 08/08 10:44:45 Phase 7: 08/08 10:44:45 08/08 10:44:45 Total run time: 1 second Quote Link to comment
JorgeB Posted August 8, 2022 Share Posted August 8, 2022 Run again without -n or nothing will be done, if it asks for it use -L. Quote Link to comment
NIronwolf Posted August 8, 2022 Author Share Posted August 8, 2022 Thank you! It's only in lost+found, but there's quite a bit there. 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.