[pkg-cryptsetup-devel] Bug#573073: Bug#573073: cryptsetup: boot fails because fsck tries to access the device before it is unlocked

[Jonas Meurer]

hey linas,

On 08/03/2010 Linas Žvirblis wrote:
> I am using cryptsetup with lvm2 and encrypted logical volumes. The setup
> was created during install with Debian Installer. The problem is that
> sometimes it boot fine, but sometimes it dies like shown in boot
> sequence transcript below. The passphrase is not being asked then.
> 
> When it dies I just rerun the script manually, and continue with boot
> sequence. To me it seems like some sort of race condition, but I was
> unable to locate the problem.

i'm not sure whether this is a race condition. according to your boot
process transcript, /etc/init.d/cryptdisks is invoked, and
vg01-swap_crypt is unlocked, but vg01-home_crypt isn't. so you'll have
to find out why vg01-home_crypt isn't unlocked at cryptdisks initscript.


> A while ago the chances of booting properly were close to 50%, but
> something in recent upgrades greatly reduced the odds, as I have not
> managed to get a proper boot in like 10 reboots.

that indeed sounds odd. maybe you could add some debugging code to
the do_start() and handle_crypttab_line_start() functions from
/lib/cryptsetup/cryptdisks.functions to see what causes vg01-home_crypt
to be ignored. the fact that _nothing_ is printed to the commandline
irritates me. you would get a warning if only the source device was
missing.

in case that you don't know any shell scripting, just tell me. i'll
prepare cryptdisks.functions with debugging output for you in that case.
but i'm rather busy right now, thus i don't know when i'll find time to
do so.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100316/952a4abd/attachment.pgp>