First off, I'll start by saying I have an Eaton UPS on the way already. However, the other day, the power company had to shut down our street, and they didn't give me enough time to do a full clean shutdown of my Unraid box. When power was restored, I noticed that my disk 6 was disabled, and the contents were emulated. Looking at the emulated contents, everything is there and accounted for. Unraid started a parity read-check and after completing, it had 0 errors. I go about the process of rebuilding disc 6 onto itself, and now the parity disk is making odd noises for the first time, the speeds are slow, the disk log shows i/o errors, and instantly I have thousands of errors on the parity disk that weren't there before. I stop the data rebuild, and all of the issues with the parity disk stop. My array contains 4 SAS drives (parity disk, and disc 6 included) connected to an LSI SAS 9207-8i controller, and 1 SATA HDD.

I had an issue months ago with another unclean shutdown that disabled my 1 SATA HDD, and it was very similar. It would click like it was broken, and the data rebuild process was going to take an obscene amount of time. I was thinking of replacing it, but decided to try a different SATA cable first, and after replacing the cable, everything was smooth sailing. I'm so confused with this new issue because I've tried different breakout cable leads, and different SATA power plugs to the SAS drives, but the errors still keep chasing me. The other 2 SAS drives connected to the controller are reading and writing just fine. I bought some replacement breakout cables for my HBA just in case, but they won't be in until next week.

I'm not sure if I'm asking for help or just documenting fixing this issue. I'll update the thread once I figure out where my issue lies. I've attached my diagnostics in the off chance that someone wants to read it. Thanks for any attention this gets.

thewired-diagnostics-20260304-1055.zip

It's not logged as a disk problem; check/replace both cables (or try another slot) for parity and post new diags after array start.

1 hour ago, JorgeB said:

It's not logged as a disk problem; check/replace both cables (or try another slot) for parity and post new diags after array start.

Apologies, when you say slot, do you mean PCI slot? I was contemplating doing so, even if that's not what you meant. The HBA has 2 breakout cables that split into 4 connectors each and I've tried switching the adapters around and also the SATA power plugs that go on the back. My brand new breakout cables should be here on Monday, so I'll swap them out then. I know these cables are very fragile/unreliable and prone to errors.

I'll update when possible, thanks!

10 minutes ago, Friarsgate_Customs said:

Apologies, when you say slot, do you mean PCI slot?

Disk slot, this only if you are using a case with a backplane/hot swap; if it's just regular cables, check replace those, power and SAS.

I don't know how much of it was weird coincidence, but I used the new SAS cables I bought, and switched the sata power splitter to one with the 3.3v line cut. I'm now 50% through a drive rebuild with 0 errors on any drive. I was using a sata splitter with the 3.3v line intact before the power outage and it was never giving me errors pre-power outage. Regardless of which cable was malfunctioning, I've got my UPS installed and configured now, so hopefully I won't have to deal with this again.