Sind die Daten noch zu retten?

Warum Debian und/oder eine seiner Spielarten? Was muss ich vorher wissen? Wo geht es nach der Installation weiter?
Antworten
Benutzeravatar
Patsche
Beiträge: 3261
Registriert: 21.06.2013 01:47:54
Lizenz eigener Beiträge: MIT Lizenz
Wohnort: /home/10001101001

Sind die Daten noch zu retten?

Beitrag von Patsche » 01.10.2016 21:35:50

Hi,

ich kann seit heute meine verschlüsselte Festplatte nicht mehr einhängen. Hier mal ein paar Infos:

Code: Alles auswählen

cryptsetup luksDump /dev/sda1
LUKS header information for /dev/sda1

Version:       	1
Cipher name:   	aes
Cipher mode:   	xts-plain64
Hash spec:     	sha512
Payload offset:	4096
MK bits:       	512
MK digest:     	46 02 b3 12 a6 19 5e d2 20 04 01 7b 84 87 55 68 0c c3 8c 1c 
MK salt:       	ed c0 ec f3 b8 de e7 52 17 25 c7 f7 bd cf 3d 1c 
               	64 b1 a6 e0 24 15 bd b9 17 53 82 56 e3 15 4c 23 
MK iterations: 	39500
UUID:          	09bc59f5-fe31-48f7-948c-c3fdf040fd6b

Key Slot 0: ENABLED
	Iterations:         	157634
	Salt:               	76 da de fe 20 4c 5c 37 7e 20 fd e6 0d 04 0a 76 
	                      	51 bb f1 4a 06 7f 26 87 2e 03 04 90 9f e3 01 80 
	Key material offset:	8
	AF stripes:            	4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED

Code: Alles auswählen

mount /dev/mapper/mnt /mnt
mount: wrong fs type, bad option, bad superblock on /dev/mapper/mnt,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

Code: Alles auswählen

dmesg | tail
[  339.474235] ata1.00: error: { UNC }
[  339.502573] ata1.00: configured for UDMA/133
[  339.502601] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  339.502608] sd 0:0:0:0: [sda] tag#5 Sense Key : Medium Error [current] [descriptor] 
[  339.502613] sd 0:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
[  339.502619] sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 74 44 18 00 00 00 08 00
[  339.502623] blk_update_request: I/O error, dev sda, sector 1950619648
[  339.502657] ata1: EH complete
[  339.502687] JBD2: IO error reading journal superblock
[  339.502698] EXT4-fs (dm-0): error loading journal

Code: Alles auswählen

Disk /dev/sda: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x948de944

Device     Boot Start        End    Sectors  Size Id Type
/dev/sda1        2048 3907028991 3907026944  1,8T 83 Linux
Welche Angaben braucht ihr noch?

Edit:
Hier habe ich noch mehr Infos:

Code: Alles auswählen

 dumpe2fs -h /dev/mapper/mnt
dumpe2fs 1.42.12 (29-Aug-2014)
Filesystem volume name:   Intenso
Last mounted on:          /media/marco/Intenso
Filesystem UUID:          49835323-adab-41f6-8707-64481b2ffd4c
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              122101760
Block count:              488377856
Reserved block count:     24418892
Free blocks:              27242085
Free inodes:              121785552
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      907
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Thu Jan  1 13:10:04 2015
Last mount time:          Tue Sep 20 22:02:32 2016
Last write time:          Tue Sep 20 23:01:07 2016
Mount count:              353
Maximum mount count:      -1
Last checked:             Thu Jan  1 13:10:04 2015
Check interval:           0 (<none>)
Lifetime writes:          3002 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      3007b323-5901-4275-aaa5-3d4f2347693a
Journal backup:           inode blocks
dumpe2fs: Der Versuch, einen Block vom Dateisystem zu lesen, endete in kurzem Lesen beim Lesen des Journal-Superblocks

DeletedUserReAsG

Re: Sind die Daten noch zu retten?

Beitrag von DeletedUserReAsG » 01.10.2016 21:56:47

Der Status des Laufwerks selbst, also die SMART-Sachen, wären noch von Interesse.

Benutzeravatar
smutbert
Moderator
Beiträge: 8331
Registriert: 24.07.2011 13:27:39
Wohnort: Graz

Re: Sind die Daten noch zu retten?

Beitrag von smutbert » 01.10.2016 22:06:31

ich würde aus dem Bauch heraus vorschalgen irgendwo mit Debiangddrescue ein Image des unverschlüsselte Blockdevices (/dev/mapper/mnt) anzulegen, vor allem damit die vielleicht/vermutlich beschädigte Hardware nicht beim 2. Rettungsversuch komplett versagt.

