OVH Community, votre nouvel espace communautaire.

disque dur qui lâche ?


Nowwhat
18/03/2015, 13h24
Citation Envoyé par traaf
.....
ils sont sensé ne faire que du support matériel, mais quand je les contacte par ce biais, on me répond de m'adresser à kimsufi o_O
faut croire qu'ils redirigent tout le courrier vers ovh, et qu'ovh botte en touche en répondant que ca ne les concerne pas :/
Oh, si, t'inquiète, ce contact fonctionne très bien pour le support matériel (dans 95 % des cas : disque dur mort).

Mais sache qu'il y a une procédure à respecter.

Exemple: Ceci :
Bonjour,

Mon serveur marche pas - faut faire quelque chose !
Aura comme réponse:
Salut,
Va voir sur le forum.kimsufi.com pour support.
Par contre, un message qui respecte scrupuleusement tout ce qui est demandé ici http://forum.kimsufi.com/showthread....ter-le-support sera rapidement pris en charge.

Sache que le support reçoit principalement ce genre de demande : http://forum.kimsufi.com/showthread....9-%2864bits%29
Au début, c'est HYPER rigolo, mais à la fin, ça freine énormément le support.

traaf
18/03/2015, 10h54
Citation Envoyé par Nowwhat
La bas, t'as toutes les réponses comme par exemple :
Important : Contacter le support
oui, je connais cette page
ils sont sensé ne faire que du support matériel, mais quand je les contacte par ce biais, on me répond de m'adresser à kimsufi o_O
faut croire qu'ils redirigent tout le courrier vers ovh, et qu'ovh botte en touche en répondant que ca ne les concerne pas :/

fritz2cat
17/03/2015, 13h08
En effet, ceci est tout mauvais:
197 Current_Pending_Sector 0x0012 074 074 000 Old_age Always - 4303
198 Offline_Uncorrectable 0x0010 074 074 000 Old_age Offline - 4303
A tous les autres, surveillez ces paramètres, et dès qu'ils s'éloignnt de zéro, c'est une possible panne imminente !

Nowwhat
17/03/2015, 09h15
Ah, ok il ne s'agit donc pas d'un serveur "OVH".
T'es au courant que ceci froum.kimsufi.com existe ?

La bas, t'as toutes les réponses comme par exemple :
Important : Contacter le support

traaf
17/03/2015, 09h02
un seul disque de 2 To, mais sur un kimsufi :/

Nowwhat
17/03/2015, 08h52
Pas bien sorcier

Error 8362 occurred at .....
Ton disque est archi-mort.

Contacte la service technique (par ticket dans ton manager ?!) et demande la remplace de cette disque.
Mais avant, t'as combien des disques ? (lance un fdisk -l dans la mode rescue).
Indique bien qu'il s'agit de ton disque /sda - test aussi le /sdb (et autres, si t'en a).
Poste toutes ces résultats (commandes et résultats) vers OVH.

C'est à ce moment que tu pourrais te dire: " Ouf .... j'ai des sauvegardes ...".

traaf
17/03/2015, 08h44
salut,
je trouve depuis peu des erreurs de ce type dans les logs
Code:
EXT4-fs (sda2): error count since last fsck: 572
EXT4-fs (sda2): initial error at time 1426483577: __ext4_get_inode_loc:3940: inode 79307574: block 317194553
EXT4-fs (sda2): last error at time 1426570037: __ext4_get_inode_loc:3940: inode 79307570: block 317194553
Code:
kernel: sd 0:0:0:0: [sda] CDB: 
kernel: Read(10): 28 00 99 c0 19 d1 00 00 08 00
kernel: end_request: I/O error, dev sda, sector 2579503569
kernel: Buffer I/O error on device sda2, logical block 317194554
kernel: ata1: EH complete
kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
kernel: ata1.00: BMDMA stat 0x25
kernel: ata1.00: failed command: READ DMA EXT
kernel: ata1.00: cmd 25/00:08:a9:91:40/00:00:9a:00:00/e0 tag 0 dma 4096 in
kernel:         res 51/40:00:b0:91:40/40:00:9a:00:00/00 Emask 0x9 (media error)
kernel: ata1.00: status: { DRDY ERR }
kernel: ata1.00: error: { UNC }
kernel: ata1.00: configured for UDMA/133
kernel: sd 0:0:0:0: [sda] Unhandled sense code
kernel: sd 0:0:0:0: [sda]  
kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: sd 0:0:0:0: [sda]  
kernel: Sense Key : Medium Error [current] [descriptor]
kernel: Descriptor sense data with sense descriptors (in hex):
kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
kernel:        9a 40 91 b0 
kernel: sd 0:0:0:0: [sda]  
kernel: Add. Sense: Unrecovered read error - auto reallocate failed
et ce matin, le serveur ne répondait plus... j'ai peur que le disque ne soit en train de lâcher, ou alors le filesystem, je sais pas encore
premier réflexe, vérifier que mes sauvegardes soient bien à jour, ouf, c'est bon...

j'ai ensuite lancé un smartctl mais je ne sais pas l'interpréter :/
Code:
smartctl -a /dev/sda
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST2000DM001-9YN164
Serial Number:    W2404HSW
Firmware Version: CC4H
User Capacity:    2 000 398 934 016 bytes
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:    Tue Mar 17 09:30:00 2015 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: 		 ( 609) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 255) 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   092   090   006    Pre-fail  Always       -       14016789
  3 Spin_Up_Time            0x0003   094   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       64
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       624
  7 Seek_Error_Rate         0x000f   082   060   030    Pre-fail  Always       -       4483117080
  9 Power_On_Hours          0x0032   074   074   000    Old_age   Always       -       23246
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       63
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   001   001   000    Old_age   Always       -       130
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       17180131333
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   062   055   045    Old_age   Always       -       38 (Lifetime Min/Max 36/38)
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       -       62
193 Load_Cycle_Count        0x0032   027   027   000    Old_age   Always       -       147517
194 Temperature_Celsius     0x0022   038   045   000    Old_age   Always       -       38 (0 8 0 0)
197 Current_Pending_Sector  0x0012   074   074   000    Old_age   Always       -       4303
198 Offline_Uncorrectable   0x0010   074   074   000    Old_age   Offline      -       4303
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       65859028537791
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       21964681581802
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       165052352794414

