#1 Le 18/04/2014, à 13:55
- foxylechou
[Résolu (tristement)]Disque dur, voici mon SMART log
Bonjour bonjour,
apres un certain nombre de lectures de posts sur le sujet, je vous livre directement le resultat de GSmartControl. Je suis sur liveusb, je ne peux plus demarrer sur le HDD apres mes installations.
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-51-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA MK6475GSX
Serial Number: 919UD1UHB
LU WWN Device Id: 5 000039 38b4048af
Firmware Version: GT001M
User Capacity: 640 135 028 736 bytes [640 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Apr 18 11:50:24 2014 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 197) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 2040
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2083
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 632
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 3000
10 Spin_Retry_Count 0x0033 141 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2069
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 117
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 40
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 34188
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 42 (Min/Max 12/48)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 23
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 344
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 50
222 Loaded_Hours 0x0032 095 095 000 Old_age Always - 2278
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 319
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 1203 (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 1203 occurred at disk power-on lifetime: 2999 hours (124 days + 23 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 41 02 e0 9e 86 60 Error: UNC at LBA = 0x00869ee0 = 8822496
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 00 e0 9e 86 40 00 01:57:06.835 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 01:57:06.835 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 01:57:06.835 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 01:57:06.834 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:57:06.834 SET FEATURES [Set transfer mode]
Error 1202 occurred at disk power-on lifetime: 2999 hours (124 days + 23 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 41 02 e0 9e 86 60 Error: UNC at LBA = 0x00869ee0 = 8822496
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 00 e0 9e 86 40 00 01:57:02.568 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 01:57:02.568 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 01:57:02.568 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 01:57:02.568 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:57:02.568 SET FEATURES [Set transfer mode]
Error 1201 occurred at disk power-on lifetime: 2999 hours (124 days + 23 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 41 02 e0 9e 86 60 Error: UNC at LBA = 0x00869ee0 = 8822496
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 00 e0 9e 86 40 00 01:56:58.291 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 01:56:58.291 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 01:56:58.290 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 01:56:58.290 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:56:58.290 SET FEATURES [Set transfer mode]
Error 1200 occurred at disk power-on lifetime: 2999 hours (124 days + 23 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 41 02 e0 9e 86 60 Error: UNC at LBA = 0x00869ee0 = 8822496
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 00 e0 9e 86 40 00 01:56:54.024 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 01:56:54.024 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 01:56:54.024 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 01:56:54.023 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:56:54.023 SET FEATURES [Set transfer mode]
Error 1199 occurred at disk power-on lifetime: 2999 hours (124 days + 23 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 41 02 e0 9e 86 60 Error: UNC at LBA = 0x00869ee0 = 8822496
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 00 e0 9e 86 40 00 01:56:49.679 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 01:56:49.679 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 01:56:49.679 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 01:56:49.679 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 01:56:49.679 SET FEATURES [Set transfer mode]
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% 3000 -
# 2 Extended offline Aborted by host 90% 3000 -
# 3 Short offline Completed without error 00% 2998 -
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.Dernière modification par foxylechou (Le 21/04/2014, à 18:45)
ofwgkta
------------------------------------------------------------------
Hors ligne
#2 Le 18/04/2014, à 22:07
- jamesbad000
Re : [Résolu (tristement)]Disque dur, voici mon SMART log
Bonsoir.
Il y a un nombre élevé de secteur réalloués
5 Reallocated_Sector_Ct ... 632et également un nombre élevé en attente de réallocation.
197 Current_Pending_Sector ... 344Les secteurs réalloués correspondent à des problèmes que le disque à réglé en utilisant un secteur de réserve à la place d'un secteur posant problème
Les secteurs en attente de réallocation correspondent à des secteurs que le disque n'a pas réussi à lire la dernière fois qu'il a essayé de le faire. C'est probablement ce qui empêche le démarrage.
Ce nombre élevé de secteur illisible suite à une installation est un indice de dégradation rapide du disque.
De plus la valeur 50 indiquée à "disque shift" laisse à penser que le disque à subit un choc et qu'il tourne de façon excentrée. Mais comme je ne trouve pas de données de référence du constructeur je ne saurais dire à quel point c'est grave
Si tu as des données à récupérer sur ce disque, il faut cesser de l'utiliser, sauf lorsque tu sera prêt pour en faire une copie avec gddrescue.
S'il s'agit juste de le rendre utilisable, on peut tenter une procédure de la dernière chance. En soumettant le disque à une procédure de test intensive qui l'obligera à réallouer tous les secteurs défectueux sur des secteurs de réserve. Jusqu'à ce qu'il n'y ait plus d'erreur ou qu'il n'y ait plus de réserve disponible (auquel cas le disque devra être considéré comme hors service).
L'espace et le temps sont les modes par lesquels nous pensons, et non les conditions dans lesquelles nous vivons. (Signé Albert)
Hors ligne
#3 Le 21/04/2014, à 18:44
- foxylechou
Re : [Résolu (tristement)]Disque dur, voici mon SMART log
Merci beaucoup jamesbad000, je me doutais que ce n'était pas bon signe... Il me fallait une confirmation. Je ne vais rien tenter, il n'y a rien à récupérer dessus, c'était déjà fait avant que j'effectue les tests!
Merci encore
ofwgkta
------------------------------------------------------------------
Hors ligne