jang430 Posted March 5, 2021 Share Posted March 5, 2021 Please help take a look. tower-diagnostics-20210305-0958.zip Quote Link to comment
itimpi Posted March 5, 2021 Share Posted March 5, 2021 Your syslog seems to be full of error messages related to disk8 and suggesting you run a file system check/repair. Quote Link to comment
jang430 Posted March 5, 2021 Author Share Posted March 5, 2021 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x575428e0/0x1000 btree block 1/1 is suspect, error -74 bad magic # 0 in btbno block 1/1 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0x105fc7a90/0x1000 btree block 3/1 is suspect, error -74 bad magic # 0 in btbno block 3/1 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x575428e8/0x1000 btree block 1/2 is suspect, error -74 bad magic # 0 in btcnt block 1/2 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0x105fc7a98/0x1000 btree block 3/2 is suspect, error -74 bad magic # 0 in btcnt block 3/2 Metadata CRC error detected at 0x43c89d, xfs_bnobt block 0xaea851b8/0x1000 btree block 2/1 is suspect, error -74 bad magic # 0 in btbno block 2/1 agf_freeblks 1282100, counted 0 in ag 1 agf_longest 1196437, counted 0 in ag 1 agf_freeblks 5042979, counted 0 in ag 3 agf_longest 4799269, counted 0 in ag 3 Metadata CRC error detected at 0x43c89d, xfs_cntbt block 0xaea851c0/0x1000 btree block 2/2 is suspect, error -74 bad magic # 0 in btcnt block 2/2 Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x575428f0/0x1000 btree block 1/3 is suspect, error -74 bad magic # 0 in inobt block 1/3 Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0x105fc7aa0/0x1000 btree block 3/3 is suspect, error -74 bad magic # 0 in inobt block 3/3 agf_freeblks 15221718, counted 0 in ag 2 agf_longest 15126004, counted 0 in ag 2 inode chunk claims untracked block, finobt block - agno 1, bno 1047624, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1047625, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1047626, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1047627, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1047628, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1047629, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1047630, inopb 8 inode chunk claims untracked block, finobt block - agno 1, bno 1047631, inopb 8 undiscovered finobt record, ino 2155864640 (1/8380992) agi_count 1024, counted 0 in ag 1 agi_freecount 30, counted 0 in ag 1 Metadata CRC error detected at 0x46ad5d, xfs_inobt block 0xaea851c8/0x1000 btree block 2/3 is suspect, error -74 bad magic # 0 in inobt block 2/3 inode chunk claims untracked block, finobt block - agno 3, bno 3956272, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3956273, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3956274, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3956275, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3956276, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3956277, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3956278, inopb 8 inode chunk claims untracked block, finobt block - agno 3, bno 3956279, inopb 8 undiscovered finobt record, ino 6474101120 (3/31650176) agi_count 768, counted 0 in ag 3 agi_freecount 4, counted 0 in ag 3 inode chunk claims untracked block, finobt block - agno 2, bno 6412488, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 6412489, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 6412490, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 6412491, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 6412492, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 6412493, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 6412494, inopb 8 inode chunk claims untracked block, finobt block - agno 2, bno 6412495, inopb 8 undiscovered finobt record, ino 4346267200 (2/51299904) agi_count 768, counted 0 in ag 2 agi_freecount 42, counted 0 in ag 2 sb_icount 3392, counted 832 sb_ifree 105, counted 29 sb_fdblocks 40725843, counted 19179046 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... found inodes not in the inode allocation tree 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 - agno = 3 - 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 = 1 - agno = 3 entry "TV" in shortform directory 131 references non-existent inode 2147483776 would have junked entry "TV" in directory inode 131 entry "Movies" in shortform directory 131 references non-existent inode 4336563546 would have junked entry "Movies" in directory inode 131 would have corrected i8 count in directory 131 from 1 to 0 entry "Season 3" in shortform directory 132 references non-existent inode 2147483787 would have junked entry "Season 3" in directory inode 132 entry "Season 5" in shortform directory 132 references non-existent inode 4297829003 would have junked entry "Season 5" in directory inode 132 would have corrected i8 count in directory 132 from 1 to 0 entry "Season 1" in shortform directory 133 references non-existent inode 2147483788 would have junked entry "Season 1" in directory inode 133 entry "Season 1" in shortform directory 136 references non-existent inode 4297829006 would have junked entry "Season 1" in directory inode 136 entry "Season 2" in shortform directory 136 references non-existent inode 4336599905 would have junked entry "Season 2" in directory inode 136 would have corrected i8 count in directory 136 from 2 to 0 entry "Season 3" in shortform directory 137 references non-existent inode 2147483791 would have junked entry "Season 3" in directory inode 137 entry "Season 1" in shortform directory 139 references non-existent inode 2147483793 would have junked entry "Season 1" in directory inode 139 entry "Season 2" in shortform directory 139 references non-existent inode 4297829009 would have junked entry "Season 2" in directory inode 139 entry "Season 3" in shortform directory 139 references non-existent inode 6442451089 would have junked entry "Season 3" in directory inode 139 would have corrected i8 count in directory 139 from 2 to 0 entry "Season 1" in shortform directory 140 references non-existent inode 4297829010 would have junked entry "Season 1" in directory inode 140 entry "Season 5" in shortform directory 140 references non-existent inode 6442451090 would have junked entry "Season 5" in directory inode 140 entry "Season 2" in shortform directory 140 references non-existent inode 4336599935 would have junked entry "Season 2" in directory inode 140 entry "Season 3" in shortform directory 140 references non-existent inode 6474100231 would have junked entry "Season 3" in directory inode 140 would have corrected i8 count in directory 140 from 4 to 0 entry ".." at block 0 offset 80 in directory inode 142 references non-existent inode 6442451072 entry ".." at block 0 offset 80 in directory inode 143 references non-existent inode 6442451073 entry ".." at block 0 offset 80 in directory inode 144 references non-existent inode 6442451074 entry ".." at block 0 offset 80 in directory inode 145 references non-existent inode 2147483780 entry ".." at block 0 offset 80 in directory inode 146 references non-existent inode 6442451077 entry ".." at block 0 offset 80 in directory inode 148 references non-existent inode 6442451079 entry ".." at block 0 offset 80 in directory inode 152 references non-existent inode 4297829001 entry ".." at block 0 offset 80 in directory inode 21275573 references non-existent inode 2147483786 entry "Season 4" in shortform directory 21346789 references non-existent inode 2155840040 would have junked entry "Season 4" in directory inode 21346789 entry "Season 5" in shortform directory 21346789 references non-existent inode 4336599903 would have junked entry "Season 5" in directory inode 21346789 would have corrected i8 count in directory 21346789 from 1 to 0 entry "Season 1" in shortform directory 21346791 references non-existent inode 4336599907 would have junked entry "Season 1" in directory inode 21346791 entry "Season 2" in shortform directory 21346791 references non-existent inode 6474099254 would have junked entry "Season 2" in directory inode 21346791 would have corrected i8 count in directory 21346791 from 2 to 0 entry "Season 1" in shortform directory 21346792 references non-existent inode 6474099928 would have junked entry "Season 1" in directory inode 21346792 would have corrected i8 count in directory 21346792 from 1 to 0 entry ".." at block 0 offset 80 in directory inode 21346793 references non-existent inode 2147483777 entry ".." at block 0 offset 80 in directory inode 21346796 references non-existent inode 4297828996 entry ".." at block 0 offset 80 in directory inode 21346797 references non-existent inode 4336599898 entry ".." at block 0 offset 80 in directory inode 21346798 references non-existent inode 6474099246 entry ".." at block 0 offset 80 in directory inode 21346801 references non-existent inode 6474099247 entry ".." at block 0 offset 80 in directory inode 21353740 references non-existent inode 2155840038 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. Quote Link to comment
trurl Posted March 5, 2021 Share Posted March 5, 2021 Looks like you might have a mess if you do the actual repair. Do you have backups? Quote Link to comment
jang430 Posted March 5, 2021 Author Share Posted March 5, 2021 Data is not critical. I can try to move data to another drive using Unbalance. Would this be advisable? Quote Link to comment
trurl Posted March 5, 2021 Share Posted March 5, 2021 You can try that but I would expect lots of errors. I don't know how Unbalance handles those. Repairing shouldn't make things any worse than they already are. Quote Link to comment
jang430 Posted March 5, 2021 Author Share Posted March 5, 2021 I'll repair then. I'll remove the "-n". Any other parameter I should put in? Quote Link to comment
trurl Posted March 5, 2021 Share Posted March 5, 2021 As usual if it asks for -L you will have to use it. 1 Quote Link to comment
jang430 Posted March 5, 2021 Author Share Posted March 5, 2021 (edited) I didn't put -L yet, I clicked on check, was done instantanously. I wasn't able to see the result. I ran Check again, this time, with -n, and was given this result: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - agno = 3 - 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 = 1 - agno = 3 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 Edited March 5, 2021 by jang430 add info Quote Link to comment
trurl Posted March 5, 2021 Share Posted March 5, 2021 Are your files there? Is anything in lost+found? Quote Link to comment
jang430 Posted March 5, 2021 Author Share Posted March 5, 2021 When I restarted the Array (not in maintenance mode), there are no files in the folder left . Lost and found is full of files. Does this mean the drive is still usable? I can just delete files in lost and found. Quote Link to comment
jang430 Posted March 5, 2021 Author Share Posted March 5, 2021 (edited) I performed a smart test on the drive. Please see attached file.tower-smart-20210305-1417.zip Is this drive still usable? Or do I have to replace it? Edited March 5, 2021 by jang430 Quote Link to comment
jang430 Posted March 5, 2021 Author Share Posted March 5, 2021 Hi. Can i just delete lost and found? Can the drive still be used?Sent from my iPhone using Tapatalk Quote Link to comment
trurl Posted March 5, 2021 Share Posted March 5, 2021 17 hours ago, jang430 said: I performed a smart test on the drive. According to that attached file the long smart test was still in progress. Post the results Quote Link to comment
jang430 Posted March 6, 2021 Author Share Posted March 6, 2021 This should be done by now. tower-smart-20210306-0905.zip Quote Link to comment
trurl Posted March 6, 2021 Share Posted March 6, 2021 I don't really have any experience with SAS drives but if it passed long test I guess it should be OK. Maybe someone else will take a look. 1 Quote Link to comment
jang430 Posted March 7, 2021 Author Share Posted March 7, 2021 Thank you @JorgeB 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.