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 ...
intothevoid
Oct 24, 2012Aspirant
Hmm, seems to me like we're looking at two different paths leading to the same problem.
1) running the disk test leads to an extremely high command timeout on disk1.
2) the NAS drops disk1 saying it has failed, after reboot it resyncs and the command time out has increased (to a ridiculous value).
The high load cycle count form the thread title was my original guess for the cause of the problem, but after that was fixed with the HDPARM tweak, the command timeout problem (via scenario 2) persisted.
So either there's something wrong with all our drives, and it's a coincidence they all happen to be installed in the first slot on the NAS, or there is some weird compatibility issue with these seagate ST's and the NV+ v2, which causes the drive installed as disk1 to fail.
It's still strange why for some the command time out value seems to be real and for some not though. To complicate matters, I cannot test my drives in a normal computer as i only have a laptop...
1) running the disk test leads to an extremely high command timeout on disk1.
2) the NAS drops disk1 saying it has failed, after reboot it resyncs and the command time out has increased (to a ridiculous value).
The high load cycle count form the thread title was my original guess for the cause of the problem, but after that was fixed with the HDPARM tweak, the command timeout problem (via scenario 2) persisted.
So either there's something wrong with all our drives, and it's a coincidence they all happen to be installed in the first slot on the NAS, or there is some weird compatibility issue with these seagate ST's and the NV+ v2, which causes the drive installed as disk1 to fail.
It's still strange why for some the command time out value seems to be real and for some not though. To complicate matters, I cannot test my drives in a normal computer as i only have a laptop...
Related Content
NETGEAR Academy

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