GNU bug report logs - #27242
Fail to load LUKS encrypted rootfs, attempts to open luks device before it's ready.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Mark H Weaver <mhw <at> netris.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#27242: closed (Fail to load LUKS encrypted rootfs, attempts
 to open luks device before it's ready.)
Date: Wed, 07 Jun 2017 23:11:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 07 Jun 2017 19:10:27 -0400
with message-id <87tw3rqtr0.fsf <at> netris.org>
and subject line Re: bug#27242: Fail to load LUKS encrypted rootfs, attempts to open luks device before it's ready.
has caused the debbugs.gnu.org bug report #27242,
regarding Fail to load LUKS encrypted rootfs, attempts to open luks device before it's ready.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
27242: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27242
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Adam Van Ymeren <adam <at> vany.ca>
To: bug-guix <at> gnu.org
Subject: Fail to load LUKS encrypted rootfs,
 attempts to open luks device before it's ready.
Date: Sun, 04 Jun 2017 18:06:15 -0400

On my machine when booting GuixSD, it fails to find the rootfs from the
initramfs.  It errors out attempting to find the luks device node.
Shortly after it errors is when I see the kernel dmesg output of the
nvme0 device becomining ready.

It looks like we need to wait for the device node to become ready, or
poll/sleep a few times if we fail to locate the device.

Thanks!
-Adam

[Message part 3 (message/rfc822, inline)]

From: Mark H Weaver <mhw <at> netris.org>
To: Adam Van Ymeren <adam <at> vany.ca>
Cc: 27242-done <at> debbugs.gnu.org
Subject: Re: bug#27242: Fail to load LUKS encrypted rootfs,
 attempts to open luks device before it's ready.
Date: Wed, 07 Jun 2017 19:10:27 -0400

Adam Van Ymeren <adam <at> vany.ca> writes:

> Mark H Weaver <mhw <at> netris.org> writes:
>>
>> I ran into the same problem at one point, and have applied the following
>> patch to my private branch of Guix.  Perhaps it should be applied to
>> master.
>
> Thanks, this patch works for me.  Something like this upstream would be
> nice :)

I pushed a similar patch to master as commit
f45878a80d412dd79c95e9274c3ee5dd24e1cec9.

> This can probably be unified with the resolve function defined in
> build/file-systems.scm

Thanks for pointing this out.  I don't currently have the spare time to
think about it, but feel free to propose a patch to rework this in a
nicer way :)

I'm closing this bug for now.

     Thanks!
       Mark

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.