NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
intothevoid
Oct 01, 2012Aspirant
[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
- StephenBGuru - Experienced User
That would be my advice for disk replacement too. It's just easier to get something that both Netgear and the drive manufacturer certify.HERBIEO wrote: intothevoid wrote: I will eventually start swapping out these seagate drives for something more reliable
Have a look at the WD red series specifically engineered to work with NAS devices,
WD RED WD30EFRX - 3 TB
WD RED WD20EFRX - 2 TB
WD RED WD10EFRX - 1 TB
All on the HCL for the NV+ v2 - intothevoidAspirantYeah, i was thinking about the Red drives too.
Just too bad these seagates aren't as compatible as they seemed at first glance.
Thanks guys. - _saint_AspirantI appear to be experiencing exactly the same issue. Same drive and same failure of disk 1.
On occasion the entire volume dies. When I reboot the unit it comes back okay.
I knew I was buying a non-enterprise grade option which was fine as this is for home use, however I didn't realise it wouldn't be reliable. I've had a QNAP NAS previously for a few years without any problems.
Has anyone opened a formal support case with Netgear for this, if not I might do this.
Regards
_Saint_ - _saint_AspirantIf I open user.log (after enabling ssh) I see the following:
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing reallocated sector count on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Reallocation event count: [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing spin retry count on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing end-to-end errors on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing command timeouts on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing pending sector count on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing uncorrectable errors on disk 1 [0, -1]
again all disk1?
When I check the smart stats all drives look about the same:
SMART Information for Disk 1
Model:
ST3000DM001-9YN166 2794 GB
Serial Number:
XXXXXXXX
Firmware Version:
CC4H
SMART Attribute
Spin Up Time:
0
Start Stop Count:
1031
Reallocated Sector Count:
0
Power On Hours:
790
Spin Retry Count:
0
Power Cycle Count:
56
Runtime Bad Block:
0
End-to-End Error:
0
Reported Uncorrect:
0
Command Timeout:
0
High Fly Writes:
0
Airflow Temperature Cel:
22
G-Sense Error Rate:
0
Power-Off Retract Count:
49
Load Cycle Count:
5000
Temperature Celsius:
22
Current Pending Sector:
0
Offline Uncorrectable:
0
Any thoughts?
_saint_ - intothevoidAspirantWell, a formal support case might be a good idea as these drives ARE on the HCL. You would expect them to work.
And they do work, for the most part. It just seems really odd to me that this error keeps happening for the drive in the first slot for so many people.
Saint: did you apply the HDPARM tweak? It seemed to at least slow down the problem for me. - HERBIEOAspirant
_saint_ wrote: If I open user.log (after enabling ssh) I see the following:
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing reallocated sector count on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Reallocation event count: [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing spin retry count on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing end-to-end errors on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing command timeouts on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing pending sector count on disk 1 [0, -1]
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing uncorrectable errors on disk 1 [0, -1]
again all disk1?
When I check the smart stats all drives look about the same:
SMART Information for Disk 1
Model:
ST3000DM001-9YN166 2794 GB
Serial Number:
XXXXXXXX
Firmware Version:
CC4H
SMART Attribute
Spin Up Time:
0
Start Stop Count:
1031
Reallocated Sector Count:
0
Power On Hours:
790
Spin Retry Count:
0
Power Cycle Count:
56
Runtime Bad Block:
0
End-to-End Error:
0
Reported Uncorrect:
0
Command Timeout:
0
High Fly Writes:
0
Airflow Temperature Cel:
22
G-Sense Error Rate:
0
Power-Off Retract Count:
49
Load Cycle Count:
5000
Temperature Celsius:
22
Current Pending Sector:
0
Offline Uncorrectable:
0
Any thoughts?
_saint_
Looking at the SMART info this disk looks fine. - StephenBGuru - Experienced User
Oct 3 22:22:16 nas3 RAIDiator: Detected increasing spin retry count on disk 1 [0, -1]
These lines also don't look right - HERBIEOAspirant
StephenB wrote: Oct 3 22:22:16 nas3 RAIDiator: Detected increasing spin retry count on disk 1 [0, -1]
These lines also don't look right
Yes i was wondering about those allthough the smart stats themselves look fine. - StephenBGuru - Experienced UserIt almost looks like the NAS thought the count increased from -1 to 0.
- HERBIEOAspirantDo 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.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!