Phase1 Posted December 22, 2021 Share Posted December 22, 2021 I tried to replace a drive in my server getting lots of CRC errors and ended up finding out the slot in the server was causing the issues, the new drive was getting the CRC errors after I precleared it and put it in the slot. So I stopped the array and moved the drive to a better slot and ran new config. Ever since then I have not been able to write to my storage array, cache seems to be fine. Much more stuff happened, even once Fix Common Problems told me a disk (the new one) was read only but not getting that anymore after getting the array clean again (another disk rebuilt) no more emulated disks. So a lot happened but in the end I just want to figure out how to write again to the disks? Attaching my diagnostics. Let me know if you need more info. Thanks for your help. media-diagnostics-20211221-1950.zip Quote Link to comment
Solution JorgeB Posted December 22, 2021 Solution Share Posted December 22, 2021 Check filesystem on disk6 Quote Link to comment
Phase1 Posted December 23, 2021 Author Share Posted December 23, 2021 Thank You Jorge! I saw you post this on another topic but I wasnt sure if it was the answer for mine. Worked like a charm. First scan. 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... agf_freeblks 1794208, counted 2348207 in ag 3 agf_longest 285672, counted 577407 in ag 3 agf_freeblks 7171354, counted 8192197 in ag 2 agi_freecount 39, counted 58 in ag 3 agi_freecount 78, counted 81 in ag 2 sb_ifree 628, counted 650 sb_fdblocks 1065708472, counted 1080908261 - 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 imap claims in-use inode 4333133617 is free, would correct imap data fork in ino 4333133618 claims free block 541656860 imap claims in-use inode 4333133618 is free, would correct imap imap claims in-use inode 4333133619 is free, would correct imap - agno = 3 data fork in ino 6445012872 claims free block 805626607 imap claims in-use inode 6445012872 is free, would correct imap data fork in ino 6445012874 claims free block 1048917620 imap claims in-use inode 6445012874 is free, would correct imap data fork in ino 6445012876 claims free block 805626624 imap claims in-use inode 6445012876 is free, would correct imap imap claims in-use inode 6445012878 is free, would correct imap data fork in ino 6445012880 claims free block 805830353 imap claims in-use inode 6445012880 is free, would correct imap imap claims in-use inode 6445012882 is free, would correct imap imap claims in-use inode 6445012884 is free, would correct imap data fork in ino 6445012886 claims free block 805830373 imap claims in-use inode 6445012886 is free, would correct imap data fork in ino 6445012888 claims free block 805830384 imap claims in-use inode 6445012888 is free, would correct imap imap claims in-use inode 6445012890 is free, would correct imap imap claims in-use inode 6445012892 is free, would correct imap data fork in ino 6445012894 claims free block 805830397 imap claims in-use inode 6445012894 is free, would correct imap data fork in ino 6445012896 claims free block 805830406 imap claims in-use inode 6445012896 is free, would correct imap imap claims in-use inode 6445012898 is free, would correct imap data fork in ino 6445012900 claims free block 805626638 imap claims in-use inode 6445012900 is free, would correct imap imap claims in-use inode 6445012902 is free, would correct imap data fork in ino 6445012904 claims free block 805830431 imap claims in-use inode 6445012904 is free, would correct imap data fork in ino 6446486471 claims free block 805810807 data fork in ino 6446486513 claims free block 1026185368 imap claims in-use inode 6446486513 is free, would correct imap data fork in ino 6446486514 claims free block 805830316 imap claims in-use inode 6446486514 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 = 2 - agno = 6 - agno = 7 - agno = 3 - agno = 4 - agno = 5 - agno = 1 setting reflink flag on inode 4333133617 setting reflink flag on inode 4343559590 Missing reference count record for (2/236955880) len 1020811 count 2 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. Next I tried the repair Quote Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. That last error tripped me up a bit but all I had to do was stop the array, and start it in normal mode. Left it in normal for about 10 seconds and then stopped it again and then started it in maintenance mode again. Then ran the repair again: Quote Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... agf_freeblks 1794208, counted 2348207 in ag 3 agf_longest 285672, counted 577407 in ag 3 agf_freeblks 7171353, counted 8192196 in ag 2 agi_freecount 39, counted 58 in ag 3 agi_freecount 76, counted 79 in ag 2 sb_ifree 622, counted 644 sb_fdblocks 1078761067, counted 1080335909 - 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 correcting imap data fork in ino 4333133618 claims free block 541656860 correcting imap correcting imap - agno = 3 data fork in ino 6445012872 claims free block 805626607 correcting imap data fork in ino 6445012874 claims free block 1048917620 correcting imap data fork in ino 6445012876 claims free block 805626624 correcting imap correcting imap data fork in ino 6445012880 claims free block 805830353 correcting imap correcting imap correcting imap data fork in ino 6445012886 claims free block 805830373 correcting imap data fork in ino 6445012888 claims free block 805830384 correcting imap correcting imap correcting imap data fork in ino 6445012894 claims free block 805830397 correcting imap data fork in ino 6445012896 claims free block 805830406 correcting imap correcting imap data fork in ino 6445012900 claims free block 805626638 correcting imap correcting imap data fork in ino 6445012904 claims free block 805830431 correcting imap data fork in ino 6446486471 claims free block 805810807 data fork in ino 6446486513 claims free block 1026185368 correcting imap data fork in ino 6446486514 claims free block 805830316 correcting 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 = 5 - agno = 7 - agno = 2 - agno = 6 - agno = 4 - agno = 1 Missing reference count record for (2/236955880) len 1020811 count 2 setting reflink flag on inode 4333133617 setting reflink flag on inode 4343559590 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done 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.