Disque Transcend StoreJet 25H3 mort?

Support Debian
#1

Synthèse des infos obtenues à la suite de la discussion précédente
( Disque cassé?)

1 lsblk -f et sudo blkid ne montrent pas ce disque USB
branché

sudo dmesg affiche , pendant que le disque tourne et couine de temps en temps (parfois toutes les 5 ou 10 sec, parfois silence plus de 30 sec)

$sudo dmesg | tail -50
[1633814.365827] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=150936 end=150937) time 3002 us, min 1073, max 1079, scanline start 991, end 68
[1634268.447827] EXT4-fs (sda2): mounted filesystem d0bfb7f4-5e22-4612-9158-053ddf3194c8 r/w with ordered data mode. Quota mode: none.
[1634268.675846] mate-drivemount[2164774]: segfault at 555f0d6709b6 ip 0000555a57a7d2dc sp 00007ffe38000210 error 4 in mate-drivemount-applet[72dc,555a57a7a000+4000] likely on CPU 14 (core 22, socket 0)
[1634268.675857] Code: 64 4c 8b 34 25 28 00 00 00 4c 89 74 24 68 49 89 fe e8 78 ff ff ff 4d 85 f6 0f 84 4f 02 00 00 48 89 c6 49 8b 06 48 85 c0 74 05 <48> 39 30 74 10 4c 89 f7 e8 17 d4 ff ff 85 c0 0f 84 2f 02 00 00 49
[1634421.309707] EXT4-fs (sda2): unmounting filesystem d0bfb7f4-5e22-4612-9158-053ddf3194c8.
[1637115.568676] usb 3-6: USB disconnect, device number 5
[1637115.568690] usb 3-6.4: USB disconnect, device number 6
[1637115.568696] usb 3-6.4.1: USB disconnect, device number 7
[1637115.594527] usb 2-1: USB disconnect, device number 4
[1637115.594530] usb 2-1.2: USB disconnect, device number 6
[1637115.632365] r8152 3-6.4.3:1.0 enp0s20f0u6u4u3: Stop submitting intr, status -71
[1637115.722071] r8152-cfgselector 3-6.4.3: USB disconnect, device number 8
[1637115.767091] usb 2-1.3: USB disconnect, device number 7
[1637115.877302] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[1637115.877322] sd 2:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[1637115.909464] usb 3-6.4.4: USB disconnect, device number 9
[1637428.913884] usb 3-2: new high-speed USB device number 38 using xhci_hcd
[1637429.053376] usb 3-2: New USB device found, idVendor=8564, idProduct=7000, bcdDevice=80.00
[1637429.053392] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[1637429.053398] usb 3-2: Product: StoreJet Transcend
[1637429.053403] usb 3-2: Manufacturer: StoreJet Transcend
[1637429.053407] usb 3-2: SerialNumber:      WD-WX71E191H3JX
[1637429.058761] scsi host0: uas
[1637429.060787] scsi 0:0:0:0: Direct-Access     StoreJet Transcend        0    PQ: 0 ANSI: 6
[1637429.064710] sd 0:0:0:0: Attached scsi generic sg0 type 0
[1637429.173219] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[1637429.173227] sd 0:0:0:0: [sda] 4096-byte physical blocks
[1637429.173548] sd 0:0:0:0: [sda] Write Protect is off
[1637429.173552] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[1637429.174111] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[1637429.174287] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[1637429.174289] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[1637435.734231] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1637435.734242] sd 0:0:0:0: [sda] tag#3 Sense Key : Illegal Request [current] 
[1637435.734247] sd 0:0:0:0: [sda] tag#3 Add. Sense: Invalid field in cdb
[1637435.734253] sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[1637435.734256] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1637435.734266] Buffer I/O error on dev sda, logical block 0, async page read
[1637435.863226]  sda: sda1
[1637435.863837] sd 0:0:0:0: [sda] Attached SCSI disk
[1637439.957754] sd 0:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=4s
[1637439.957771] sd 0:0:0:0: [sda] tag#24 Sense Key : Illegal Request [current] 
[1637439.957778] sd 0:0:0:0: [sda] tag#24 Add. Sense: Invalid field in cdb
[1637439.957786] sd 0:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 e8 e0 88 00 00 00 08 00
[1637439.957791] critical target error, dev sda, sector 3907028992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[1637445.089380] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=4s
[1637445.089399] sd 0:0:0:0: [sda] tag#25 Sense Key : Illegal Request [current] 
[1637445.089407] sd 0:0:0:0: [sda] tag#25 Add. Sense: Invalid field in cdb
[1637445.089414] sd 0:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 e8 e0 87 a8 00 00 08 00
[1637445.089419] critical target error, dev sda, sector 3907028904 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

