Listmates, Latest fresh install of 11.0 has been quite frustrating. The original install went fine and the system booted fine. After 2nd online-update (1st update just updated zypper/package mgmt) the machine is left unbootable with GRUB ERROR 17. I have included as much information about the setup as I can manually type from within (Rescue# ). Why did online update break the boot loader config and how do I fix grub now? The setup is a simple 2-disk ATA md raid1 install on an older i386 box (abit kt7, 1G of ram, 2 250G Maxtor drives). Both disks are partitioned identically: sda1 100M primary sda5 20G logical sda6 2G swap sda7 220G logical sdb1 100M primary sdb5 20G logical sdb6 2G swap sdb7 220G logical md0 (sda1 sdb1) as /boot md1 (sda5 sdb5) as / md2 (sda7 sdb7) as /home As noted the fresh install booted fine. I was able to configure kde, and do online updates. The reboot from the 2nd online update which included the kernel update is where the problem started. I didn't mess with anything in Yast except to configure the network card and to do an online update. Here is the configuration information: Current grub setup: ---menu.lst--- root(hd0,0) kernel /vmlinuz-2.6.25.11-0.1-pae root=/dev/md1 resume=/dev/sda6 splash=silent showopts vga=0x317 ---device.map--- (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb ---grub.conf--- setup --stage2=/boot/grub/stage2 (hd1,0) (hd0,0) quit ---grub.conf.old (this was in /etc from the install - changing made no difference)--- setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0) setup --stage2=/boot/grub/stage2 (hd1,0) (hd0,0) quit Booting to the 11.0 rescue system, cat proc partitions shows md0, md1 and md2 just fine. mdadm reports that all md raids are fine and are using the right partitions. Mounting the drives with: mount /dev/md1 /mnt mount /dev/md0 /mnt/boot mount /dev/md2 /mnt/home all works fine. I can access and edit all the files. However for some reason the grub config is gone and it fails during the boot sequence. I have tried manually starting the installed system from the cd, but selecting sda5 or sdb5 or sda1 or sdb1 results in nothing. I have tried specifying /dev/sda5 and /dev/sdb5 in grub menu.lst, but nothing works. It seems like in 10.3 I could manually boot the system by choosing the root partition on either drive in the raid and it would work. Not so here. I have been unsuccessful using grub-install from rescue mode and I can't get yast to work with everything mounted under /mnt. I need help. Anybody know what voodoo is required to straighted grub out in this situation? Anything else I can provide? Thanks in advance for any help or wisdom you can provide. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org