April 4, 20233 yr Author I don't understand next step... Yesterday I posted new diags after assigning old (256gb ssd) to be the only cache pool device. Or should I assign the other 256GB ssd?
April 4, 20233 yr Community Expert The btrfs balance was still going on, I want to make sure it finished, post new diags without changing anything else.
April 4, 20233 yr Community Expert Balance finished without errors, you can now add the 1TB device to this pool, post new diags if there are any issues.
April 7, 20233 yr Author It worked out fine, not sure why I had problems the first two times. Anyways, thank you for your time and help! Appreciate it
April 9, 20233 yr Author Happy Easter to all who celebrate it Could you please help me out with one more case? Recently I got a warning that my syslog is 100% full, turns out that it got spammed with BTRFS errors... Is it related to my previous problem, or should I change the sata cable that connects sdg to the motherboard? the-beast-diagnostics-20230409-2143.zip
April 9, 20233 yr Community Expert Apr 4 22:25:36 The-Beast kernel: ata6.00: disable device Apr 4 22:25:36 The-Beast kernel: ata6: EH complete Apr 4 22:25:36 The-Beast kernel: sd 6:0:0:0: [sdg] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=121s Apr 4 22:25:36 The-Beast kernel: sd 6:0:0:0: [sdg] tag#21 CDB: opcode=0x2a 2a 00 00 10 9e c8 00 0a 00 00 Apr 4 22:25:36 The-Beast kernel: I/O error, dev sdg, sector 1089224 op 0x1:(WRITE) flags 0x104000 phys_seg 20 prio class 0 This device dropped offline, start by replacing cables, also see here for better pool monitoring.
April 14, 20233 yr Author Hi there, "Docker Service failed to start." after changing cables. I'm starting to feel guilty for bothering you... Could yo uplease help me to get my server back ? :) the-beast-diagnostics-20230414-2112.zip
April 15, 20233 yr Community Expert First run a scrub on the pool, if there aren't uncorrectable errors recreate the docker image.
April 17, 20233 yr Author Does that mean I'll have to reconfigure all my docker containers? If so, could it be possible to use very first drive that I took out of the system (256gb SSD)? Actually I already tried that, but cache pool just displayed error: UNMOUNTABLE: NO POOL UUID Edited April 17, 20233 yr by JunkoZane
April 18, 20233 yr Community Expert 12 hours ago, JunkoZane said: Does that mean I'll have to reconfigure all my docker containers? No, see the link, but first post new diags.
April 18, 20233 yr Author I somehow misinterpreted info in that link... Also, it's kind'a strange that after running scrub with "repair corrupted blocks" enabled I got a bunch uncorrectable blocks. But after second time I did same thing - I have cache pool with 0 uncorrectable blocks the-beast-diagnostics-20230418-2152.zip
April 19, 20233 yr Community Expert 11 hours ago, JunkoZane said: But after second time I did same thing - I have cache pool with 0 uncorrectable blocks It doesn't make much sense, but if it's not detecting errors at the moment see how it goes.
May 3, 20233 yr Author Hi there, unfortunately I'm getting SDE (one of cache pool drives) errors again... If not cable, what else could it be? MB, the drive itself? Thank you in advance the-beast-diagnostics-20230503-2348.zip Edited May 3, 20233 yr by JunkoZane
May 4, 20233 yr Community Expert See if this helps: https://forums.unraid.net/topic/134954-warning-crucial-mx500-ssds-world-of-pain-stay-away-from-these/?do=findComment&comment=1255816
July 2, 20242 yr Author Hello again, sorry somehow I missed your last comment. A year passed by with docker failing to start from time to time. I just deleted the docker image every time and recreated containers. I've tried replacing cables and motherboard. Now I suspect new SSD was faulty all along (since this whole thread was started after I installed them into server to replace my old cache drives). Now I'm prepared to replace one of those SSDs to end this misery once and for all. What should be the replacement sequence? Appreciate your help! (to such noob as myself ) the-beast-diagnostics-20240702-1336.zip
July 2, 20242 yr Community Expert You can follow this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419
July 2, 20242 yr Community Expert That's the docker image, you can just recreate it, but taking another look at the syslog, there are a LOT of errors for both pool devices: Jul 2 13:25:39 The-Beast kernel: BTRFS info (device sdf1): bdev /dev/sdf1 errs: wr 50487191, rd 1634110, flush 8901094, corrupt 8507526, gen 134 Jul 2 13:25:39 The-Beast kernel: BTRFS info (device sdf1): bdev /dev/sdg1 errs: wr 174356609, rd 28754240, flush 20845342, corrupt 37956524, gen 14162 They could be old or not, so before doing anything else run a correcting scrub and post the results.
July 2, 20242 yr Author I've checked "Repair corrupted blocks". And i've noticed it was aborted. But not by me the-beast-diagnostics-20240702-1523.zip
July 2, 20242 yr Community Expert Try again, if it still aborts I don't recommend trying a replacement, try to backup whatever you can instead, then create a new pool with the new device.
July 2, 20242 yr Community Expert Should be OK now, but just make sure, reset the stats with btrfs dev stats -z /mnt/cache Then run another scrub, then post output of btrfs dev stats /mnt/cache
July 2, 20242 yr Author Worked like a charm Should I proceed with the instructions? 4 hours ago, JorgeB said: You can follow this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419
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.