Well, at least when this situation happens there should be a big warning
*and* a link to the page you just mentioned. I was not aware of it.
Thanks,
--
edgy does not boot
https://bugs.launchpad.net/bugs/61113
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It is recommended that you use UUIDs instead of /dev/hde1 etc. . . to
prevent this type of situation. You can learn more about using UUIDs at
https://wiki.ubuntu.com/UsingUUID . Thanks.
** Changed in: Ubuntu
Assignee: (unassigned) = Brian Murray
Status: Needs Info = Rejected
--
If you go into /boot/grub/menu.lst and change hde to sde and reboot does
it boot than? change the line in the kernel that you are trying to boot
to.
** Changed in: Ubuntu
Status: Unconfirmed = Needs Info
--
edgy does not boot
https://launchpad.net/bugs/61113
--
ubuntu-bugs mailing list
OK-- I'll try that.
Meanwhile I have new info: I tried a fresh install from knot3 on that
same computer. It worked... until I updated to the latest packages. I
think I saw at least the kernel being upgraded.
I'll try /dev/sde1 but I find it strange since my disks are all udma.
Anyway, thanks for
That's fixed!
Your solution did *not* fix my problem-- but looking more closely at the
messages I saw that the new kernel found an unexpected hda drive.
In fact I have an unusual config with two on-board disks and one off-
board (on a PCI controller). Previous kernels named the on-board disks
