> From: "Bruno Prior" <[EMAIL PROTECTED]> > > > Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP and > > > two 40G > > > 7200rpm disks. One disk on the main controller, the other on the > > > onboard promise controller. > > > > > > Booted mandrake 9.0 disk #1, partitioned as follows: > > > > > > /dev/hda1 256M - /boot [ext2] > > > /dev/hda2 24G - added to md0 > > > /dev/hda3 1G swap > > > /dev/hds4 reat - addes to md1 > > > > > > /dev/hde1 256M - /tmp [reiserfs] > > > /dev/hde2 24G - added to md0 > > > /dev/hde3 1G swap > > > /dev/hde4 reat - addes to md1 > > > > > > md0 is mode 0 / > > > md1 is mode 1 /home > > > > > > Installed mandrake, went fine, rebooted, failed ! > > > > I've been using Mandrake for a while (since the 7.x versions), and I am > > a huge admirer. However, Mandrake's implementation of software-RAID is, > > and has been as long as I have used it, complete pants! It is, by a long > > chalk, the worst thing about the distro. > > > > Software-RAID has been fantastically simple since Ingo Molnar wrote the > > new raidtools several years ago. Auto-recognition makes everything very > > easy. But as far as I can tell, Mandrake have yet to get to grips with > > auto-recognition. It seems that they are still trying to fire up the > > arrays from rc.sysinit. This is presumably because they have always left > > RAID support as modules, rather than building it into the default > > kernels. This is OK, so long as none of the files involved in booting > > are on any of your arrays. As soon as you try something like root-RAID, > > it all falls down. Or at least, this is my interpretation of why every > > time I upgrade my root-RAID Mandrake-based server, I have to remember to > > leave behind a purpose-built kernel and add an extra entry to lilo.conf > > to point to it. If you forget to do this, you are stuffed. Every version > > of Mandrake I have used has kernel-paniced on bootup when using the > > default kernels and initrds on my root-RAID system. As soon as you use a > > kernel with RAID-support built in, it boots fine. This says to me that > > Mandrake does not support root-RAID. > > > > If I were setting up a root-RAID system based on Mandrake, I would do > > the following (I am assuming that this is on RAID-1 or -5, it's not a > > good plan to put / on RAID-0 anyway): > > > > Install / originally to one of the partitions that will be in the > > root-RAID. Leave the other partitions in the array unassigned for now. > >
Funny, I have no problem what so ever with the soft raid, and I have 3 systems set up this way, 2 with scsi disks, and one with ide disks... my setup: RAID -1 /dev/md0 -> /boot (sda1,sdb1 or hda1,hdc1) /dev/md1 -> / (sda6,sdb6 or hda6,hdc6) /dev/md2 -> /usr (sda7,sdb7 or hda7,hdc7) /dev/md3 -> /var (sda8,sdb8 or hda8,hdc8) /dev/md4 -> /home (sda9,sdb9 or hda9,hdc9) the swaps are on /dev/sda5 and /dev/sdb5 (or /dev/hda5 and /dev/hdc5) (the swaps could also be on raid, but I haven't felt the need to place them there...) and btw. take a look at lilo docs (/usr/share/doc/lilo-22.3.2/README.raid1.bz2) at the beginning it states: RESTRICTIONS ============ Only RAID1 is supported. LILO may be used to boot a system containing other RAID level partitions, but it may not be installed on any RAID partition other than RAID 1. Thomas *** T�m� viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! ***
