Public bug reported:
i have found this to happen on two different computer (my desktop and my
laptop), with both i386 and x86-64 versions of lucid (final release)
steps to reproduce:
1, make a bootable usb pendrive with the release iso image and the usb creator
tool found in ubuntu. (i used the setting to discard all changes, ie.
non-persistent install)
2, boot the system with the pendrive to install lucid, use the bios'
boot menu to select the usb device to be the boot drive.
3, in the installer, choose advanced partitioning (in my case, there
were always multiple hard drives present, and the installer always
wanted to install on the wrong drive, so i had to guide the installer
manually. on the laptop, i installed lucid i386 onto a wd passport usb
drive (and not onto the laptop's internal drive). on my desktop, i have
an onboard raid0 (dmraid), a third and a fourth hard drive. the fourth
is for ubuntu.)
4, since i was upgrading on both systems, i didn't create any
partitions, instead, i used the already existing ones, just reformatted
them to ext4. so in the installer, i selected manual partitioning,
selected the correct target drive, and selected the target partitions
(/, /home, /data, swap) one by one, and in the properties, i selected
the new filesystem and to format the partition, and also selected their
mount points.
5, after selecting what is mounted to where (and selecting the right
drive at the final step for the grub2 installer), the install finishes
correctly, then asks for a reboot.
6, remove the usb drive, and let it reboot.
7, the first boot hangs with a message: /home (or /data or swap, etc) is
not mounted yet, and ask if i want to wait for the mounts to become
available, or go to the root terminal.
8, in the root terminal, only the root partition was mounted, and the
others weren't, that's why it hung.
9, after manually mounting the rest of the partitions, booting continues
and is successful.
the problem: when booting off the pendrive, one has to select it to be
the temporary booting device in the bios boot menu. this changes the
drive order (as seen by the installer kernel), and the pendrive becomes
/dev/sda (as it's the boot device), and the other hard drive(s) are
going to be /sdb, /sdc, /sdd, etc. say, we want to install on the hard
drive called /dev/sdd. after selecting the partitions and their mount
points in the installer, it writes /dev/sddX references into fstab.
after rebooting, removing the pendrive, and selecting that other drive
(the target drive with the freshly isntalled system on it) in the bios
bootmenu, it becomes /dev/sda again (instead of /dev/sdd), and the
references to mount in fstab become invalid, and booting stops.
the root partiion is mounted, because grub passes its reference with its
uuid.
resolution: the installer should write uuid references into fstab
instead of /dev/sdX. (wasn't this the default behavior earlier?)
actually, i think, the installer would only work on systems with only
one hard drive and one optical drive, when the installer is run from the
optical media. this situation won't change the /dev/sdX references. in
all other cases, device names would always change and fstab would become
invalid.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: 10.04 device fstab lucid mount names uuid
--
system fails to (re)boot after install
https://bugs.launchpad.net/bugs/574009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