Maintenant que /dev/sda est identifié:

$sudo fdisk -l /dev/sda
Disque /dev/sda : 1,82 TiB, 2000398934016 octets, 3907029168 secteurs
Modèle de disque : Transcend       
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 : dos
Identifiant de disque : 0xde783f9d

Périphérique Amorçage Début        Fin   Secteurs Taille Id Type
/dev/sda1                63 3907026943 3907026881   1,8T 83 Linux

La partition 1 ne commence pas sur une frontière de cylindre physique.

La commande sudo smartctl -x /dev/sda affiche:

$sudo smartctl -x /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.90+deb13-rt-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue Mobile (SMR)
Device Model:     WDC WD20SPZX-00UA7T0
Serial Number:    WD-WX71E191H3JX
LU WWN Device Id: 5 0014ee 2665fe4a8
Firmware Version: 01.01A01
User Capacity:    2 000 398 934 016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jun 20 14:03:17 2026 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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: 		(23040) seconds.
Offline data collection
capabilities: 			 (0x71) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 371) minutes.
Conveyance self-test routine
recommended polling time: 	 (   3) minutes.
SCT capabilities: 	       (0x3035)	SCT Status 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   243   215   021    -    808
  4 Start_Stop_Count        -O--CK   100   100   000    -    276
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   097   097   000    -    2755
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    112
192 Power-Off_Retract_Count -O--CK   200   200   000    -    74
193 Load_Cycle_Count        -O--CK   200   200   000    -    1059
194 Temperature_Celsius     -O---K   107   094   000    -    40
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   100   253   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x24       GPL     R/O    288  Current Device Internal Status Data log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      76  Device vendor specific log
0xb9       GPL,SL  VS       4  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
Device State:                        Active (0)
Current Temperature:                    40 Celsius
Power Cycle Min/Max Temperature:     40/40 Celsius
Lifetime    Min/Max Temperature:     17/53 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    128 (78)

Index    Estimated Time   Temperature Celsius
  79    2026-06-20 11:57    51  ********************************
 ...    ..( 47 skipped).    ..  ********************************
 127    2026-06-20 12:45    51  ********************************
   0    2026-06-20 12:46     ?  -
   1    2026-06-20 12:47    52  *********************************
   2    2026-06-20 12:48     ?  -
   3    2026-06-20 12:49    51  ********************************
   4    2026-06-20 12:50     ?  -
   5    2026-06-20 12:51    50  *******************************
   6    2026-06-20 12:52    49  ******************************
   7    2026-06-20 12:53    50  *******************************
   8    2026-06-20 12:54     ?  -
   9    2026-06-20 12:55    50  *******************************
  10    2026-06-20 12:56     ?  -
  11    2026-06-20 12:57    49  ******************************
  12    2026-06-20 12:58     ?  -
  13    2026-06-20 12:59    48  *****************************
 ...    ..(  9 skipped).    ..  *****************************
  23    2026-06-20 13:09    48  *****************************
  24    2026-06-20 13:10     ?  -
  25    2026-06-20 13:11    48  *****************************
  26    2026-06-20 13:12     ?  -
  27    2026-06-20 13:13    48  *****************************
  28    2026-06-20 13:14     ?  -
  29    2026-06-20 13:15    48  *****************************
  30    2026-06-20 13:16     ?  -
  31    2026-06-20 13:17    48  *****************************
  32    2026-06-20 13:18     ?  -
  33    2026-06-20 13:19    48  *****************************
  34    2026-06-20 13:20     ?  -
  35    2026-06-20 13:21    48  *****************************
  36    2026-06-20 13:22     ?  -
  37    2026-06-20 13:23    48  *****************************
  38    2026-06-20 13:24     ?  -
  39    2026-06-20 13:25    46  ***************************
  40    2026-06-20 13:26     ?  -
  41    2026-06-20 13:27    45  **************************
  42    2026-06-20 13:28     ?  -
  43    2026-06-20 13:29    44  *************************
  44    2026-06-20 13:30     ?  -
  45    2026-06-20 13:31    27  ********
  46    2026-06-20 13:32     ?  -
  47    2026-06-20 13:33    40  *********************
  48    2026-06-20 13:34     ?  -
  49    2026-06-20 13:35    40  *********************
  50    2026-06-20 13:36     ?  -
  51    2026-06-20 13:37    38  *******************
  52    2026-06-20 13:38     ?  -
  53    2026-06-20 13:39    36  *****************
  54    2026-06-20 13:40     ?  -
  55    2026-06-20 13:41    32  *************
  56    2026-06-20 13:42    32  *************
  57    2026-06-20 13:43     ?  -
  58    2026-06-20 13:44    35  ****************
  59    2026-06-20 13:45     ?  -
  60    2026-06-20 13:46    37  ******************
  61    2026-06-20 13:47     ?  -
  62    2026-06-20 13:48    32  *************
  63    2026-06-20 13:49     ?  -
  64    2026-06-20 13:50    35  ****************
  65    2026-06-20 13:51     ?  -
  66    2026-06-20 13:52    25  ******
  67    2026-06-20 13:53     ?  -
  68    2026-06-20 13:54    29  **********
  69    2026-06-20 13:55     ?  -
  70    2026-06-20 13:56    33  **************
  71    2026-06-20 13:57     ?  -
  72    2026-06-20 13:58    35  ****************
  73    2026-06-20 13:59     ?  -
  74    2026-06-20 14:00    36  *****************
  75    2026-06-20 14:01     ?  -
  76    2026-06-20 14:02    39  ********************
  77    2026-06-20 14:03     ?  -
  78    2026-06-20 14:04    40  *********************

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            1  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4            1  Vendor specific

