I logged into my server today and noticed drive 10 was disabled. I shut down my array, removed the disk, started the array and ran an SMART extended self-test and the Drive came back fine. Moved it to another slot on my server which was on a different cable and started the array, and started a sync. 

Then after a few hours I went to check on things, and i was getting read errors from my parity drive. Rebuild on drive 10 was at 4% I shut down the server, expecting I may have an issue with the cable that cable because they are close on the backplane board and my HBA uses ssf-8643 connectors on both ends. 

Update: The drives are not same section of the backplane so they were using two different cables to connect to the HBA. 

After reboot, my 8th drive, also likely on the same cable was disabled. I was able to mount and read it fine, by removing it from the array. I was also able to mount drive number 10, but I don't know how the sync works. was it writing over existing data? my parity should have been fine prior to my recent issues. 

now have have two drives in a new state and cant sync both. 

 

I made changes to my server over the weekend connecting a Jetkvm to my server, and the jumpers are in the area that my HBA is. It does not look like anything was dislodged, and I made sure all the cables are secure. Server case is a Homelabs HL15 with a LSI 9300-16i as my HBA if that information helps. 

Looking for a recommendation on how to proceed. 

ozunraid-diagnostics-20250506-2158.zip

Edited May 7, 20251 yr by southloven

If both disks are believed to be OK, and they look OK, you can do a new config, check parity is already valid, then run a correcting parity check.

 

P.S. you should upgrade to the latest stable, the issue of two invalid disks with single parity occurring in some cases is a resolved bug.