Hi This may very well not be an AutoYaST problem, but ... I am trying to duplicate a problem at a customer that has a RAID1 setup with /boot, / and other partitions on md. For this I install SLES10SP2 as step one and upgrade to SLES10SP3 as step2. Doing this manually works fine, but when installing SP2 or upgrading to SP3 using AutoYaST, the system fails to boot and reports "Invalid partition table" before even reaching the grub menu. Whether I use initialize true on sda, sdb and md in the installation profile or not, makes no difference. The strange thing is when I install SLES manually after being in the error situation, it recognizes all partitions and RAID setup. When booting into rescue mode and doing an fdisk -l it sees all sd{a,b}* partitions correct, bootable is /dev/sdb1. It also lists the /dev/md{0-4], but only md0 is claimed to contain a valid partition table (though not containing any partitions). md1-4 are marked as invalid. mdadm --scan --detail print shows that all RAID devices contain two devices. /boot/grub/menu.lst refers to /dev/md? and I have tried configuring device.map to map to both /dev/sd? and /dev/disk/by-id/*. Another funny observation : Switching the bootable flag from sdb1 to sda1 changes the boot error from "Invalid partition able" to "No operating system" So it looks like the RAID setup somehow does not make it to disk when using AutoYaST. Any ideas ? Thank you. Best regards Andreas Taschner Designated Support Engineer Novell -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org