NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Problems with Ultra4+ and ST2000DL003's after 4.2.22 upgrade
Ok, this may be a firmware issue only or may be specific to the drives, so I'm posting here. After upgrading to RAIDiator 4.2.22, I am having some real issues with my Ultra4+. When it goes to sleep (disk spin-down), it often will not wake up unless I hit the button on the front. More disturbingly, I've gotten errors of the type
I was a few versions old before the upgrade (4.2.18, I think) and all was running fine. I only upgraded because I got a used NVX that has the latest firmware and I intend to swap the drives in the Ultra4 into the NVX.
These drives are on the hardware compatibility list and are about a year and a half old. SMART all looks fine except the "head flying hours" is a few million years (which must be a problem with how RAIDiator interprets the data).
I've turned off disk spin-down for now to prevent the problem with it not waking properly and will see if the command time-outs are affected, but that's not really how I want to keep it. Any recommendations on other courses of action? Anyone else with similar issues?
This happened on two drives at the same time. Pretty hard to believe two drives really had an issue at the same time. Also tough to believe that it's coincidental that it all started when I upgraded RAIDiator. The time-outs may have occurred at a point the unit didn't wake properly, but they do not happen every time it doesn't wake.
Detected increasing command timeouts[65537] on disk 3 [ST2000DL003-9VT166, XXXXXXXX]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
I was a few versions old before the upgrade (4.2.18, I think) and all was running fine. I only upgraded because I got a used NVX that has the latest firmware and I intend to swap the drives in the Ultra4 into the NVX.
These drives are on the hardware compatibility list and are about a year and a half old. SMART all looks fine except the "head flying hours" is a few million years (which must be a problem with how RAIDiator interprets the data).
I've turned off disk spin-down for now to prevent the problem with it not waking properly and will see if the command time-outs are affected, but that's not really how I want to keep it. Any recommendations on other courses of action? Anyone else with similar issues?
4 Replies
Replies have been turned off for this discussion
- Beisser said on a different thread that 4.2.22 is alerting on more SMART parameters than previous releases. Before the alerts were only done for reallocated sector counts and ATA timeouts. Now more "critical" parameters generate alerts when they increase. So it is likely that these errors were happening before the upgrade, but that you didn't notice them.
When you say "SMART all looks fine", are you saying that the count for command timeouts reported on the disk health SMART pop-up is different from that is being logged on drive 3?
BTW, what firmware are your drives running?
Issues with drives not spinning up could of course be a RAIDiator issue. - also the drive in question is known to cause issues as well.
the drive may require a firmwareupdate. - My drives do have the firmware CC32, which some have reported as having problems. But they have been running just fine for over a year where most with problems have it immediately and consistently. I have read about the CC35 firmware and how to force an update even if the tool does not recognize it as being required. But the fact that there are different firmwares for different ages of drives tells me there are some real hardwre differences between them, so I have assumed that my drives are properly matched to the CC32 software while some of a newer vintage may not be. The Seagate site definately says CC32 is the latest for my serial numbers. I suppose, however, that they may have always been riding on the edge and a small change in RAIDiator may have thrown them over that edge.
The drive's SMART reports do include a couple of command time-outs, nowhere near the number reported in the log. Maybe RAIDiator's just mis-reading the count when doing so for the log but not in the SMART report itself. The number of time-outs reported in SMART is the same number of times the alert was entered in the log and the number reported in the log minus 65535. But that still means that they ran more than a year with none before upgrading to 4.2.22. If RAIDator is mis-reading the count, maybe it just missed the time-out on one drive until the other occurred and that's why it appears that they happened at the same time. I can believe that a lot more than that both drives genuinely had a problem at precisely the same time that was not induced by RAIDiator. But that they were somehow induced by RAIDiator also remains on the list of possibilities.
Have since found other posts blaming 4.2.22 firmware for contributing to premature failures with these drives. I think I'm going to go backwards to 4.2.21 until more is known. - If reverting back to 4.2.21 makes you more comfortable, then go ahead - it does no harm.
It sounds to me like the 65535 report might be a bug in the alert message itself. If there are just a few timeouts then I would simply watch for now.
BTW you will see the same command timeout issue with these drives reported on the QNAP forum
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
