Conversation
precedente ou
suivante
vérifier un disque dure
Envoyé par:
seblinux
J'aurais voulu savoir quel programe vous utilisez pour tester vos disques dures. Je sais que j'ai des secteurs défectueux et je voudrait les "trouver"... sur ma partition windows, pas de problème pour le faire mais je cale sur mon linux...
Poste le Wednesday 8 March 2006 14:19:42
Re: vérifier un disque dure
Envoyé par:
P Hoquet
e2fsck appelant badblocks.
Exemple:
# e2fsck -c /dev/fd0
e2fsck 1.36 (05-Feb-2005)
Checking for bad blocks (read-only test): done
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
OU:
# e2fsck -c -c /dev/fd0
e2fsck 1.36 (05-Feb-2005)
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern:
done 440
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Exemple:
# e2fsck -c /dev/fd0
e2fsck 1.36 (05-Feb-2005)
Checking for bad blocks (read-only test): done
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
OU:
# e2fsck -c -c /dev/fd0
e2fsck 1.36 (05-Feb-2005)
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern:
done 440
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Poste le Wednesday 8 March 2006 14:33:09
Re: vérifier un disque dur
Envoyé par:
Basile STARYNKEVITCH
A mon avis, un disque dur dont certains secteurs sont abimés est bon pour la poubelle.
(car les secteurs consécutifs logiquement ne sont pas voisins physiquement...). les disques récents réorganisent leurs sectorisations.
Outre e2fsck, il y a aussi smartctl ....
les disques durs d'aujourd'hui ne sont pas ceux de l'époque originelle d'Unix (1970-80). La défaillance d'un secteur est maintenant gérée par le contrôleur interne du disque, et non plus par le noyau. Il y a probablement plus de code à l'intérieur d'un disque dur IDE ou SATA (dans son firmware) que dans tout le système Unix originel.
En gros, je pense que ce n'est pas la peine de s'embêter pour un disque ayant un secteur abimé. Il vaut mieux le changer... je considère les disques comme des consommables. Pënsez à faire des sauvegardes, vous en aurez besoin....
PS. Je suis assez vieux pour avoir pratiqué SunOS3.2 en 1986, qui était très proche d'un vieux BSD et encore voisin d'Unix ATTv7. A l'époque, récupérer un secteur abimé avait du sens (et le disque dur de l'époque coutait cent fois plus cher que le disque de 200Go SATA actuel, pour une capacité mille fois moindre, et un bruit insupportable). De nos jours, ca me parait avoir beaucoup moins de sens (et d'expérience, un disque dur abimé crashe rapidement).
----
Basile STARYNKEVITCH
Membre de l'APRIL « promouvoir et défendre le logiciel libre » - adhérez vous aussi à l'APRIL!
Projet logiciel libre: RefPerSys
(car les secteurs consécutifs logiquement ne sont pas voisins physiquement...). les disques récents réorganisent leurs sectorisations.
Outre e2fsck, il y a aussi smartctl ....
les disques durs d'aujourd'hui ne sont pas ceux de l'époque originelle d'Unix (1970-80). La défaillance d'un secteur est maintenant gérée par le contrôleur interne du disque, et non plus par le noyau. Il y a probablement plus de code à l'intérieur d'un disque dur IDE ou SATA (dans son firmware) que dans tout le système Unix originel.
En gros, je pense que ce n'est pas la peine de s'embêter pour un disque ayant un secteur abimé. Il vaut mieux le changer... je considère les disques comme des consommables. Pënsez à faire des sauvegardes, vous en aurez besoin....
PS. Je suis assez vieux pour avoir pratiqué SunOS3.2 en 1986, qui était très proche d'un vieux BSD et encore voisin d'Unix ATTv7. A l'époque, récupérer un secteur abimé avait du sens (et le disque dur de l'époque coutait cent fois plus cher que le disque de 200Go SATA actuel, pour une capacité mille fois moindre, et un bruit insupportable). De nos jours, ca me parait avoir beaucoup moins de sens (et d'expérience, un disque dur abimé crashe rapidement).
----
Basile STARYNKEVITCH
Membre de l'APRIL « promouvoir et défendre le logiciel libre » - adhérez vous aussi à l'APRIL!
Projet logiciel libre: RefPerSys
Poste le Wednesday 8 March 2006 18:36:32
Re: vérifier un disque dur
Envoyé par:
nicola
Pour prévenir avant la casse, il y a les smartmontools et le démon qui va avec.
--
On ne prête qu’aux riches, et on a bien raison, parce que les autres remboursent difficilement.
-+- Tristan Bernard (1866-1947) -+-
--
On ne prête qu’aux riches, et on a bien raison, parce que les autres remboursent difficilement.
-+- Tristan Bernard (1866-1947) -+-
Poste le Wednesday 8 March 2006 19:31:32
Re: vérifier un disque dure
Envoyé par:
seblinux
merci pour vos réponse, mon disque est toujours sur garantie mais avant de recevoir le technicien, il me faut obligatoirement travailler... voilà ma démarche de trouver les secteurs défectueux...
Poste le Wednesday 8 March 2006 23:46:34
Re: vérifier un disque dure
Envoyé par:
seblinux
voilà ce que donne la commande avec smartctl:
D-link:/home/sebastien # smartctl -i -H -d ata /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is [smartmontools.sourceforge.net]
=== START OF INFORMATION SECTION ===
Device Model: Maxtor 7Y250M0
Serial Number: Y65XSSBE
Firmware Version: YAR51HW0
User Capacity: 250,000,000,000 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Thu Mar 9 00:11:06 2006 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
bizzard quand même, après avoir vérivier toutes mes partitions, j'ai plus ou moins 10 gb de secteurs défectueux... est-ce que se serait parcequ'ils sont "marqués" maintenant? (c'est du sata)
D-link:/home/sebastien # smartctl -i -H -d ata /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is [smartmontools.sourceforge.net]
=== START OF INFORMATION SECTION ===
Device Model: Maxtor 7Y250M0
Serial Number: Y65XSSBE
Firmware Version: YAR51HW0
User Capacity: 250,000,000,000 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Thu Mar 9 00:11:06 2006 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
bizzard quand même, après avoir vérivier toutes mes partitions, j'ai plus ou moins 10 gb de secteurs défectueux... est-ce que se serait parcequ'ils sont "marqués" maintenant? (c'est du sata)
Poste le Thursday 9 March 2006 00:15:24
Re: vérifier un disque dure
Envoyé par:
seblinux
ok il me trouve bien des erreurs:
D-link:/windows/c # smartctl -a -d ata /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is [smartmontools.sourceforge.net]
=== START OF INFORMATION SECTION ===
Device Model: Maxtor 7Y250M0
Serial Number: Y65XSSBE
Firmware Version: YAR51HW0
User Capacity: 250,000,000,000 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Thu Mar 9 00:31:32 2006 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: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 118) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 363) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 106) minutes.
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
3 Spin_Up_Time 0x0027 194 177 063 Pre-fail Always - 14480
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 709
5 Reallocated_Sector_Ct 0x0033 185 185 063 Pre-fail Always - 689
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0
8 Seek_Time_Performance 0x0027 251 243 187 Pre-fail Always - 35906
9 Power_On_Minutes 0x0032 248 248 000 Old_age Always - 879h+48m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 712
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 0
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 0
194 Temperature_Celsius 0x0032 253 253 000 Old_age Always - 52
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 2059
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 185 185 000 Old_age Offline - 689
198 Offline_Uncorrectable 0x0008 252 252 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 6
202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 3
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0
209 Offline_Seek_Performnce 0x0024 192 192 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
SMART Error Log Version: 1
Warning: ATA error count 7021 inconsistent with error log pointer 5
ATA Error Count: 7021 (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
S.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 7021 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c5 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac5 = 223941
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 01 c5 6a 03 e0 00 03:33:27.360 READ DMA EXT
25 00 02 c4 6a 03 e0 00 03:33:26.272 READ DMA EXT
25 00 03 c3 6a 03 e0 00 03:33:25.184 READ DMA EXT
25 00 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
Error 7020 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c4 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac4 = 223940
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 02 c4 6a 03 e0 00 03:33:26.272 READ DMA EXT
25 00 03 c3 6a 03 e0 00 03:33:25.184 READ DMA EXT
25 00 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
Error 7019 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c3 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac3 = 223939
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 03 c3 6a 03 e0 00 03:33:25.184 READ DMA EXT
25 00 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:15.328 READ DMA EXT
Error 7018 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c2 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac2 = 223938
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 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:15.328 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:14.240 READ DMA EXT
Error 7017 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c1 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac1 = 223937
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 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:15.328 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:14.240 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:13.024 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short captive Completed: read failure 60% 1791 6671615
# 2 Short offline Completed without error 00% 0 -
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.
D-link:/windows/c # smartctl -a -d ata /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is [smartmontools.sourceforge.net]
=== START OF INFORMATION SECTION ===
Device Model: Maxtor 7Y250M0
Serial Number: Y65XSSBE
Firmware Version: YAR51HW0
User Capacity: 250,000,000,000 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Thu Mar 9 00:31:32 2006 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: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 118) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 363) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 106) minutes.
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
3 Spin_Up_Time 0x0027 194 177 063 Pre-fail Always - 14480
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 709
5 Reallocated_Sector_Ct 0x0033 185 185 063 Pre-fail Always - 689
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0
8 Seek_Time_Performance 0x0027 251 243 187 Pre-fail Always - 35906
9 Power_On_Minutes 0x0032 248 248 000 Old_age Always - 879h+48m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 712
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 0
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 0
194 Temperature_Celsius 0x0032 253 253 000 Old_age Always - 52
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 2059
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 185 185 000 Old_age Offline - 689
198 Offline_Uncorrectable 0x0008 252 252 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 6
202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 3
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0
209 Offline_Seek_Performnce 0x0024 192 192 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
SMART Error Log Version: 1
Warning: ATA error count 7021 inconsistent with error log pointer 5
ATA Error Count: 7021 (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
S.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 7021 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c5 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac5 = 223941
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 01 c5 6a 03 e0 00 03:33:27.360 READ DMA EXT
25 00 02 c4 6a 03 e0 00 03:33:26.272 READ DMA EXT
25 00 03 c3 6a 03 e0 00 03:33:25.184 READ DMA EXT
25 00 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
Error 7020 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c4 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac4 = 223940
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 02 c4 6a 03 e0 00 03:33:26.272 READ DMA EXT
25 00 03 c3 6a 03 e0 00 03:33:25.184 READ DMA EXT
25 00 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
Error 7019 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c3 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac3 = 223939
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 03 c3 6a 03 e0 00 03:33:25.184 READ DMA EXT
25 00 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:15.328 READ DMA EXT
Error 7018 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c2 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac2 = 223938
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 04 c2 6a 03 e0 00 03:33:24.128 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:15.328 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:14.240 READ DMA EXT
Error 7017 occurred at disk power-on lifetime: 1843 hours (76 days + 19 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c1 6a 03 e0 Error: UNC 1 sectors at LBA = 0x00036ac1 = 223937
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 05 c1 6a 03 e0 00 03:33:23.024 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:16.416 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:15.328 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:14.240 READ DMA EXT
25 00 05 c1 6a 03 e0 00 03:32:13.024 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short captive Completed: read failure 60% 1791 6671615
# 2 Short offline Completed without error 00% 0 -
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.
Poste le Thursday 9 March 2006 00:33:53
Ce forum !
vérifier un disque dure
Vous voulez savoir si votre matériel est supporté par Linux, ou vous avez un problème pour installer un module ? Ce forum est pour vous !
Sauf mention contraire, les documentations publiées sont sous licence Creative-Commons