![](https://seccdn.libravatar.org/avatar/82c736e2a6d33a3618c97c928642f703.jpg?s=120&d=mm&r=g)
Well I have a few questions to answer so here goes: I am using lilo as it was the default and I have read numerous places that is easier to work with for the RAID stuff but switching to grub can be done as well if that is the answer. I was testing by removing one of the two drives and rebooting. Now I am in more of a pickle though because last night I found a page explaining how to setup lilo for booting to both drives and it said the following: issue command "lilo -v" and it would take care of it. The output looked like what they showed but after rebooting I experienced the same problem. I then looked a the man pages for lilo and noticed that the -v option said nothing about adding the boot sector to the other drive but the -M option said that was what it did. So I executed a "lilo -M /dev/sdb" and the correct output displayed telling me it had copied the information to the other drive. I then tried to reboot after removing one of the drives but the system didn't boot. I then replaced the drive to try something else and now there is no boot sector on either drive. The system is completely shut down. I tried to go into rescue mode but as usual SUSE doesn't explain how to do anything in rescue mode so now i"m not able to figure out how to mount my / partition to check my lillo settings or to do anything else for that matter. I can't believe that a task that is so simple for everyone else could be this difficult. Actually setting up the RAID proved very simple but the testing of the RAID is where the problems are coming in. I'm beginning to wonder how many people out there are running RAID and never tested what would actually happen if a drive died. Any help as usual is appreciated but still in the (or worse) fix... cybercrypt