Après ces explorations, la commande lsblk -f montre:

$lsblk -f
NAME           FSTYPE      FSVER    LABEL     UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                 
└─sda1                                                                                              
nvme1n1                                                                                             
├─nvme1n1p1    vfat        FAT32              5FC7-2F70                               323,6M     3% /boot/efi

[etc.]

$sudo blkid -i /dev/sda
/dev/sda: MINIMUM_IO_SIZE="4096" PHYSICAL_SECTOR_SIZE="4096" DISKSEQ="37" LOGICAL_SECTOR_SIZE="512"

Voila ce que je sais dire à l’heure actuelle à ce sujet.

Disque cassé?
Disque cassé?
#2

Bon il semble bien que le boitier USB est un StoreJet Transcend avec dedans un disque Western Digital ( WD-WX71E191H3JX).

Ce disque affiche 2T

Par ailleurs, les données smartctl sont excellentes alors qu’il y a une erreur sur une simple lecture de secteur. Plus ça va, plus je pense que c’est le controleur qui merdouille, ça expliquerait à peu près tout. Y’a-t-il moyen de changer de controleur disque?

Pour vérifier essaye

dd if=/dev/sda bs=512 skip=3907029152 count=16 | hexdump -C

plusieurs fois, change éventuellement le nombre après skip.

#3

Merci Fran.b

je suppose que boitier et contrôleur de disque signifie la même chose? si c’est le cas je vais me renseigner auprès d’un professionnel.

#4

Le boitier tel que je l’ai écrit veut dire effectivement controleur.

New USB device found, idVendor=8564, idProduct=7000, bcdDevice=80.00

correspond à un boitier, 3 cas

  1. Le disque est directement soudé sur une carte controleur sortie USB. Dans ce cas c’est mal barré. C’est le cas des disques WD externes vendus directement (du moins ce que j’ai)
  2. Le disque est un SATA plus un carte SATA → USB (assez fréquent), dans ce cas tu récupères tout.
  3. J’ai mal interprété les logs et je me vautre (mais je ne pense pas, ça me parait très cohérent). Le disque est naze.

Ce que je ferais:

  1. le test de lecture un peu partout pour voir
  2. Un essai d’ouverture du boitier (éventuellement montre une photo de l’engin, peut être quelqu’un connait) pour voir dans quel cas tu es.
#5

ça se fait comment?

#6

C’est la commande

dd if=/dev/sda bs=512 skip=3907029152 count=16 | hexdump -C

où tu changes le nombre skip par des nombres compris en 0 et 3907029152 (=nb secteurs moins 16)

En regardant si internet il semble que ton disque soit un SATA dans un boitier. Je pense que ça vaut le coup. Le smartctl est quand même bien.

Tu peux même te lancer dans un test interne puisque les commandes smartctl passent, essaye

smartctl -t short /dev/sda

(tout ça sous root ou bien en mettant sudo devant).

Mais vérifie que ton disque est branché. Si tu veux repartir sur des bases saines, commences par

  • Tu enlèves le disque
  • Tu fais lsblk
  • Tu remets le disque, tu attends 15-20s
  • Tu refais lsblk
    et tu vois où il est apparu
#7 
$dd if=/dev/sda bs=512 skip=390702915 count=16 | hexdump -C
dd: impossible d'ouvrir '/dev/sda': Aucun fichier ou dossier de ce nom
#8

