[smartmontools-support] LITEON IT LCS-256L9S strange hours and possible failure?

Thane K. Sherrington thane at computerconnectionltd.com
Tue Apr 10 19:37:33 CEST 2018


Hi Dan,

     I was referring to the self-test results (the lifetime hours are 9984).

MART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining 
LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00% 9984         -
# 2  Extended offline    Aborted by host               90% 4352         -
# 3  Extended offline    Completed without error       00% 9984         -
# 4  Extended offline    Interrupted (host reset)      90% 9728         -
# 5  Extended offline    Interrupted (host reset)      90% 9728         -
# 6  Extended offline    Completed without error       00% 9216         -
# 7  Short offline       Completed without error       00% 7680         -
# 8  Extended offline    Aborted by host               90% 7680         -
# 9  Extended offline    Completed without error       00% 7680         -
#10  Extended offline    Completed without error       00% 7680         -
#11  Extended offline    Completed without error       00% 7680         -
#12  Extended offline    Completed without error       00% 7680         -
#13  Extended offline    Completed without error       00% 7680         -
#14  Extended offline    Completed without error       00% 7168         -
#15  Extended offline    Completed without error       00% 7168         -
#16  Extended offline    Completed without error       00% 7168         -
#17  Extended offline    Completed without error       00% 7168         -
#18  Extended offline    Interrupted (host reset)      90% 7168         -
#19  Extended offline    Interrupted (host reset)      90% 7168         -
#20  Short offline       Completed without error       00% 4864         -
#21  Extended offline    Aborted by host               90% 4864         -

And these errors:

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 2

ATA Error Count: 0
     CR = Command Register [HEX]
     FR = Features Register [HEX]
     SC = Sector Count Register [HEX]
     SN = Sector Number Register [HEX]
     CL = Cylinder Low Register [HEX]
     CH = Cylinder High Register [HEX]
     DH = Device/Head Register [HEX]
     DC = Device Command Register [HEX]
     ER = Error register [HEX]
     ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 0 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
   When the command that caused the error occurred, the device was in an 
unknown state.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   af 10 02 00 00 00 00

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   00 af 02 00 00 00 00 b8      00:00:00.000  NOP [Reserved subcommand] 
[OBS-ACS-2]
   00 af 02 00 00 00 00 b4      00:00:00.000  NOP [Reserved subcommand] 
[OBS-ACS-2]
   00 af 02 00 00 00 00 b1      00:00:00.000  NOP [Reserved subcommand] 
[OBS-ACS-2]
   00 af 02 00 00 00 00 ae      00:00:00.000  NOP [Reserved subcommand] 
[OBS-ACS-2]

Error -1 occurred at disk power-on lifetime: 768 hours (32 days + 0 hours)
   When the command that caused the error occurred, the device was in an 
unknown state.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   00 00 00 00 00 10 00

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   00 00 00 00 00 00 00 02  34d+02:40:19.456  NOP [Abort queued commands]
   00 00 00 00 00 00 00 02  34d+02:37:02.848  NOP [Abort queued commands]
   00 00 00 00 00 00 00 02  34d+02:33:46.240  NOP [Abort queued commands]
   00 00 00 00 00 00 00 02  34d+02:30:29.632  NOP [Abort queued commands]
   00 00 00 00 00 00 00 00  34d+02:27:13.024  NOP [Abort queued commands]

Error -2 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
   When the command that caused the error occurred, the device was in an 
unknown state.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   00 af 00 00 00 00 9b

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   af 00 00 00 00 00 98 00      00:00:00.002  [RESERVED]
   af 00 00 00 00 00 95 00      00:00:00.002  [RESERVED]
   af 00 00 00 00 00 92 00      00:00:00.002  [RESERVED]
   af 00 00 00 00 00 8f 00      00:00:00.002  [RESERVED]
   00 00 00 00 00 03 00 00      00:00:00.000  NOP [Abort queued commands]

Error -3 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
   When the command that caused the error occurred, the device was in an 
unknown state.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   00 00 00 00 8c af 02

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   00 00 00 00 89 af 02 00      00:00:00.000  NOP [Abort queued commands]
   00 00 00 00 86 af 02 00      00:00:00.000  NOP [Abort queued commands]
   00 00 00 00 82 af 02 00      00:00:00.000  NOP [Abort queued commands]
   00 00 00 00 7f af 02 00      00:00:00.000  NOP [Abort queued commands]
   00 00 00 03 00 00 00 00      00:00:00.000  NOP [Abort queued commands]

Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
   When the command that caused the error occurred, the device was in an 
unknown state.

   After command completion occurred, registers were:
   ER ST SC SN CL CH DH
   -- -- -- -- -- -- --
   00 00 7c af 02 00 00

   Commands leading to the command that caused the error were:
   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
   -- -- -- -- -- -- -- --  ----------------  --------------------
   00 00 79 af 02 00 00 00      00:00:00.000  NOP [Abort queued commands]
   00 00 76 af 02 00 00 00      00:00:00.000  NOP [Abort queued commands]
   00 00 73 af 02 00 00 00      00:00:00.000  NOP [Abort queued commands]
   00 00 0d 93 01 00 00 00      00:00:00.000  NOP [Abort queued commands]
   00 03 00 00 00 00 00 00      00:00:00.000  NOP [Reserved subcommand] 
[OBS-ACS-2]

Thane K. Sherrington

Computer Connection, Ltd.  ...taking the mystery out of computers since 1982.
Winner of the 2012 Ian Spencer - Excellence in Business Award
Winner of the 2016 Reader's Choice Best Computer Store
Winner of the 2017 Reader's Choice Best Computer Store
95 College St., Antigonish,
NS B2G 1X6
902-863-3361 (phone)
902-863-2580 (fax)
thane at computerconnectionltd.com

On 10/04/2018 2:25 PM, Dan Lukes wrote:
> On 10.4.2018 18:48, Thane K. Sherrington wrote:
>> 1)Why are the hours so high when it's brand new?
>
>>> 9 Power_On_Hours 0x0002 100 100 000 Old_age Always - 39
>
> I see 39 hours. It's not so high. It may be manufacturing test.
>
>> 2)Do I worry about the errors reported
>
> I see no errors reported. Neither in Error Log nor in Self-test log.
>
> Dan
>
>
>






More information about the Smartmontools-support mailing list