Seagate ST2000DL003-9VT166

I read a few threads on adjusting drive timeout values in Linux - noting that no one claims success & not having much else to do I applied the method and have flogged the unit for 2 weeks now with no dead drives. It seems pretty stable. I cant say if its just luck or if it actually works. Time will tell- if you would like to try it - here it is. After a reboot (can be automated via /etc/rc.local), I run the following commands:- echo 300 > /sys/block/sda/device/timeout echo 300 > /sys/block/sdb/device/timeout xxxx Default is 30 - I do this for every drive in the raid group. In the Ultra 6 it ends up being for sda, sdb, ..... sdf Give t a try..... If it continues to works ... it saves me going and getting WD red NAS drives.

I. too. am very interested in how this holds up. It still doesn't explain why going back to RAIDiator 4.2.21 has fixed the problem for me, though. To me, that clearly indicates that there is a fix that Netgear could implement if they only had a clue what they changed (intentionally or not) in the 4.2.22 update that affected this. The default timeout in 4.2.21 is also 30, so that's not it. I would like to update RAIDiator on my NAS's, but dare not due to this issue. I keep the ones without the ST2000DL003's at 4.2.21 also, in case the NAS with them has a hardware problem and I need to swap the disks to another.

I ran more than a year and a half with these drives with no problems. Upgraded to 4.2.22 and had problems within a week. Downgraded to 4.2.21 and have been going strong for another year. Yeah, it's a Seagate problem. :roll: