Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Disque dur HS

k3rl0u4rn

Bonjour,

j'ai un disque dur qui vient de lâcher sans préavis et je suis en train d'essayer d'en récupérer les quelques gigas qui n'étaient pas sauvegardés. Il s'agit dun disque Seagate Barracuda ST3000DM001 de 3To. Je l'ai utilisé depuis plusieurs années avec beaucoup de satisfaction mais il semble qu'il aie juste lâché du jour au lendemain. Il est toujours détecte dans le BIOS mais je reçois un avertissement SMART me recommandant de remplacer le disque. Lorsque je le branche sur le port hot SATA, je reçois les logs suivants:

[82736.372402] ata6: link is slow to respond, please be patient (ready=0)
[82740.212395] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[82740.213013] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[82740.213033] No Local Variables are initialized for Method [_GTF]
[82740.213035] No Arguments are initialized for method [_GTF]
[82740.213039] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[82740.213521] ata6.00: ATA-9: ST3000DM001-1CH166, CC27, max UDMA/133
[82740.213525] ata6.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[82740.214237] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[82740.214255] No Local Variables are initialized for Method [_GTF]
[82740.214258] No Arguments are initialized for method [_GTF]
[82740.214261] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[82740.214730] ata6.00: configured for UDMA/133
[82740.214891] scsi 5:0:0:0: Direct-Access     ATA      ST3000DM001-1CH1 CC27 PQ: 0 ANSI: 5
[82740.215241] sd 5:0:0:0: Attached scsi generic sg6 type 0
[82740.215702] sd 5:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[82740.215707] sd 5:0:0:0: [sdf] 4096-byte physical blocks
[82740.215789] sd 5:0:0:0: [sdf] Write Protect is off
[82740.215794] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
[82740.215955] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[82740.323939]  sdf: sdf1 sdf2
[82740.324685] sd 5:0:0:0: [sdf] Attached SCSI disk
[82761.236309] ata6: link is slow to respond, please be patient (ready=0)
[82765.916361] ata6: COMRESET failed (errno=-16)
[82771.268323] ata6: link is slow to respond, please be patient (ready=0)
[82775.956338] ata6: COMRESET failed (errno=-16)
[82781.312343] ata6: link is slow to respond, please be patient (ready=0)
[82810.556286] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[82810.561237] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[82810.561249] No Local Variables are initialized for Method [_GTF]
[82810.561250] No Arguments are initialized for method [_GTF]
[82810.561252] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[82810.562178] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[82810.562188] No Local Variables are initialized for Method [_GTF]
[82810.562189] No Arguments are initialized for method [_GTF]
[82810.562191] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[82810.562533] ata6.00: configured for UDMA/133
[82823.120277] ata6: link is slow to respond, please be patient (ready=0)
[82827.812282] ata6: COMRESET failed (errno=-16)
[82833.168260] ata6: link is slow to respond, please be patient (ready=0)
[82837.852246] ata6: COMRESET failed (errno=-16)
[82843.208271] ata6: link is slow to respond, please be patient (ready=0)
[82872.908237] ata6: COMRESET failed (errno=-16)
[82872.908248] ata6: limiting SATA link speed to 3.0 Gbps
[82877.964213] ata6: COMRESET failed (errno=-16)
[82877.964220] ata6: reset failed, giving up
[82877.964223] ata6.00: disabled
[82877.964296] sd 5:0:0:0: [sdf] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[82877.964303] sd 5:0:0:0: [sdf] tag#19 CDB: Read(16) 88 00 00 00 00 01 5d 50 9f f8 00 00 00 08 00 00
[82877.964308] blk_update_request: I/O error, dev sdf, sector 5860532216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[82877.964334] sd 5:0:0:0: [sdf] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[82877.964338] sd 5:0:0:0: [sdf] tag#20 CDB: Read(16) 88 00 00 00 00 00 00 00 08 08 00 00 00 08 00 00
[82877.964341] blk_update_request: I/O error, dev sdf, sector 2056 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[82877.964412] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[82877.964415] sd 5:0:0:0: [sdf] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[82877.964421] sd 5:0:0:0: [sdf] tag#1 CDB: Read(16) 88 00 00 00 00 01 5d 50 9f f8 00 00 00 08 00 00
[82877.964427] blk_update_request: I/O error, dev sdf, sector 5860532216 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[82877.964433] Buffer I/O error on dev sdf2, logical block 464130815, async page read
[82877.964452] sd 5:0:0:0: [sdf] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[82877.964456] sd 5:0:0:0: [sdf] tag#4 CDB: Read(16) 88 00 00 00 00 00 00 00 08 08 00 00 00 08 00 00
[82877.964460] blk_update_request: I/O error, dev sdf, sector 2056 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[82877.964464] Buffer I/O error on dev sdf1, logical block 1, async page read
[82877.967130] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[82877.967202] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[83411.143028] sd 5:0:0:0: [sdf] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[83411.143031] sd 5:0:0:0: [sdf] tag#6 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00

L'extrait suivant me dit que les deux partitions sont initialement détectées même si Linux abandonne la configuration du disque à la fin:

[82740.214730] ata6.00: configured for UDMA/133
[82740.214891] scsi 5:0:0:0: Direct-Access     ATA      ST3000DM001-1CH1 CC27 PQ: 0 ANSI: 5
[82740.215241] sd 5:0:0:0: Attached scsi generic sg6 type 0
[82740.215702] sd 5:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[82740.215707] sd 5:0:0:0: [sdf] 4096-byte physical blocks
[82740.215789] sd 5:0:0:0: [sdf] Write Protect is off
[82740.215794] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
[82740.215955] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[82740.323939]  sdf: sdf1 sdf2
[82740.324685] sd 5:0:0:0: [sdf] Attached SCSI disk

Après les erreurs de lecture sur sdf1 et sdf2, impossible de faire quoi que ce soit avec les deux partitions. Même si elles sont listées dans le /dev, fdisk ne list pas ces partitions lorsque je fais un fdisk -l

Auriez vous des recommandations pour pouvoir récupérer les données de ce disque à ce stade ? ou est ce mort mort ? 🙂

Merci d'avance!

geole

Bonjour
Dans un premier temps, il serait bon de regarder l'état physique du disque, ce n'est peut-être qu'un câble de connexion
Mais, ce ce n'est pas le cas , il faut acheter un autre disque d'au moins la même capacité et y dupliquer les données lisibles.

A la vitesse actuelle du disque,

[82843.208271] ata6: link is slow to respond, please be patient (ready=0)

Si c'est pour rechercher seulement quelques Go, je ne suis pas certain que le jeu en vaille le coup
https://doc.ubuntu-fr.org/smartmontools
1) Installation

sudo apt-get install --no-install-recommends smartmontools

Puis tu postes le retour de

sudo smartctl -s on -a /dev/sdf

pour interprétation

k3rl0u4rn

Bonjour et merci pour les conseils. Non en fait cela doit être un peu plus que quelques gigas, j'avais en gros la moitié du disque dur qui n'était pas sauvegardée... si je ne la récupère pas ce n'est pas un drame, mais c'est pratique de l'avoir à dispo 🙂

J'ai essayé d'inverser les cables avec les autres disques et périphériques SATA ces derniers jours mais ça n'a pas semblé aider.

Voici le retour de smartctl, il est plus bavard aujourd'hui qu'il ne l'a été ces derniers jours, mais tout cela ne m'aide pas vraiment 🙂 Est ce que ca nous dit quelque chose d'intéressant ?

Merci!

▶ sudo smartctl -s on -a /dev/sdf
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-51-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1CH166
Serial Number:    Z1F3L8C5
LU WWN Device Id: 5 000c50 0645f8424
Firmware Version: CC27
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Oct 20 19:05:19 2020 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
Read SMART Data failed: scsi error badly formed scsi parameters


=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

