kiwininja Posted March 1, 2021 Share Posted March 1, 2021 So I was replacing an old failing drive in my array and everything was going fine. When the process completed I was surprised to see a different drive in the array was now disabled. I have no idea how or why, there has been no issues with the drive previously, it had been working without issues for months. I stopped the array, rebooted the server, and now I'm getting the message that this drive is "Unmountable: No file system". I did some searching on the forums already and found this thread from a couple years ago: https://forums.unraid.net/topic/69765-solved-unmountable-no-file-system/page/2/ Not sure if I should follow the steps in that thread or not. Any help would be greatly appreicated. harrier-diagnostics-20210301-1359.zip Quote Link to comment
itimpi Posted March 1, 2021 Share Posted March 1, 2021 Handling of unmountable disks is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the unRaid GUI. Quote Link to comment
kiwininja Posted March 2, 2021 Author Share Posted March 2, 2021 Ok, I mounted it in maintence mode, ran a check on it, found a bunch of errors, and went ahead and did a repair. The repair log is huge, +300k lines, but the bulk of it looks like this 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... Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x3c09dc188/0x1000 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x311f56fd8/0x1000Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x417f1ea60/0x1000 btree block 11/8 is suspect, error -74 btree block 12/8 is suspect, error -74 bad magic # 0x7b50eae6 in btbno block 11/8 btree block 9/8 is suspect, error -74 bad magic # 0xc45ced5e in btbno block 9/8 bad magic # 0x96306338 in btbno block 12/8 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x417f1ea50/0x1000 btree block 12/6 is suspect, error -74 bad magic # 0xf6500f3f in btcnt block 12/6 agf_freeblks 137168192, counted 0 in ag 12 agf_longest 136980482, counted 0 in ag 12 agf_btreeblks 10, counted 0 in ag 12 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x311f56fc8/0x1000 btree block 9/6 is suspect, error -74 bad magic # 0xc45ceddd in btcnt block 9/6 agf_freeblks 153991353, counted 0 in ag 9 agf_longest 153690905, counted 0 in ag 9 agf_btreeblks 10, counted 0 in ag 9 Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x311f704b8/0x1000 btree block 9/12964 is suspect, error -74 bad magic # 0xe3a7d737 in inobt block 9/12964 inode chunk claims untracked block, finobt block - agno 9, bno 8300, inopb 8 inode chunk claims untracked block, finobt block - agno 9, bno 8301, inopb 8 inode chunk claims untracked block, finobt block - agno 9, bno 8302, inopb 8 inode chunk claims untracked block, finobt block - agno 9, bno 8303, inopb 8 inode chunk claims untracked block, finobt block - agno 9, bno 8304, inopb 8 inode chunk claims untracked block, finobt block - agno 9, bno 8305, inopb 8 inode chunk claims untracked block, finobt block - agno 9, bno 8306, inopb 8 inode chunk claims untracked block, finobt block - agno 9, bno 8307, inopb 8 undiscovered finobt record, ino 19327419232 (9/66400) undiscovered finobt record, ino 19327419296 (9/66464) undiscovered finobt record, ino 19327421536 (9/68704 Phase 3 - for each AG... - scan and clear agi unlinked lists... found inodes not in the inode allocation tree found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 Metadata CRC error detected at 0x4598a9, xfs_dir3_block block 0x3697b5500/0x1000 bad directory block magic # 0x94ddd42c in block 0 for directory inode 4299986059 corrupt block 0 in directory inode 4299986059 will junk block no . entry for directory 4299986059 no .. entry for directory 4299986059 problem with directory contents in inode 4299986059 cleared inode 4299986059 - agno = 3 - agno = 4 - agno = 5 - agno = 6 Metadata CRC error detected at 0x4598a9, xfs_dir3_block block 0x3c49f5eb0/0x1000 bad directory block magic # 0xf651cca3 in block 0 for directory inode 12888387655 corrupt block 0 in directory inode 12888387655 will junk block no . entry for directory 12888387655 no .. entry for directory 12888387655 problem with directory contents in inode 12888387655 cleared inode 12888387655 - agno = 7 - agno = 8 Metadata corruption detected at 0x435c33, xfs_inode block 0x2bab45be0/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2bab45c00/0x4000 Metadata corruption detected at 0x435c33, xfs_inode block 0x2bab46440 bad CRC for inode 17181119776 bad magic number 0x566 on inode 17181119776 bad version number 0x24 on inode 17181119776 inode identifier 11108147623858496690 mismatch on inode 17181119776 bad CRC for inode 17181119777 bad magic number 0x6ad8 on inode 17181119777 bad version number 0x64 on inode 17181119777 inode identifier 13067490434406963586 mismatch on inode 17181119777 The bad CRC for inode, versino number, and magic number lines repeat forever, with some metadata corrouption detected errors every so often. Eventually it gets to phase 4 and I start seeing entries like these. Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 4 - agno = 5 - agno = 1 - agno = 3 - agno = 0 entry "Prancer (1989).mp4" at block 0 offset 1824 in directory inode 4297828966 references non-existent inode 25773790676 entry "temp" in shortform directory 6442451040 references non-existent inode 19328899583 entry "Data" in shortform directory 10737418336 references non-existent inode 19327352928 clearing inode number in entry at offset 1824... junking entry "Data" in directory inode 10737418336 entry "Planet Terror (2007).mp4" at block 0 offset 2000 in directory inode 4297828966 references non-existent inode 23623319597 entry "64" at block 0 offset 144 in directory inode 8589934691 references non-existent inode 19327352929 corrected i8 count in directory 10737418336, was 5, now 4 clearing inode number in entry at offset 144... Phase 5 & 6 look like this. Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... entry "Wrestling" in dir ino 102 doesn't have a .. entry, will set it in ino 6658268659. entry "MMA" in dir ino 102 doesn't have a .. entry, will set it in ino 4522158591. entry ".." in directory inode 255489 points to non-existent inode 27984402686 bad hash table for directory inode 255489 (no data entry): rebuilding Phase 7 - verify and correct link counts... resetting inode 4297829346 nlinks from 6 to 5 resetting inode 4297829360 nlinks from 6 to 5 resetting inode 4297829376 nlinks from 8 to 7 resetting inode 6442451040 nlinks from 8 to 7 resetting inode 10737418336 nlinks from 7 to 6 resetting inode 17179869285 nlinks from 3 to 2 resetting inode 17179869286 nlinks from 3 to 2 resetting inode 23622320240 nlinks from 5 to 4 resetting inode 17179869303 nlinks from 4 to 2 resetting inode 23622320252 nlinks from 46 to 34 Once it completed I tried to bring the array online, but I now get a warring that all existing data on the device will be overwritten, so i'm not exactly sure where to go from here. I grabbed the SMART report for the drive as well. harrier-smart-20210301-1942.zip Quote Link to comment
kiwininja Posted March 2, 2021 Author Share Posted March 2, 2021 Well, I had left in maintence mode and forgot that my monthly parity check is scheduled for the evening of the first. It's now in the process of rebuilding the drive, so I guess i'm just going to wait and see what happens. 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.