copie puis récupération de données disque dur

Utiliser TestDisk pour réparer le système de fichier
Post Reply
Message
Author
Naziel
Posts: 5
Joined: 12 Feb 2019, 19:26

copie puis récupération de données disque dur

#1 Post by Naziel »

Bonjour,
J'ai un disque dur de 1 To qui n'est pas en bon état:

Code: Select all

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-96-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ01ABD...
Device Model:     TOSHIBA MQ01ABD100
Serial Number:    Y5OYTNFVT
LU WWN Device Id: 5 000039 6a2089c32
Firmware Version: AX003J
User Capacity:    1 000 204 886 016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Apr 17 09:51:38 2020 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: 		(  120) 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.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 232) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

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   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       1437
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       5506
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       10400
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       2157
 10 Spin_Retry_Count        0x0033   208   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1636
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       1764
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       26
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       11051
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       29 (Min/Max 9/54)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       202
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       1928
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   096   096   000    Old_age   Always       -       1983
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       184
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 604 (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 604 occurred at disk power-on lifetime: 2157 hours (89 days + 21 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 08 c8 37 3a 40  Error: UNC 8 sectors at LBA = 0x003a37c8 = 3815368

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 da 08 c8 37 3a 40 00      00:17:37.382  READ DMA EXT
  25 da 08 c8 37 3a 40 00      00:17:33.463  READ DMA EXT
  25 da 08 c0 37 3a 40 00      00:17:33.463  READ DMA EXT
  25 da 08 b8 37 3a 40 00      00:17:33.463  READ DMA EXT
  25 da 08 b0 37 3a 40 00      00:17:33.462  READ DMA EXT

Error 603 occurred at disk power-on lifetime: 2157 hours (89 days + 21 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 08 c8 37 3a 40  Error: UNC 8 sectors at LBA = 0x003a37c8 = 3815368

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 da 08 c8 37 3a 40 00      00:17:33.463  READ DMA EXT
  25 da 08 c0 37 3a 40 00      00:17:33.463  READ DMA EXT
  25 da 08 b8 37 3a 40 00      00:17:33.463  READ DMA EXT
  25 da 08 b0 37 3a 40 00      00:17:33.462  READ DMA EXT
  25 da 08 a8 37 3a 40 00      00:17:33.462  READ DMA EXT

Error 602 occurred at disk power-on lifetime: 2157 hours (89 days + 21 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 08 98 e7 39 40  Error: UNC 8 sectors at LBA = 0x0039e798 = 3794840

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 da 08 98 e7 39 40 00      00:17:29.538  READ DMA EXT
  25 da 08 98 e7 39 40 00      00:17:25.630  READ DMA EXT
  25 da 08 90 e7 39 40 00      00:17:25.630  READ DMA EXT
  25 da 08 88 e7 39 40 00      00:17:25.630  READ DMA EXT
  25 da 08 80 e7 39 40 00      00:17:25.630  READ DMA EXT

Error 601 occurred at disk power-on lifetime: 2157 hours (89 days + 21 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 08 98 e7 39 40  Error: UNC 8 sectors at LBA = 0x0039e798 = 3794840

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 da 08 98 e7 39 40 00      00:17:25.630  READ DMA EXT
  25 da 08 90 e7 39 40 00      00:17:25.630  READ DMA EXT
  25 da 08 88 e7 39 40 00      00:17:25.630  READ DMA EXT
  25 da 08 80 e7 39 40 00      00:17:25.630  READ DMA EXT
  25 da 08 78 e7 39 40 00      00:17:25.629  READ DMA EXT

Error 600 occurred at disk power-on lifetime: 2157 hours (89 days + 21 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 08 70 97 39 40  Error: UNC 8 sectors at LBA = 0x00399770 = 3774320

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 da 08 70 97 39 40 00      00:17:21.705  READ DMA EXT
  25 da 08 70 97 39 40 00      00:17:17.795  READ DMA EXT
  25 da 08 68 97 39 40 00      00:17:17.795  READ DMA EXT
  25 da 08 60 97 39 40 00      00:17:17.795  READ DMA EXT
  25 da 08 58 97 39 40 00      00:17:17.795  READ DMA EXT

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%       941         -
# 2  Short offline       Completed without error       00%       210         -

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.

J'aimerais récupérer les données dessus, pour cela j'ai branché un autre disque de 1 To:

Code: Select all

Disque /dev/sdb : 931,5 GiB, 1000170586112 octets, 1953458176 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : gpt
Identifiant de disque : 674F14BD-2979-4FA7-ACA6-D7624D39ED29

Périphérique Début        Fin   Secteurs Taille Type
/dev/sdb1     2048 1953456127 1953454080 931,5G Données de base Microsoft


Disque /dev/sdc : 931,5 GiB, 1000204886016 octets, 1953525168 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : gpt
Identifiant de disque : 5821A566-C4AC-4B9B-8990-EDF132D46699

Périphérique      Début        Fin   Secteurs Taille Type
/dev/sdc1          2048     206847     204800   100M Système EFI
/dev/sdc2        206848     239615      32768    16M Réservé Microsoft
/dev/sdc3        239616 1951731485 1951491870 930,6G Données de base Microsoft
/dev/sdc4    1951731712 1953523711    1792000   875M Environnement de récupération Windows
Manque de pot, le disque qui reçoit (/dev/sdb) a quelques secteurs de moins que le disque source.
Je n'ai pas pensé à passer -b 4096 , je ne m'en suis rendu compte trop tard.
J'ai lancé la copie avec ddrescue, j'ai copié environ 200 Gb, et comme le disque galérait pas mal, j'ai décidé de passer -i 500 Gb ce qui m'a permis de copier la deuxième moitié du disque sans problème, sauf à la fin où ddrescue m'annonce une erreur d'écriture sur le disque /dev/sdb (car il est un peu plus petit, après c'est pas grave vu que c'est visiblement une partition de récupération). Actuellement il reste 170 Gb à récupérer et ils sont regroupés au même endroit. Si besoin je peux donner le log de ddrescue.

Comment faire pour que le ddrescue n'essaie pas d'accéder à la fin du disque et comment faire pour que ddrescue récupère le plus gros des données?

Par ailleurs, j'ai regardé ce que donne testdisk sur la grosse partition, et il ne trouve qu'un dossier intel et recyble.bin . Est-ce parce qu'il manque 170 Gb? Selon testdisk la mft et la backup de la mft sont identiques.

Edit: finalement j'ai passé le paramètre -i 200GB -s 160GB et cela a permis de lancer ddrescue sur la partie que je veux, donc ça devrait être bon pour ddrescue


Merci d'avance,
Naziel

Sponsored links

Post Reply