SMART Error Log Version: 1
ATA Error Count: 824 (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 824 occurred at disk power-on lifetime: 46614 hours (1942 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 08 ff ff ff ef 00      01:52:45.485  READ DMA EXT
  ef 10 02 00 00 00 a0 00      01:52:45.484  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      01:52:45.484  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      01:52:45.483  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      01:52:45.483  SET FEATURES [Set transfer mode]

Error 823 occurred at disk power-on lifetime: 46614 hours (1942 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 08 ff ff ff ef 00      01:52:40.819  READ DMA EXT
  25 00 08 ff ff ff ef 00      01:52:40.818  READ DMA EXT
  25 00 08 ff ff ff ef 00      01:52:40.762  READ DMA EXT
  25 00 08 ff ff ff ef 00      01:52:40.736  READ DMA EXT
  25 00 08 ff ff ff ef 00      01:52:40.735  READ DMA EXT

Error 822 occurred at disk power-on lifetime: 46614 hours (1942 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 00 ff ff ff ef 00      01:52:34.503  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:52:34.376  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:52:33.352  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:52:33.351  READ DMA EXT
  25 00 00 ff ff ff ef 00      01:52:33.350  READ DMA EXT

Error 821 occurred at disk power-on lifetime: 46609 hours (1942 days + 1 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 00 ff ff ff ef 00   1d+17:30:23.037  READ DMA EXT
  25 00 00 ff ff ff ef 00   1d+17:30:23.034  READ DMA EXT
  25 00 00 ff ff ff ef 00   1d+17:30:23.016  READ DMA EXT
  25 00 00 ff ff ff ef 00   1d+17:30:18.684  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+17:30:18.682  READ DMA EXT

Error 820 occurred at disk power-on lifetime: 46609 hours (1942 days + 1 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 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 00 08 ff ff ff ef 00   1d+17:29:25.785  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+17:29:22.831  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+17:29:22.768  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+17:29:22.768  READ DMA EXT
  25 00 08 ff ff ff ef 00   1d+17:29:22.767  READ DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

geole

Bonjour
J'ai regardé en détails tous les résultats de la recherche sur le message d'erreur https://www.google.fr/search?as_q=&as_epq=SMART+Status+command+failed%3A+scsi+error+badly+formed+scsi+parameters&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=&cr=&as_qdr=all&as_sitesearch=&as_occt=any&safe=images&as_filetype=&tbs=
Je n'ai pas trouvé de pistes ni d'explications

Je pense que le firmware a un problème.
En espérant qu'il a un mode dégradé.

sudo smartctl -s on -a -d sat /dev/sdf

On va regarder s'il sait encore un peu lire et à quelle vitesse.

sudo apt install gddrescue

https://doc.ubuntu-fr.org/ddrescue

sudo ddrescue   -f    -n   -N   --idirect  --input-position=4096M   --size=3072M  -b4096 /dev/sdf     /dev/null   Suivi

Par exemple

a@a:~$ sudo ddrescue             -f    -n   -N   --idirect  --input-position=4096M   --size=4096M  -b4096  /dev/sda     /dev/null   Suivi
GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
(sizes limited to domain 4096000000 B to 8192000000 B of 1000204886016 B)
rescued: 904000 kB, tried: 0 B, bad-sector: 0 B, bad areas: 0

Current status
     ipos:    8191 MB, non-trimmed:        0 B,  current rate:  93192 kB/s
     opos:    8191 MB, non-scraped:        0 B,  average rate:    102 MB/s
non-tried:        0 B,  bad-sector:        0 B,    error rate:       0 B/s
  rescued:    4096 MB,   bad areas:        0,        run time:         30s
pct rescued:  100.00%, read errors:        0,  remaining time:         n/a
                              time since last successful read:         n/a
Finished                                     
a@a:~$

k3rl0u4rn

Voici, j'ai essaye plusieurs fois. La premiere fois etait des que j'ai connecte le disque et donc il a un resultat un peu different des suivants qui ont ete lance apres que le kernel aie laisse tomber le disque.

Premier lancement:

▶ sudo ddrescue   -f    -n   -N   --idirect  --input-position=4096M   --size=3072M  -b4096 /dev/sdf     /dev/null   Suivi                                                                                                                     
GNU ddrescue 1.23
Press Ctrl-C to interrupt                                                                                              
     ipos:    7167 MB, non-trimmed:    3070 MB,  current rate:       0 B/s
     opos:    7167 MB, non-scraped:        0 B,  average rate:   21845 B/s
non-tried:        0 B,  bad-sector:        0 B,    error rate:   3070 MB/s
  rescued:    1507 kB,   bad areas:        0,        run time:      1m  8s
pct rescued:    0.04%, read errors:    46852,  remaining time:         n/a
                              time since last successful read:          0s
Finished

Second lancement:

▶ sudo ddrescue   -f    -n   -N   --idirect  --input-position=4096M   --size=3072M  -b4096 /dev/sdf     /dev/null   Suivi
GNU ddrescue 1.23
Press Ctrl-C to interrupt                                                                                                                                                                                                                     
Initial status (read from mapfile)
(sizes limited to domain 4096000000 B to 7168000000 B of 3000592982016 B)
rescued: 1507 kB, tried: 3070 MB, bad-sector: 0 B, bad areas: 0                                                
                                                           
Current status                     
     ipos:        0 B, non-trimmed:    3070 MB,  current rate:       0 B/s
     opos:        0 B, non-scraped:        0 B,  average rate:       0 B/s
non-tried:        0 B,  bad-sector:        0 B,    error rate:       0 B/s
  rescued:    1507 kB,   bad areas:        0,        run time:          0s
pct rescued:    0.04%, read errors:        0,  remaining time:         n/a
                              time since last successful read:         n/a
Finished

Troisieme lancement en retirant le fichier Suivi:

▶ sudo ddrescue   -f    -n   -N   --idirect  --input-position=4096M   --size=3072M  -b4096 /dev/sdf     /dev/null   Suivi
GNU ddrescue 1.23
Press Ctrl-C to interrupt                                                                                                                                                                                                                     
Initial status (read from mapfile)
(sizes limited to domain 4096000000 B to 7168000000 B of 3000592982016 B)
rescued: 1507 kB, tried: 3070 MB, bad-sector: 0 B, bad areas: 0                                                
                                                           
Current status                     
     ipos:        0 B, non-trimmed:    3070 MB,  current rate:       0 B/s
     opos:        0 B, non-scraped:        0 B,  average rate:       0 B/s
non-tried:        0 B,  bad-sector:        0 B,    error rate:       0 B/s
  rescued:    1507 kB,   bad areas:        0,        run time:          0s
pct rescued:    0.04%, read errors:        0,  remaining time:         n/a
                              time since last successful read:         n/a
Finished

Pensez vous que le remplacement de la carte controlleur pourrait suffir ? Ou est il possible de mettre a jour le firmware meme si le disque est dans cet etat ?

geole

Bonjour
Résultat très mauvais
Le premier passage a récupéré 1507 kB et en a laissé sur le coté 3070 MB soit un taux de récupération de 0.04% mais avec une bonne vitesse.

Le second passage, en consultant le fichier de suivi, a constaté que le travail avait déjà été fait et n'a rien fait
Idem pour le troisième passage car c'était toujours le même nom de fichier (suivi)
Je vais ajouter un autre paramètre.

sudo ddrescue   -f    -n   -N  -c1  --idirect  --input-position=8192M   --size=3072M  -b4096 /dev/sdf     /dev/null   Suivi4

Si le résultat est semblable et que tu tiennes à tes données, il faudra passer par un professionnel qui changera le firmware du disque.
https://forum.ubuntu-fr.org/viewtopic.php?id=447877 ou un autre de ton choix
RMY est joinable en messagerie privée si elle fonctionne

k3rl0u4rn

Ca ne semble pas briant en effet 🙂

▶ sudo ddrescue   -f    -n   -N  -c1  --idirect  --input-position=8192M   --size=3072M  -b4096 /dev/sdf     /dev/null   Suivi4
GNU ddrescue 1.23
Press Ctrl-C to interrupt
     ipos:   11263 MB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:   11263 MB, non-scraped:        0 B,  average rate:   14517 B/s
non-tried:        0 B,  bad-sector:    3069 MB,    error rate:    301 MB/s
  rescued:    2134 kB,   bad areas:        1,        run time:      2m 26s
pct rescued:    0.06%, read errors:   749479,  remaining time:         n/a
                              time since last successful read:          9s
Finished

Pourquoi penses tu que le firmware est en cause ? N'est ce pas quelque chose que je peux faire moi meme avec les utilitaires de Seagate ? Aussi j'imagine que le firmware est contenu dans le carte controleur du disque et celle ci est facile a remplacer, n'est ce pas aussi une option ?

Merci!

k3rl0u4rn

Petite update, je viens de mettre à jour le firmware du disque avec les utilitaires Seagate (CC27 -> CC29) et j'ai regagné accès aux données!! Sauvegarde en cours (et petite danse en attendant 🙂 ). Merci Geole pour le coup de main!

Une petite question me turlupine encore, comment est ce que le disque a pu partir en vrille du jour au lendemain et la mise à jour du firmware lui permet de repartir ? Est ce que le firmware peut s'endommager en usage normal du disque ?

Nuliel

Oui, un firmware peut s'endommager lui-même ou se bloquer lui-même. Car oui, un firmware n'est qu'un programme, et il peut aussi y avoir des bugs dedans.
Lorsque la mise à jour du firmware avec l'outil du constructeur ne fonctionne pas (typiquement le disque a disparu définitivement des radars), il est parfois possible de se connecter au port série pour l'aider à repartir (un exemple ici). Mais c'est bien plus compliqué que de faire juste une maj avec l'outil du constructeur.
A noter aussi que la maj du firmware n'est pas une opération sans risque (typiquement la coupure de courant en plein milieu de la maj et c'est la cata)

geole

Bonjour
Excellente initiative que je n'aurais pas pensé à proposer dans uin contexte de mauvais fonctionnement...
Pourras-tu refaire un rapport smartctl afin de connaître l'état des plateaux?

k3rl0u4rn

Merci pour les explications... Je viens d'essayer de refaire un diagnostique avec smartctl et rien n'y fait, le disque n'est plus détecté correctement... J'ai l'impression que j'ai été très chanceux sur ce coup. Je vais retenter demain et voir si il ré-apparaît

k3rl0u4rn

J'ai réessayé plusieurs fois depuis mon précédent post mais rien n'y fait, plus d'accès du tout au disque. Voici en substance ce que j'obtiens de dmesg:

[   40.144456] ata6: link is slow to respond, please be patient (ready=0)
[   43.915702] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   43.916146] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[   43.916155] No Local Variables are initialized for Method [_GTF]
[   43.916156] No Arguments are initialized for method [_GTF]
[   43.916158] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[   43.916547] ata6.00: ATA-9: ST3000DM001-1CH166, CC29, max UDMA/133
[   43.916549] ata6.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[   43.917114] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[   43.917121] No Local Variables are initialized for Method [_GTF]
[   43.917122] No Arguments are initialized for method [_GTF]
[   43.917124] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[   43.917475] ata6.00: configured for UDMA/133
[   43.917547] scsi 5:0:0:0: Direct-Access     ATA      ST3000DM001-1CH1 CC29 PQ: 0 ANSI: 5
[   43.917725] sd 5:0:0:0: Attached scsi generic sg6 type 0
[   43.917872] sd 5:0:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[   43.917874] sd 5:0:0:0: [sdf] 4096-byte physical blocks
[   43.917920] sd 5:0:0:0: [sdf] Write Protect is off
[   43.917922] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
[   43.917969] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   43.993160]  sdf: sdf1 sdf2
[   43.993662] sd 5:0:0:0: [sdf] Attached SCSI disk
[   64.744029] ata6: link is slow to respond, please be patient (ready=0)
[   69.426063] ata6: COMRESET failed (errno=-16)
[   74.777987] ata6: link is slow to respond, please be patient (ready=0)
[   79.457929] ata6: COMRESET failed (errno=-16)
[   84.809866] ata6: link is slow to respond, please be patient (ready=0)
[  114.517722] ata6: COMRESET failed (errno=-16)
[  114.517731] ata6: limiting SATA link speed to 3.0 Gbps
[  116.269724] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  116.281401] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[  116.281423] No Local Variables are initialized for Method [_GTF]
[  116.281426] No Arguments are initialized for method [_GTF]
[  116.281430] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[  116.282472] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[  116.282492] No Local Variables are initialized for Method [_GTF]
[  116.282495] No Arguments are initialized for method [_GTF]
[  116.282499] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[  116.282883] ata6.00: configured for UDMA/133
[  128.813681] ata6: link is slow to respond, please be patient (ready=0)
[  133.493666] ata6: COMRESET failed (errno=-16)
[  138.853664] ata6: link is slow to respond, please be patient (ready=0)
[  143.537677] ata6: COMRESET failed (errno=-16)
[  148.901683] ata6: link is slow to respond, please be patient (ready=0)
[  178.561654] ata6: COMRESET failed (errno=-16)
[  178.561664] ata6: limiting SATA link speed to 1.5 Gbps
[  183.617639] ata6: COMRESET failed (errno=-16)
[  183.617649] ata6: reset failed, giving up
[  183.617652] ata6.00: disabled
[  183.617716] sd 5:0:0:0: [sdf] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  183.617721] sd 5:0:0:0: [sdf] tag#14 CDB: Read(16) 88 00 00 00 00 00 80 00 08 08 00 00 00 08 00 00
[  183.617726] blk_update_request: I/O error, dev sdf, sector 2147485704 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  183.617746] sd 5:0:0:0: [sdf] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  183.617750] sd 5:0:0:0: [sdf] tag#20 CDB: Read(16) 88 00 00 00 00 00 00 00 08 00 00 00 00 08 00 00
[  183.617753] blk_update_request: I/O error, dev sdf, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  183.617865] sd 5:0:0:0: [sdf] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  183.617871] sd 5:0:0:0: [sdf] tag#2 CDB: Read(16) 88 00 00 00 00 00 80 00 08 08 00 00 00 08 00 00
[  183.617875] blk_update_request: I/O error, dev sdf, sector 2147485704 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  183.617882] Buffer I/O error on dev sdf2, logical block 1, async page read
[  183.617893] sd 5:0:0:0: [sdf] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  183.617896] sd 5:0:0:0: [sdf] tag#3 CDB: Read(16) 88 00 00 00 00 00 00 00 08 00 00 00 00 08 00 00
[  183.617900] blk_update_request: I/O error, dev sdf, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  183.617903] Buffer I/O error on dev sdf1, logical block 0, async page read

Je crois que j'ai eu beaucoup de chance d'avoir eu une fenêtre ouverte pour faire le transfert l'autre jour, et d'avoir pris le temps de le faire à ce moment là!!

Merci encore pour l'aide!