cf Message ci dessus que j’ai fini après ta réponse.
Rq: Ça peut être l’electronique du disque mais j’y crois bcp moins

#10

après débranché puis rebranché, lsblk le retouve en /dev/sda, mais smartctl échoue:

$sudo smartctl -t short /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.90+deb13-rt-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Read SMART Data failed: scsi error unsupported field in scsi command
#11

Hum, ça c’est une erreur du controleur plutôt que du disque je crois. Que donne

sudo dmesg | tail -n 100

il devrait y avoir des FAILED plutôt que des ERROR

#12

(je peux raccourcir la fin si ça soulage le forum)

$sudo dmesg | tail -n 100
[1641200.149001] sd 0:0:0:0: [sda] tag#10 Sense Key : Illegal Request [current] 
[1641200.149005] sd 0:0:0:0: [sda] tag#10 Add. Sense: Invalid field in cdb
[1641200.149008] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 00 4d 00 00 01 00
[1641200.149009] critical target error, dev sda, sector 77 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641200.149013] Buffer I/O error on dev sda1, logical block 14, async page read
[1641200.149018] sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=4s
[1641200.149021] sd 0:0:0:0: [sda] tag#11 Sense Key : Illegal Request [current] 
[1641200.149024] sd 0:0:0:0: [sda] tag#11 Add. Sense: Invalid field in cdb
[1641200.149027] sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 00 00 00 4e 00 00 01 00
[1641200.149028] critical target error, dev sda, sector 78 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641200.149031] Buffer I/O error on dev sda1, logical block 15, async page read
[1641206.640317] sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641206.640330] sd 0:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current] 
[1641206.640336] sd 0:0:0:0: [sda] tag#8 Add. Sense: Invalid field in cdb
[1641206.640342] sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 00 00 00 3f 00 00 08 00
[1641206.640346] critical target error, dev sda, sector 63 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[1641237.221429] sd 0:0:0:0: [sda] tag#15 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD 
[1641237.221443] sd 0:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 00 00 00 46 00 00 01 00
[1641237.221457] sd 0:0:0:0: [sda] tag#14 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD 
[1641237.221461] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 00 00 00 45 00 00 01 00
[1641237.221468] sd 0:0:0:0: [sda] tag#13 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD 
[1641237.221472] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 00 00 00 44 00 00 01 00
[1641237.221479] sd 0:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD 
[1641237.221482] sd 0:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 00 00 00 43 00 00 01 00
[1641237.221488] sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD 
[1641237.221492] sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 00 00 00 42 00 00 01 00
[1641237.245494] scsi host0: uas_eh_device_reset_handler start
[1641237.365779] usb 3-2: reset high-speed USB device number 43 using xhci_hcd
[1641237.507468] scsi host0: uas_eh_device_reset_handler success
[1641249.498423] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=42s
[1641249.498447] sd 0:0:0:0: [sda] tag#3 Sense Key : Illegal Request [current] 
[1641249.498458] sd 0:0:0:0: [sda] tag#3 Add. Sense: Invalid field in cdb
[1641249.498470] sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 00 44 00 00 01 00
[1641249.498477] critical target error, dev sda, sector 68 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641249.498498] Buffer I/O error on dev sda1, logical block 5, async page read
[1641249.498535] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=42s
[1641249.498545] sd 0:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[1641249.498554] sd 0:0:0:0: [sda] tag#0 Add. Sense: Invalid field in cdb
[1641249.498561] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 00 43 00 00 01 00
[1641249.498566] critical target error, dev sda, sector 67 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641249.498577] Buffer I/O error on dev sda1, logical block 4, async page read
[1641249.498592] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=42s
[1641249.498599] sd 0:0:0:0: [sda] tag#4 Sense Key : Illegal Request [current] 
[1641249.498607] sd 0:0:0:0: [sda] tag#4 Add. Sense: Invalid field in cdb
[1641249.498614] sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 00 00 42 00 00 01 00
[1641249.498619] critical target error, dev sda, sector 66 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641249.498627] Buffer I/O error on dev sda1, logical block 3, async page read
[1641253.566337] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[1641253.566351] sd 0:0:0:0: [sda] tag#7 Sense Key : Illegal Request [current] 
[1641253.566357] sd 0:0:0:0: [sda] tag#7 Add. Sense: Invalid field in cdb
[1641253.566363] sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 00 00 00 47 00 00 08 00
[1641253.566367] critical target error, dev sda, sector 71 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[1641260.292341] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292354] sd 0:0:0:0: [sda] tag#4 Sense Key : Illegal Request [current] 
[1641260.292360] sd 0:0:0:0: [sda] tag#4 Add. Sense: Invalid field in cdb
[1641260.292366] sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 00 00 47 00 00 01 00
[1641260.292371] critical target error, dev sda, sector 71 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292384] Buffer I/O error on dev sda1, logical block 8, async page read
[1641260.292407] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292413] sd 0:0:0:0: [sda] tag#5 Sense Key : Illegal Request [current] 
[1641260.292417] sd 0:0:0:0: [sda] tag#5 Add. Sense: Invalid field in cdb
[1641260.292420] sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 00 00 48 00 00 01 00
[1641260.292423] critical target error, dev sda, sector 72 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292428] Buffer I/O error on dev sda1, logical block 9, async page read
[1641260.292436] sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292440] sd 0:0:0:0: [sda] tag#6 Sense Key : Illegal Request [current] 
[1641260.292444] sd 0:0:0:0: [sda] tag#6 Add. Sense: Invalid field in cdb
[1641260.292448] sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 00 00 00 49 00 00 01 00
[1641260.292450] critical target error, dev sda, sector 73 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292454] Buffer I/O error on dev sda1, logical block 10, async page read
[1641260.292461] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292465] sd 0:0:0:0: [sda] tag#7 Sense Key : Illegal Request [current] 
[1641260.292469] sd 0:0:0:0: [sda] tag#7 Add. Sense: Invalid field in cdb
[1641260.292472] sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 00 00 00 4a 00 00 01 00
[1641260.292474] critical target error, dev sda, sector 74 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292478] Buffer I/O error on dev sda1, logical block 11, async page read
[1641260.292488] sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292491] sd 0:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current] 
[1641260.292495] sd 0:0:0:0: [sda] tag#8 Add. Sense: Invalid field in cdb
[1641260.292498] sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 00 00 00 4b 00 00 01 00
[1641260.292500] critical target error, dev sda, sector 75 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292504] Buffer I/O error on dev sda1, logical block 12, async page read
[1641260.292511] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292514] sd 0:0:0:0: [sda] tag#9 Sense Key : Illegal Request [current] 
[1641260.292518] sd 0:0:0:0: [sda] tag#9 Add. Sense: Invalid field in cdb
[1641260.292521] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 00 00 4c 00 00 01 00
[1641260.292523] critical target error, dev sda, sector 76 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292527] Buffer I/O error on dev sda1, logical block 13, async page read
[1641260.292533] sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292537] sd 0:0:0:0: [sda] tag#10 Sense Key : Illegal Request [current] 
[1641260.292541] sd 0:0:0:0: [sda] tag#10 Add. Sense: Invalid field in cdb
[1641260.292544] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 00 4d 00 00 01 00
[1641260.292546] critical target error, dev sda, sector 77 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292550] Buffer I/O error on dev sda1, logical block 14, async page read
[1641260.292556] sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1641260.292559] sd 0:0:0:0: [sda] tag#11 Sense Key : Illegal Request [current] 
[1641260.292563] sd 0:0:0:0: [sda] tag#11 Add. Sense: Invalid field in cdb
[1641260.292567] sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 00 00 00 4e 00 00 01 00
[1641260.292569] critical target error, dev sda, sector 78 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1641260.292572] Buffer I/O error on dev sda1, logical block 15, async page read
#13

