Dice1122

Got a new drive and restored everything that was on it. Everyone is back to normal so it does look like it was a purely hardware issue. Thanks for the second opinion!

When it happened the first time i just started some downloads and i was updating some docker containers. But docker become unresponsive. I did test with everything docker disabled and i can cause it to happen just by transferring large files to the cache.

I am having issues with my cache drive, the drive just seems to stop working or slowing down so much its unusable. I did a manual test where i just wrote a large file to the cache drive and it goes steady until it reaches a couple of gigs transferred and then it just drops to 0. Transferring directly to the array has no issues what so ever. So i wonder if i have a broken drive or if there is something in my setup that is wrong/broken/messed up? I added 2 diagnostics, one is after the drive goes haywire the other is after a fresh boot. cube-n2-diagnostics-20230714-1747 (Fresh Boot).zip cube-n2-diagnostics-20230714-1720 (Broken State).zip