Read Carefully:
I have a PRODUCTION web server hosted by OVH that has a bad disk drive in one of the two drive arrays.
I DO NOT want to lose any data. I am not sure if the problem is the boot drive or the mirrored drive
here is that error message they sent:
~~~
A DegradedArray event had been detected on md device /dev/md2.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
md2 : active raid1 sda2[0]
61438912 blocks [2/1] [U_]
md3 : active raid1 sda3[0]
1,885,926,336 blocks [2/1] [U_]
unused devices: <none>
~~~
when I get ion the server and do a parted -l I get this:
root@pools:~# parted -l
Model: ATA HGST HUS724020AL (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 20.5kB 1049kB 1029kB primary bios_grub
2 2097kB 62.9GB 62.9GB ext4 primary raid
3 62.9GB 1994GB 1931GB ext4 primary raid
4 1994GB 2000GB 6290MB primary
Model: Linux Software RAID Array (md)
Disk /dev/md2: 62.9GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 62.9GB 62.9GB ext4
Model: Linux Software RAID Array (md)
Disk /dev/md3: 1931GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 1931GB 1931GB ext4
~~~
here is their instruction page on how to rebuild the raid array. I have root access to this server.
I need someone that will be available AT ANY TIME as soon as they replace the drive. P I can schedule the drive to be replaced in the next two days - you must be available do do the work as soon as the drive is replace - even if it's the middle of the night. No excuses.
I will need help identifying for them which drive is bad also.
this is the email on how to identify the drive an how to fix things.
Provide the serial number of the disk(s) being changed (note - If this number can’t be retrieved, we would need the serial numbers of all the disks NOT being replaced. Guide: [login to view URL]).
RAID 1 – Two disks in RAID 1 will ensure a first level of redundancy. In the case one of the disks fails, you will have to resynchronize the RAID with the brand new disk (in the case of software RAID).
This could take several hours depending on the amount of data on your drives. Hardware RAID will usually resync on its own, but making sure it does will only ensure you lose no data in the whole process.
Send us your response as soon as possible, and in return we will be able to change your disk promptly. Normally, this operation should take no more than 30 minutes. Please note that OVH will not be liable in the event of data loss resulting from the replacement of a hard drive.
Here is a guide to help you with rebuilding the software raid: http:// [login to view URL]
Here is a guide to help you with rebuilding the hardware raid: http:// [login to view URL]