Il essaye de lire le système de fichier, n’y arrive pas. Pourtant rien dans ta sortie smartctl. Pour moi c’est le boitier.
Un boitier controleur vide ne coute pas cher. Je te suggère de le changer. Pour cela tu peux

  1. soit démonter ton disque et le mettre dans un nouveau boitier
  2. soit aller chez ton magasin préféré lui demander de faire l’opération. Si c’est impossible il te le dira (mais je ne crois pas), sinon il fait l’échange. Si ça ne marche pas après, tu peux acheter un disque SATA 2.5" qu’il met dans le boitier et tu auras un disque externe tout neuf (ça évite de perdre ton argent)
#14

Je viens de trouver un boitier vide, je vais essayer d’y monter ce disque.

Sinon je suivrais votre 2e conseil.

Encore un grand merci

#15

J’ai réussi à changer le contrôleur, mais les résultats de dmesg (et le clic) semblent identiques, en particulier les secteurs marqués error sont les mêmes que dans le boîtier précédent. (j’ignore si ce contrôleur est bon, j’ignore d’où il vient, (sans doute de mon fils qui bidouille bien loin d’ici depuis longtemps).
Est-il possible que 2 contrôleurs défaillants affichent ce même résultat?

$sudo dmesg | egrep sector
    [1643299.754858] critical target error, dev sda, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
    [1643314.400316] critical target error, dev sda, sector 3907028904 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
    [1643322.409942] critical target error, dev sda, sector 3907028768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
    [1643328.572426] critical target error, dev sda, sector 3907028768 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643335.320146] critical target error, dev sda, sector 63 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
    [1643342.988777] critical target error, dev sda, sector 66 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643342.988826] critical target error, dev sda, sector 67 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643342.988851] critical target error, dev sda, sector 68 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643342.988872] critical target error, dev sda, sector 69 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643342.988920] critical target error, dev sda, sector 70 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643362.084371] critical target error, dev sda, sector 63 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
    [1643369.421443] critical target error, dev sda, sector 63 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643369.421492] critical target error, dev sda, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643369.421519] critical target error, dev sda, sector 65 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643369.421545] critical target error, dev sda, sector 66 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643369.421568] critical target error, dev sda, sector 67 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643369.421590] critical target error, dev sda, sector 68 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643369.421612] critical target error, dev sda, sector 69 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643369.421633] critical target error, dev sda, sector 70 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643377.686473] critical target error, dev sda, sector 71 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
    [1643381.215694] critical target error, dev sda, sector 71 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643381.215752] critical target error, dev sda, sector 72 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643381.215782] critical target error, dev sda, sector 73 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643381.215809] critical target error, dev sda, sector 74 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643381.215867] critical target error, dev sda, sector 75 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643381.215894] critical target error, dev sda, sector 76 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643381.215920] critical target error, dev sda, sector 77 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    [1643381.215945] critical target error, dev sda, sector 78 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

