Joe Morris wrote:
On 08/22/2008 05:18 AM, David C. Rankin wrote:
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? My guess is your grub.conf is the problem. BTW, I have no idea why you have a separate /boot partition in your setup, but not the problem. To fix it, boot to the rescue system, and reinstall grub to your MBR of sda, i.e. mount /dev/md1 /mnt mount /dev/md0 /mnt/boot mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt
#Then reinstall grub via grub command line: root (hd0,0) setup (hd0) #Then to install in the other drives MBR for possible fallover: root (hd1,0) setup (hd1) quit #That will leave grub command line. exit shutdown -r now That should get you going.
Thank you Joe and Brian, Damn that was frustrating. Evidently, something in the online-update/kernel update wiped out a mbr or something else grub relied on to boot successfully. What was particularly STRANGE was NOTHING was changed in either /boot/grub/menu.lst /boot/grub/device.map or /etc/grub.conf. For my setup with md0=/boot md1=/ md2=/home, the following corrected the problem. (1) boot from the install DVD (2) choose "Rescue System", login as "root" (no password needed) (3) mount all md devices under /mnt, then bind dev/, proc/ and sys/ and chroot as mentioned by Joe above. **Note, you need to mount the md device containing the / (root) filesystem first. Otherwise the /boot and /home directories will not exist: mount /dev/md1 /mnt mount /dev/md0 /mnt/boot mount /dev/md2 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt (4) use grub as mentioned above to fix the mbr on you raid discs (mine were hd0 and hd1): grub
root (hd0,0) setup (hd0) *** few lines of grub output *** root (hd1,0) setup (hd1) *** more lines of grub output *** quit
(5) exit (to exit chroot) and reboot I don't know if this also helped, but I used fdisk to set the /boot and / partitions on each disc as bootable with fdisk /dev/sda and toggling the boot flag with the "a" option. Anyway, it boots normally again. Thanks again for the help. Hopefully this will not happen again on the next kernel update... -- 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