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 ...
Just thought I'd add that I'm experiencing the same issue with my NV+ v2 and Seagate ST2000DM001. I've had the NV+ v2 and 3x ST2000DM001 working fine for just over 3 months now. All drives were updated by me the CC4H firmware when new, prior to being installed in the NAS. Also, prior to installing, I checked each disk with all Seatools tests (boot disk) and all were fine.
Suddenly, yesterday, I got an email from the NAS telling me that all 3 disks had failed. I ended up having to unplug the NAS from the wall to get it to power off (it was unresponsive). When I rebooted, my volume was back to normal and everything seems fine.
However, looking at the SMART info I see a command timeout value for Disk 1 of 4295032833. Both Drives 2 and 3 have a command timeout of "0". I have no idea what this value was before yesterday's incident or whether the two are related...
Seems like there might be a compatibility issue between these Seagate drives and the NV+ V2. Strange that it's always Drive 1 that has these super high command timeouts and that the high numbers are always about the same, if not identical.
I have never run any full disk check in the NAS (that you access through the boot menu) only the shorter volume check on reboot. My spin-down time is set for 60 min and has been so for months. have been on 5.3.5 the whole time.
Suddenly, yesterday, I got an email from the NAS telling me that all 3 disks had failed. I ended up having to unplug the NAS from the wall to get it to power off (it was unresponsive). When I rebooted, my volume was back to normal and everything seems fine.
However, looking at the SMART info I see a command timeout value for Disk 1 of 4295032833. Both Drives 2 and 3 have a command timeout of "0". I have no idea what this value was before yesterday's incident or whether the two are related...
Seems like there might be a compatibility issue between these Seagate drives and the NV+ V2. Strange that it's always Drive 1 that has these super high command timeouts and that the high numbers are always about the same, if not identical.
I have never run any full disk check in the NAS (that you access through the boot menu) only the shorter volume check on reboot. My spin-down time is set for 60 min and has been so for months. have been on 5.3.5 the whole time.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