lsblk -f affiche une partition:

lsblk -f
NAME           FSTYPE      FSVER    LABEL     UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                 
└─sda1                                                                                              
nvme1n1

et le test smartctl échoue:

$sudo smartctl -t short /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.90+deb13-rt-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported field in scsi command

If this is a USB connected device, look at the various --device=TYPE variants
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
#16

Hum, il doit y avoir autre chose que ces erreurs. Peux tu direce que donne avec le nouveau controleur:

  1. Tu débranches et rebranches le disque puis tu donne le résultat de
sudo dmesg | tail -n 40
  1. Le résultat de
smartctl -a /dev/sda

(le tout sous root ou via sudo)

#17 
$sudo dmesg | tail -n 40
[1643381.215918] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 00 4d 00 00 01 00
[1643381.215920] critical target error, dev sda, sector 77 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1643381.215924] Buffer I/O error on dev sda1, logical block 14, async page read
[1643381.215931] sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[1643381.215935] sd 0:0:0:0: [sda] tag#11 Sense Key : Illegal Request [current] 
[1643381.215939] sd 0:0:0:0: [sda] tag#11 Add. Sense: Invalid field in cdb
[1643381.215943] sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 00 00 00 4e 00 00 01 00
[1643381.215945] critical target error, dev sda, sector 78 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1643381.215949] Buffer I/O error on dev sda1, logical block 15, async page read
[1643486.481393] usb 3-2: stat urb: no pending cmd for uas-tag 44020
[1643547.363419] sd 0:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
[1643547.363433] sd 0:0:0:0: [sda] tag#20 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[1643547.391362] scsi host0: uas_eh_device_reset_handler start
[1643547.511482] usb 3-2: reset high-speed USB device number 44 using xhci_hcd
[1643547.653804] scsi host0: uas_eh_device_reset_handler success
[1644329.337645] usb 3-2: USB disconnect, device number 44
[1644329.396838] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[1644329.716597] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[1644339.472699] usb 3-2: new high-speed USB device number 45 using xhci_hcd
[1644339.612104] usb 3-2: New USB device found, idVendor=174c, idProduct=5106, bcdDevice=80.00
[1644339.612121] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[1644339.612127] usb 3-2: Product: StoreJet Transcend
[1644339.612131] usb 3-2: Manufacturer: StoreJet Transcend
[1644339.612135] usb 3-2: SerialNumber:      WD-WX71E191H3JX
[1644339.617113] scsi host0: uas
[1644339.618958] scsi 0:0:0:0: Direct-Access     StoreJet Transcend        0    PQ: 0 ANSI: 6
[1644339.622163] sd 0:0:0:0: Attached scsi generic sg0 type 0
[1644339.754206] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[1644339.754219] sd 0:0:0:0: [sda] 4096-byte physical blocks
[1644339.754884] sd 0:0:0:0: [sda] Write Protect is off
[1644339.754897] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[1644339.756067] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[1644339.756493] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[1644339.756503] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[1644346.676377] sd 0:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=6s
[1644346.676392] sd 0:0:0:0: [sda] tag#20 Sense Key : Illegal Request [current] 
[1644346.676399] sd 0:0:0:0: [sda] tag#20 Add. Sense: Invalid field in cdb
[1644346.676405] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[1644346.676409] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[1644346.676422] Buffer I/O error on dev sda, logical block 0, async page read


