Wow, bon alors après avoir lancé le test long, j'ai regardé les erreurs et j'avais déjà un "read failure"..
J'ai aussi vu la commande "smartctl -l error", qui me retourne un paquet d'erreurs: === START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 220 (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 220 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 5f 1b 00 e0 Error: UNC at LBA = 0x00001b5f = 7007
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 5f 1b 00 e0 08 00:20:14.170 READ DMA
ec 00 00 00 00 00 a0 08 00:20:14.160 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 00:20:14.160 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 08 00:20:13.190 IDENTIFY DEVICE
220 erreurs..arg
Je comprends pas vraiment les erreurs là, mais est-ce qu'il y a moyen d'être sûr que ce soit le disque dur le fautif où ça pourrait venir du contrôleur SATA/de la carte mère ?
[^] # Re: disque qui rend l'âme
Posté par Sphax . En réponse au message Disque dur non reconnu après un benchmark Bonnie++. Évalué à 2.
J'ai aussi vu la commande "smartctl -l error", qui me retourne un paquet d'erreurs:
=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 220 (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 220 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 5f 1b 00 e0 Error: UNC at LBA = 0x00001b5f = 7007
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 5f 1b 00 e0 08 00:20:14.170 READ DMA
ec 00 00 00 00 00 a0 08 00:20:14.160 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 00:20:14.160 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 08 00:20:13.190 IDENTIFY DEVICE
220 erreurs..arg
Je comprends pas vraiment les erreurs là, mais est-ce qu'il y a moyen d'être sûr que ce soit le disque dur le fautif où ça pourrait venir du contrôleur SATA/de la carte mère ?