festplatten error auswerten

Dieses Thema im Forum "Laufwerke / Speichermedien" wurde erstellt von oyster-manu, 17.05.2007.

  1. #1 oyster-manu, 17.05.2007
    oyster-manu

    oyster-manu toast

    Dabei seit:
    26.06.2003
    Beiträge:
    1.055
    Zustimmungen:
    0
    hallo,
    ich habe ein Problem mit der Festplatte meiner Freundin: immer wenn der PC eingeschaltet wird, brummt die festplatte extrem laut für ca. 5min. Danach sinkt der pegel wieder auf normale lautstärke ab.
    Ich habe nun smartmontools durchlaufen lassen. Ich blicke allerdings nicht durch die Fehlermeldungen durch....


    Code:
    linux:~ # smartctl -a /dev/hda
    [AUSZUG]
    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:     MAXTOR 6L040J2
    Serial Number:    662205153313
    Firmware Version: A93.0500
    User Capacity:    40,027,029,504 bytes
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   5
    ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
    Local Time is:    Thu May 17 22:14:03 2007 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:  (0x80) Offline data collection activity
                                            was never started.
                                            Auto Offline Data Collection: Enabled.
    Self-test execution status:      (  16) The self-test routine was aborted by
                                            the host.
    Total time to complete Offline
    data collection:                 (  35) 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.
    
    
    SMART Error Log Version: 1
    ATA Error Count: 7 (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 7 occurred at disk power-on lifetime: 573 hours (23 days + 21 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
      -- -- -- -- -- -- --
      40 d1 10 f7 6f 09 e0  Error: UNC at LBA = 0x00096ff7 = 618487
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c4 00 10 f7 6f 09 e0 09      00:01:45.503  READ MULTIPLE
      c6 00 10 00 00 00 ef 09      00:01:45.502  SET MULTIPLE MODE
      91 00 3f 00 00 00 af 09      00:01:45.502  INITIALIZE DEVICE PARAMETERS [OBS-6]
      10 00 00 00 00 00 a0 09      00:01:45.500  RECALIBRATE [OBS-4]
      ff ff ff ff ff ff ff ff      00:01:45.314  [VENDOR SPECIFIC]
    
    Error 6 occurred at disk power-on lifetime: 573 hours (23 days + 21 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
      -- -- -- -- -- -- --
      40 d1 10 f7 6f 09 e0  Error: UNC at LBA = 0x00096ff7 = 618487
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c4 00 10 f7 6f 09 e0 09      00:01:40.303  READ MULTIPLE
      c6 00 10 00 00 00 ef 09      00:01:40.302  SET MULTIPLE MODE
      91 00 3f 00 00 00 af 09      00:01:40.302  INITIALIZE DEVICE PARAMETERS [OBS-6]
      10 00 00 00 00 00 a0 09      00:01:40.300  RECALIBRATE [OBS-4]
      ff ff ff ff ff ff ff ff      00:01:40.114  [VENDOR SPECIFIC]
    
    Error 5 occurred at disk power-on lifetime: 573 hours (23 days + 21 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
      -- -- -- -- -- -- --
      40 d1 10 f7 6f 09 e0  Error: UNC at LBA = 0x00096ff7 = 618487
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c4 00 10 f7 6f 09 e0 09      00:01:35.103  READ MULTIPLE
      c6 00 10 00 00 00 ef 09      00:01:35.103  SET MULTIPLE MODE
      91 00 3f 00 00 00 af 09      00:01:35.102  INITIALIZE DEVICE PARAMETERS [OBS-6]
      10 00 00 00 00 00 a0 09      00:01:35.100  RECALIBRATE [OBS-4]
      ff ff ff ff ff ff ff ff      00:01:34.914  [VENDOR SPECIFIC]
    
    Error 4 occurred at disk power-on lifetime: 573 hours (23 days + 21 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
      -- -- -- -- -- -- --
      40 d1 10 f7 6f 09 e0  Error: UNC at LBA = 0x00096ff7 = 618487
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c4 00 10 f7 6f 09 e0 09      00:01:29.903  READ MULTIPLE
      c6 00 10 00 00 00 ef 09      00:01:29.902  SET MULTIPLE MODE
      91 00 3f 00 00 00 af 09      00:01:29.902  INITIALIZE DEVICE PARAMETERS [OBS-6]
      10 00 00 00 00 00 a0 09      00:01:29.900  RECALIBRATE [OBS-4]
      ff ff ff ff ff ff ff ff      00:01:29.723  [VENDOR SPECIFIC]
    
    Error 3 occurred at disk power-on lifetime: 573 hours (23 days + 21 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
      -- -- -- -- -- -- --
      40 d1 10 f7 6f 09 e0  Error: UNC at LBA = 0x00096ff7 = 618487
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c4 00 10 f7 6f 09 e0 09      00:01:24.708  READ MULTIPLE
      c4 00 10 e7 6f 09 e0 09      00:01:24.703  READ MULTIPLE
      c6 00 10 00 00 00 ef 09      00:01:24.702  SET MULTIPLE MODE
      91 00 3f 00 00 00 af 09      00:01:24.702  INITIALIZE DEVICE PARAMETERS [OBS-6]
      10 00 00 00 00 00 a0 09      00:01:24.700  RECALIBRATE [OBS-4]
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Abort offline test  Aborted by host               00%      5360         -
    # 2  Abort offline test  Aborted by host               00%      5360         -
    # 3  Short offline       Completed without error       00%      5359         -
    # 4  Abort offline test  Aborted by host               70%      5359         -
    # 5  Abort offline test  Aborted by host               30%      5359         -
    # 6  Abort offline test  Aborted by host               00%      5359         -
    # 7  Extended offline    Completed without error       00%      5359         -
    # 8  Short offline       Completed without error       00%      2693         -
    
    Device does not support Selective Self Tests/Logging
    
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
Thema:

festplatten error auswerten

Die Seite wird geladen...

festplatten error auswerten - Ähnliche Themen

  1. GRUB Geom Error - auch bei Festplattenschaden möglich?

    GRUB Geom Error - auch bei Festplattenschaden möglich?: Hallo Community! Habe in letzter Zeit häufiger Schwierigkeiten beim Booten, nach einigen Resets klappt es dann zumeist. Verwende WinXP und SuSE...
  2. Kurztipp: Clonezilla: Festplatten per Klick kopieren

    Kurztipp: Clonezilla: Festplatten per Klick kopieren: Auf der bisherigen Festplatte ist kein Platz mehr, und der Inhalt soll auf eine neue Platte umziehen. Bei dieser Aufgabe und bei der...
  3. Kurztipp: Festplattengeschwindigkeit mit hdparm vermessen

    Kurztipp: Festplattengeschwindigkeit mit hdparm vermessen: Die weniger bekannte Option »--offset« ermöglicht es, die Geschwindigkeit der Festplatte an verschiedenen Stellen zu bestimmen. Weiterlesen...
  4. Kernel: Festplattenfehler wirbelt Merge-Prozess durcheinander

    Kernel: Festplattenfehler wirbelt Merge-Prozess durcheinander: Ein Hardware-Fehler hat die noch zu erledigende Arbeit beim Merge von Funktionen des neuen Kernels in das Daten-Nirvana gerissen. Nun bittet der...
  5. Festplattenforensik

    Festplattenforensik: Hi zusammen, ich hab nen Fehler gemacht: Ich hab mit meiner Kickstartinstallation ein CentOS auf meinem neuen Storageserver installiert. Das...