walndyn

Since the error only occurs when the system is spinning the disk up and not when manually spinning them up, could it be that it tries to read data before the disk is totally ready and the firmware isn't delaying it enough? If that would be the case, is there a way to tell the system to wait a few seconds after spinning up and before reading the data?

Well, this would be all my array drives...

Hmm... Is there any way I can change the firmware or find another firmware that works with spin ups/downs? Or can I ignore this error without risking data loss?

Thanks for the fast response. These are refurbished HP Enterprise 4TB 7.2k disks (Modell Nr. MB4000GDUPB)

Hey, I have a strange issue where when a drive (doesn't matter which) in the array is spun up because Unraid or a container accesses it, it throws a read error. But when I spin the disk up manually from the GUI I don't get any errors. I tried reseating SATA and power cables, rebooting, updating the drives firmware and even using xfs rather than zfs on one disk to exclude a problem with the filesystem. When I disable disk spindown the drives behave just fine. I would be very glad if someone can help me, since I want to reduce my power consumption by spinning the HDDs down. Best regards Valentin unraid-diagnostics-20260326-1722.zip