#1 Le 05/03/2020, à 19:13
- Benamoul
Erreurs disque dur : Signification ? Grave ? Réparable?
Bonjour,
On m'a donné un disque dur HGST 5K1000-750.
Après l'avoir formaté pour créer une partition unique ext4, je décide de vérifier l'intégrité du DD avec gsmartcontrol.
4 erreurs "Interface CRC error, Command aborted" sont décelées :
Complete error log:
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 11 (device log contains only the most recent 4 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 11 [2] occurred at disk power-on lifetime: 11468 hours (477 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 81 00 00 01 f0 4e 3f 01 00 Error: ICRC, ABRT at LBA = 0x01f04e3f = 32525887
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 08 00 08 00 00 12 c7 9a b8 40 00 00:15:24.471 READ FPDMA QUEUED
60 00 a0 00 00 00 00 01 f0 4e 20 40 00 00:15:24.465 READ FPDMA QUEUED
60 00 40 00 00 00 00 01 2e f6 40 40 00 00:15:24.459 READ FPDMA QUEUED
60 00 40 00 00 00 00 01 2c 3f 40 40 00 00:15:24.449 READ FPDMA QUEUED
60 00 40 00 00 00 00 01 24 5e 00 40 00 00:15:24.444 READ FPDMA QUEUED
Error 10 [1] occurred at disk power-on lifetime: 11467 hours (477 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 b9 00 00 02 18 3c 0f 02 00 Error: ICRC, ABRT at LBA = 0x02183c0f = 35142671
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 d8 00 08 00 00 02 18 3b f0 40 00 02:35:28.163 READ FPDMA QUEUED
60 01 00 00 00 00 00 02 18 3a f0 40 00 02:35:28.163 READ FPDMA QUEUED
60 00 80 00 10 00 00 09 da 74 78 40 00 02:35:28.153 READ FPDMA QUEUED
60 00 30 00 18 00 00 04 47 ab 28 40 00 02:35:28.142 READ FPDMA QUEUED
60 01 00 00 08 00 00 04 47 aa 28 40 00 02:35:28.142 READ FPDMA QUEUED
Error 9 [0] occurred at disk power-on lifetime: 11427 hours (476 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 10 00 00 12 2d 8e 40 02 00 Error: ICRC, ABRT at LBA = 0x122d8e40 = 304975424
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 a0 00 10 00 00 00 86 d6 a0 40 00 00:01:46.765 READ FPDMA QUEUED
61 00 20 00 08 00 00 13 03 37 80 40 00 00:01:46.764 WRITE FPDMA QUEUED
60 00 20 00 38 00 00 00 50 71 c0 40 00 00:01:46.753 READ FPDMA QUEUED
61 00 48 00 30 00 00 1b 50 64 a0 40 00 00:01:46.753 WRITE FPDMA QUEUED
61 00 88 00 28 00 00 12 2d 8e 50 40 00 00:01:46.753 WRITE FPDMA QUEUED
Error 8 [3] occurred at disk power-on lifetime: 11407 hours (475 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 18 00 00 00 85 5a 48 00 00 Error: ICRC, ABRT at LBA = 0x00855a48 = 8739400
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 28 00 00 00 00 00 85 5a 38 40 00 00:02:18.698 WRITE FPDMA QUEUED
60 00 10 00 00 00 00 00 fa bb 70 40 00 00:02:18.693 READ FPDMA QUEUED
60 00 10 00 00 00 00 00 fa bb 70 40 00 00:02:18.692 READ FPDMA QUEUED
60 00 10 00 00 00 00 00 fa bb 70 40 00 00:02:18.691 READ FPDMA QUEUED
61 00 10 00 00 00 00 00 fa bb 70 40 00 00:02:18.690 WRITE FPDMA QUEUEDEst-ce grave ? Peut-on réparer ?
Merci d'avance à tous les membres de la communauté Ubuntu pour leurs réponses.
Hors ligne
#2 Le 06/03/2020, à 13:16
- geole
Re : Erreurs disque dur : Signification ? Grave ? Réparable?
Bonjour
Ce que tu fournis est totalement insuffisant pour connaître l'état actuel du disque.
On sait juste qu'il y a eu 11 erreurs enregistrées dans le disque. En soit c'est peu.
Que les dernières étaient des erreurs de transfert de données (ICRC). Souvent, il suffit de changer le câble de liaison. Voir de le brancher solidement.
Que la dernière enregistrée a eu lieu lorsque le disque avait 11468 heures de fonctionnement. C'était peut-être hier ou il y a un an.
Merci de donner le retour de cette commande en remplaçant la lettre X par ce qui convient
sudo smartctl -a /dev/sdXIl y a pas mal compteurs à examiner pour avoir une petite idée de l'état du disque.
Dernière modification par geole (Le 06/03/2020, à 13:18)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#3 Le 06/03/2020, à 19:04
- Benamoul
Re : Erreurs disque dur : Signification ? Grave ? Réparable?
Merci pour ton aide geole.
Voici le retour de la commande :
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.15.0-88-generic] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: HGST Travelstar 5K1000
Device Model: HGST HTS541075A9E680
Serial Number: JD1100190MU3NK
LU WWN Device Id: 5 000cca 766c90157
Firmware Version: JA2OA560
User Capacity: 750156374016 bytes [750 GB]
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 T13/1699-D revision 6
SATA Version is: SATA 2.6, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Fri Mar 6 19:02:57 2020 CET
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: ( 45) 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: ( 203) 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 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 192 192 033 Pre-fail Always - 1
4 Start_Stop_Count 0x0012 032 032 000 Old_age Always - 107705
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 070 070 000 Old_age Always - 13314
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 096 096 000 Old_age Always - 6852
191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 251
193 Load_Cycle_Count 0x0012 025 025 000 Old_age Always - 759670
194 Temperature_Celsius 0x0002 253 253 000 Old_age Always - 19 (Min/Max 10/47)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 11
223 Load_Retry_Count 0x000a 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 11 (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 11 occurred at disk power-on lifetime: 11468 hours (477 days + 20 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
-- -- -- -- -- -- --
84 51 81 3f 4e f0 01 Error: ICRC, ABRT at LBA = 0x01f04e3f = 32525887
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 08 b8 9a c7 40 00 00:15:24.471 READ FPDMA QUEUED
60 a0 00 20 4e f0 40 00 00:15:24.465 READ FPDMA QUEUED
60 40 00 40 f6 2e 40 00 00:15:24.459 READ FPDMA QUEUED
60 40 00 40 3f 2c 40 00 00:15:24.449 READ FPDMA QUEUED
60 40 00 00 5e 24 40 00 00:15:24.444 READ FPDMA QUEUED
Error 10 occurred at disk power-on lifetime: 11467 hours (477 days + 19 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
-- -- -- -- -- -- --
84 51 b9 0f 3c 18 02 Error: ICRC, ABRT at LBA = 0x02183c0f = 35142671
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 d8 08 f0 3b 18 40 00 02:35:28.163 READ FPDMA QUEUED
60 00 00 f0 3a 18 40 00 02:35:28.163 READ FPDMA QUEUED
60 80 10 78 74 da 40 00 02:35:28.153 READ FPDMA QUEUED
60 30 18 28 ab 47 40 00 02:35:28.142 READ FPDMA QUEUED
60 00 08 28 aa 47 40 00 02:35:28.142 READ FPDMA QUEUED
Error 9 occurred at disk power-on lifetime: 11427 hours (476 days + 3 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
-- -- -- -- -- -- --
84 51 10 40 8e 2d 02 Error: ICRC, ABRT at LBA = 0x022d8e40 = 36539968
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 a0 10 a0 d6 86 40 00 00:01:46.765 READ FPDMA QUEUED
61 20 08 80 37 03 40 00 00:01:46.764 WRITE FPDMA QUEUED
60 20 38 c0 71 50 40 00 00:01:46.753 READ FPDMA QUEUED
61 48 30 a0 64 50 40 00 00:01:46.753 WRITE FPDMA QUEUED
61 88 28 50 8e 2d 40 00 00:01:46.753 WRITE FPDMA QUEUED
Error 8 occurred at disk power-on lifetime: 11407 hours (475 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 18 48 5a 85 00 Error: ICRC, ABRT at LBA = 0x00855a48 = 8739400
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 28 00 38 5a 85 40 00 00:02:18.698 WRITE FPDMA QUEUED
60 10 00 70 bb fa 40 00 00:02:18.693 READ FPDMA QUEUED
60 10 00 70 bb fa 40 00 00:02:18.692 READ FPDMA QUEUED
60 10 00 70 bb fa 40 00 00:02:18.691 READ FPDMA QUEUED
61 10 00 70 bb fa 40 00 00:02:18.690 WRITE FPDMA QUEUED
Error 7 occurred at disk power-on lifetime: 11162 hours (465 days + 2 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
-- -- -- -- -- -- --
84 51 01 df 4b 09 0f Error: ICRC, ABRT at LBA = 0x0f094bdf = 252267487
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b8 c8 ac 0a 40 00 00:00:02.066 READ FPDMA QUEUED
60 08 b0 c0 fb f8 40 00 00:00:02.066 READ FPDMA QUEUED
60 08 a8 60 25 0c 40 00 00:00:02.066 READ FPDMA QUEUED
60 30 a0 90 be f8 40 00 00:00:02.066 READ FPDMA QUEUED
60 08 98 d8 4b 09 40 00 00:00:02.066 READ FPDMA QUEUED
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% 13314 -
# 2 Short offline Completed without error 00% 13313 -
# 3 Short offline Completed without error 00% 13313 -
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.Hors ligne
#4 Le 06/03/2020, à 19:16
- geole
Re : Erreurs disque dur : Signification ? Grave ? Réparable?
Benamoul a écrit :
Merci pour ton aide geole.
Voici le retour de la commande :=== START OF INFORMATION SECTION === Model Family: HGST Travelstar 5K1000 ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 062 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0 4 Start_Stop_Count 0x0012 032 032 000 Old_age Always - 107705 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 070 070 000 Old_age Always - 13314 191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 253 253 000 Old_age Always - 19 (Min/Max 10/47) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 Error 11 occurred at disk power-on lifetime: 11468 hours (477 days + 20 hours)
On voit donc qu'il y a quasiment 2000 heures que le dernier incident est survenu....
Tous les indicatifs sont au beau fixe. Sauf un seul dont tu hérites
4 Start_Stop_Count 0x0012 032 032 000 Old_age Always - 107705
Le moteur du disque s'arrête très souvent (Toutes les sept minutes) Mais cela dépend de l'utilisation faite par le précédant propriétaire et de ce que tu vas en faire. Au rythme passé, le moteur risque de lâcher théoriquement dans les 6265 heures 13314/(100-32)*32
Actuellement il est estimé à 30% de sa vie. En théorie, il a encore 31066 heures de vie 13314/(100-70)*70
Dernière modification par geole (Le 06/03/2020, à 19:31)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#5 Le 06/03/2020, à 19:50
- Benamoul
Re : Erreurs disque dur : Signification ? Grave ? Réparable?
Merci pour cette analyse. Il a donc encore de beaux jours devant lui ce DD (surtout qu'il sera utilisé en appoint pour l'instant).
Quelle utilisation pouvait provoquer cet arrêt moteur récurrent ? Peut-il engendrer des corruptions de données ou autres problèmes ?
Hors ligne