jjdemello123 Posted February 18, 2020 Share Posted February 18, 2020 after about 25-30 min of my server running the LOG fills up and then my dockers like Sabnzb suffers and stops downloading. Quote Link to comment
testdasi Posted February 18, 2020 Share Posted February 18, 2020 Tools -> Diagnostics -> attach zip file on your next post. Quote Link to comment
jjdemello123 Posted February 19, 2020 Author Share Posted February 19, 2020 here it is. something else is also happening. after a reboot of my computer not all of mt media is showing up in plex. i have around 1800 movies but now its only showing 1400. all the drives are connected. tower-diagnostics-20200219-1617.zip Quote Link to comment
Squid Posted February 19, 2020 Share Posted February 19, 2020 Run the file system checks on disk 6 https://wiki.unraid.net/Check_Disk_Filesystems Quote Link to comment
jjdemello123 Posted February 20, 2020 Author Share Posted February 20, 2020 here is the smart report for disk 6 tower-smart-20200220-1125.zip Quote Link to comment
JorgeB Posted February 20, 2020 Share Posted February 20, 2020 8 minutes ago, jjdemello123 said: here is the smart report for disk 6 Disk isn't the problem, it's the filesystem, like mentioned above you need to do a filesystem check. Quote Link to comment
jjdemello123 Posted February 20, 2020 Author Share Posted February 20, 2020 i did a file system check on disk 6 and nothing was found Quote Link to comment
jjdemello123 Posted February 20, 2020 Author Share Posted February 20, 2020 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... Metadata CRC error detected at 0x43c8ad, xfs_bnobt block 0xe8e05f38/0x1000 btree block 2/1 is suspect, error -74 Metadata CRC error detected at 0x43c8ad, xfs_bnobt block 0x74702fa0/0x1000 bad magic # 0x60fd2189 in btbno block 2/1 btree block 1/1 is suspect, error -74 bad magic # 0x648d1cfc in btbno block 1/1 Metadata CRC error detected at 0x43c8ad, xfs_cntbt block 0xe8e05f40/0x1000Metadata CRC error detected at 0x43c8ad, xfs_cntbt block 0x74702fa8/0x1000 btree block 1/2 is suspect, error -74 bad magic # 0xdc98e8d0 in btcnt block 1/2 btree block 2/2 is suspect, error -74 bad magic # 0x8d006701 in btcnt block 2/2 agf_freeblks 243711720, counted 0 in ag 2 agf_longest 243711720, counted 0 in ag 2 agf_freeblks 244188650, counted 0 in ag 1 agf_longest 244188650, counted 0 in ag 1 Metadata CRC error detected at 0x46af5d, xfs_inobt block 0xe8e05f48/0x1000 Metadata CRC error detected at 0x46af5d, xfs_inobt block 0x74702fb0/0x1000 btree block 2/3 is suspect, error -74 btree block 1/3 is suspect, error -74 bad magic # 0xfc60406c in inobt block 1/3 bad magic # 0xf7a0f353 in inobt block 2/3 sb_fdblocks 491841636, counted 3941266 - 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 - 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 = 3 - agno = 1 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 Maximum metadata LSN (2064875260:-1117995775) is ahead of log (2:1075257). Would format log to cycle 2064875263. No modify flag set, skipping filesystem flush and exiting. Quote Link to comment
JorgeB Posted February 20, 2020 Share Posted February 20, 2020 Run again without -n, or nothing will be 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.