Salut à tous,

Je dispose d'un serveur KimSufi sur lequel j'ai installé Ubuntu 12.04.3 et l'outil d’administration à distance Webmin.
Depuis quelques jours, cet outil m'indique des erreurs SMART sur le disque dur.
J'ai lancé une analyse de ces données mais je ne sais pas interpréter les résultats.
Si vous pouviez me donner un coup de main :)

Voici un extrait du rapport :

smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.10.9-xxxx-grs-ipv6-64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model: ST1000DM003-9YN162
Serial Number: S1D3YH1N
LU WWN Device Id: 5 000c50 051bd0b88
Firmware Version: CC4H
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu May 1 09:44:58 2014 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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 249) Self-test routine in progress...
90% of test remaining.
Total time to complete Offline
data collection: ( 575) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 110) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
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 090 085 006 Pre-fail Always - 149337519
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 50
5 Reallocated_Sector_Ct 0x0033 077 052 036 Pre-fail Always - 30752
7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 232266673
9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 12391
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 49
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 061 061 000 Old_age Always - 39
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 068 047 045 Old_age Always - 32 (Min/Max 22/34)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 48
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 642
194 Temperature_Celsius 0x0022 032 053 000 Old_age Always - 32 (0 16 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 16
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 16
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 158866545324064
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 25060559130749
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 151703985668260

SMART Error Log Version: 1
ATA Error Count: 39 (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 39 occurred at disk power-on lifetime: 12391 hours (516 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
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

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 00 18 ff ff ff 4f 00 17d+09:15:16.354 WRITE FPDMA QUEUED
60 00 20 ff ff ff 4f 00 17d+09:15:15.729 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 17d+09:15:15.729 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 17d+09:15:15.729 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 17d+09:15:15.450 READ FPDMA QUEUED

Error 38 occurred at disk power-on lifetime: 12389 hours (516 days + 5 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 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

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 00 18 60 eb 06 41 00 17d+07:34:29.492 WRITE FPDMA QUEUED
60 00 20 ff ff ff 4f 00 17d+07:34:28.708 READ FPDMA QUEUED
61 00 08 28 12 80 40 00 17d+07:34:28.708 WRITE FPDMA QUEUED
61 00 08 88 11 80 40 00 17d+07:34:28.708 WRITE FPDMA QUEUED
61 00 08 58 10 80 40 00 17d+07:34:28.708 WRITE FPDMA QUEUED

Nota : Je n'ai mis que les 2 dernières erreurs, il s'agit de 39 fois la même chose.

A toute fin utile, voici la fin de rapport :

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Self-test routine in progress 90% 12391 -
# 2 Extended offline Completed without error 00% 12335 -
# 3 Short offline Aborted by host 40% 12329 -
# 4 Short offline Completed without error 00% 8346 -
# 5 Short offline Completed without error 00% 8341 -
# 6 Short offline Completed without error 00% 8341 -
# 7 Short offline Completed without error 00% 5881 -
# 8 Short offline Completed without error 00% 5874 -
# 9 Short offline Completed without error 00% 5874 -
#10 Short offline Completed without error 00% 5856 -
#11 Short offline Completed without error 00% 5855 -
#12 Short offline Completed without error 00% 5849 -
#13 Short offline Completed without error 00% 5849 -
#14 Short offline Completed without error 00% 5849 -
#15 Short offline Completed without error 00% 4848 -
#16 Short offline Completed without error 00% 4842 -
#17 Short offline Completed without error 00% 4842 -
#18 Short offline Completed without error 00% 3829 -
#19 Short offline Completed without error 00% 3823 -
#20 Short offline Completed without error 00% 3823 -
#21 Short offline Completed without error 00% 52 -

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.

Je vous remercie.

Naga

Edit : Désolé, j'ai eu quelques soucis de mise en forme du message.

C'est de nouveau moi ^^

J'en suis maintenant à 51 erreurs.

Ça commence à m'inquiéter sérieusement.

Naga

Kikoo,

Toujours personne qui pourrait éclairer ma lanterne ?

Ce souci est toujours d'actualité.

Naga

le SMART permet de déterminer la fiabilité du disque par une série de tests.

En cas d'échec, ce qui est ton cas, tu dois changer le disque avant qu'il ne lâche ou que tu ne perdes des données. Je te le conseille même si certains tests ratés ne sont pas déterminants d'une panne mais d'une baisse de performance anormale.

Tu peux télécharger (en version d'essai) hard drive Inspector pro pour avoir confirmation de la santé du DD..

Salut, Merci Super_GEGE,

Je viens de voir ton message (étonnement je n'ai pas reçu de mail quand tu m'a répondu). Désolé du retard pour ma réponse.

En fait c'est un serveur distant auquel je n'ai pas accès physiquement.

Je souhaiterais être sur qu'il ne s'agisse pas d'un faux positif avant de faire intervenir une équipe de maintenance (ce qui est assez compliqué je crois).

Je testerais l'outil que tu me propose à condition qu'il tourne sous Linux et un mode console.

Naga