Question Seagate CDI reports high number on Command Timeout but still in “Good” condition

Nov 25, 2021
42
0
30
0
"Network unavailable or slow. iCloud Photos is taking longer to load than expected."

The raw values consist of three 16-bit hexadecimal numbers :

0001 / 0002 / 0004 -> 1 / 2 /4 (decimal)​
000C / 000C / 000C -> 12 / 12 / 12​
0000 / 0000 / 0001 -> 0 / 0 / 1​
0017 /0017 / 0019 -> 23 / 23 / 25​
These numbers are explained in the following document.

Seagate SMART Attribute Specification:
http://t1.daumcdn.net/brunch/service/user/axm/file/zRYOdwPu3OMoKYmBOby1fEEQEbU.pdf
http://www.hddoracle.com/download/file.php?id=5129

These numbers become a problem when the first two values are non-zero. They correspond to timeouts lasting 7 seconds. When these occur, there will be a noticeable lag.
 
Nov 25, 2021
42
0
30
0
"Network unavailable or slow. iCloud Photos is taking longer to load than expected."

The raw values consist of three 16-bit hexadecimal numbers :

0001 / 0002 / 0004 -> 1 / 2 /4 (decimal)​
000C / 000C / 000C -> 12 / 12 / 12​
0000 / 0000 / 0001 -> 0 / 0 / 1​
0017 /0017 / 0019 -> 23 / 23 / 25​
These numbers are explained in the following document.

Seagate SMART Attribute Specification:
http://t1.daumcdn.net/brunch/service/user/axm/file/zRYOdwPu3OMoKYmBOby1fEEQEbU.pdf
http://www.hddoracle.com/download/file.php?id=5129

These numbers become a problem when the first two values are non-zero. They correspond to timeouts lasting 7 seconds. When these occur, there will be a noticeable lag.
I understand but why CDI still reports Command Timeout “Good” if they have a high raw values?
 
Last edited:
Strictly speaking, a SMART attribute is considered to have failed when its Current normalised value falls below the Threshold value. CDI and other SMART tools use their own value judgments to decide on pre-emptive warnings and cautions for certain attributes (eg reallocated and pending sectors), but it appears that Command Timeouts is not singled out for special treatment.
 
Nov 25, 2021
42
0
30
0
Strictly speaking, a SMART attribute is considered to have failed when its Current normalised value falls below the Threshold value. CDI and other SMART tools use their own value judgments to decide on pre-emptive warnings and cautions for certain attributes (eg reallocated and pending sectors), but it appears that Command Timeouts is not singled out for special treatment.
Here is my CDI result

Command Timeout
Current Worst Threshold Raw Values
100 99 0 000000000004

https://share.icloud.com/photos/0L12WxGOzTtIHgBGEJyMuyCCQ#Meycauayan_City_-_Pandayan

Please help me interpret this.
 
Last edited:

ASK THE COMMUNITY

Latest posts