"Hazel Lopez" <[EMAIL PROTECTED]> writes: > That would mean, I would leave a /boot partition on any of the disks? > But that wouldn't it undermine the purpose of having raid1 at all? My > machine ought to run via any one of the disks that have the filesystem > on, right?
Note that /boot is system-critical but easily rebuilt. /boot usually contains a) boot loader files (GRUB in this case) and b) kernel image and kernel initrd. It shouldn't be too much of a problem to have /boot in a non-RAID partition. As Orly mentioned in a reply, the problem is GRUB can't read the next stage for the bootloader precisely because that file is in /boot which is in a MD (software RAID) partition, which is not a format that GRUB can read natively. OTOH, it *might* be possible to do this in LILO, although I wouldn't suggest you go that route -- it's a 64-bit server, and I'm not really sure if LILO'll run on it. So, the safest bet is to move /boot outside of the RAID partitions into a separate partition, have /boot flagged as bootable. -- JM Ibanez Software Architect Orange & Bronze Software Labs, Ltd. Co. [EMAIL PROTECTED] http://software.orangeandbronze.com/ _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