$sudo smartctl -a /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.90+deb13-rt-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue Mobile (SMR)
Device Model:     WDC WD20SPZX-00UA7T0
Serial Number:    WD-WX71E191H3JX
LU WWN Device Id: 5 0014ee 2665fe4a8
Firmware Version: 01.01A01
User Capacity:    2 000 398 934 016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jun 20 15:48:54 2026 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Thresholds failed: scsi error unsupported field in scsi command

=== 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: 		(23040) seconds.
Offline data collection
capabilities: 			 (0x71) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 371) minutes.
Conveyance self-test routine
recommended polling time: 	 (   3) minutes.
SCT capabilities: 	       (0x3035)	SCT Status 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     0x002f   200   200   ---    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   244   215   ---    Pre-fail  Always       -       783
  4 Start_Stop_Count        0x0032   100   100   ---    Old_age   Always       -       276
  5 Reallocated_Sector_Ct   0x0033   200   200   ---    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   ---    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   097   097   ---    Old_age   Always       -       2755
 10 Spin_Retry_Count        0x0032   100   100   ---    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   ---    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   ---    Old_age   Always       -       112
192 Power-Off_Retract_Count 0x0032   200   200   ---    Old_age   Always       -       74
193 Load_Cycle_Count        0x0032   200   200   ---    Old_age   Always       -       1059
194 Temperature_Celsius     0x0022   112   094   ---    Old_age   Always       -       35
196 Reallocated_Event_Count 0x0032   200   200   ---    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   ---    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   ---    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   ---    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   ---    Old_age   Offline      -       0

Read SMART Log Directory failed: scsi error unsupported field in scsi command

Read SMART Error Log failed: scsi error device will be ready soon

Read SMART Self-test Log failed: scsi error unsupported field in scsi command

Read SMART Selective Self-test Log failed: scsi error unsupported field in scsi command

The above only provides legacy SMART information - try 'smartctl -x' for more

Et avec smarctl -x:

$sudo smartctl -x /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.90+deb13-rt-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue Mobile (SMR)
Device Model:     WDC WD20SPZX-00UA7T0
Serial Number:    WD-WX71E191H3JX
LU WWN Device Id: 5 0014ee 2665fe4a8
Firmware Version: 01.01A01
User Capacity:    2 000 398 934 016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jun 20 15:50:56 2026 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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: 		(23040) seconds.
Offline data collection
capabilities: 			 (0x71) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 371) minutes.
Conveyance self-test routine
recommended polling time: 	 (   3) minutes.
SCT capabilities: 	       (0x3035)	SCT Status 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   245   215   021    -    750
  4 Start_Stop_Count        -O--CK   100   100   000    -    277
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   097   097   000    -    2755
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    113
192 Power-Off_Retract_Count -O--CK   200   200   000    -    75
193 Load_Cycle_Count        -O--CK   200   200   000    -    1060
194 Temperature_Celsius     -O---K   111   094   000    -    36
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   100   253   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x24       GPL     R/O    288  Current Device Internal Status Data log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      76  Device vendor specific log
0xb9       GPL,SL  VS       4  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
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.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
Device State:                        Active (0)
Current Temperature:                    36 Celsius
Power Cycle Min/Max Temperature:     36/36 Celsius
Lifetime    Min/Max Temperature:     17/53 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    128 (86)

