How to turn an existing drive into a raid one?

Portal Home > Knowledgebase > Articles Database > How to turn an existing drive into a raid one?

Posted by martin33, 10-18-2013, 06:03 PM
Hi, I just saw there were a bug in the ovh provisioning tool, and i got a dedicated server with material raid LSI with only the first hard disk formatted, with the system on it. root:~# mdadm --detail /dev/md1 mdadm: cannot open /dev/md1: No such file or directory root:~# mdadm --detail /dev/md0 mdadm: cannot open /dev/md0: No such file or directory We already created vm's on this server. Should take a very long time to migrate all those data : it's over 2Tb. So i am wondering if there is a way for me to create this LSI raid without loosing any data? Let me know if you require the output of some commands in order to help me Here is an fdisk : fdisk -l WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 255 heads, 63 sectors/track, 243133 cylinders, total 3905945600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 3905945599 1952972799+ ee GPT Partition 1 does not start on physical sector boundary. Disk /dev/mapper/vps-vs1001: 42.9 GB, 42949672960 bytes 255 heads, 63 sectors/track, 5221 cylinders, total 83886080 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00032c86 Device Boot Start End Blocks Id System /dev/mapper/vps-vs1001p1 2048 83886079 41942016 83 Linux Disk /dev/mapper/vps-vs1002: 10.5 GB, 21474836480 bytes 255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000846dc Device Boot Start End Blocks Id System /dev/mapper/vps-vs1002p1 2048 41943039 20970496 83 Linux Disk /dev/mapper/vps-vs1003: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders, total 62914560 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0005fa9e Device Boot Start End Blocks Id System /dev/mapper/vps-vs1003p1 2048 62914559 31456256 83 Linux Disk /dev/mapper/vps-vs1004: 10.5 GB, 21474836480 bytes 255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00007263 Last edited by martin33; 10-18-2013 at 06:09 PM.
Posted by serve-you, 10-18-2013, 09:01 PM
mdadm is a software raid tool. You will not see a hardware raid from the OS without using the hardware card's software tool. You would know if it was NOT setup, by there being an sda & sdb apparent to the OS via fdisk. If it is setup, the OS is only going to see a single disk since that's what the card is presenting it.