After adding initrd entries to menu.lst - which have been there for all old
hardy kernel entries but none of the initrepid kernels - booting is fine again.
Although update-grub has been run several times before, e.g. when reinstallting
kernels, it did not change menu.lst accordingly. Now back in
I just found the initrd entries missing in the generated grub menu.lst
and testing in qemu works so far.
--
boot from crypto disk + md/raid1 fails after upgrade
https://bugs.launchpad.net/bugs/293057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
I used qemu and a hardy live cd to boot grub and the new 2.6.27 kernel. Please
find the log attached.
It does not hint any access to md-raid.
** Attachment added: boot.log
http://launchpadlibrarian.net/19390368/boot.log
--
boot from crypto disk + md/raid1 fails after upgrade
provisionally assigning to the linux source package, but might be a grub
bug
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
--
boot from crypto disk + md/raid1 fails after upgrade
https://bugs.launchpad.net/bugs/293057
You received this bug notification because you are a member
possibly related?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393728
--
boot from crypto disk + md/raid1 fails after upgrade
https://bugs.launchpad.net/bugs/293057
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
