Jonathan Stucklen

This started happening to me pretty regularly on a supermicro virtualization server (X10SDV-8C-TLN4F). I have 4 500GB crucial MX500's in a 2x2 mirrored pool with one hot spare. Every couple...

I do have trim enabled on the pool. Perhaps it could be related to this: https://github.com/openzfs/zfs/issues/8552. Though these aren't Samsung drives. I can try the noncq setting on the next...

Also, you can disable NCQ without a reboot using this technique: https://unix.stackexchange.com/a/611496

Disabling NCQ with the above technique (the technique that doesn't require rebooting) was not effective for me. I'm going to try disabling autotrim and just leave it to the monthly...

Nope. That didn't work either. :-P I'm starting to suspect failing hardware for me now too (or a kernel bug in a recent update). To my knowledge, the D-1541 Xeon's...

Yep, thanks @livelace. Doesn't apply in my case either though since the current problem I'm having is with Crucial MX500's (5 of them, all brand new, 2x2 mirrored pairs and...

I do have a bit of a performance hit, but so far everything is working on the backplane whereas every day for the past week I was getting at least...

Huh. This is the same symptoms from years ago on the exact same MB I'm using, though it's with intel SSDs instead of crucial. In that case it was the...

I'm seeing a similar, though not identical, error from grpc while using the firebase-admin JS library (which uses google/firestore). The exact error I'm seeing is: > 12:17:53 PM: 2020-01-07T17:17:53.280Z e5cf6caf-cbc5-4cd8-a1fa-a73df0be9983...

I don't have useful logging to provide (complications with getting the debug logs to send to our log service). But, I can say that after implementing retry logic (retries up...