December 1st, 2008, 11:11 AM
Dual-Booting and RAID0
recently, i've been looking into RAID0. initially i assumed that if RAID0 were implemented in the hardware then it would be invisible to the software, and so i assumed that all software, including the boot-loader, would just see a single HDD.
although, after looking into it. it now seems that this is not the case and using RAID0 can cause problems for the boot-loader. therefore, i was wondering if any of you guys have dealt with the problem and how you overcame it?
i am also interested in what is generally considered the best setup for a RAID0 system? i am currently considering a setup where i have 3 HDD-s the first of which acts as a normal HDD (i.e. no RAID) and is the drive from which i boot OS-s, then having the other 2 HDD setup with RAID0 and using them to store video and games etc.
Last edited by Threads; December 1st, 2008 at 11:14 AM.
December 1st, 2008, 08:44 PM
December 2nd, 2008, 10:47 AM
thanks for your advice. i understand that with RAID0, drives are striped together, thus if one drive fails all the data on the RAID0 array is corrupted. i have looked at RAID01 and RAID10 as you suggested, which look like really good solutions for servers. although as i'm interested in using RAID0 on my home gaming machine, i'm not too conserned with lose of data. as drive failure is pretty rare, and i keep back-ups and i can re-install my games. i'm not so interested in increasing drive size, my main focus is to increase performance.
you said that RAID0 should not affect the bootloader or OS, which is what i assumed, providing RAID0 is implemented at the hardware layer and setup in the BIOS. but i have read many posts on various disscussion boards, that speak of RAID0 causing problems with LILO and GRUB. i also read a tutorial where a driver had to be installed before the Windows Installer would install Windows on a RAID0 drive. therefore i was just wondering, when you said that "RAID0 should not affect the bootloader or OS", have you experience of this being true or are you simply making the same assumption as i did?
i am very grateful for any help and advice that you can give me.
December 2nd, 2008, 02:32 PM
With Linux: I would backup /boot/grub. leave the file device.map alone for now. Decide whether you want to raid the entire drive or just partitions of your choosing. use mdadmn software raid to setup your raid array. Copy the magic numbers it gives you and place them into mdadm.conf. Next edit both fstab and mtab to point to /dev/mdx where x is the number representing mounted paired drives. Recompile the kernel and it will do the magic for you. It recreated initrd to load your HDD drivers and automatically create the raid. last, use grub root and grub setup to make all your drives bootable.
Originally Posted by Threads
BTW, Raid 0 is junk. Raid 1+0 since you have a spare drive. mdadm knows how to handle that. Your hardware raid0 in bios is crap. They are kissing Microcrap shlt.
December 7th, 2008, 03:41 PM
In which case you don't want RAID, as it will reduce performance.
i'm not so interested in increasing drive size, my main focus is to increase performance.
Yes, you are prompted to hit F6 to activate a RAID capable PC. You then insert the CD that came with the motherboard to install the software. The reason is that the MoBo will support non-RAID and RAID but the default is non-RAID. It doesn't matter if it is RAID0, just that it is a RAID array.
i also read a tutorial where a driver had to be installed before the Windows Installer would install Windows on a RAID0 drive.
December 9th, 2008, 05:01 PM
A Gaming PC, eh? Your weakest link is your network connection.