NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
blacey
Sep 29, 2012Aspirant
3 drive failures w/in 10 days of 4.2.22 upgrade? #19570015
Within two days of upgrading my Ultra 6 with 6 2 TB drives in it to 4.2.22, it marked a drive dead. I always keep a spare so I swapped the drive out and completed a cross-ship RMA with Seagate. Befo...
Mr__Bear
Nov 13, 2012Aspirant
I am also seeing similar issue with 4.2.22 on my ReadyNAS 2100. The 2100 was running without issue with 3x 2TB ST32000644NS and 1x 2TB ST2000NM0011 prior to 4.2.22, the odd ST2000NM0011 was a replacement from NETGEAR about a year ago for a failed ST32000644NS, a 6Gbps 2TB disk that is on the 2100 HCL.
As soon as 4.2.22 is applied, the ST2000NM0011 start throwing Command Timeout Error at an alarming rate (30+ timeout in a day) especially when the unit is under load. While waiting for NETGEAR to RMA the drive, we replaced the ST2000NM0011 with another identical brand new (no error whatsoever on SMART) and instantly the same Command Timeout errors were thrown. Looking at the logs, we are seeing once the unit is under load, it was throwing multiple errors similar to the one below -
Nov 7 07:15:40 emboar kernel: ata5.00: status: { DRDY }
Nov 7 07:15:40 emboar kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Nov 7 07:15:40 emboar kernel: ata5.00: cmd 61/08:88:d0:90:a2/00:00:08:00:00/40 tag 17 ncq 4096 out
Nov 7 07:15:40 emboar kernel: res 40/00:b0:c8:9c:a2/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Nov 7 07:15:40 emboar kernel: ata5: hard resetting link
Nov 7 07:15:40 emboar kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Nov 7 07:15:40 emboar kernel: ata5.00: configured for UDMA/133
Nov 7 07:15:40 emboar kernel: ata5: EH complete
Sometime it will attempt to reset the link @ 3.0 Gbps but that will always timeout again and lead to another reset to 1.5Gbps where things will stabilize and the timeout errors stop. Once the unit is reboot and the link reestablished at 5.0Gbps as it should be, the timeout error will quickly return leading to another downgrade to 1.5Gbps.
We then replaced the second ST2000NM0011 with NETGEAR's replacement ST32000644NS, the error went away completely and we can stress the unit and it sticks at 5.0 Gbps without any errors. We did a full long test using SEATools on the ST2000NM0011 without any problem.
I would say there is something in 4.2.22 at least in my case that affected compatibility with certain drives. More detail @ http://www.readynas.com/forum/viewtopic.php?f=24&t=67736
A level 2 case was also opened #19802848.
As soon as 4.2.22 is applied, the ST2000NM0011 start throwing Command Timeout Error at an alarming rate (30+ timeout in a day) especially when the unit is under load. While waiting for NETGEAR to RMA the drive, we replaced the ST2000NM0011 with another identical brand new (no error whatsoever on SMART) and instantly the same Command Timeout errors were thrown. Looking at the logs, we are seeing once the unit is under load, it was throwing multiple errors similar to the one below -
Nov 7 07:15:40 emboar kernel: ata5.00: status: { DRDY }
Nov 7 07:15:40 emboar kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Nov 7 07:15:40 emboar kernel: ata5.00: cmd 61/08:88:d0:90:a2/00:00:08:00:00/40 tag 17 ncq 4096 out
Nov 7 07:15:40 emboar kernel: res 40/00:b0:c8:9c:a2/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Nov 7 07:15:40 emboar kernel: ata5: hard resetting link
Nov 7 07:15:40 emboar kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Nov 7 07:15:40 emboar kernel: ata5.00: configured for UDMA/133
Nov 7 07:15:40 emboar kernel: ata5: EH complete
Sometime it will attempt to reset the link @ 3.0 Gbps but that will always timeout again and lead to another reset to 1.5Gbps where things will stabilize and the timeout errors stop. Once the unit is reboot and the link reestablished at 5.0Gbps as it should be, the timeout error will quickly return leading to another downgrade to 1.5Gbps.
We then replaced the second ST2000NM0011 with NETGEAR's replacement ST32000644NS, the error went away completely and we can stress the unit and it sticks at 5.0 Gbps without any errors. We did a full long test using SEATools on the ST2000NM0011 without any problem.
I would say there is something in 4.2.22 at least in my case that affected compatibility with certain drives. More detail @ http://www.readynas.com/forum/viewtopic.php?f=24&t=67736
A level 2 case was also opened #19802848.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!