LaMont's failure is much more straightforward to understand, From
/var/log/installer/syslog:
Feb 10 17:24:37 grub-installer: info: Installing grub on '(hd0)'
Feb 10 17:24:38 grub-installer: info: grub-install supports --no-floppy
Feb 10 17:24:38 grub-installer: info: Running chroot /target grub-install
--no-floppy "(hd0)"
Feb 10 17:24:38 grub-installer: Probing devices to guess BIOS drives. This may
take a long time.
Feb 10 17:24:38 grub-installer: Unknown partition table signature
Feb 10 17:24:38 grub-installer: Unknown partition table signature
Feb 10 17:24:39 grub-installer: Searching for GRUB installation directory ...
found: /boot/grub
Feb 10 17:24:40 grub-installer: Unknown partition table signature
Feb 10 17:24:40 grub-installer: Unknown partition table signature
Feb 10 17:24:41 grub-installer: Unknown partition table signature
Feb 10 17:24:41 grub-installer: Unknown partition table signature
Feb 10 17:24:42 grub-installer: Unknown partition table signature
Feb 10 17:24:42 grub-installer: Unknown partition table signature
Feb 10 17:24:43 grub-installer: Unknown partition table signature
Feb 10 17:24:43 grub-installer: Unknown partition table signature
Feb 10 17:24:44 grub-installer: Unknown partition table signature
Feb 10 17:24:44 grub-installer: Unknown partition table signature
Feb 10 17:24:45 grub-installer: The file /boot/grub/stage1 not read correctly.
Feb 10 17:24:45 grub-installer: error: Running 'grub-install --no-floppy
"(hd0)"' failed.
Feb 11 05:24:00 main-menu[3051]: WARNING **: Configuring 'grub-installer'
failed with error code 1
Feb 11 05:24:00 main-menu[3051]: WARNING **: Menu item 'grub-installer' failed.
Feb 11 05:24:01 main-menu[3051]: INFO: Modifying debconf priority limit from
'high' to 'medium'
[...]
Feb 11 05:24:23 main-menu[3051]: INFO: Menu item 'nobootloader' selected
So yes, evidently grub-installer failed to complete, and you opted to
skip bootloader configuration rather than resolve the underlying error.
That's always going to cause problems with the bootloader integration.
Ultimately, that particular problem should be fixed by having the
bootloader install a hook to /etc/kernel/post{inst,rm}.d/ instead of
relying on the installer to modify /etc/kernel-img.conf.
--
jaunty to karmic upgrade failed to update menu.lst (update-grub missing from
kernel-img.conf)
https://bugs.launchpad.net/bugs/470265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
