OVH Community, your new community space.

ks309280.kimsufi.com con harddisk sdb rotto


torpado
19.09.2013, 15.24
Citazione Originariamente Scritto da torpado

Sto verificando il problema
Problema di encoding del ticket, provvedo a riaprire un nuovo ticket

torpado
19.09.2013, 09.55
Citazione Originariamente Scritto da nabla2
Bene per prendermi io in carico il ripristino del raid1.
Pu˛ anche consultare questa guida per avere maggiori informazioni :

http://guida.ovh.it/RaidSoft

Per il ticket 1512001, io non riesco a visualizzarlo da quando ho postato i dati da voi richiesti (fdisk, smartctl, ...). Il precedente ticket 1509556 lo visualizzo correttamente ma non posso riaprirlo per ticket gia' aperto.

Quindi, o mi sistema il ticket aperto, o io non ho possibilita' se non qui di interagire con voi.
Sto verificando il problema

nabla2
19.09.2013, 09.45
Bene per prendermi io in carico il ripristino del raid1.

Per il ticket 1512001, io non riesco a visualizzarlo da quando ho postato i dati da voi richiesti (fdisk, smartctl, ...). Il precedente ticket 1509556 lo visualizzo correttamente ma non posso riaprirlo per ticket gia' aperto.

Quindi, o mi sistema il ticket aperto, o io non ho possibilita' se non qui di interagire con voi.

torpado
19.09.2013, 09.37
Citazione Originariamente Scritto da nabla2
Le garantisco che i vostri strumenti presentano notevoli errori.
In particolare l'accesso alla pagina del ticket https://www.ovh.it/managerv3/service...cketId=1512001 mi ritorna errore e quindi sul manager io non posso fare nulla.

Rispondo comunque qui alla vostra email.

mi chiedete 'deve dare espressa conferma di esecuzione del backup'
immagino intendiate chiedere se ho effettuato un backup, confermo che
ho effettuato un backup lunedi' sera, i dati nel frattempo pero' sono cambiati
per cui per me e' essenziale mantenere in vita sda

immagino che sostituirete il disco sdb, il ripristino del raid1 poi lo fate
voi o lo faccio io?

mi chiedete 'deve indicare la sua preferenza per il nostro intervento in questa fascia oraria...'

richiedo l'intervento per oggi giovedi' 19 settembre alle ore 19:00

Mi faccia comunque sapere se pensate voi al ripristino del raid1.
Le sue risposte al ticket le visualizzo correttamente, mancavano solo una parte di informazioni nella sua risposta. Verifico e provo a riprodurre gli errori che riscontra.

Il Raid deve essere ricostruito da chi gestisce il server, una volta sostituito il disco guasto.

nabla2
19.09.2013, 09.30
Le garantisco che i vostri strumenti presentano notevoli errori.
In particolare l'accesso alla pagina del ticket https://www.ovh.it/managerv3/service...cketId=1512001 mi ritorna errore e quindi sul manager io non posso fare nulla.

Rispondo comunque qui alla vostra email.

mi chiedete 'deve dare espressa conferma di esecuzione del backup'
immagino intendiate chiedere se ho effettuato un backup, confermo che
ho effettuato un backup lunedi' sera, i dati nel frattempo pero' sono cambiati
per cui per me e' essenziale mantenere in vita sda

immagino che sostituirete il disco sdb, il ripristino del raid1 poi lo fate
voi o lo faccio io?

mi chiedete 'deve indicare la sua preferenza per il nostro intervento in questa fascia oraria...'

richiedo l'intervento per oggi giovedi' 19 settembre alle ore 19:00

Mi faccia comunque sapere se pensate voi al ripristino del raid1.

torpado
19.09.2013, 09.24
Citazione Originariamente Scritto da nabla2
Sinceramente piu' che un 'grazie per la collaborazione' mi aspetterei un piano di recupero del guasto con tempi e modalita' di ripristino.

Mi faccia sapere.
Sinceramente Ŕ da ieri, data apertura ticket incidente, che attendo di sapere la sua disponibilitÓ per l'esecuzione dell'intervento e la sua conferma di avvenuto backup dei dati di sicurezza

Sul forum viene trattata l'analisi del problema che l'utente riscontra, dopodichŔ una volta in presenza di un ticket incidente Ŕ necessario fornire le informazioni richieste tramite ticket, Ŕ necessario fornirle sul ticket.