Dann kannst du ja ausprobieren inwieweit der Dateisystemtreiber mit dem Image (oder besser einer weiteren Kopie des Images) zurechtkommt und schlimmstenfalls auf so etwas wie photorec (aus Debiantestdisk) zurückgreifen, um zu retten, was zu retten ist.

Benutzeravatar
Patsche
Beiträge: 3261
Registriert: 21.06.2013 01:47:54
Lizenz eigener Beiträge: MIT Lizenz
Wohnort: /home/10001101001

Re: Sind die Daten noch zu retten?

Beitrag von Patsche » 01.10.2016 22:29:59

Ich glaube zwar nicht mehr dran, aber hier noch ein paar Angaben.

Code: Alles auswählen

smartctl -i /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.6.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST2000DM001-9YN164
Serial Number:    Z1F15GLB
LU WWN Device Id: 5 000c50 04e46936d
Firmware Version: CC4B
User Capacity:    2.000.398.934.016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Oct  1 22:19:20 2016 CEST

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Code: Alles auswählen

smartctl -H /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.6.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Code: Alles auswählen

smartctl -a /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.6.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST2000DM001-9YN164
Serial Number:    Z1F15GLB
LU WWN Device Id: 5 000c50 04e46936d
Firmware Version: CC4B
User Capacity:    2.000.398.934.016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Oct  1 22:21:26 2016 CEST

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en

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:      ( 241)	Self-test routine in progress...
					10% of test remaining.
Total time to complete Offline 
data collection: 		(  609) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 267) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x3085)	SCT Status supported.

SMART Attributes Data Structure revision number: 10
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   090   090   006    Pre-fail  Always       -       68157329
  3 Spin_Up_Time            0x0003   092   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   091   091   020    Old_age   Always       -       9691
  5 Reallocated_Sector_Ct   0x0033   053   053   036    Pre-fail  Always       -       62752
  7 Seek_Error_Rate         0x000f   072   060   030    Pre-fail  Always       -       18456468
  9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       8047
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1218
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       149
188 Command_Timeout         0x0032   100   015   000    Old_age   Always       -       15 15 1002
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       172
190 Airflow_Temperature_Cel 0x0022   051   046   045    Old_age   Always       -       49 (Min/Max 23/49)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       169
193 Load_Cycle_Count        0x0032   065   065   000    Old_age   Always       -       71219
194 Temperature_Celsius     0x0022   049   054   000    Old_age   Always       -       49 (0 15 0 0 0)
197 Current_Pending_Sector  0x0012   001   001   000    Old_age   Always       -       31024
198 Offline_Uncorrectable   0x0010   001   001   000    Old_age   Offline      -       31024
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       5935h+34m+01.462s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       41499364475109
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       5551924677154

