The only way I found around this so far is that I have created /boot in a normal partition which is 100m and ensured that yast creates the same partition on the other disk and mounds it as /bootmirror. In my postinstall I now have a script which takes a backup of /boot, unmounts it and figurtes out which devices are under /boot and /bootmirror. It then converts the two partitions to a raid1, creates the fs and mounts it under /boot. Once the contents of /boot are in place it will do a "lilo -b /dev/sda ; lilo -b /dev/sdb ; lilo -b /dev/md0" This way Lilo will write a boot record to both disks and the raid device. Obviously I do all the essential munging of /etc/fstab and /etc/lilo.conf as well. Anybody got a better solution let me know. - I also have to do a similar thing to be able to create the swap space within a logical volume. Yast seems to be incapable of doing that as well Regards Hubba On Tue, 10 Dec 2002, Frank Pascher wrote:

Date: Tue, 10 Dec 2002 08:43:04 +0100 From: Frank Pascher <fpascher@mpifr-bonn.mpg.de> To: suse-autoinstall@suse.com Subject: [suse-autoinstall] Raid 1

Hi,

I'm having massiv problems with software Raid 1.

1.: There is no way to set it up via autoyast2 menu. 2.: If I set it up manually it doesn't work.

Does anyone have a working example ?

Next thing is:

On some computers Software Raid 1 is working without problems (manually installed); on the next machine there is no boot.

Any help is appreciated.