cryptsetup crypttab luks

  • my "/etc/crypttab" file content


    cat /etc/crypttab
    # <target name> <source device> <key file> <options>
    luks-sdb1 /dev/sdb1 /sys/devices/virtual/dmi/id/product_uuid luks
    luks-sdc1 /dev/sdc1 /sys/devices/virtual/dmi/id/product_uuid luks



    "/dev/sdb1 /dev/sdc1" use keyfile "/sys/devices/virtual/dmi/id/product_uuid"


    But report errors when rebooting


    "/dev/mapper/luks-sdc1" successfully loaded, but /dev/mapper/luks-sdb1 failed


    But after entering the system, manual "cryptdisks_start luks-sdb1" loading can succeed.Explain that configuration "/etc/crypttab" is not a problem!

    • Offizieller Beitrag

    The luks plugin doesn't add any entries to /etc/crypttab for auto-unlock. This is not a plugin problem.


    Did you regenerate your initramfs? Maybe this is race condition where the drive is not ready when it tries to unlock??

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.6 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!