We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

diskfailure on ks3296876


skinkie
08/10/2014, 11h59

skinkie
08/10/2014, 11h41
Citation Envoyé par heise
In "BOOT" you have to change "hd (Boot from hard drive (no netboot))" to boot from "rescue mode" or what ever it is called in your control panel. Then run tests again.

Why did you not say, that you don't know how to switch to rescue mode??
Don't be so arrogant Heise. Should I make you a movie that I actually changing to rescue-pro but, but it never updates the interface?

heise
08/10/2014, 00h51
In "BOOT" you have to change "hd (Boot from hard drive (no netboot))" to boot from "rescue mode" or what ever it is called in your control panel. Then run tests again.

Why did you not say, that you don't know how to switch to rescue mode??

skinkie
07/10/2014, 18h03

TomOVH
07/10/2014, 13h09
hello,

please include a screenshot of the error message received when trying to access rescue mode.

skinkie
30/09/2014, 18h33
Since the server can't boot into rescue mode and the server only shows one disk I kindly request to replace the disk.

skinkie
26/09/2014, 10h25
The server is unable to reboot into rescue mode. See the intervention of last night.

Secondary the manager gives: An error occurred during the reboot request. (User not granted for this request)
I have rebooted it manually, which let to the intervention.

TomOVH
16/09/2014, 16h59
Hello,

Please run tests in rescue mode, we will then check into this for you.

heise
13/09/2014, 22h18
He has two HDD, so server will reboot into rescue mode and since one HDD still comes up, I don't think technician will not change immediatly. I guess there was a case with ubuntu in the past, that gave wrong fdisk values (no HDD found). I guess that is why - out of principle - they ask for rescue mode. Besides if Linux looses connection to a driver and doesn't reconnect, testing will fail. And there is always the possiblilty that some drivers are incompatible with the kernel, hence giving wrong results. To avoid all that and get standarized results, I guess they ask all customers to run the tests in rescue mode.

buddy
13/09/2014, 21h36
Hi,

if your server cannot reboot correctly (hard drive not detected), normally the technician change the hard drive straight

skinkie
13/09/2014, 21h06
Citation Envoyé par TomOVH
We cannot start an intervention until the tests are run in rescue mode. Please backup your data and then do this.
Tom, why don't you change the FAQ? It is explicitly mentioned that Linux user may run smartctl directly.

@Heise thanks for your comment and best pracise. It seems you have some time spend around here. Indeed, I am moving the services running on that machine to a different system. I have paid for multiple servers for year contracts (Kimsufi, SoYouStart, etc.) with serveral extension earlier. I find myself bitten for not upgrading every time faster and newer servers become available.

heise
13/09/2014, 00h56
I am not advising you but telling you out of experience how it works here. If you are running sensible things, I recommend, that you get yourself temporarly a server, move everything there and move back once it is fixed. First it takes time for them to open a ticket after you posted here. Then a technician has to actually exchange your HDD and there have been cases where everything took up to two months and as far as I know, Kimsufi did not give any compensation for the downtime.

TomOVH
12/09/2014, 14h04
Hello,

We cannot start an intervention until the tests are run in rescue mode. Please backup your data and then do this.

skinkie
11/09/2014, 21h30
Citation Envoyé par heise
Run in rescue mode.
You are advising me to create downtime on my server, never be able to boot it anymore because the primary harddrive failed and grub will not be found anymore?

Code:
21:31:19 up 246 days, 18:43,  1 user,  load average: 0.01, 0.06, 0.05
Sounds like a really good idea, not. The information is there, OVH needs to act.

heise
10/09/2014, 22h15
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.12.6-gentoo] (local build)
Run in rescue mode.

skinkie
10/09/2014, 22h01
Code:
fdisk -l
fdisk: cannot open /dev/sda: Input/output error
Code:
smartctl -a -d ata /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.12.6-gentoo] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: Input/output error

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Code:
smartctl -a -d ata /dev/sdb
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.12.6-gentoo] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" HDD DT01ACA...
Device Model:     TOSHIBA DT01ACA050
Serial Number:    Z2CJ975FS
LU WWN Device Id: 5 000039 ff2c76897
Firmware Version: MS1OA750
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Sep 10 22:00:32 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:  (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:                ( 4998) 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.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (  84) minutes.
SCT capabilities:              (0x003d) 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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   136   136   054    Pre-fail  Offline      -       92
  3 Spin_Up_Time            0x0007   142   142   024    Pre-fail  Always       -       185 (Average 138)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       11
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   115   115   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   098   098   000    Old_age   Always       -       14196
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       10
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       28
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       28
194 Temperature_Celsius     0x0002   181   181   000    Old_age   Always       -       33 (Min/Max 15/48)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

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%        13         -
# 2  Short offline       Completed without error       00%         9         -
# 3  Short offline       Completed without error       00%         8         -
# 4  Short offline       Completed without error       00%         1         -

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.
Code:
cat /proc/mdstat 
Personalities : [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] 
md1 : active raid1 sdb1[1] sda1[2](F)
      10485696 blocks [2/1] [_U]
      
md2 : active raid1 sdb2[1] sda2[2](F)
      477370304 blocks [2/1] [_U]
      
unused devices: 

TomOVH
10/09/2014, 10h40
Could you please run the tests listed in the How To post thread and paste the results here?

skinkie
08/09/2014, 22h32
The primairy harddisk (sda) of ks3296876 failed last Saturday. OVH NL directed me to this forum. The system is configured with soft-raid 1.

The only thing regarding the harddrive that I can currently find is in dmesg.
Code:
[21061746.863294] sd 0:0:0:0: [sda] Unhandled error code
[21061746.863298] sd 0:0:0:0: [sda]  
[21061746.863300] Result: hostbyte=0x04 driverbyte=0x00
[21061746.863302] sd 0:0:0:0: [sda] CDB: 
[21061746.863304] cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00
[21061746.863315] end_request: I/O error, dev sda, sector 0
fdisk: cannot open /dev/sda: Input/output error.

I would like to request to replace the harddisk.