[opensuse] problematic grub
![](https://seccdn.libravatar.org/avatar/f0ad86a443e23d8412160985c73d3b1b.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a computer with three grubs in the main disk, each on a separate "boot" partition (1, 2, 3). The code in the MBR is set to boot whichever partition is active - ie, the "generic" mbr code. This was working till the moment I used "grub-install" on partition 1. If the active partition is #3, it boots fine. In the grub menu #3, I have an entry to boot grub #1: title Bombadil -- (via configfile in /dev/sda1) root (hd0,0) configfile /boot/grub/menu.lst If I use this entry, the partition #1 grub (bombadil) loads, and I can boot that oS. Therefore, its menu.lst is correct. In #3 I have another entry: title Bombadil -- via chainload - changes active boot to /dev/sda1 rootnoverify (hd0,0) makeactive chainloader +1 This one, which worked, does not work now. What it does is mark partition #1 as bootable, then boot it. This suggests that the boot code in #1 is incorrect. The symptoms is that, I see a message like "grub loadin stage something" (goes too fast for me to read it), blank screen, then the bios boot scren, and repeat, for ever. If I boot #1, and attempt to reinstall grub, it works, but later it fails to boot as described above: bombadillo:~ # grub-install GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> setup --stage2=/boot/grub/stage2 --force-lba (hd0,0) (hd0,0) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal) Running "embed /boot/grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal) Running "install --force-lba --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,0) /boot/grub/stage2 p /boot/grub/menu.lst "... succeeded Done. grub> quit bombadillo:~ # If I run "yast2 bootloader" and request it to reinstate the boot code, or change it to boot from root partition, exit, run again, change nopw to boot from boot partition (which is the sequece to force yast to rewrite things), it fails to boot later, same as described above. If I run the automated rescue (11.2 retail DVD), and indicate I want to correct the boot loader, it insists on checking the filesystem (which is entirely correct), then insists on repairing fstab, which was correct, and in fact, destroys some entries that worked, and now don't. I had to remake fstab by hand. And worse, it does not repair boot from partition #1. How on earth can I FORCE Yast or grub to reinstall grub properly and sucesfuly? Short of reinstalling Suse, which is the only remaining idea, then replacing all files from backup. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkts2s4ACgkQtTMYHG2NR9VqqQCfT+9/9uqrfNDdG9/NMxORqD2e epIAoI+FdqcFxY1MJhlV8mxuvcMC3EDu =L2s1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/247f3737bfdd07c80a5411399e9a504c.jpg?s=120&d=mm&r=g)
Carlos E. R. wrote:
If I run "yast2 bootloader" and request it to reinstate the boot code, or change it to boot from root partition, exit, run again, change nopw to boot from boot partition (which is the sequece to force yast to rewrite things), it fails to boot later, same as described above.
If I run the automated rescue (11.2 retail DVD), and indicate I want to correct the boot loader, it insists on checking the filesystem (which is entirely correct), then insists on repairing fstab, which was correct, and in fact, destroys some entries that worked, and now don't. I had to remake fstab by hand. And worse, it does not repair boot from partition #1.
How on earth can I FORCE Yast or grub to reinstall grub properly and sucesfuly? Short of reinstalling Suse, which is the only remaining idea, then replacing all files from backup.
Carlos, I had some trouble with grub recently. I confess I haven't read your post in detail and also I don't profess to be a grub expert. However I can mention one fascinating fact I observed during my tribulations. There are many options on the 11.2 DVD, reached by different paths, that look similar but actually result in a different environment (i.e. a different kernel running with the same file system). For example I found that entering the repair system by first going to the install menu and then selecting repair worked, whilst other routes to the repair system did not work. Perhaps that will help you sort out your problem. I found the whole menu system and the dialogs for managing grub to be too confusing. It seemed really difficult to be sure you'd selected exactly the correct options etc. So I concentrated on trying to get into a grub session and then doing everything from the grub shell. But you still need to watch for any drive mapping issues. HTH, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Carlos E. R.
-
Dave Howorth