This is my problem. While setting up the raids, it wouldn't let me raid the /boot parition.
Coz Linux needs to access the boot partition in order to load the raid drivers persumably.
This how the paritions are set up at the moment. I've obviously got a partition spare (sdb2) the same size as sda2 with nothing on it.
/dev/md0 / /dev/sda2 /boot /dev/md1 /home /dev/md2 /export
You don't say how large your partitions are. If you want a relatively bombproof system then - 1. keep boot and raid partitons on separate drives. 2. keep 2 boot partitions on separate drives. So assuming disk space is not an issue, you have: sda2 /boot sdb2 /boot copy md0 / raid stack etcetc You need a disaster recovery plan, whch involves disabling sda2 and verifying you can boot using sdb2. I also wonder whether it's wise to have all system files and software on the raid partition? Once the machine's set up, system folders don't change all that much. User data does, and that's what it's vital to cover. I would be tempted to raid the "home" area. -- ******************************************************************************** All mail sent and received may be examined to prevent transmission of unacceptable material. Wellington College does not accept responsibility for email contents. Problems to postmaster@wellington-college.berks.sch.uk. Website: http://www.wellington-college.berks.sch.uk ********************************************************************************