Hi,

I have a system running unraid 7.2.4 with an LSI 9305-16i with a number of 16TB SAS drives attached. Since I set this system up and enabled the SAS Spindown plugin I see the error count on the disks increase when it is spinning up. The errors only occur at spin up and not at initial boot time. Looking in the logs I see errors like below.

Jun 24 22:45:27 Tower kernel: sd 11:0:1:0: [sdc] tag#4212 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s

Jun 24 22:45:27 Tower kernel: sd 11:0:1:0: [sdc] tag#4212 Sense Key : 0x2 [current] [descriptor] 

Jun 24 22:45:27 Tower kernel: sd 11:0:1:0: [sdc] tag#4212 ASC=0x4 ASCQ=0x1c 

Jun 24 22:45:27 Tower kernel: sd 11:0:1:0: [sdc] tag#4212 CDB: opcode=0x88 88 00 00 00 00 03 80 0f 16 e0 00 00 00 08 00 00

Jun 24 22:45:27 Tower kernel: I/O error, dev sdc, sector 15033374432 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

I have carried out a number of trouble shooting steps to try resolve this:

1 - replaced the SAS cables

2 - replaced the power supply

3 - checked the drives are balanced on different power cables

4 - updated the SAS Card firmware

5 - Increased the timeout value on the card and by changing it in unraid using a script.

None of these worked, but as I understand it the issue is happening because the drive is returning NOT_READY when its asked for a read while spinning up. has anyone had this issue and found a solution?

Unraid doesn't support spinning down SAS drives, and the plugin doesn't work correclty with every model, suggest posting in the existing plugin support thread.

Thank you JorgeB, I will try that.