SMART question

Discussion in 'Mac Accessories' started by yg17, Nov 29, 2006.

  1. yg17 macrumors G5

    yg17

    Joined:
    Aug 1, 2004
    Location:
    St. Louis, MO
    #1
    Due to the possibility that my PB's hard drive is dying (clicking noises, but they stopped), I installed smartmontools to find out the SMART status of my drive. This is what I got:

    Code:
    Todds-PowerBook:~ todd$ smartctl  -a /dev/disk0
    smartctl version 5.36 [powerpc-apple-darwin8.8.0] Copyright (C) 2002-6 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    
    === START OF INFORMATION SECTION ===
    Model Family:     Fujitsu MHTxxxxAH family
    Device Model:     FUJITSU MHT2080AH
    Serial Number:    NP0PT562BG40
    Firmware Version: 81EC
    User Capacity:    80,026,361,856 bytes
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   6
    ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 3a
    Local Time is:    Thu Nov 30 00:37:23 2006 CST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    
    General SMART Values:
    Offline data collection status:  (0x00) Offline data collection activity
                                            was never started.
                                            Auto Offline Data Collection: Disabled.
    Self-test execution status:      (   0) The previous self-test routine completed
                                            without error or no self-test has ever 
                                            been run.
    Total time to complete Offline 
    data collection:                 ( 587) seconds.
    Offline data collection
    capabilities:                    (0x7b) SMART execute Offline immediate.
                                            Auto Offline data collection on/off support.
                                            Suspend Offline collection upon new
                                            command.
                                            Offline surface scan supported.
                                            Self-test supported.
                                            Conveyance Self-test supported.
                                            Selective Self-test supported.
    SMART capabilities:            (0x0003) Saves SMART data before entering
                                            power-saving mode.
                                            Supports SMART auto save timer.
    Error logging capability:        (0x01) Error logging supported.
                                            General Purpose Logging supported.
    Short self-test routine 
    recommended polling time:        (   2) minutes.
    Extended self-test routine
    recommended polling time:        (  80) minutes.
    Conveyance self-test routine
    recommended polling time:        (   2) minutes.
    
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000f   100   100   046    Pre-fail  Always       -       196109
      2 Throughput_Performance  0x0005   100   100   030    Pre-fail  Offline      -       23855104
      3 Spin_Up_Time            0x0003   100   100   025    Pre-fail  Always       -       1
      4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1277
      5 Reallocated_Sector_Ct   0x0033   100   100   024    Pre-fail  Always       -       8589934592000
      7 Seek_Error_Rate         0x000f   100   100   047    Pre-fail  Always       -       68
      8 Seek_Time_Performance   0x0005   100   100   019    Pre-fail  Offline      -       0
      9 Power_On_Seconds        0x0032   097   097   000    Old_age   Always       -       1585h+36m+46s
     10 Spin_Retry_Count        0x0013   100   100   020    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1230
    192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       194
    193 Load_Cycle_Count        0x0032   096   096   000    Old_age   Always       -       49794
    194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       43 (Lifetime Min/Max 14/60)
    195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       1210
    196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       286785536
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       5
    200 Multi_Zone_Error_Rate   0x000f   100   100   060    Pre-fail  Always       -       11207
    203 Run_Out_Cancel          0x0002   100   100   000    Old_age   Always       -       433759257341
    
    SMART Error Log Version: 1
    ATA Error Count: 5
            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 5 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
      -- -- -- -- -- -- --
      84 51 00 a5 f9 d0 46  Error: ICRC, ABRT at LBA = 0x06d0f9a5 = 114358693
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      ca 00 00 a6 f8 d0 46 02      00:01:40.426  WRITE DMA
      ca 00 00 a6 f8 d0 46 02      00:01:24.190  WRITE DMA
      ca 00 00 a6 f8 d0 46 02      00:01:07.953  WRITE DMA
      ca 00 00 a6 f8 d0 46 02      00:00:59.854  WRITE DMA
      ef 03 43 00 00 00 a0 02      00:00:59.851  SET FEATURES [Set transfer mode]
    
    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 active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 a5 f9 d0 46  Error: ICRC, ABRT at LBA = 0x06d0f9a5 = 114358693
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      ca 00 00 a6 f8 d0 46 02      00:01:24.190  WRITE DMA
      ca 00 00 a6 f8 d0 46 02      00:01:07.953  WRITE DMA
      ca 00 00 a6 f8 d0 46 02      00:00:59.854  WRITE DMA
      ef 03 43 00 00 00 a0 02      00:00:59.851  SET FEATURES [Set transfer mode]
      ca 00 00 a6 f8 d0 46 02      00:00:58.678  WRITE DMA
    
    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 active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 a5 f9 d0 46  Error: ICRC, ABRT at LBA = 0x06d0f9a5 = 114358693
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      ca 00 00 a6 f8 d0 46 02      00:01:07.953  WRITE DMA
      ca 00 00 a6 f8 d0 46 02      00:00:59.854  WRITE DMA
      ef 03 43 00 00 00 a0 02      00:00:59.851  SET FEATURES [Set transfer mode]
      ca 00 00 a6 f8 d0 46 02      00:00:58.678  WRITE DMA
      c5 00 01 b7 f8 d0 e6 02      00:00:58.677  WRITE MULTIPLE
    
    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 active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      84 51 00 a5 f9 d0 46  Error: ICRC, ABRT at LBA = 0x06d0f9a5 = 114358693
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      ca 00 00 a6 f8 d0 46 02      00:00:59.854  WRITE DMA
      ef 03 43 00 00 00 a0 02      00:00:59.851  SET FEATURES [Set transfer mode]
      ca 00 00 a6 f8 d0 46 02      00:00:58.678  WRITE DMA
      c5 00 01 b7 f8 d0 e6 02      00:00:58.677  WRITE MULTIPLE
      c5 00 01 b6 f8 d0 e6 02      00:00:58.676  WRITE MULTIPLE
    
    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
      -- -- -- -- -- -- --
      84 51 00 a5 f9 d0 46  Error: ICRC, ABRT at LBA = 0x06d0f9a5 = 114358693
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      ca 00 00 a6 f8 d0 46 02      00:00:58.678  WRITE DMA
      c5 00 01 b7 f8 d0 e6 02      00:00:58.677  WRITE MULTIPLE
      c5 00 01 b6 f8 d0 e6 02      00:00:58.676  WRITE MULTIPLE
      c5 00 08 ae f8 d0 e6 02      00:00:58.674  WRITE MULTIPLE
      c5 00 08 a6 f8 d0 e6 02      00:00:58.672  WRITE MULTIPLE
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Short offline       Completed without error       00%      1585         -
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    
    My main concern is the number of reallocated sectors...8589934592000??? Are there even that many sectors on my drive? Seems like such a huge number. One HD in my PowerMac has 3 reallocated sectors and the other HD in my PM has none. Is this a false reading or something? Is there anything else in the SMART status that would imply my drive is dying? I don't know what half of that stuff means. Thanks
     
  2. michael301080 macrumors newbie

    Joined:
    Jul 3, 2008
    #2
    Same issue

    Hi,

    I have the exact same values you listed for Reallocated_Sector_Ct (8589934592000). The value for Run_out_Cancel is 2628567433572 for my drive but is already older the your drive was (Power_On_Hours 2588).
    I hope it doesn't mean the drive is dying. Since a year and a half has passed since your post, is your drive still OK? Do I need to worry about replacing this drive?

    I guess we're the only ones messing around with smartmontools on our mac, since no one has replied to you before.
     
  3. texastwister macrumors newbie

    Joined:
    Jul 10, 2008
    #3
    Same here -- only not on a MAC

    A google search brought me here and I note with curiosity that the Reallocated_Sector_Ct is *exactly* the same on my HD which is in a Dell Laptop running Ubuntu. The commonality I see is that we're both (maybe all three of us?) using Fujitsu drives. I've noticed in my Google searching that there seems to be considerable variation from one drive manuf. to another in how they use the various values specified by the standard. My strong suspicion is that this particular value need not be a cause for concern for us.
     

Share This Page