The workaround proposed here will not work in the archive at large. I
believe the correct fix is to signal mountall to rescan at the end of
the do_swap() and do_tmp() functions in
/lib/cryptsetup/cryptdisks.functions. Could someone test whether this
fixes the issue?:
PID=$(status mountall
Thanks a lot for the workaround, I had the same problem here, now it works.
It also fixed a problem at bootup, where I sometimes got the message
/dev/mapper/crypttemp already mounted or /tmp busy, which resulted in
mountall to fail, dropped into a root-shell and I needed to press CRTL-D to
Hi out there!
I had the same problem. On jaunty no problems but on karmic (complete
updated on 4th Dec).
The new canonical-special init-system isn't perfect.
This routes to the unmountable (non-luks-) cryptsetup-devices:
The new init-system don't use the old /etc/inittab. That file is
replaced
** Package changed: mountall (Ubuntu) = cryptsetup (Ubuntu)
--
/dev/mapper/tmp encrypted with /dev/urandom not mounted on bootup
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
