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 ...
Hi all,
a quick update. After i posted this topic I went ahead and performed the HDPARM tweaks, after that all seemed well. Load cycle count only increases very slowly now.
But today, disk 1 failed. After rebooting the NAS, it recognized the drive again, and started resyncing the volume. When I checked the smart status, the command timeout on the disk turned out to have increased again. The three other disks are fine though, with command timeout still at 0.
Reading all replies here, it struck me as odd that it seems like it's always disk 1 that's having these problems... Is there maybe something different in the way the NV+v2 treats the drive in the first slot? Is it for instance always the parity drive that gets written to more often?
Either way, as long as it's always the same disk, and it can be fixed by reboot & resync, i guess it's ok to keep it like this for a while. I will eventually start swapping out these seagate drives for something more reliable though :-)
Or should I try to return the defective drive to seagate and hope the replacement will be fine?
EDIT: grammar
a quick update. After i posted this topic I went ahead and performed the HDPARM tweaks, after that all seemed well. Load cycle count only increases very slowly now.
But today, disk 1 failed. After rebooting the NAS, it recognized the drive again, and started resyncing the volume. When I checked the smart status, the command timeout on the disk turned out to have increased again. The three other disks are fine though, with command timeout still at 0.
Reading all replies here, it struck me as odd that it seems like it's always disk 1 that's having these problems... Is there maybe something different in the way the NV+v2 treats the drive in the first slot? Is it for instance always the parity drive that gets written to more often?
Either way, as long as it's always the same disk, and it can be fixed by reboot & resync, i guess it's ok to keep it like this for a while. I will eventually start swapping out these seagate drives for something more reliable though :-)
Or should I try to return the defective drive to seagate and hope the replacement will be fine?
EDIT: grammar
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
