May 5, 201214 yr Through unraid all versions I tried, 4.7, 5.0b12a, 5.0b14 and now 5.0RC-2 my syslog fills up with this: May 5 12:08:54 Hal kernel: mdcmd (134): spindown 0 May 5 12:09:04 Hal kernel: mdcmd (135): spindown 0 May 5 12:09:04 Hal kernel: mdcmd (136): spindown 1 May 5 12:09:15 Hal kernel: mdcmd (137): spindown 0 May 5 12:09:25 Hal kernel: mdcmd (138): spindown 0 Is there something that can be done about this? This is a test-server with 1 data-disk and cache and parity disk on a Areca ARC1200 controller in RAID0/RAID1 volumes.
May 5, 201214 yr Try setting the spin-down time on each drive individually through the emhttp management console (web page). It's possible that your raid controller does NOT support pass-through of spin-down commands, so you may be unable to use that feature.
May 5, 201214 yr Through unraid all versions I tried, 4.7, 5.0b12a, 5.0b14 and now 5.0RC-2 my syslog fills up with this: May 5 12:08:54 Hal kernel: mdcmd (134): spindown 0 May 5 12:09:04 Hal kernel: mdcmd (135): spindown 0 May 5 12:09:04 Hal kernel: mdcmd (136): spindown 1 May 5 12:09:15 Hal kernel: mdcmd (137): spindown 0 May 5 12:09:25 Hal kernel: mdcmd (138): spindown 0 Is there something that can be done about this? This is a test-server with 1 data-disk and cache and parity disk on a Areca ARC1200 controller in RAID0/RAID1 volumes. Set the spin-down to never. Those are status messages. Apparently your RAID controller does not allow spindown control and unRAID is attempting to spin them down, again and again.
Archived
This topic is now archived and is closed to further replies.