Festplatte defekt? Diskwarrior machtlos

Dieses Thema im Forum "Mac OS X" wurde erstellt von sevY, 17.07.2005.

  1. sevY

    sevY Thread Starter Gast

    Hi,

    ich habe mich vor einiger Zeit schon mal gemeldet wegen einer defekten 120GB Platte aus der Firma, welche wichtige Daten enthält.
    Damals wollten wir diese mit „Boardmitteln“ wie fsck und dump/restore wieder hinbiegen… ging aber nicht.
    Daher sind folgende Tools eingekauft worden:

    1.) Diskwarrior
    2.) Data Rescue X


    Diskwarrior… tja… Diskwarrior sagte direkt „Kein Mac Format“… konnte also mit der Platte nichts anfangen… das Disk Utitlity (Festplattendienstprogramm) konnte die Festplatte allerdings am IDE Controller sehen, jedoch nicht mounten. Ein Versuch ein dmg davon zu erstellen schlug bei jeweils 4GB Größe des Images fehl… gibt es hier eine Grenze?

    Manuelles mounten über das Terminal mit mount funktionieren auch nicht.


    Smartmontools (via Darwinports installiert) sagen folgendes:

    Code:
    === START OF INFORMATION SECTION ===
    Device Model:     Maxtor 6Y200P0
    Serial Number:    Y618ZBBE
    Firmware Version: YAR41BW0
    User Capacity:    203,928,109,056 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:    Sat Jul 16 23:29:12 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:  (0x82)	Offline data collection activity
    					was completed without error.
    					Auto Offline Data Collection: Enabled.
    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: 		 ( 363) seconds.
    Offline data collection
    capabilities: 			 (0x5b) 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.
    					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: 	 (   2) minutes.
    Extended self-test routine
    recommended polling time: 	 (  82) minutes.
    
    SMART Error Log Version: 1
    Warning: ATA error count 1752 inconsistent with error log pointer 5
    
    ATA Error Count: 1752 (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 1752 occurred at disk power-on lifetime: 653 hours (27 days + 5 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
      -- -- -- -- -- -- --
      84 51 00 fd d4 34 fe  Error: ICRC, ABRT at LBA = 0x0e34d4fd = 238343421
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 fd d4 34 fe 00      01:07:32.896  READ DMA
      c8 00 01 fc d4 34 fe 00      01:07:32.896  READ DMA
      c8 00 08 f4 d4 34 fe 00      01:07:32.896  READ DMA
      c8 00 01 f3 d4 34 fe 00      01:07:32.896  READ DMA
      c8 00 08 eb d4 34 fe 00      01:07:32.896  READ DMA
    
    Error 1751 occurred at disk power-on lifetime: 649 hours (27 days + 1 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
      -- -- -- -- -- -- --
      84 51 00 f0 d6 0a ff  Error: ICRC, ABRT at LBA = 0x0f0ad6f0 = 252368624
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 09 f0 d6 0a ff 00      02:45:53.904  READ DMA
      c8 00 05 eb d6 0a ff 00      02:45:53.904  READ DMA
      c8 00 01 ea d6 0a ff 00      02:45:53.904  READ DMA
      c8 00 08 e2 d6 0a ff 00      02:45:53.904  READ DMA
      c8 00 01 e1 d6 0a ff 00      02:45:53.904  READ DMA
    
    Error 1750 occurred at disk power-on lifetime: 646 hours (26 days + 22 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
      -- -- -- -- -- -- --
      84 51 00 50 f2 47 f1  Error: ICRC, ABRT at LBA = 0x0147f250 = 21492304
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 09 50 f2 47 f1 00      00:13:30.016  READ DMA
      c8 00 05 4b f2 47 f1 00      00:13:30.016  READ DMA
      c8 00 01 4a f2 47 f1 00      00:13:30.016  READ DMA
      c8 00 08 42 f2 47 f1 00      00:13:30.016  READ DMA
      c8 00 01 41 f2 47 f1 00      00:13:30.016  READ DMA
    
    Error 1749 occurred at disk power-on lifetime: 646 hours (26 days + 22 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
      -- -- -- -- -- -- --
      84 51 00 c0 79 47 f1  Error: ICRC, ABRT at LBA = 0x014779c0 = 21461440
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 09 c0 79 47 f1 00      00:13:21.648  READ DMA
      c8 00 05 bb 79 47 f1 00      00:13:21.648  READ DMA
      c8 00 01 ba 79 47 f1 00      00:13:21.648  READ DMA
      c8 00 08 b2 79 47 f1 00      00:13:21.648  READ DMA
      c8 00 01 b1 79 47 f1 00      00:13:21.632  READ DMA
    
    Error 1748 occurred at disk power-on lifetime: 646 hours (26 days + 22 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
      -- -- -- -- -- -- --
      84 51 00 d8 6a 47 f1  Error: ICRC, ABRT at LBA = 0x01476ad8 = 21457624
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 09 d8 6a 47 f1 00      00:13:20.560  READ DMA
      c8 00 05 d3 6a 47 f1 00      00:13:20.560  READ DMA
      c8 00 01 d2 6a 47 f1 00      00:13:20.544  READ DMA
      c8 00 08 ca 6a 47 f1 00      00:13:20.544  READ DMA
      c8 00 01 c9 6a 47 f1 00      00:13:20.544  READ DMA
    
    SMART Self-test log structure revision number 1
    No self-tests have been logged.  [To run self-tests, use: smartctl -t]
    
    
    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.
    
    
    
    
    smartctl version 5.33 [powerpc-apple-darwin8.2.0] Copyright (C) 2002-4 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    
    === 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%       811         -
    



    fsck_hfs sagt:

    Code:
    ** /dev/rdisk1s9
    	Block 2 is not an MDB or Volume Header 
    	Block 268433909 is not an MDB or Volume Header 
    	CheckForClean - unknown volume type 
    	IVChk - unknown volume type 
    ** Volume check failed.
    volume check failed with error 6 
    	unknown volume type 
    	primary MDB is at block 0 0x00 
    	alternate MDB is at block 0 0x00 
    	primary VHB is at block 0 0x00 
    	alternate VHB is at block 0 0x00 
    	sector size = 512 0x200 
    	VolumeObject flags = 0x01 
    	total sectors for volume = 268433911 0xffff9f7 
    	total sectors for embedded volume = 0 0x00 
    
     
  2. sevY

    sevY Thread Starter Gast

    Dann… die letze Chance:

    Data Rescue X:

    Hier wurden zumindest alle Files gefunden und konnte restored werden! Aber leider ohne Verzeichnisstruktur und ohne korrekten Namen… nur anhand einer inkrementellen Nummer benannt… das Backup ist hier also fast schon unbrauchbar, da bei 120GB Daten in diesem durcheinander keiner mehr weiss, was genau was ist.

    Allerdings… Data Rescue X versucht anhand von 100 Dateien eine „automatische Kalibrierung“… diese ist fehlgeschlagen, es gibt jedoch auch die Möglichkeit manuell zu kalibrieren… hat jemand eine Erfahrung damit?

    Die Festplatte ist unter Panther mit HFS+ (Journaled) als Datenplatte installiert worden.

    //Edit:

    Es stehen eine Maxtor 300GB Firewire Platte, sowie 3 Mac's als „Reparaturplattforum“ zur Verfügung
     
  3. sevY

    sevY Thread Starter Gast

    Weitere Infos von Data Rescue X:

    Code:
    Data Rescue 10.4.3 - © 2001-2004, Prosoft Engineering, Inc.
    Found HFS+ Volume Header at physical sector #262210, volume size 79926165504
    Volume: Mac OS X, HFS+, Block Size = 8, Total Blocks = 19513224, Catalog nodeSize = 0
    From Volume Header, Total Files = 129655, Total Folders = 22801
    Volume is larger than reported drive size, volume name is 'Ohne Titel'
    volume size = 194480 MB, 398295534 blocks, drivesize = 131071 MB, 268435455 blocks
    FillVolumeMenu: [no errors]
    Found HFS+ Volume Header at physical sector #262210, volume size 79926165504
    Volume: Mac OS X, HFS+, Block Size = 8, Total Blocks = 19513224, Catalog nodeSize = 0
    From Volume Header, Total Files = 129655, Total Folders = 22801
    Volume is larger than reported drive size, volume name is 'Ohne Titel'
    volume size = 194480 MB, 398295534 blocks, drivesize = 131071 MB, 268435455 blocks
    FillVolumeMenu: [no errors]
    Found HFS+ Volume Header at physical sector #262210, volume size 79926165504
    Volume: Mac OS X, HFS+, Block Size = 8, Total Blocks = 19513224, Catalog nodeSize = 0
    From Volume Header, Total Files = 129655, Total Folders = 22801
    Volume is larger than reported drive size, volume name is 'Ohne Titel'
    volume size = 194480 MB, 398295534 blocks, drivesize = 131071 MB, 268435455 blocks
    FillVolumeMenu: [no errors]
    Scanning /dev/disk1: Maxtor 6Y200P0 Media (131071 MB).
    Standard volume, Thorough scan.
    Possible partition offset=15292278 ($E95776)
    Possible partition offset=15292279 ($E95777)
    Extent: file 5 ($0005), DATA
     start allocation block: 6 ($06), count: 65259 ($FEEB)
    New group starting at block #15292303
    Possible partition offset=15294486 ($E96016)
    Possible partition offset=15294487 ($E96017)
    Extent: file 5 ($0005), DATA
     start allocation block: 6 ($06), count: 65259 ($FEEB)
    New group starting at block #15294511
    Possible partition offset=32816062 ($1F4BBBE)
    Possible partition offset=32816063 ($1F4BBBF)
    Extent: file 5 ($0005), DATA
     start allocation block: 6 ($06), count: 65259 ($FEEB)
    New group starting at block #32816087
    Possible partition offset=32818270 ($1F4C45E)
    Possible partition offset=32818271 ($1F4C45F)
    Extent: file 5 ($0005), DATA
     start allocation block: 6 ($06), count: 65259 ($FEEB)
    New group starting at block #32818295
    Possible partition offset=108688591 ($67A74CF)
    Possible partition offset=163685484 ($9C1A46C)
    Possible partition offset=242867608 ($E79DD98)
    Possible partition offset=242900344 ($E7A5D78)
    24 files found.
    1 folders found.
    Total: 25 items.
    Initial phase read 25 keys
    JPEG Fil error: No FF where expected
    
    JPEG Fil error: No FF where expected
    
    JPEG Fil error: No FF where expected
    
    JPEG Fil error: No FF where expected
    
    JPEG Fil error: No FF where expected
    
    Purged 18 true duplicate nodes
    Renumbered 0 duplicate node IDs
    Found 0 orphans
    0 duplicate names hidden
    0 empty directories hidden
    
    About the allocation blocks layout:
    The allocation blocks layout cannot be estimated because partitioning is ignored.
    Found 1694 unique calibration items
    
    Calibrating allocation blocks layout.
    Equation #1: ab=73607336 lb=4249016
    Equation #2: ab=78595955 lb=7542368
    Equation #3: ab=72133424 lb=16641784
    Equation #1: ab=254245528 lb=39944224
    Equation #1: ab=254245528 lb=72061088
    Equation #2: ab=190267408 lb=84252600
    Equation #3: ab=73607048 lb=103940872
    Equation #3: ab=73607336 lb=169189016
    Equation #4: ab=78385152 lb=180608224
    Equation #4: ab=48181760 lb=230948296
    Equation #5: ab=268245352 lb=262466200
    Equation #6: ab=54636992 lb=268238024
    5 files found for calibration.
    Sorry, no match.
    ScanDisk: [no errors]
    
     
  4. sevY

    sevY Thread Starter Gast

    *Bump*
     
Die Seite wird geladen...
Ähnliche Themen - Festplatte defekt Diskwarrior
  1. SpecialFighter

    festplatte defekt?

    SpecialFighter, 19.02.2016, im Forum: Mac OS X
    Antworten:
    4
    Aufrufe:
    232
  2. blue vision
    Antworten:
    9
    Aufrufe:
    267
    rembremerdinger
    12.02.2016
  3. Winter Sorbeck
    Antworten:
    6
    Aufrufe:
    416
    WeDoTheRest
    07.08.2015
  4. MacKangaroo
    Antworten:
    33
    Aufrufe:
    1.817
    MacKangaroo
    05.10.2014
  5. pacdan
    Antworten:
    8
    Aufrufe:
    1.747
    pacdan
    20.08.2014