Festplatte beschädigt? Hilfe zu smart..



  • Hallo!

    Als ich gestern meinen PC gestartet habe (Gentoo Linux), meinte fdisk
    /dev/hdb wäre seit einigen tausend Tagen nicht mehr gecheckt worden.
    Ich hab mir nix dabei gedacht, der Test lief ohne Fehler durch, arbeiten
    war normal möglich.
    Heute morgen sagte fdisk auf /dev/hdb wäre seit 1336 Tagen nichts mehr
    geprüft worden.
    Mh, komisch.. Platte ist eigentlich recht neu.

    Das sagt mir smartctl -a /dev/hdb (s.u.)

    Kann damit einer von euch was anfangen? Ich nicht.
    Danke für Hilfe und so schonmal im voraus 🙂

    smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    
    === START OF INFORMATION SECTION ===
    Device Model:     SAMSUNG SP1213N
    Serial Number:    S00UJ10XA19488
    Firmware Version: TL100-24
    User Capacity:    120,060,444,672 bytes
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   7
    ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
    Local Time is:    Sun Jun  5 14:39:42 2005 CEST
    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: 		 (4320) seconds.
    Offline data collection
    capabilities: 			 (0x1b) SMART execute Offline immediate.
    					Auto Offline data collection on/off support.
    					Suspend Offline collection upon new
    					command.
    					Offline surface scan supported.
    					Self-test supported.
    					No Conveyance Self-test supported.
    					No 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.
    					No General Purpose Logging support.
    Short self-test routine 
    recommended polling time: 	 (   1) minutes.
    Extended self-test routine
    recommended polling time: 	 (  72) 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     0x000b   100   100   051    Pre-fail  Always       -       24
      3 Spin_Up_Time            0x0007   065   001   000    Pre-fail  Always       -       5952
      4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       264
      5 Reallocated_Sector_Ct   0x0033   253   253   010    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000b   253   253   051    Pre-fail  Always       -       0
      8 Seek_Time_Performance   0x0024   253   253   000    Old_age   Offline      -       0
      9 Power_On_Half_Minutes   0x0032   100   100   000    Old_age   Always       -       472h+19m
     10 Spin_Retry_Count        0x0013   253   253   049    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       246
    194 Temperature_Celsius     0x0022   097   082   000    Old_age   Always       -       47
    195 Hardware_ECC_Recovered  0x000a   100   100   000    Old_age   Always       -       234777501
    196 Reallocated_Event_Count 0x0012   253   253   000    Old_age   Always       -       0
    197 Current_Pending_Sector  0x0033   253   253   010    Pre-fail  Always       -       0
    198 Offline_Uncorrectable   0x0031   253   253   010    Pre-fail  Offline      -       0
    199 UDMA_CRC_Error_Count    0x000b   100   100   051    Pre-fail  Always       -       1
    200 Multi_Zone_Error_Rate   0x000b   100   100   051    Pre-fail  Always       -       0
    201 Soft_Read_Error_Rate    0x000b   100   100   051    Pre-fail  Always       -       0
    
    SMART Error Log Version: 1
    ATA Error Count: 203 (device log contains only the most recent five errors)
    	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 203 occurred at disk power-on lifetime: 472 hours (19 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
      -- -- -- -- -- -- --
      04 51 00 00 4f c2 f0  Error: ABRT
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      b0 da 00 00 4f c2 f0 00      03:15:44.063  SMART RETURN STATUS
      ec 00 00 01 4f c2 f0 00      03:15:44.063  IDENTIFY DEVICE
      ef 02 00 00 00 00 f0 00      00:00:31.438  SET FEATURES [Enable write cache]
      c6 00 10 00 00 00 f0 00      00:00:31.438  SET MULTIPLE MODE
      10 00 ff 00 00 00 f0 00      00:00:31.438  RECALIBRATE [OBS-4]
    
    Error 202 occurred at disk power-on lifetime: 469 hours (19 days + 13 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
      -- -- -- -- -- -- --
      04 51 00 01 4f c2 b0  Error: ABRT
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      b0 d9 00 01 4f c2 b0 00      00:00:15.375  SMART DISABLE OPERATIONS
      ec 00 ff 01 00 00 b0 00      00:00:15.375  IDENTIFY DEVICE
      10 00 ff 3e c5 fa b0 00      00:00:15.375  RECALIBRATE [OBS-4]
      91 00 ff 3e c5 fa bf 00      00:00:15.375  INITIALIZE DEVICE PARAMETERS [OBS-6]
      ec 00 ff 01 00 00 b0 00      00:00:15.313  IDENTIFY DEVICE
    
    Error 201 occurred at disk power-on lifetime: 469 hours (19 days + 13 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
      -- -- -- -- -- -- --
      04 51 00 01 4f c2 b0  Error: ABRT
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      b0 d9 00 01 4f c2 b0 00      00:01:34.000  SMART DISABLE OPERATIONS
      ec 00 ff 01 00 00 b0 00      00:01:34.000  IDENTIFY DEVICE
      10 00 ff 3e c5 fa b0 00      00:01:34.000  RECALIBRATE [OBS-4]
      91 00 ff 3e c5 fa bf 00      00:01:34.000  INITIALIZE DEVICE PARAMETERS [OBS-6]
      ec 00 ff 01 00 00 b0 00      00:01:33.938  IDENTIFY DEVICE
    
    Error 200 occurred at disk power-on lifetime: 469 hours (19 days + 13 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
      -- -- -- -- -- -- --
      04 51 00 01 4f c2 b0  Error: ABRT
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      b0 d9 00 01 4f c2 b0 00      00:00:37.188  SMART DISABLE OPERATIONS
      ec 00 ff 01 00 00 b0 00      00:00:37.188  IDENTIFY DEVICE
      10 00 ff 3e c5 fa b0 00      00:00:37.188  RECALIBRATE [OBS-4]
      91 00 ff 3e c5 fa bf 00      00:00:37.188  INITIALIZE DEVICE PARAMETERS [OBS-6]
      ec 00 ff 01 00 00 b0 00      00:00:37.125  IDENTIFY DEVICE
    
    Error 199 occurred at disk power-on lifetime: 469 hours (19 days + 13 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
      -- -- -- -- -- -- --
      04 51 00 01 4f c2 b0  Error: ABRT
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      b0 d9 00 01 4f c2 b0 00      00:00:33.313  SMART DISABLE OPERATIONS
      ec 00 ff 01 00 00 b0 00      00:00:33.313  IDENTIFY DEVICE
      10 00 ff 3e c5 fa b0 00      00:00:33.313  RECALIBRATE [OBS-4]
      91 00 ff 3e c5 fa bf 00      00:00:33.313  INITIALIZE DEVICE PARAMETERS [OBS-6]
      ec 00 ff 01 00 00 b0 00      00:00:33.250  IDENTIFY DEVICE
    
    SMART Self-test log structure revision number 1
    No self-tests have been logged.  [To run self-tests, use: smartctl -t]
    
    Device does not support Selective Self Tests/Logging
    

    Edit: smartctl -H /dev/hdb sagt PASSED 😕



  • liegt die zeit der hwclock vllt irgendwo in der vergangenheit??.. so 1336 tage? sonst würd er wohl nicht augrund der vergangenen zeit checken wollen..



  • Ich weiß nicht, wies auf anderen System ist, aber ich Stufe SMART inzwischen gemischt ein. Meine Platte ist ca. 3 Jahre alt inzwischen. Nach einem Jahr nölte SMART rum dass ein Verrecken bevorsteht. Nachdem ich SMART dann deaktiviert hatte, war Ruhe, nach ca. zwei Jahren hab ichs wiede rangemacht, wieder ein dreiviertel Jahr Ruhe, dann wieder Fehler dass es bald bergab geht. Die Platte läuft immernoch. Wie soll ich ein System mit so viel Fehlalarm ernst nehmen 😕


Anmelden zum Antworten