I had a similar problem which I originally reported as a kernel issue.
After 2.6.17-7 (8 and 9) the system would not boot with the error:

Begin: Waiting for root file system

My /etc/fstab shows:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda10 -- converted during upgrade to edgy
UUID=67f18326-0ffc-4835-9de5-67d173f6ca84 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5 -- converted during upgrade to edgy
UUID=2aed16dc-cfb2-49c7-b656-ae238b383997 /media/sda5 ext3 defaults 0 2
# /dev/sda6 -- converted during upgrade to edgy
UUID=f8048a1c-68e7-4f26-9d6e-0e43de790488 /media/sda6 ext3 defaults 0 2
# /dev/sda7 -- converted during upgrade to edgy
UUID=2f0175ef-bd42-41e2-8e32-c92a155da5ab /media/sda7 ext3 defaults 0 2
# /dev/sda9 -- converted during upgrade to edgy
UUID=2854cb27-da6e-44bd-ba7c-18879b5621e3 /media/sda9 ext3 defaults 0 2
# /dev/sdb5 -- converted during upgrade to edgy
UUID=6707952b-349c-4cc4-96e4-34147b25930d /media/sdb5 ext3 defaults 0 2
# /dev/sda8 -- converted during upgrade to edgy
UUID=fb837170-93eb-45bf-a8e5-6b7e8f0f4d06 none swap sw 0 0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0

But in /boot/grub/menu.lst the relevant boot line showed:

/boot/vmlinuz-2.6.17-9-generic root=/dev/sda10 ro

If I replaced this with the "right" root location according to
/etc/fstab i.e. with

/boot/vmlinuz-2.6.17-9-generic
root=UUID=67f18326-0ffc-4835-9de5-67d173f6ca84 ro

then the system booted without problem.

It seems that in upgrading from dapper the filesystem or partition
information in /etc/fstab has been changed but this change has not been
reflected in the grub entry.

Following a suggestion by Ben Collins I removed kopt lines in 
/boot/grub/menu.lst and ran grub-update. This had the effect of replacing 
root=/dev/sda10 with root=/dev/hda1 which was veru strange and this also did 
not help the system boot.

I think this is a major bug because I installed a standard dapper and
then did a standard upgrade to edgy and the sytem did not boot.

-- 
[Edgy] Wrong boot disk parameter since 2.6.17-7
https://launchpad.net/bugs/61578

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to