Juicebox

I have this problem too -- did you ever figure it out?

Replacement drive on the way! Thank you trurl and itimpi!

Thank you -- that all makes sense! I attached my SMART report... (didn't realize it took that long to do a SMART check!) With my limited understanding of it, I'm assuming my parity drive is about to crap out and replacement is wise? Once I pop a new drive in, is best practice to just stop the array, assign new drive as parity, start the array and just let it rebuild? None of my other disks show any warnings like that. On the unrelated note -- I have appdata set to Only : Cache, and system is set to Prefer : Cache. If I update system to Only : Cache, what else would I need to do? Why would appdata have files on the array if it's set to Only : Cache? Thanks again for your help! Edit: Upon googling, it sounds like Only : Cache is wrong, and it should be set to Prefer : Cache? I set appdata to Prefer, stopped all my Docker containers, and invoked the mover. Hope it really is that easy. ganymede-smart-20220205-0820.zip

Hello! I came home yesterday and none of my home automation was working. The Docker that manages the zwave integration on my Unraid box had stopped and was throwing errors that the filesystem was read-only. I thought it was strange, as I certainly hadn't touched anything and it had been running smoothly for months and months. I decided to reboot my Unraid box, but noticed that it was struggling to stop the array (taking a really long time). It eventually just rebooted itself. When it came back up, it automatically started a parity check. There were a couple yellow notification bubbles that there were some parity errors. The attached screenshot shows 1175 errors on the Parity drive (it used to read 0, iirc), but the Parity history shows 0, and it shows 'Parity is valid.' Should I be concerned? Any specific action I should take? Also strangely concerned that one of my Dockers thought it's filesystem was turned to read-only, but I didn't get any logs from that, and it appears to be working fine after the reboot. Thanks in advance for any support anyone can provide. ganymede-diagnostics-20220204-1215.zip