Pages : 1
#1 Le 12/10/2013, à 10:09
- NoizzY
Comment intérpreter résultats smartctl?
Bonjour, j'ai un souci de transfert avec un de mes disques:
Pour écrire dessus:
Taux de transfert entrée variant entre 30 et 85 Mio/s (ok)
Taux de transfert sortie plafonne entre 05 et 08 Mio/s (Bad!)
le résultat de la commande
smartctl -a /dev/sdxsmartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.8.0-32-generic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Blue Serial ATA
Device Model: WDC WD5000AAKS-00A7B0
Serial Number: (xxxxxxxxxxxxxxxxxxxxxxxxxxxx)
LU WWN Device Id: 5 0014ee 055d39262
Firmware Version: 01.03B01
User Capacity: 500.107.862.016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sat Oct 12 09:23:21 2013 CEST
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: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
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: (12000) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 140) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) 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 0x000f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0003 146 143 021 Pre-fail Always - 5683
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 114
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0
9 Power_On_Hours 0x0032 076 076 000 Old_age Always - 18144
10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3103
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 581
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3103
194 Temperature_Celsius 0x0022 103 092 000 Old_age Always - 44
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 5
200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 4
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 4 occurred at disk power-on lifetime: 1965 hours (81 days + 21 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 08 1a 32 c6 e0 Error: UNC 8 sectors at LBA = 0x00c6321a = 12988954
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 08 1a 32 c6 34 00 00:13:16.164 READ DMA EXT
35 00 08 62 67 40 05 00 00:13:16.164 WRITE DMA EXT
25 00 08 7f 52 d8 04 00 00:13:16.164 READ DMA EXT
35 00 08 47 76 c8 04 00 00:13:16.164 WRITE DMA EXT
35 00 80 f7 ec 79 00 00 00:13:16.163 WRITE DMA EXT
Error 3 occurred at disk power-on lifetime: 1965 hours (81 days + 21 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 08 1a 32 c6 e0 Error: UNC 8 sectors at LBA = 0x00c6321a = 12988954
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 08 1a 32 c6 34 00 00:13:13.050 READ DMA EXT
35 00 08 82 0c b8 1a 00 00:13:13.050 WRITE DMA EXT
25 00 30 4f 53 d8 04 00 00:13:13.050 READ DMA EXT
35 00 04 9f 56 c6 04 00 00:13:13.049 WRITE DMA EXT
35 00 80 77 ec 79 00 00 00:13:13.049 WRITE DMA EXT
Error 2 occurred at disk power-on lifetime: 1965 hours (81 days + 21 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 08 1a 32 c6 e0 Error: UNC 8 sectors at LBA = 0x00c6321a = 12988954
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 08 1a 32 c6 34 00 00:13:10.099 READ DMA EXT
35 00 50 27 ec 79 00 00 00:13:10.098 WRITE DMA EXT
35 00 48 e7 37 5e 00 00 00:13:10.098 WRITE DMA EXT
35 00 01 c7 a9 0c 00 00 00:13:10.098 WRITE DMA EXT
25 00 80 1a 32 c6 34 00 00:13:07.154 READ DMA EXT
Error 1 occurred at disk power-on lifetime: 1965 hours (81 days + 21 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 80 1a 32 c6 e0 Error: UNC 128 sectors at LBA = 0x00c6321a = 12988954
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 80 1a 32 c6 34 00 00:13:07.154 READ DMA EXT
25 00 80 9a 31 c6 34 00 00:13:07.152 READ DMA EXT
25 00 80 1a 31 c6 34 00 00:13:07.151 READ DMA EXT
25 00 80 9a 30 c6 34 00 00:13:07.150 READ DMA EXT
25 00 80 1a 30 c6 34 00 00:13:07.149 READ DMA EXT
SMART Self-test log structure revision number 1
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. Comment interpréter cela?
Merci.
Intel® Core™ i5-2500 CPU @ 3.30GHz ×4 - GeForce GT 440
Kubuntu
Hors ligne
#2 Le 12/10/2013, à 10:19
- lann
Re : Comment intérpreter résultats smartctl?
Un petit lien pour ton problème :
http://smartmontools.sourceforge.net/badblockhowto.html
En ligne
#3 Le 12/10/2013, à 11:09
- NoizzY
Re : Comment intérpreter résultats smartctl?
Merci IANN
La suite:
La commande
$ tune2fs -l /dev/sdx | grep Blockdonne:
tune2fs: Numéro magique invalide dans le super-bloc lors de la tentative d'ouverture de /dev/sdx
Impossible de trouver un superbloc de système de fichiers valide.Dernière modification par NoizzY (Le 12/10/2013, à 11:10)
Intel® Core™ i5-2500 CPU @ 3.30GHz ×4 - GeForce GT 440
Kubuntu
Hors ligne
#4 Le 12/10/2013, à 12:10
- NoizzY
Re : Comment intérpreter résultats smartctl?
Bon, j'ai résolu mon problème de taux de transfert en formatant le disque en ext3 (il était en ext4 avant).
Le taux est maintenant très élevé puisqu'il transfert 1.5 Go en moins de 10 secondes.
Dernière modification par NoizzY (Le 12/10/2013, à 12:11)
Intel® Core™ i5-2500 CPU @ 3.30GHz ×4 - GeForce GT 440
Kubuntu
Hors ligne
#5 Le 12/10/2013, à 17:38
- lann
Re : Comment intérpreter résultats smartctl?
Tu aurais pu (du) le formatter en Ext4
En ligne