Skip Navigation

boot on LUKS encrypted drive ( initramfs Vs initrd ) ?

Hi,

I'm trying to encrypt the root filesystem / of a raspberry pi 4 device running under Devuan rpi ( custom kernel )

I'm following LUKS on Raspberry Pi 2021 guide

That explain step by step how achieve this.

But the guide use initramfs and my distro seem to use initrd

So the question, is: should I migrate to initramfs ? and how check whats is inside my current initrd

or keep-up with initrd but then how insert the necessary to enable LUKS drive to be mounted by it ( initrd ) ?

Thanks.

14

You're viewing a single thread.

14 comments
  • Thank you very much all, for your inputs !

    I've did

    root: file /boot/broadcom/initrd.gz
    initrd.gz: Zstandard compressed data ....
    
    root: unmkinitramfs /boot/broadcom/initrd.gz Extracted/
    # data where extracted to Extracted/
    # but I go few error like:
    # cpio: cannot link usr/sbin/vconfig to usr/sbin/watchdog: Operation not permitted
    
    `tree -Fan -L 2 Extracted`
    Extracted//
    |-- conf/
    |   |-- arch.conf*
    |   |-- conf.d/
    |   `-- initramfs.conf*
    |-- etc/
    |   |-- fstab*
    |   |-- ld.so.cache*
    |   |-- ld.so.conf*
    |   |-- ld.so.conf.d/
    |   |-- modprobe.d/
    |   `-- udev/
    |-- init*
    |-- run/
    |-- scripts/
    |   |-- functions*
    |   |-- init-bottom/
    |   |-- init-top/
    |   |-- local*
    |   |-- local-bottom/
    |   |-- local-premount/
    |   `-- nfs*
    `-- usr/
        |-- bin/
        |-- lib/
        `-- sbin/
    

    So it tend to confirm that even if the file is named initrd.gz it's actually an initramfs method.... ( damn this is so misleading )

    So I guess I can follow preparing-linux from the guide and overwrite the initrd.gz ?

14 comments