Comment 136 for bug 477104
Revision history for this message
| Ciprian Enache (ciprian-enache) wrote | #136 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hello all,
Same problem here after upgrade to "-19". I've tried replacing the wubildr (comment #90). Problem didn't go away.
Managed to boot into "-16" and "-14" manually with [linux , initrd , boot] sequence. When I tried to see grub.cfg from grub a complete mess was displayed.
I've run update-grub2 once and I was still being pushed to the grub2 prompt. I've booted manually again, run update-grub2 and this time I made it to the menu!
Still, when I try to boot into "-19" the system automatically reboots. I will reinstall the package.
My 2cents:
Since people can recover via a manual [linux, initrd, boot] sequence grub.cfg must necessarily be readable until root=(loopX) is executed. And it becomes mysteriously unreadable afterwards.
On the other hand I needed to do update-grub2 a few times until I managed to get the menu back - somehow the way grub.cfg was stored on disk was making all the difference.