Bug#422459: same problem here, no software raid

[Statu Nascendi]

Seems like somewhere in the process of upgrading to the last kernel
image, kernel entry gets messed up in menu.lst, putting the wrong
root=.... For example, before upgrade I had root=/dev/hda3, but now
probably is /dev/hda1(i can't really log on to that system anymore,
being a remote host.). Anyway, same thing happened when I upgraded from
sarge to etch 2-3 weeks ago... (only that i forgot bout it today and
happily upgraded the kernel and rebooted without correcting menu.lst
:D). Can you please specify what actual script does modify menu.lst
while upgrading a kernel? Thanks.

Note that i did an aptitude update, then aptitude upgrade today in order
to upgrade to the last packages.

Oh... and the system ends up in busy-box after some /dev/hda... no such
file or directory, /dev/.static no such file or directory, etc, etc...
But basically the problem is in the way the upgrading process updates
menu.lst.


Have a nice day.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20070510/a1382ee1/attachment.html