Index    Estimated Time   Temperature Celsius
  87    2026-06-20 13:45    51  ********************************
 ...    ..( 39 skipped).    ..  ********************************
 127    2026-06-20 14:25    51  ********************************
   0    2026-06-20 14:26     ?  -
   1    2026-06-20 14:27    52  *********************************
   2    2026-06-20 14:28     ?  -
   3    2026-06-20 14:29    51  ********************************
   4    2026-06-20 14:30     ?  -
   5    2026-06-20 14:31    50  *******************************
   6    2026-06-20 14:32    49  ******************************
   7    2026-06-20 14:33    50  *******************************
   8    2026-06-20 14:34     ?  -
   9    2026-06-20 14:35    50  *******************************
  10    2026-06-20 14:36     ?  -
  11    2026-06-20 14:37    49  ******************************
  12    2026-06-20 14:38     ?  -
  13    2026-06-20 14:39    48  *****************************
 ...    ..(  9 skipped).    ..  *****************************
  23    2026-06-20 14:49    48  *****************************
  24    2026-06-20 14:50     ?  -
  25    2026-06-20 14:51    48  *****************************
  26    2026-06-20 14:52     ?  -
  27    2026-06-20 14:53    48  *****************************
  28    2026-06-20 14:54     ?  -
  29    2026-06-20 14:55    48  *****************************
  30    2026-06-20 14:56     ?  -
  31    2026-06-20 14:57    48  *****************************
  32    2026-06-20 14:58     ?  -
  33    2026-06-20 14:59    48  *****************************
  34    2026-06-20 15:00     ?  -
  35    2026-06-20 15:01    48  *****************************
  36    2026-06-20 15:02     ?  -
  37    2026-06-20 15:03    48  *****************************
  38    2026-06-20 15:04     ?  -
  39    2026-06-20 15:05    46  ***************************
  40    2026-06-20 15:06     ?  -
  41    2026-06-20 15:07    45  **************************
  42    2026-06-20 15:08     ?  -
  43    2026-06-20 15:09    44  *************************
  44    2026-06-20 15:10     ?  -
  45    2026-06-20 15:11    27  ********
  46    2026-06-20 15:12     ?  -
  47    2026-06-20 15:13    40  *********************
  48    2026-06-20 15:14     ?  -
  49    2026-06-20 15:15    40  *********************
  50    2026-06-20 15:16     ?  -
  51    2026-06-20 15:17    38  *******************
  52    2026-06-20 15:18     ?  -
  53    2026-06-20 15:19    36  *****************
  54    2026-06-20 15:20     ?  -
  55    2026-06-20 15:21    32  *************
  56    2026-06-20 15:22    32  *************
  57    2026-06-20 15:23     ?  -
  58    2026-06-20 15:24    35  ****************
  59    2026-06-20 15:25     ?  -
  60    2026-06-20 15:26    37  ******************
  61    2026-06-20 15:27     ?  -
  62    2026-06-20 15:28    32  *************
  63    2026-06-20 15:29     ?  -
  64    2026-06-20 15:30    35  ****************
  65    2026-06-20 15:31     ?  -
  66    2026-06-20 15:32    25  ******
  67    2026-06-20 15:33     ?  -
  68    2026-06-20 15:34    29  **********
  69    2026-06-20 15:35     ?  -
  70    2026-06-20 15:36    33  **************
  71    2026-06-20 15:37     ?  -
  72    2026-06-20 15:38    35  ****************
  73    2026-06-20 15:39     ?  -
  74    2026-06-20 15:40    36  *****************
  75    2026-06-20 15:41     ?  -
  76    2026-06-20 15:42    39  ********************
  77    2026-06-20 15:43     ?  -
  78    2026-06-20 15:44    40  *********************
  79    2026-06-20 15:45     ?  -
  80    2026-06-20 15:46    39  ********************
  81    2026-06-20 15:47     ?  -
  82    2026-06-20 15:48    35  ****************
  83    2026-06-20 15:49     ?  -
  84    2026-06-20 15:50    36  *****************
  85    2026-06-20 15:51     ?  -
  86    2026-06-20 15:52    36  *****************

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            1  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4            1  Vendor specific
#18

Bon, je ne vois toujours pas d’erreurs vraiment due au disque lui même en revanche ce sont les mêmes que celles précedentes. Donc le pbm se déplace sur l’électronique du disque lui même. Ce que je veux dire c’est que je pense que le support physique va sans doute bien mais que la carte electronique du disque semble poser souci. J’avais parié sur le controleur car c’est le plsu fréquent mais là, ça n’est clairement pas ça. Si tu as des données très importantes, elles sont récupérables modulo un budget conséquent auprès d’un spécialiste. Mais sinon, ça me parait quasi impossible de tout récupérer. Tu peux essayer avec ddrescue voir si il peut finir par lire les secteurs mais ça risque de durer des journées pour un piètre résultat :frowning:
Bref, à mon avis, c’est mort. Et pour moi (mais je peux faire fausse route depuis le début même si j’en doute), c’est l’electronique du disque lui même qui est foutue

PS: Tu peux essayer de le brancher à u port SATA direct mais je suis très pessimiste à ce stade

Disque cassé?
#19

Je ne saurais pas faire ça sur un portable. Merci pour vos efforts et votre aide.(je garde donc le contrôleur qui peut être OK).
Pour ne pas répéter ma bévue précédente, j’attends un peu avant de marquer «Résolu» au cas où …