Bug 493818 – >=sys-kernel/genkernel-next-40 USE=-cryptsetup - initramfs shows error /bin/cryptsetup not found

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Walter Meinl 2013-12-10 08:01:19 UTC]

#LUKS=no in /etc/genkernel.conf (default setting) and USE=-cryptsetup
plymouth start screen disappears and the error mentioned is shown. No error message in genkernel-next-35 but in versions >=40

Reproducible: Always

[Comment 1 Yixun Lan 2013-12-10 08:53:21 UTC]

same problem here.. 

the logic here is 

defaults/linuxrc:
# Initialize LUKS root device except for livecd's
is_livecd || start_luks

defaults/initrd.d/00-crypt.sh:
start_luks() {
    if [ ! -e "${CRYPTSETUP_BIN}" ]; then
        bad_msg "${CRYPTSETUP_BIN} not found inside the initramfs"
          return 1
    fi
    ..
}

or is that possible to export ${LUKS}, and test it while system boot up?

start_luks() {
    if [ "${LUKS}" == "no" ]; then
         return 0
    fi

    ..
}

[Comment 2 Yixun Lan 2013-12-10 09:15:45 UTC]

Created attachment 365032 [details, diff]
fix "cryptsetup not found" warning

actually this error doesn't harm the system, we can just safely ignore it.

but if there is anyone really found it annoy and want to get rid of it, he/she can try attached patch. the downside is that user who do want luks support need to append "doluks" to kernel command args.

I'm not sure @lxnay like it or not...

[Comment 3 Walter Meinl 2013-12-10 23:49:49 UTC]

(In reply to Dennis 'dlan' Lan from comment #2)
> Created attachment 365032 [details, diff] [details, diff]
> fix "cryptsetup not found" warning
> 
> actually this error doesn't harm the system, we can just safely ignore it.
> 
yes, the system started
> but if there is anyone really found it annoy and want to get rid of it,
the annoyance is that the initial plymouth screen disappears to spit out this warning.

> he/she can try attached patch. the downside is that user who do want luks
> support need to append "doluks" to kernel command args.
Would there be an alternative way depending whether or not the setting LUKS=yes appears in genkernel.conf?
I'll try your patch and report back (ASAP)

> 
> I'm not sure @lxnay like it or not...

[Comment 4 Fabio Erculiani (RETIRED) 2013-12-11 11:00:28 UTC]

commit 9097998cada3c2b291249c57a5013087304d8586
Author: Fabio Erculiani <[e-mail]>
Date:   Wed Dec 11 11:59:13 2013 +0100

    00-crypt.sh: only warn about missing cryptsetup if CRYPT_ROOTS or CRYPT_SWAPS is set
    
    This fixes Gentoo bug #493818

Fixed in git. genkernel-next-51 will have the fix.