On Wed, 2003-09-03 at 00:36, Gideon N. Guillen wrote: > > > 2. Second problem is if I simulate a disk failure on my Primary > > > IDE, my secondary IDE won't boot. I read from a RH7.1 manual the > > > I have to use the LILO loader but i still get the same problem. > > > I also set my /boot partition to use RAID 1. > > > > > > sortof a chicken and egg problem, whereas i've never figured this > > out myself, i would mention this as the second best option: > > config /boot and /etc NON-raid, the rest of them in raid. > > remember, the raid config itself lives in /etc. And you want > > to recover that directory in case of emergency. (if its on > > raid for xample you'll need a kernel that understands raid > > just to read /etc). those are easy to backup anyway. > > Actually it's ok to put the /etc and /boot on RAID. I think the reason > why the other disk won't boot is that no boot loader has been installed > on the second hard disk. Software RAID on Linux is on a per partition > basis, not per disk. So on RAID 1, you're mirroring partitions, not the > whole disk itself. The boot loader installed on the 1st hard disk is not > copied to the 2nd hard disk (if you installed LILO or Grub on the MBR).
sure..but my point was that /boot was on a raid partition, but in order to mount that he'll need a kernel that recognizes...raid partitions. the chicken & egg part comes in when you realize that the kernel itself is on /boot...not to mention raidtab.conf which is on /etc (another raid partition?) so on manual recovery, however he brings up the kernel he'd better be mounting /dev/md0 instead of /dev/hda1. just wanted to point that out, since in case of a disaster i wouldnt want to be in a position to figure how the partitions should look like.(especially if i cant find /etc/fstab and /etc/raidtab.conf). that being said, i believe no longer an issue nowadays since kernels come with built-in raid support already (uh..i think). there used to be a ROOT-RAID howto on this, (possibly now obsolete). personally though i would want /etc and /boot to be on a simple filesystem where i can find them quick in an emergency. Its also possible i would yank the disks out of desperation and mount it on a different machine, just to get the files..i mean anything can happen in an emergency.. just wanted to point that out as a caution, though i'm sure the newer kernels would "see" the /dev/md's just fine. if this entire thing is wrong..my apologies, i've setup raid 3 years ago and havent changed my style...since my server was so stable i just leave it alone and havent really kept up with technology... anyhow.. have a nice day JondZ <[EMAIL PROTECTED]> -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
