michaelhthomas

I bet that's it! The OPNsense VM was being passed a PCIe device which is no longer attached (network card), so the device ids must have shifted around and ended up causing the SATA controller to be passed through instead.

I did catch those, but what I found strange is that those are all from after the parity drive was pulled from the array (as far as I can tell). Once the parity drive is removed, it looks like every single drive has read errors for every read, based on what was shown in the web UI. I was wondering if it was some motherboard issue. What's weird is that, last time this occurred, I was able to rebuild the parity drive and operate without errors for about a month. There are no power splitters or anything unusual.

Hi all, I'm a bit baffled and could use some assistance with filesystem errors. This is now the second time that, following a reboot, my UNRAID server reports 1 error on the Parity drive and then removes it from the array. I have run (short) SMART tests on all drives and found nothing out of the ordinary. Strangely, the only errors I see in the syslog appear to be related to a corrupted docker image? There's a good chance I'm missing something here, so if you wouldn't mind taking a look, that would be great. Currently, I've stopped the array, and I am waiting to restart it until I've gotten this figured out. gringotts-diagnostics-20240513-0825.zip