NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Maxpower411
Aug 14, 2017Aspirant
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...
- Aug 14, 2017
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)?
StephenB
Aug 14, 2017Guru - Experienced User
I'd wait a while and see if the counts continue to rise.
It could be that disk 6 is bad though.
Maxpower411
Aug 14, 2017Aspirant
There was a 4th drive that I sent back at 17,000+ timeouts
But the question is is this normal "all drives seeing command timeouts and all being new??
- StephenBAug 14, 2017Guru - Experienced User
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)?
- Maxpower411Aug 14, 2017Aspirant
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: 65Device: 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: 75Device: 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- mdgm-ntgrAug 15, 2017NETGEAR Employee Retired
smart_history.log shows the changes in key SMART values over time.
- StephenBAug 15, 2017Guru - Experienced User
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.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!