nabla2
19.09.2013, 09.09
Sinceramente piu' che un 'grazie per la collaborazione' mi aspetterei un piano di recupero del guasto con tempi e modalita' di ripristino.

Mi faccia sapere.

torpado
19.09.2013, 09.01
Grazie per la collaborazione

nabla2
18.09.2013, 17.38
Inoltro quanto richiesto via email:

# fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
181 heads, 41 sectors/track, 263242 cylinders
Units = cylinders of 7421 * 512 = 3799552 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1413 5242880 fd Linux raid autodetect
/dev/sda2 1413 263242 971516560+ 5 Extended
/dev/sda5 1413 4045 9766071+ fd Linux raid autodetect
/dev/sda6 4046 9310 19535762 fd Linux raid autodetect
/dev/sda7 9311 11943 9769726 fd Linux raid autodetect
/dev/sda8 11944 14050 7818003 82 Linux swap / Solaris
/dev/sda9 14051 263242 924626895+ fd Linux raid autodetect

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
181 heads, 41 sectors/track, 263242 cylinders
Units = cylinders of 7421 * 512 = 3799552 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 1413 5242880 fd Linux raid autodetect
/dev/sdb2 1413 263242 971516560+ 5 Extended
/dev/sdb5 1413 4045 9766071+ fd Linux raid autodetect
/dev/sdb6 4046 9310 19535762 fd Linux raid autodetect
/dev/sdb7 9311 11943 9769726 fd Linux raid autodetect
/dev/sdb8 11944 14050 7818003 82 Linux swap / Solaris
/dev/sdb9 14051 263242 924626895+ fd Linux raid autodetect

Disk /dev/md5: 946.8 GB, 946817859584 bytes
2 heads, 4 sectors/track, 231156704 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md5 doesn't contain a valid partition table

Disk /dev/md4: 10.0 GB, 10004070400 bytes
2 heads, 4 sectors/track, 2442400 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md4 doesn't contain a valid partition table

Disk /dev/md3: 20.0 GB, 20004536320 bytes
2 heads, 4 sectors/track, 4883920 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md3 doesn't contain a valid partition table

Disk /dev/md2: 10.0 GB, 10000334848 bytes
2 heads, 4 sectors/track, 2441488 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/md1: 5368 MB, 5368643584 bytes
2 heads, 4 sectors/track, 1310704 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Device Boot Start End Blocks Id System
]0;root@ks1:~[root@ks1 ~]# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
md1 : active raid1 sda1[0]
5242816 blocks [2/1] [U_]

md2 : active raid1 sda5[0]
9765952 blocks [2/1] [U_]

md3 : active raid1 sda6[0]
19535680 blocks [2/1] [U_]

md4 : active raid1 sda7[0]
9769600 blocks [2/1] [U_]

md5 : active raid1 sda9[0]
924626816 blocks [2/1] [U_]

