NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Netgar ReadyNas 516 New Drive Install Seagate-Command Timeouts
Problem with ReadNas 516 Diskless Firmware on NAS 6.75 All New Drives Seagate ST6000NE0021 3 No Problems with new install in a used NAS except for Disk 3 has 20 command timeouts, Disk 5 has 7 Comm...
I haven't seen this myself. I believe the drive counts ATA errors, but the OS drivers might be counting the command timeouts. If so, I think that an issue with one drive can cause sata bus timeouts on other drives.
Can you look in disk_info.log, and see if there are ATA errors there (and if they are tracking the command timeouts)?
This is the log you asked for no ata error at all
Device: sda
Controller: 0
Channel: 3
Model: ST6000NE0021-2EN11C
Serial: ZA16JSPT
Firmware: EN02
Class: SATA
RPM: 7200
Sectors: 11721045168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: 7c6e0cf4
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 20
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 50
Start/Stop Count: 56
Power-On Hours: 114
Power Cycle Count: 56
Load Cycle Count: 65
Device: sdb
Controller: 0
Channel: 4
Model: ST6000NE0021-2EN11C
Serial: ZA16J3E8
Firmware: EN02
Class: SATA
RPM: 7200
Sectors: 11721045168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: 7c6e0cf4
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 7
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 53
Start/Stop Count: 47
Power-On Hours: 114
Power Cycle Count: 47
Load Cycle Count: 75
Device: sdc
Controller: 0
Channel: 5
Model: ST6000NE0021-2EN11C
Serial: ZA16K95A
Firmware: EN02
Class: SATA
RPM: 7200
Sectors: 11721045168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: 7c6e0cf4
Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 113
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 50
Start/Stop Count: 41
Power-On Hours: 97
Power Cycle Count: 41
Load Cycle Count: 75
smart_history.log shows the changes in key SMART values over time.
I'd watch it longer, and see if the count on any disk continues to climb. Scheduling a scrub is one way to create a lot of disk activity.
The one I'd watch most closely is ZA16K95A. If you still can exchange that for free, then maybe just do it as a precaution.
Thanks for the feeback- I had moved all drives around durring the process of troubleshooting. (prior to removing the 17,000+ error drive) But also did notice from the time of that post that there were no more warnings and and the count did not move. It seemed that
the bad drive I sent back was causing all the warnings which did increase incramentally as the drive created a volume and resynced.
At some point I cleared the log did a factory reset and then all warnings stopped, the drive now has the same amount of timeout errors that it did prior to the factory reset, with no error messages as well as no incremental upgrades to these numbers I posted. Hopefully When I get my new drive and install it I can find out which came first the chicken or the egg? It does seem that one bad drive can make all the others begin to incrementally increase and report timeout errors, as this was the case. ZA16K95A is suspect still, but there are no error messages and again no increases in timeout count. I will wait for the new drive and resysc the volume and watch. New does not mean good, just untested thanks!!
I will report my finding shortly.
I'm Back it is Friday, and I have replaced the drive that had 17000+ errors. There are no more incremental timeouts on any of the drives.
The ReadyNas 516 is preforming flawlessly with no more timeouts on any of the drives. I belive that One Bad Apple can spoil the whole bunch. Truly I believe that the Bad drive was truly cusing all the others to incrementally increase with warnings, as well as it called out itself at 17,000+ errors. I syill can change out that 100+ drive, but feel that all the counting on the drives was created by the "Bad Apple",
which is now bad, but gone- error counts staying as they were. Resyning will contine for another 24 hours or so, starting at about 40+ hours- But no errors at all except the old logs which all remain the same. I believe all drives except the 17,000+ drive were good but that
drive made the others count incrementally. Any feedback ? will report back at the end of the resyncing, any feedback on the new 6.80 OS
Thanks to all helpfull people, I do enjoy the idea of paying it back.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
