Re: [gentoo-user] Grub broke out of the blue
Am Dienstag, 17. Februar 2009 05:44:07 schrieb Stroller: > To avoid automounting and autoinstalling with /boot, > just export the DONT_MOUNT_BOOT variable. There's still a bug open to remove this stupid behaviour. BTW: Once it's in your MBR, you can just "paludis --uninstall grub" (or whatever is its emerge equivalent ;-) ) Bye... Dirk signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Grub broke out of the blue
Nikos Chantziaras wrote: I've no idea how it broke, but after an emerge --sync, a kernel (gentoo-sources) update was there. After I compiled the kernel, I did the usual "make modules_install && make install". I edited grub.conf only to the point of changing the booted kernel to the new one (just a matter of changing -r1 to -r2 at the end of the kernel filename). I reboot, Grub stops working. It just displays "GRUB" and hangs there. I normally don't edit my grub.conf, instead I have entries for vmlinuz and vmlinuz.old (make install updates these). When I do edit grub.conf, I always run grub-install afterwards. I don't know if this is necessary, but it's my habit... HTH, Roy
Re: [gentoo-user] Grub broke out of the blue
On Tue, 17 Feb 2009 06:17:07 +0200, Nikos Chantziaras wrote: > I've no idea how it broke, but after an emerge --sync, a kernel > (gentoo-sources) update was there. After I compiled the kernel, I did > the usual "make modules_install && make install". I edited grub.conf > only to the point of changing the booted kernel to the > new one (just a matter of changing -r1 to -r2 at the end of the kernel > filename). I reboot, Grub stops working. It just displays "GRUB" and > hangs there. Could you have inadvertently made more of a change to grub.conf than that? Grub is notoriously fragile when it comes to its config file? Why did you edit it in the first place? As you used make install,you will have symlinks from vmlinuz and vmlinuz.old to the new and previous kernels. Use these in GRUB and there's no need to edit anything. -- Neil Bothwick File Not Found - Loading something that looks similar signature.asc Description: PGP signature
Re: [gentoo-user] Grub broke out of the blue
On 17 Feb 2009, at 04:17, Nikos Chantziaras wrote: I've no idea how it broke, but after an emerge --sync, a kernel (gentoo-sources) update was there. After I compiled the kernel, I did the usual "make modules_install && make install". I edited grub.conf only to the point of changing the booted kernel to the new one (just a matter of changing -r1 to -r2 at the end of the kernel filename). I reboot, Grub stops working. It just displays "GRUB" and hangs there. What might have cause this? $ cat /var/log/portage/elog/sys-boot:grub-0.97-r6:20090117-194927.log LOG: preinst To avoid automounting and autoinstalling with /boot, just export the DONT_MOUNT_BOOT variable. WARN: postinst *** IMPORTANT NOTE: you must run grub and install the new version's stage1 to your MBR. Until you do, stage1 and stage2 will still be the old version, but later stages will be the new version, which could cause problems such as an unbootable system. This means you must use either grub-install or perform root/setup manually! For more help, see the handbook: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=10#grub-install-auto LOG: postinst To interactively install grub files to another device such as a USB stick, just run the following and specify the directory as prompted: emerge --config =grub-0.97-r6 Alternately, you can export GRUB_ALT_INSTALLDIR=/path/to/use to tell grub where to install in a non-interactive way. $ Stroller.
[gentoo-user] Grub broke out of the blue
I've no idea how it broke, but after an emerge --sync, a kernel (gentoo-sources) update was there. After I compiled the kernel, I did the usual "make modules_install && make install". I edited grub.conf only to the point of changing the booted kernel to the new one (just a matter of changing -r1 to -r2 at the end of the kernel filename). I reboot, Grub stops working. It just displays "GRUB" and hangs there. What might have cause this? /boot is a 50MB ext3 partition with 14MB free. I had to boot from a live CD and make sda1 bootable (Windows XP) so I can get online and burn a repair CD that supports ext4 (/).
