No, not anymore. As far as I can see, this was most probably a mistake
on my part. Somehow.
So I am closing this INVALID.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
chainload grub2 fails on /boot on different partition
https://bugs.launchpad.net/bugs/385055
You receiv
Thank you for taking the time to report this bug. Can you reproduce
this in Karmic Alpha 6 or greater?
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
chainload grub2 fails on /boot on different partition
https://bugs.launchpad.net/bugs/385055
You received this bug notificatio
ran apt-get --purge remove grub-pc, the files were still left in. Then
went into a sequence of reinstall/reboot/uninstall/reboot, and at one
point removed 'grub' instead of 'grub2' -- as such completely destroying
my case...
I will build up a VM, and try again.
--
chainload grub2 fails on /boot
I haven't had a chance to look at your log yet, but regarding
installing/removing grub2, have a look at 'apt-cache show grub2'. Here's
an edited version to emphasise the relevant bits:
Package: grub2
Depends: grub-pc
Description: GRand Unified Bootloader, version 2 (dummy package)
This is a dummy
Weird. Wrote a nice comment here, formatted nice (not beautiful, but
still nice), saved and... it vanished. Ah well. I will try again, but
now short & direct.
Looking at the update-grub output I can see the chainload entry being
correctly created. Here is my guess: the grub2 installation does not
** Attachment added: "update-grub output"
http://launchpadlibrarian.net/27693899/update-grub.out
** Changed in: grub2 (Ubuntu)
Status: Incomplete => New
--
chainload grub2 fails on /boot on different partition
https://bugs.launchpad.net/bugs/385055
You received this bug notification b
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27677074/Dependencies.txt
** Description changed:
Binary package hint: grub2
Installed GRUB2, selected chainloading to verify.
- GRUB2 installation seems to look like:
+ GRUB2 installation on /boot/grub/menu.lst s
