I found the attached workaround on the internet and everything worked fine until today.
Then there was this apt-get update : ....... Préparation du remplacement de cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7.2 (en utilisant .../cryptsetup_2%3a1.0.6+20090405.svn49-1ubuntu7.2_amd64.deb) ... Dépaquetage de la mise à jour de cryptsetup ... Traitement des actions différées (« triggers ») pour « ureadahead »... ureadahead will be reprofiled on next reboot Traitement des actions différées (« triggers ») pour « man-db »... Paramétrage de cryptsetup (2:1.0.6+20090405.svn49-1ubuntu7.2) ... update-initramfs: deferring update (trigger activated) update-rc.d: warning: cryptdisks-early start runlevel arguments (none) do not ma tch LSB Default-Start values (S) update-rc.d: warning: cryptdisks start runlevel arguments (none) do not match LS B Default-Start values (S) So I rolled back to the original mountall.conf, but the situation is as bad as it was before : It need serveral reboot attempts to enter the password. What is wrong? ** Attachment added: "mountall.conf.modified" http://launchpadlibrarian.net/37933713/mountall.conf.modified -- cryptsetup init scripts are redundant and can break the boot https://bugs.launchpad.net/bugs/473615 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