SMART Error Log Version: 1
ATA Error Count: 147 (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 147 occurred at disk power-on lifetime: 8047 hours (335 days + 7 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
  -- -- -- -- -- -- --
  40 51 00 f8 1c 80 0d  Error: UNC at LBA = 0x0d801cf8 = 226499832

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 f8 1c 80 4d 00      05:38:00.130  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      05:38:00.130  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      05:38:00.130  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      05:38:00.130  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      05:38:00.129  SET FEATURES [Set transfer mode]

Error 146 occurred at disk power-on lifetime: 8047 hours (335 days + 7 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
  -- -- -- -- -- -- --
  40 51 00 f8 1c 80 0d  Error: UNC at LBA = 0x0d801cf8 = 226499832

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 f8 1c 80 4d 00      05:37:57.158  READ FPDMA QUEUED
  60 00 08 f0 1c 80 4d 00      05:37:56.233  READ FPDMA QUEUED
  60 00 08 e8 1c 80 4d 00      05:37:55.321  READ FPDMA QUEUED
  b0 da 00 00 4f c2 00 00      05:35:12.445  SMART RETURN STATUS
  b0 d0 01 00 4f c2 00 00      05:35:12.245  SMART READ DATA

Error 145 occurred at disk power-on lifetime: 8046 hours (335 days + 6 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
  -- -- -- -- -- -- --
  40 51 00 e0 1c 80 0d  Error: UNC at LBA = 0x0d801ce0 = 226499808

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 e0 1c 80 4d 00      05:26:33.135  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      05:26:33.135  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      05:26:33.135  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      05:26:33.134  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      05:26:33.134  SET FEATURES [Set transfer mode]

Error 144 occurred at disk power-on lifetime: 8046 hours (335 days + 6 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
  -- -- -- -- -- -- --
  40 51 00 e0 1c 80 0d  Error: UNC at LBA = 0x0d801ce0 = 226499808

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 e0 1c 80 4d 00      05:26:30.113  READ FPDMA QUEUED
  60 00 08 d8 1c 80 4d 00      05:26:29.069  READ FPDMA QUEUED
  61 00 08 b8 1c 80 4d 00      05:26:19.514  WRITE FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      05:26:06.430  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      05:26:06.430  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 143 occurred at disk power-on lifetime: 8046 hours (335 days + 6 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
  -- -- -- -- -- -- --
  40 51 00 d0 1c 80 0d  Error: UNC at LBA = 0x0d801cd0 = 226499792

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 d0 1c 80 4d 00      05:26:03.463  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      05:26:03.463  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      05:26:03.463  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      05:26:03.462  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      05:26:03.462  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Self-test routine in progress 10%      8047         -

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.
Beim Versuch das Filesystem zu reparieren gab es nur noch rödeln und klackgeräusche. Das wird wohl nichts mehr. Zum Glück habe ich von den wichtigen Sachen ein Backup.
Entschuldigt bitte diesen unnützen Beitrag. Habe aus mangelnder Erfahrung mit Festplattenanalysen gleich einen Beitrag aufgemacht um Hilfe zu erhalten.
Erst dann kamen die Ideen, was gemacht werden muss.
Selbst der Smartselftest hört bei 10% auf. Er geht dann nicht weiter, wenn ich es mit

Code: Alles auswählen

smartctl -l selftest /dev/sda
überprüfen möchte.

Edit:
Hier noch eine letzte Ausgabe:

Code: Alles auswählen

smartctl -l selftest /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.6.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-14, 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  Short offline       Aborted by host               10%      8047         -

root@Patsche:/home/marco# smartctl -A /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.6.0-0.bpo.1-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
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   090   090   006    Pre-fail  Always       -       68157329
  3 Spin_Up_Time            0x0003   092   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   091   091   020    Old_age   Always       -       9691
  5 Reallocated_Sector_Ct   0x0033   053   053   036    Pre-fail  Always       -       62752
  7 Seek_Error_Rate         0x000f   072   060   030    Pre-fail  Always       -       18456468
  9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       8047
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1218
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       149
188 Command_Timeout         0x0032   100   015   000    Old_age   Always       -       15 15 1002
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       172
190 Airflow_Temperature_Cel 0x0022   051   046   045    Old_age   Always       -       49 (Min/Max 23/50)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       169
193 Load_Cycle_Count        0x0032   065   065   000    Old_age   Always       -       71219
194 Temperature_Celsius     0x0022   049   054   000    Old_age   Always       -       49 (0 15 0 0 0)
197 Current_Pending_Sector  0x0012   001   001   000    Old_age   Always       -       31024
198 Offline_Uncorrectable   0x0010   001   001   000    Old_age   Offline      -       31024
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       5935h+44m+46.958s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       41499364475109
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       5551924677154

rendegast
Beiträge: 15041
Registriert: 27.02.2006 16:50:33
Lizenz eigener Beiträge: MIT Lizenz

Re: Sind die Daten noch zu retten?

Beitrag von rendegast » 02.10.2016 00:49:15

5 Reallocated_Sector_Ct 0x0033 053 053 036 Pre-fail Always - 62752

197 Current_Pending_Sector 0x0012 001 001 000 Old_age Always - 31024
198 Offline_Uncorrectable 0x0010 001 001 000 Old_age Offline - 31024
Platte kaputt.


2TB-Platte besorgen,
Rettungsimage Debiangddrescue

Code: Alles auswählen

# Erstdurchgang
ddrescue -r0 kaputt image logfile

# dann virtuos kombiniert
ddrescue -r1 [--direct] [--revers] kaputt image logfile
Die Anzahl der Fehlstellen wird dabei zurückgehen,
das heißt jedoch nicht, daß die Daten wirklich ausgelesen werden konnten.
Das Programm ersetzt gegebenenfalls durch NULL.
Sector Sizes: 512 bytes logical, 4096 bytes physical
Dem sollte wohl durch Angabe '--sector-size=' Rechnung getragen werden:

Code: Alles auswählen

# Erstdurchgang
ddrescue -b 4096 -r0 kaputt image logfile

# dann virtuos kombiniert
ddrescue -b 4096 -r1 [--direct] [--revers] kaputt image logfile
mfg rendegast
-----------------------
Viel Eifer, viel Irrtum; weniger Eifer, weniger Irrtum; kein Eifer, kein Irrtum.
(Lin Yutang "Moment in Peking")

Antworten