Guybrush Posted May 6, 2020 Share Posted May 6, 2020 (edited) Hello, I have an issue with one of my drive I tried to fix it following the wiki, and the check seems to fails as i still have the errors (edited for readability). Quote 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... bad magic number Metadata CRC error detected at 0x438fd6, xfs_agf block 0x27fffffd9/0x200 bad on-disk superblock 5 - bad magic number primary/secondary superblock 5 conflict - AG superblock geometry info conflicts with filesystem geometry would zero unused portion of secondary superblock (AG #5) bad magic # 0x241a9c92 for agf 5 bad version # 1837485677 for agf 5 bad sequence # 1871924434 for agf 5 bad length 1157422139 for agf 5, should be 268435455 flfirst -1545983250 in agf 5 too large (max = 118) fllast -1596419389 in agf 5 too large (max = 118) bad uuid aa939e81-254c-5ddd-d725-b1ba1cc7686b for agf 5 would reset bad sb for ag 5 would reset bad agf for ag 5 bad uncorrected agheader 5, skipping ag... sb_icount 96384, counted 85696 sb_ifree 3170, counted 3008 sb_fdblocks 308284623, counted 244418079 - 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 0x435c33, xfs_inode block 0x18ade340/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x18ade360/0x4000 bad CRC for inode 414049088 bad magic number 0x241a on inode 414049088 bad version number 0x6d on inode 414049088 inode identifier 1575615604729810958 mismatch on inode 414049088 - agno = 1 - agno = 2 - agno = 3 Metadata corruption detected at 0x435c33, xfs_inode block 0x185379468/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x185379488/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x1853794a8/0x4000 bad CRC for inode 6529979520 bad magic number 0x241a on inode 6529979520 ad version number 0x6d on inode 6529979520 inode identifier 1575615604729810958 mismatch on inode 6529979520 bad CRC for inode 6529979521 bad magic number 0x241a on inode 6529979521 bad version number 0x6d on inode 6529979521 inode identifier 1575615604729810958 mismatch on inode 6529979521 inode identifier 1575615604729810958 mismatch on inode 6529979775 imap claims in-use inode 6577379950 is free, would correct imap - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 1 entry "Season 20" in shortform directory 6442451072 references non-existent inode 10737418368 would have junked entry "Season 20" in directory inode 6442451072 would have corrected i8 count in directory 6442451072 from 5 to 4 entry "dl" at block 0 offset 112 in directory inode 131 references non-existent inode 10737418386 would clear inode number in entry at offset 112... entry "Season 1996" in directory inode 15571258390 points to non-existent inode 11012605688, would junk entry entry "Season 2011" in directory inode 15571258390 points to non-existent inode 11012605691, would junk entry bad hash table for directory inode 15571258390 (no data entry): would rebuild - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 254074768, would move to lost+found disconnected dir inode 254074769, would move to lost+found would have reset inode 9744415789 nlinks from 3 to 2 No modify flag set, skipping filesystem flush and exiting.fractal-smart-20200506-2136.zip Any help would be appreciated. fractal-diagnostics-20200506-2134.zip Edited May 12, 2020 by Guybrush Quote Link to comment
trurl Posted May 6, 2020 Share Posted May 6, 2020 19 minutes ago, Guybrush said: No modify flag set, skipping filesystem flush and exiting Since you didn't allow it to modify, it only checked and didn't fix anything. Try again without the -n flag. Quote Link to comment
Guybrush Posted May 7, 2020 Author Share Posted May 7, 2020 My mistake. Changed the flag and after that was able to restart the array, but what could be the root cause (faulty drive maybe ?) Quote 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... bad magic number Metadata CRC error detected at 0x438fd6, xfs_agf block 0x27fffffd9/0x200 bad on-disk superblock 5 - bad magic number primary/secondary superblock 5 conflict - AG superblock geometry info conflicts with filesystem geometry zeroing unused portion of secondary superblock (AG #5) bad magic # 0x241a9c92 for agf 5 bad version # 1837485677 for agf 5 bad sequence # 1871924434 for agf 5 bad length 1157422139 for agf 5, should be 268435455 flfirst -1545983250 in agf 5 too large (max = 118) fllast -1596419389 in agf 5 too large (max = 118) bad uuid aa939e81-254c-5ddd-d725-b1ba1cc7686b for agf 5 reset bad sb for ag 5 reset bad agf for ag 5 Metadata CRC error detected at 0x438bf4, xfs_agfl block 0x27fffffdb/0x200 agfl has bad CRC for ag 5 bad agbno 3378612021 in agfl, agno 5 freeblk count 1 != flcount -865284709 in ag 5 bad agbno 2552588239 for btbno root, agno 5 bad agbno 1064823489 for btbcnt root, agno 5 bad agbno 2907194019 for refcntbt root, agno 5 agf_freeblks 2605949033, counted 0 in ag 5 agf_longest 2030167188, counted 0 in ag 5 agf_btreeblks 1926582071, counted 0 in ag 5 sb_ifree 3170, counted 3180 sb_fdblocks 308284623, counted 244418080 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 Metadata corruption detected at 0x435c33, xfs_inode block 0x18ade340/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x18ade360/0x4000 correcting imap - agno = 4 - agno = 5 Metadata corruption detected at 0x435c33, xfs_inode block 0x280000058/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x280000078/0x4000 - agno = 6 - agno = 7 - process newly discovered inodes... 150ef8860700: Badness in key lookup (length) bp=(bno 0x280000058, len 16384 bytes) key=(bno 0x280000058, len 4096 bytes) 150ef8860700: Badness in key lookup (length) bp=(bno 0x280000078, len 16384 bytes) key=(bno 0x280000078, len 4096 bytes) Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 entry "Season 20" in shortform directory 6442451072 references non-existent inode 10737418368 entry "dl" at block 0 offset 112 in directory inode 131 references non-existent inode 10737418386 clearing inode number in entry at offset 112... entry "enginesupport" in shortform directory 9022914071 references non-existent inode 10737418401 junking entry "enginesupport" in directory inode 9022914071 corrected i8 count in directory 9022914071, was 2, now 1 entry "enginesupport" in shortform directory 9022914075 references non-existent inode 10737418402 junking entry "enginesupport" in directory inode 9022914075 corrected i8 count in directory 9022914075, was 2, now 1 entry "packfiles" in shortform directory 9022914098 references non-existent inode 10737418409 junking entry "packfiles" in directory inode 9022914098 corrected i8 count in directory 9022914098, was 4, now 3 entry ".." at block 0 offset 80 in directory inode 2742138026 references non-existent inode 10737418386 - agno = 5 entry "SRT" in shortform directory 6577379950 references free inode 6577379953 junking entry "SRT" in directory inode 6577379950 corrected i8 count in directory 6577379950, was 2, now 1 - agno = 6 entry ".." at block 0 offset 80 in directory inode 12884902076 references non-existent inode 10737418409 - agno = 7 entry ".." at block 0 offset 80 in directory inode 15276360798 references non-existent inode 10737418409 entry ".." at block 0 offset 80 in directory inode 15540160880 references non-existent inode 10737418386 entry ".." at block 0 offset 80 in directory inode 13069572148 references non-existent inode 10737418386 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 hash table for directory inode 131 (no data entry): rebuilding rebuilding directory inode 131 entry ".." in directory inode 254074771 points to non-existent inode 10737418409 bad hash table for directory inode 254074771 (no data entry): rebuilding rebuilding directory inode 254074771 rebuilding directory inode 264706878 bad hash table for directory inode 2147483776 (no data entry): rebuilding rebuilding directory inode 2147483776 bad hash table for directory inode 2411279122 (no data entry): rebuilding rebuilding directory inode 2411279122 entry ".." in directory inode 2742138026 points to non-existent inode 10737418386 bad hash table for directory inode 2742138026 (no data entry): rebuilding rebuilding directory inode 2742138026 bad hash table for directory inode 4730457579 (no data entry): rebuilding rebuilding directory inode 4730457579 entry ".." in directory inode 4973806733 points to non-existent inode 10737418386 bad hash table for directory inode 4973806733 (no data entry): rebuilding rebuilding directory inode 4973806733 bad hash table for directory inode 6528187596 (no data entry): rebuilding rebuilding directory inode 6528187596 entry ".." in directory inode 6554180230 points to non-existent inode 10737418386 bad hash table for directory inode 6554180230 (no data entry): rebuilding rebuilding directory inode 6554180230 entry ".." in directory inode 12884902076 points to non-existent inode 10737418409 bad hash table for directory inode 12884902076 (no data entry): rebuilding rebuilding directory inode 12884902076 entry ".." in directory inode 13069572148 points to non-existent inode 10737418386 bad hash table for directory inode 13069572148 (no data entry): rebuilding rebuilding directory inode 13069572148 entry ".." in directory inode 15276360798 points to non-existent inode 10737418409 bad hash table for directory inode 15276360798 (no data entry): rebuilding rebuilding directory inode 15276360798 entry ".." in directory inode 15540160880 points to non-existent inode 10737418386 bad hash table for directory inode 15540160880 (no data entry): rebuilding rebuilding directory inode 15540160880 - traversal finished ... disconnected dir inode 15540160880, moving to lost+found disconnected dir inode 15542107024, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 131 nlinks from 17 to 16 resetting inode 6442451072 nlinks from 9 to 8 resetting inode 8594108558 nlinks from 3 to 2 resetting inode 9022914064 nlinks from 5 to 4 resetting inode 9022914071 nlinks from 3 to 2 resetting inode 9022914075 nlinks from 3 to 2 resetting inode 9022914098 nlinks from 6 to 5 resetting inode 575475625 nlinks from 2 to 31 resetting inode 6577379950 nlinks from 3 to 2 resetting inode 4730457579 nlinks from 5 to 4 resetting inode 2147483776 nlinks from 42 to 39 resetting inode 2411279122 nlinks from 28 to 25 Maximum metadata LSN (4:751480) is ahead of log (1:2). Format log to cycle 7. done Quote Link to comment
trurl Posted May 7, 2020 Share Posted May 7, 2020 You might run an extended SMART test on it. Quote Link to comment
Guybrush Posted May 8, 2020 Author Share Posted May 8, 2020 If i read it correctly it could be because of faulty sectors ? fractal-smart-20200507-1257.zip 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.