Hey Guys,Do I need to worry about this:"Detected increasing command timeouts[65539] on disk 2 [ST31000340AS, 9QJ1AFDD]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy."I looked up command timeout errors for SMART and it states:188 BC Command Timeout A number of aborted operations due to HDD timeout. Normally this attribute value should be equal to zero and if the value is far above zero, then most likely there will be some serious problems with power supply or an oxidized data cable.I checked the SMART log and for disk 2 it says:Command Timeout: 4295032835Which seems like a lot higher than zero. LOL.I do have disk spin-down after 10 mins enabled and I think this is what's causing the high command timeout count. I get timeout error on my Mac OS X 10.8.1 from time to time when I access via AFP and it needs a few seconds before the disk spin-up.Do I need to worry about this? disk 1 command timeout count is about half of disk 2.Thanks guys/girls!

Are the drives the same make/model and running the same firmware?You could try increasing the Spindown time to something like 30 minutes and see if that has an effect. Otherwise, power down the NAS normally and remove the drive and Run SeaTools on it. That will give you a thorough diagnosis of the state of the drive. Be prepared for a bit of a wait though, as the Disk surface scan in SeaTools is mind numbingly slow in my experience.Remember to mark which bay the drive came from too and don't get that order mixed up.

I had disk spindown set at 15 minutes on a ST32000641as nad got the same error but with 4295032833 command timeouts!!!I took disk out and ran sea tools on it - every test they have on there and it passed everything - should I be concerned and should I push Seagate to accept the disk back (my warranty is still valid til 2014)?

toomanybarts wrote:I had disk spindown set at 15 minutes on a ST32000641as nad got the same error but with 4295032833 command timeouts!!!I took disk out and ran sea tools on it - every test they have on there and it passed everything - should I be concerned and should I push Seagate to accept the disk back (my warranty is still valid til 2014)?Did you ever run the full disk test (from the boot menu)?You also might want to confirm the SMART tests on your PC. Acronis Drive monitor is one freeware download that will let you see them. Seatools won't.Returning the drive to Seagate would just get you a refurbished replacement. If the NAS is performing normally I'd wait.

not sure what you mean "full disk test from boot menu" - I ran every test that was listed in the menu on sea tools inc the "advanced" ones where they warn you it may lose all your data...passed everything!There's another thread on the forums where people have verified the SMART readings, but have swapped drives from drive 1 and 2 and only drive ! increases command timeouts - it looks like seagate drives in drive 1 are susceptible to high command timeouts on the nv+ v2...thinking this is another firmware issue on the NAS.I dont have Acronis Drive monitor, but will take a look into it.

I connected ST31000340AS to my PC Desktop running Windows Home Server 2011 and ran the SMART report on the 2 drives and one was "FAILING" and the other was giving me "WARNING" of impending failure. I did the online warranty & return on seagate.com and getting replacement drives tomorrow. I figured why not just get the drives replaced since I'm under warranty. You should probably do the same.

Getting "increasing command timeouts" error on SMART

12 Replies

Replies have been turned off for this discussion

fastfwd
Virtuoso
Jun 26, 2013
ken830 wrote:
toomanybarts wrote:
the exact same 4295032833 command timeouts. Seems a bit unlikely that we would have the same exact number of errors.

Right. 4295032833 decimal is 0001 0001 0001 hexadecimal. It's unlikely that that's an actual count of anything; it looks more like the real count is only 1, but the SMART parser is misinterpreting it. The Command Timeout count is shown as a 48-bit number in the SMART spec, and that's how it's being interpreted in your case, but maybe your drive stores it as a 16-bit number and repeats it three times for some reason. Or maybe the SMART parser has a bug that makes it erroneously read the same 16 bits three times.

There might be something to worry about here, but it isn't command timeouts.
gibxxi
Guide
Sep 08, 2013
I installed the Samsung HD204UI (SpinPoint F4EG) drives in my primary NAS (At the time, a ReadyNAS Ultra 4, Now a Pro 4) At least two & a half years ago. I too had ridiculous amounts of command-timeouts in the SMART log. A quick search of the Samsung forums told me that it was an issue that was somewhat OS related and in no way related to the health or stability of the drive(s) at all.

Despite recently having a single "Pending" sector discovered recently on the parity (4th) drive which meant I was unable to Factory Default the NAS at that time, a full wipe of said disk followed by a full surface scan resulted in the offending "Pending" sector disappearing from the SMART log and all was well again.

None of the drives have used ANY of their reserve sectors at this time despite many outages, and a couple of issues where the UPS failed to shut down the NAS or the PC connected to it in time due to an ageing battery.

Forum Discussion

Getting "increasing command timeouts" error on SMART

12 Replies

Related Content

Getting Started - Registration

R7000 V1.0.6.28_1.1.8 "OpenVPN connection timeout"

I'm getting freezing

OpenVPN client "Server poll timeout"

Couldn't get IP address

NETGEAR Academy

ProSupport for Business