Sorry was away for a few weeks.
Bug can be closed as resolved.
Wiped my upped 9.10a4 installation and installed with final release image.
Everything works fine, no more boot issues with manually configured lukfs
crypted home partition.
Thanks regards, Simon
** Changed in: mountall (Ubuntu)
No contact from the reporter in 1 month, closing out this bug.
inode77, if you're still experiencing this problem please reopen the bug
and provide the requested information
** Changed in: mountall (Ubuntu)
Status: Incomplete = Invalid
--
waits for cryptsetup even when cryptsetup
inode77,
Could you please also post your /etc/crypttab? Since that's the missing
link that maps filesystem entries to block devices, it may help shed
some light on why cryptsetup thinks it needs to do something at boot
time.
--
waits for cryptsetup even when cryptsetup disabled
Sorry about the issues with the previous PPA versions, as usual things
worked just fine when I tested it in the various rigs I have here - of
course it flatly failed when installed on normal systems because I
hadn't actually tested that ;)
I've uploaded a new ~boot4 version, this one feels much
I've uploaded a new mountall package to the ubuntu-boot PPA:
https://launchpad.net/~ubuntu-boot/+archive/ppa
I would appreciate it if you could install this and try it out.
*BEFORE* you reboot though, could you run sudo mountall --debug
mountall.log 21 and attach that to this bug - then after
You missunderstood (sorry my english isn't that good):
Situation:
pam_mount uses cryptsetup to mount partition at logintime (no boottime action
needed)
before mountall:
cryptsetup installed, system boots fine, partition is decrypted upon login
with mountall:
crypsetup/mountall hangs upon boot,
I'm not sure why it's waiting for those cryptsetup devices, they should
be outside of the FHS namespace.
Note that you didn't attach your fstab but the output of fsck, could you
attach your fstab again?
** Summary changed:
- stuck on fstab with cryptsetup
+ waits for cryptsetup even when
