We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Hi DaveM,
Thanks for reporting this to us, and sorry no-one got back to you. Have you
experienced this problem in a supported version of Ubuntu, i.e. Hardy 8.04 LTS
onwards? If you need help upgrading, you can follow the instructions at
https://help.ubuntu.com/community/EOLUpgrades Thank you.
*
I had a similar thing happen when updating from kernel 2.6.24-2 to
2.6.24-3 using an otherwise (mostly) Gutsy 7.10 installation. The update
got both the root drive AND the UUID wrong in menu.lst and so nothing
would boot.
The update set all images to boot off hd0,6 (the last drive in the
system, a
Thank your for your report
** Changed in: grub (Ubuntu)
Sourcepackagename: None => grub
--
Kernel update to 2.6.20-16, won't boot now (grub)
https://bugs.launchpad.net/bugs/158442
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Description changed:
- The latest update I got for Feisty upgraded the kernel to 2.6.20-16. The
- system wouldn't boot afterwards. I replaced menu.lst with the backup
- copy and it booted ok. I then tried just replacing all "2.6.20-15" with
- "2.6.20-16" and it's still ok. The menu.lst prior t
