Sorry Scott, but I have to disagree. That I've purged cryptsetup is not
the point here. But I fully understand that you can't overview all these
bug reports opened after the recent change in the boot system.
Cryptsetup was only installed to manually mount a luks partition, which
is not one of the important system partitions.
The good news is that I could finally fix this problem this morning :-)
The cause for the problem and the solution are trivial. All my
partitions are on an LVM volume. The device names are for instance
/dev/mapper/apus-root. I configured this scheme with the alternative
installation CD. Later, using system-config-lvm, I set up a new
partition on the LVM for the /home area. This program adds a line to
fstab too - and it reference the device /dev/apus/home (as you can see
above in my fstab). It worked this way until mountall was introduced.
I'm not sure if it is a valid name, though. So please have a look into
this case, if either my fstab was not consistent with the standard of if
mountall is missing a possible configuration.
Changing /dev/apus/home to the UUID solved my problem. I'll set this
report to "status confirmed".
** Changed in: mountall (Ubuntu)
Status: New => Confirmed
--
upstart/mountall hangs with LVM on RAID setup
https://bugs.launchpad.net/bugs/431951
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
