*** This bug is a duplicate of bug 439604 ***
https://bugs.launchpad.net/bugs/439604
I am not convinced it is a duplicate, as I saw this problem on a
separate machine -the OS was not booting when referencing disks by UUID,
but only by /dev/sdXX entries:
http://www.1060.org/blogxter/entry?publicid=E9A13D9C371E4C17503E0762175B8F7D
Narchya, boot from the CD in the "try out ubuntu" mode, then mount the
hard disk in that, you can edit fstab there.
The fix was to edit fstab so that instead of asking for things by UUID,
going back to asking for them by disk ID. This was the only way to get
an older laptop to boot
Here is the fstab I ended up with
proc /proc proc defaults 0 0
# Entry for /dev/sda1 :
/dev/sda1 / ext3 norelatime,noatime,nodiratime,errors=remount-ro 0 1
# Entry for /dev/sda5 :
/dev/sda5 /home ext3 norelatime,noatime,nodiratime 0 2
# Entry for /dev/sda6 :
/dev/sda6 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
This is not a bootwait problem
1. adding bootwait doesnt help
2. This is / we are talking about here, not any other file system; it is meant
to be always mounted
instead it is that UUID -> device mapping seems not to be working
--
mount at startup problem jaunty upgrade -> karmic
https://bugs.launchpad.net/bugs/482228
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
