March 7, 201115 yr When I click on the "spin up" all drive link from unraid, I now get this error: Mar 7 07:25:03 RCNAS emhttp: Spinning up all drives... Mar 7 07:25:03 RCNAS emhttp: shcmd (56): /usr/sbin/hdparm -S0 /dev/sdk >/dev/null Mar 7 07:25:03 RCNAS kernel: mdcmd (41): spinup 0 Mar 7 07:25:03 RCNAS kernel: mdcmd (42): spinup 1 Mar 7 07:25:03 RCNAS kernel: mdcmd (43): spinup 2 Mar 7 07:25:03 RCNAS kernel: mdcmd (44): spinup 3 Mar 7 07:25:03 RCNAS kernel: mdcmd (45): spinup 4 Mar 7 07:25:03 RCNAS kernel: mdcmd (46): spinup 5 Mar 7 07:25:03 RCNAS kernel: mdcmd (47): spinup 6 Mar 7 07:25:18 RCNAS kernel: ata12.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 7 07:25:18 RCNAS kernel: ata12.01: failed command: IDLE Mar 7 07:25:18 RCNAS kernel: ata12.01: cmd e3/00:00:00:00:00/00:00:00:00:00/50 tag 0 Mar 7 07:25:18 RCNAS kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 7 07:25:18 RCNAS kernel: ata12.01: status: { DRDY } Mar 7 07:25:19 RCNAS kernel: ata12: soft resetting link Mar 7 07:25:19 RCNAS kernel: ata12.00: configured for UDMA/133 Mar 7 07:25:19 RCNAS kernel: ata12.01: configured for UDMA/133 Mar 7 07:25:19 RCNAS kernel: ata12: EH complete Mar 7 07:25:20 RCNAS emhttp: shcmd (57): /usr/sbin/hdparm -y /dev/sdk >/dev/null Should I be worried about the ata12.01 failures? otherwise my server seems to be running correctly with no other issues. Thanks,
March 7, 201115 yr When I click on the "spin up" all drive link from unraid, I now get this error: Mar 7 07:25:03 RCNAS emhttp: Spinning up all drives... Mar 7 07:25:03 RCNAS emhttp: shcmd (56): /usr/sbin/hdparm -S0 /dev/sdk >/dev/null Mar 7 07:25:03 RCNAS kernel: mdcmd (41): spinup 0 Mar 7 07:25:03 RCNAS kernel: mdcmd (42): spinup 1 Mar 7 07:25:03 RCNAS kernel: mdcmd (43): spinup 2 Mar 7 07:25:03 RCNAS kernel: mdcmd (44): spinup 3 Mar 7 07:25:03 RCNAS kernel: mdcmd (45): spinup 4 Mar 7 07:25:03 RCNAS kernel: mdcmd (46): spinup 5 Mar 7 07:25:03 RCNAS kernel: mdcmd (47): spinup 6 Mar 7 07:25:18 RCNAS kernel: ata12.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 7 07:25:18 RCNAS kernel: ata12.01: failed command: IDLE Mar 7 07:25:18 RCNAS kernel: ata12.01: cmd e3/00:00:00:00:00/00:00:00:00:00/50 tag 0 Mar 7 07:25:18 RCNAS kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 7 07:25:18 RCNAS kernel: ata12.01: status: { DRDY } Mar 7 07:25:19 RCNAS kernel: ata12: soft resetting link Mar 7 07:25:19 RCNAS kernel: ata12.00: configured for UDMA/133 Mar 7 07:25:19 RCNAS kernel: ata12.01: configured for UDMA/133 Mar 7 07:25:19 RCNAS kernel: ata12: EH complete Mar 7 07:25:20 RCNAS emhttp: shcmd (57): /usr/sbin/hdparm -y /dev/sdk >/dev/null Should I be worried about the ata12.01 failures? otherwise my server seems to be running correctly with no other issues. Thanks, Is your power supply capable of spinning up all the drives at the same time?
March 7, 201115 yr Author Thought so... but I will now have to check to make sure that is the case I did buy a new one with single 12v rail (same one Lime-Tech uses) so that I would make sure to "future proof" mine... guess I need to install it sooner rather than later and find out if that is the cause. Thanks once again Joe!
March 7, 201115 yr I see those errors every now and then but not every drive spin-up. In my case it seems to be 2 Seagate drive, even though 1 is worse than the other. The worse one has been throwing 1 or 2 of those errors a week for 2 years now and it's still working fine otherwise. You could check your power connection and replace the SATA cable and see if it improves. Peter
March 10, 201115 yr Author Well, all new high-quality SATA cables and the Corsair 650W power supply that Lime-Tech uses installed... still get the same error if Spinning up all drives from sleep from the unraid menu (only have 8 drives). Otherwise things seem to work great.
March 10, 201115 yr I would not worry about those drive "errors". The link resets so it's nothing to worry about. Peter
Archived
This topic is now archived and is closed to further replies.