SMART Error Log Version: 1
ATA Error Count: 8362 (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 8362 occurred at disk power-on lifetime: 23246 hours (968 days + 14 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: UNC 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      00:01:30.751  READ DMA EXT
  ea 00 00 67 90 88 a1 00      00:01:30.722  FLUSH CACHE EXT
  ca 00 08 f0 32 44 e1 00      00:01:30.722  WRITE DMA
  ea 00 00 ff ff ff af 00      00:01:30.722  FLUSH CACHE EXT
  27 00 00 00 00 00 e0 00      00:01:30.720  READ NATIVE MAX ADDRESS EXT

Error 8361 occurred at disk power-on lifetime: 23246 hours (968 days + 14 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: UNC 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      00:01:27.823  READ DMA EXT
  ca 00 10 e0 32 44 e1 00      00:01:27.821  WRITE DMA
  27 00 00 00 00 00 e0 00      00:01:27.819  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:01:27.811  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:01:27.804  SET FEATURES [Set transfer mode]

Error 8360 occurred at disk power-on lifetime: 23246 hours (968 days + 14 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: UNC 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      00:01:24.954  READ DMA EXT
  27 00 00 00 00 00 e0 00      00:01:24.951  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:01:24.943  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:01:24.936  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:01:24.911  READ NATIVE MAX ADDRESS EXT

Error 8359 occurred at disk power-on lifetime: 23246 hours (968 days + 14 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: UNC 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      00:01:22.105  READ DMA EXT
  27 00 00 00 00 00 e0 00      00:01:22.103  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:01:22.094  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      00:01:22.094  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:01:22.075  READ NATIVE MAX ADDRESS EXT

Error 8358 occurred at disk power-on lifetime: 23246 hours (968 days + 14 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: UNC 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00      00:01:19.247  READ DMA EXT
  25 00 08 ff ff ff ef 00      00:01:19.246  READ DMA EXT
  25 00 08 ff ff ff ef 00      00:01:19.246  READ DMA EXT
  25 00 08 ff ff ff ef 00      00:01:19.246  READ DMA EXT
  25 00 08 ff ff ff ef 00      00:01:19.245  READ DMA EXT

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%      3545         -
# 2  Short offline       Completed without error       00%      3533         -
# 3  Short offline       Completed without error       00%      3533         -
# 4  Short offline       Completed without error       00%        19         -
# 5  Short offline       Completed without error       00%         7         -
# 6  Short offline       Completed without error       00%         7         -
# 7  Short offline       Completed without error       00%         2         -

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.
quelqu'un peut m'aider à décrypter ca ?
merci