Hi all,

My unraid server is version 7.2.6. I'm running two SilverStone FS305-12G hot-swap cages (5-bay each) in my Unraid server. According to the cage manual, the front LED on each bay behaves as follows:

• Blue (solid) = HDD inserted, power on

• Purple (blinking) = HDD being accessed

I've noticed that Parity 2's bay LED is constantly showing purple, indicating continuous access activity, while Parity 1's LED remains solid blue (normal). To rule out a faulty bay, I swapped Parity 2 to different physical bay positions across the cage and each time, the purple LED followed the disk, not the bay. So it's definitely something accessing Parity 2 specifically, not a hardware fault with the cage slot itself.

However, in the Unraid's main tab, Parity 2's read/write is showing 0 B/s, so whatever is accessing it isn't showing up in the normal disk activity view.

I also ran a parity check and it came back clean with no errors.

What I've tried so far:

• Physically swapping the disk to different bays (LED follows the disk)

• Monitoring dashboard read/write (shows 0 B/s)

• Running a full parity check (passed, no errors)

Any suggestions on what else I should do to determine what might be accessing Parity 2?

Don't see how this can be an Unraid issue, are both disks on the same firmware?

Maybe the parity 2 drive is a SAS drive? If it is, then install the SAS spindown plugin.

On 6/3/2026 at 1:43 AM, JorgeB said:

Don't see how this can be an Unraid issue, are both disks on the same firmware?

Hi, both parity drives are using the same firmware (SN04). Have attached the drives report here too. Parity 2 is the disk that has LED purple.

On the other hand, I also noticed that my parity checks (over the two months) have errors, though once I execute correcting parity check, the error will become 0. But when the scheduled parity check is executed (after the previous correcting parity check), the error will appear again.

Parity 1.txt Parity 2.txt

On 6/3/2026 at 3:14 AM, strike said:

Maybe the parity 2 drive is a SAS drive? If it is, then install the SAS spindown plugin.

Drive is a SATA drive though :/

5 hours ago, yongweifu said:

On the other hand, I also noticed that my parity checks (over the two months) have errors, though once I execute correcting parity check, the error will become 0. But when the scheduled parity check is executed (after the previous correcting parity check), the error will appear again.

This is an actual issue that should be resolved; post new diags after you get some errors.

On 7/2/2026 at 2:39 PM, JorgeB said:

This is an actual issue that should be resolved; post new diags after you get some errors.

Thank you for the advice @JorgeB. I have download the diagnostics for the server (after rebuilding the parity).

maxwell-server-diagnostics-20260707-1237.zip

I don't see any sync errors logged.