• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Interpreting smartctl log

S

shanester

Weaksauce
Joined
Mar 1, 2011
Messages
75
Can any assist with interpreting what the output of this data is?

Code: 
selftest logfile and errors of c3t5000CCA369D1CF9Fd0 Hitachi HDS5C3020ALA632

/usr/sbin/smartctl -l selftest -d sat,12 -T permissive /dev/rdsk/c3t5000CCA369D1CF9Fd0s0

smartctl 6.0 2012-10-10 r3643 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART 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%       526         -

/usr/sbin/smartctl -l error -d sat,12 -T permissive /dev/rdsk/c3t5000CCA369D1CF9Fd0s0
   
smartctl 6.0 2012-10-10 r3643 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 2
        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 2 occurred at disk power-on lifetime: 520 hours (21 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  10 51 72 7e bc 22 07  Error: IDNF at LBA = 0x0722bc7e = 119716990

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 20 f0 d9 22 40 00   3d+04:44:00.004  WRITE FPDMA QUEUED
  61 00 18 f0 d8 22 40 00   3d+04:44:00.004  WRITE FPDMA QUEUED
  61 00 08 f0 d7 22 40 00   3d+04:44:00.004  WRITE FPDMA QUEUED
  61 00 10 f0 d6 22 40 00   3d+04:44:00.003  WRITE FPDMA QUEUED
  61 00 00 f0 d5 22 40 00   3d+04:44:00.003  WRITE FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  10 51 e3 cc 54 8d 02  Error: IDNF at LBA = 0x028d54cc = 42816716

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 40 2f 95 8d 40 00      00:27:43.103  WRITE FPDMA QUEUED
  61 80 20 af 94 8d 40 00      00:27:43.102  WRITE FPDMA QUEUED
  61 80 00 2f 94 8d 40 00      00:27:43.102  WRITE FPDMA QUEUED
  61 80 38 af 93 8d 40 00      00:27:43.101  WRITE FPDMA QUEUED
  61 00 18 af 92 8d 40 00      00:27:43.101  WRITE FPDMA QUEUED
 
You must log in or register to reply here.
Back
Top