unused devices:
]0;root@ks1:~[root@ks1 ~]# smartctl -a -d ata /dev/sda
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: ST1000DM003-1CH162
Serial Number: Z1D2CMS1
Firmware Version: CC43
User Capacity: 1,000,204,886,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: Wed Sep 18 18:35:09 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: (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: ( 592) 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: ( 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 117 099 006 Pre-fail Always - 139956288
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 16
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 080 060 030 Pre-fail Always - 101179000
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 7876
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 16
183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Unknown_Attribute 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 064 052 045 Old_age Always - 36 (Lifetime Min/Max 35/37)
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 - 16
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 73
194 Temperature_Celsius 0x0022 036 048 000 Old_age Always - 36 (0 21 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 9852654984885
241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 5328133330
242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 67208721984

SMART Error Log Version: 1
No Errors Logged

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% 333 -

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.

nabla2
18.09.2013, 17.27
Ho riavviato il nostro server ks309280.kimsufi.com in modalita' rescue per eseguire i diagnostici hardware del server.
Mi e' arrivata l'email per l'accesso al server in modalita' rescue.
Quando effettuo il login all'interfaccia web dei diagnostici ottengo l'errore 'Internal server error' e quindi non riesco ad eseguire i vostri diagnostici.

torpado
18.09.2013, 17.22
Citazione Originariamente Scritto da nabla2
Il server ks309280.kimsufi.com ha due dischi sda e sdb in raid1 software.
Il disco sdb e' rotto....
Grazie per la collaborazione, riceverai a breve nostra notifica via email per l'intervento sul server

nabla2
18.09.2013, 17.17
Il server ks309280.kimsufi.com ha due dischi sda e sdb in raid1 software.
Il disco sdb e' rotto.
Qui di seguito allego l'output del comando 'smartctl --all' del disco sdb rotto.
Vi chiediamo di sostituire il disco sdb.
Il disco sda contiene i dati validi del nostro server.

smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: ST31000528AS
Serial Number: 9VP2S4ZZ
Firmware Version: CC38
User Capacity: 1,000,204,886,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: Wed Sep 18 16:09:34 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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

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: ( 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: (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: ( 179) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table 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 119 098 006 Pre-fail Always - 226989708
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 80
5 Reallocated_Sector_Ct 0x0033 003 003 036 Pre-fail Always FAILING_NOW 3974
7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 188917383
9 Power_On_Hours 0x0032 063 063 000 Old_age Always - 33094
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 40
183 Unknown_Attribute 0x0032 003 003 000 Old_age Always - 97
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 046 046 000 Old_age Always - 54
188 Unknown_Attribute 0x0032 100 093 000 Old_age Always - 433801199770
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 069 053 045 Old_age Always - 31 (Lifetime Min/Max 28/32)
194 Temperature_Celsius 0x0022 031 047 000 Old_age Always - 31 (0 14 0 0)
195 Hardware_ECC_Recovered 0x001a 033 014 000 Old_age Always - 226989708
197 Current_Pending_Sector 0x0012 099 099 000 Old_age Always - 72
198 Offline_Uncorrectable 0x0010 099 099 000 Old_age Offline - 72
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 102976135922091
241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4274747974
242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2934442056

SMART Error Log Version: 1
ATA Error Count: 54 (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 54 occurred at disk power-on lifetime: 19739 hours (822 days + 11 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 b6 fa 5b 00 Error: UNC at LBA = 0x005bfab6 = 6027958

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 00 81 f8 5b e0 00 32d+12:21:48.561 READ DMA EXT
27 00 00 00 00 00 e0 00 32d+12:21:48.560 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 32d+12:21:48.552 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 32d+12:21:48.547 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 32d+12:21:48.520 READ NATIVE MAX ADDRESS EXT

Error 53 occurred at disk power-on lifetime: 19739 hours (822 days + 11 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 b6 fa 5b 00 Error: UNC at LBA = 0x005bfab6 = 6027958

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 00 81 f8 5b e0 00 32d+12:21:45.373 READ DMA EXT
27 00 00 00 00 00 e0 00 32d+12:21:45.372 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 32d+12:21:45.364 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 32d+12:21:45.358 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 32d+12:21:45.332 READ NATIVE MAX ADDRESS EXT

Error 52 occurred at disk power-on lifetime: 19739 hours (822 days + 11 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 b6 fa 5b 00 Error: UNC at LBA = 0x005bfab6 = 6027958

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 00 81 f8 5b e0 00 32d+12:21:42.200 READ DMA EXT
27 00 00 00 00 00 e0 00 32d+12:21:42.199 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 32d+12:21:42.191 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 32d+12:21:42.186 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 32d+12:21:42.159 READ NATIVE MAX ADDRESS EXT

Error 51 occurred at disk power-on lifetime: 19739 hours (822 days + 11 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 b6 fa 5b 00 Error: UNC at LBA = 0x005bfab6 = 6027958

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 00 81 f8 5b e0 00 32d+12:21:39.020 READ DMA EXT
27 00 00 00 00 00 e0 00 32d+12:21:39.019 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 32d+12:21:39.011 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 32d+12:21:39.006 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 32d+12:21:38.979 READ NATIVE MAX ADDRESS EXT

Error 50 occurred at disk power-on lifetime: 19739 hours (822 days + 11 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 b6 fa 5b 00 Error: UNC at LBA = 0x005bfab6 = 6027958

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 00 81 f8 5b e0 00 32d+12:21:35.848 READ DMA EXT
27 00 00 00 00 00 e0 00 32d+12:21:35.847 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 32d+12:21:35.838 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 32d+12:21:35.834 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 32d+12:21:35.807 READ NATIVE MAX ADDRESS 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% 25553 -

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.