[debbugs-tracker] bug#27242: closed (Fail to load LUKS encrypted rootfs, attempts to open luks device before it's ready.)

[GNU bug Tracking System]

Your message dated Wed, 07 Jun 2017 19:10:27 -0400
with message-id <address@hidden>
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
address@hidden)


-- 
27242: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27242
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> 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
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
>
>
>
>
> 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
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> 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
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
>
>
>
>
> Adam Van Ymeren <address@hidden> writes:
>
> > Mark H Weaver <address@hidden> 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
>
>
> --- End Message ---