NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
[Solved] Seagate ST3000DM001-9YN166: Load Cycle Count
Hi,
sorry if this has been discussed already, all i could find are topics about upgrading the firmware on these drives.
I've got a NV+v2 with 4 3TB ST3000DM001-9YN166 disks in it, firmware CCH4 (the latest).
System has been running for a couple of months now, and all was working smoothly until i got a warning 2 weeks ago:
Looking into the SMART status, it indeed gives some ridiculously high number (4295032833) on command time out for disk 1. On the other 3 disks it's 0.
Another thing i noticed in the SMART status for all disks though, is that the load count cycle is quite high: around 43000 after 1800 power on hours.
After a bit of googling however, all i could find was this problem cropping up on WD green drives. The solution seems to be to set the idle time a bit higher.
I did find this old topic (http://www.readynas.com/forum/viewtopic.php?f=36&t=51536) explaining how to do it on some other seagate model, but i wanted to get some feedback before i attempt to change things via ssh. Don't wanna corrupt anything.
So basically my questions are:
1) Is the command time out problem in anyway related to the lcc problem, or is this drive just about to die no matter what?
2) Does anybody else have these high lcc numbers with the ST3000DM001 drives?
3) Is it worthwhile changing the idle time setting with hdparm?
3b) If yes, are the instructions in that old topic still valid?
On a related note, i did install the ssh add-on and looked around a little, however when i try to get drive status with hdparm i get this:
Same for sdb, sdc, and sdd
Am i using the right identifiers here? Sorry for the ignorance :oops:
Hope this isn't all too confusing, i tried to cram a lot of information in this post :-)
Thanks in advance for any help!
EDIT: apparently i do not have permission to use the url tag..
sorry if this has been discussed already, all i could find are topics about upgrading the firmware on these drives.
I've got a NV+v2 with 4 3TB ST3000DM001-9YN166 disks in it, firmware CCH4 (the latest).
System has been running for a couple of months now, and all was working smoothly until i got a warning 2 weeks ago:
Detected increasing command timeouts[65537] on disk 1 [ST3000DM001-9YN166, W1F083HJ]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Looking into the SMART status, it indeed gives some ridiculously high number (4295032833) on command time out for disk 1. On the other 3 disks it's 0.
Another thing i noticed in the SMART status for all disks though, is that the load count cycle is quite high: around 43000 after 1800 power on hours.
After a bit of googling however, all i could find was this problem cropping up on WD green drives. The solution seems to be to set the idle time a bit higher.
I did find this old topic (http://www.readynas.com/forum/viewtopic.php?f=36&t=51536) explaining how to do it on some other seagate model, but i wanted to get some feedback before i attempt to change things via ssh. Don't wanna corrupt anything.
So basically my questions are:
1) Is the command time out problem in anyway related to the lcc problem, or is this drive just about to die no matter what?
2) Does anybody else have these high lcc numbers with the ST3000DM001 drives?
3) Is it worthwhile changing the idle time setting with hdparm?
3b) If yes, are the instructions in that old topic still valid?
On a related note, i did install the ssh add-on and looked around a little, however when i try to get drive status with hdparm i get this:
root@nas:~# hdparm -i /dev/sda
/dev/sda:
HDIO_GET_IDENTITY failed: Inappropriate ioctl for device
Same for sdb, sdc, and sdd
Am i using the right identifiers here? Sorry for the ignorance :oops:
Hope this isn't all too confusing, i tried to cram a lot of information in this post :-)
Thanks in advance for any help!
EDIT: apparently i do not have permission to use the url tag..
50 Replies
Replies have been turned off for this discussion
It looks that way. To confirm it you would need to remove the disk (NAS powered down first) and check the SMART stats on another device (for instance a PC).HERBIEO wrote: Do you think there could be a bug in this firmware version that is reporting errors that are not really happening ?
because looking at the SMART info there is no errors.- Got a similar problem myself with the same disks and NV+ V2.
Got 30065229831 Command Timouts on Disk 1 after a disk test performed trough the boot menu. Powered down the nas, removed Disk 1 and ran Seatools on it without findig any faults. Put the disk back in and ran a new disk test on the nas, when that finished the command timouts had doubled to 60130459662. Incredibly high number! Had a spare disk lying around, brand new. Removed Disk 1 once again and resynced to the brand new disk. Ran a new disk test with the same result a before, 30065229831 Command Timouts on Disk 1.
What is happening here? Running RAIDiator 5.3.6
I don't believe the 30065229831 (or 60130459662) number, but there still might be something actually wrong in the SMART stats. Are you seeing this in email alerts/log entries? If so you should confirm by looking at the actual SMART statistics.spett wrote: Got a similar problem myself with the same disks and NV+ V2.
Got 30065229831 Command Timouts on Disk 1 after a disk test performed trough the boot menu. Powered down the nas, removed Disk 1 and ran Seatools on it without findig any faults. Put the disk back in and ran a new disk test on the nas, when that finished the command timouts had doubled to 60130459662. Incredibly high number! Had a spare disk lying around, brand new. Removed Disk 1 once again and resynced to the brand new disk. Ran a new disk test with the same result a before, 30065229831 Command Timouts on Disk 1.
What is happening here? Running RAIDiator 5.3.6
You might also try putting the drive into the PC again and looking at the SMART stats there (Seatools won't show them to you, but other tools will. Acronis Drive Monitor is one of several).StephenB wrote:
I don't believe the 30065229831 (or 60130459662) number, but there still might be something actually wrong in the SMART stats. Are you seeing this in email alerts/log entries? If so you should confirm by looking at the actual SMART statistics.spett wrote: Got a similar problem myself with the same disks and NV+ V2.
Got 30065229831 Command Timouts on Disk 1 after a disk test performed trough the boot menu. Powered down the nas, removed Disk 1 and ran Seatools on it without findig any faults. Put the disk back in and ran a new disk test on the nas, when that finished the command timouts had doubled to 60130459662. Incredibly high number! Had a spare disk lying around, brand new. Removed Disk 1 once again and resynced to the brand new disk. Ran a new disk test with the same result a before, 30065229831 Command Timouts on Disk 1.
What is happening here? Running RAIDiator 5.3.6
You might also try putting the drive into the PC again and looking at the SMART stats there (Seatools won't show them to you, but other tools will. Acronis Drive Monitor is one of several).
I have tried putting the drive in my computer, same number is saved in the smart stats in the drive..
Since the drive itself creates/maintains the SMART stats, that means that (a) either the drive really is seeing that many Command Timeouts, or (b) there is a bug in the drive's firmware.spett wrote: I have tried putting the drive in my computer, same number is saved in the smart stats in the drive..
If you purchased these drives yourself, you probably will need to contact Seagate support.
What firmware is the drive running? Note you can check at Seagate to see if there is a firmware update for your drives (you can enter the drive model and it's serial number, and their on-line tool should tell you).StephenB wrote:
Since the drive itself creates/maintains the SMART stats, that means that (a) either the drive really is seeing that many Command Timeouts, or (b) there is a bug in the drive's firmware.spett wrote: I have tried putting the drive in my computer, same number is saved in the smart stats in the drive..
If you purchased these drives yourself, you probably will need to contact Seagate support.
What firmware is the drive running? Note you can check at Seagate to see if there is a firmware update for your drives (you can enter the drive model and it's serial number, and their on-line tool should tell you).
They are upgraded to firmware version CC4H by me because of a note in the hardware compability list for the NV+ V+, but I do notice that this comment is removed now.
But the weird thing is that the comand timouts only increases when doing a disk test trough the boot menu. Did this test because I had frequent lock-ups using sabnzbd.
Did not find the online check at seagate.com, do you have a link?- Online check https://apps1.seagate.com/downloads/request.html
but i think you are allready running the latest firmware for those drives but worth a check. - Found out it does have to have something to do with the NV+ V2. Since I now had a drive with a high command timeout as a sparedrive I pulled out drive 2 which had 0 command timeouts and resynced with the spare drive. Ran a new disk test and once again the command timeouts of drive 1 increased with 30065229831. Drive 2 still have the same amount as before the test.
Googling command timouts i get that this is probably because of a faulty power supply or corroded contacts.
What do you think? Is this a software fault or is my NAS faulty? - The problem appears isolated to the disk test. So that would seem to rule out the supply and the contacts - they wouldn't mysteriously heal when the test completes.
It is conceivable that the disk test includes some commands that provoke the drive to fail. For instance, malformed/illegal commands, or perhaps legal but unusual commands that the drive firmware doesn't handle properly.
I'd suggest a support case.
In the meantime I would simply not run that test! And record/track the current counts and confirm that they never increase in normal operation. The problem appears isolated to the disk test. So that would seem to rule out the supply and the contacts - they wouldn't mysteriously heal when the test completes.
It is conceivable that the disk test includes some commands that provoke the drive to fail. For instance, malformed/illegal commands, or perhaps legal but unusual commands that the drive firmware doesn't handle properly.
I'd suggest a support case.
In the meantime I would simply not run that test! And record/track the current counts and confirm that they never increase in normal operation.
Is that test run automatically at boot, or on a schedule? I've never manually triggered it.
Both times my drive 'failed' (and had a higher command timeout value afterwards) the NAS was in normal operation.
EDIT: Included quote for top of page clarity.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
