Fedora Account System
Red Hat Associate
Red Hat Customer
On every boot, the following error is logged during the initrd phase: '/usr/lib/systemd/system-generators/dracut-crypt-generator' failed with exit status 2. This occurs on systems with no encrypted volumes and no /etc/crypttab. Root Cause The generator script usr/lib/systemd/system-generators/dracut-crypt-generator (installed inside the initramfs by the 90crypt dracut module) uses return statements to exit early: [ -e /etc/crypttab ] || return 0 systemd executes generators as standalone processes, not sourced shell scripts. When return is used outside of a function in a non-sourced script, the shell treats it as an error and exits with code 2. systemd then logs this as a generator failure. The script has multiple return statements that should be exit. Reproducible: Always Steps to Reproduce: 1. Boot any Fedora 45 aarch64 (or likely any arch) system with dracut 111-1.fc45 2. The system must not have encrypted volumes (no /etc/crypttab) 3. Check the journal: journalctl -b | grep dracut-crypt-generator Actual Results: Errors in boot log: (gene[NNN]: '/usr/lib/systemd/system-generators/dracut-crypt-generator' failed with exit status 2. Expected Results: No error. The generator should exit cleanly with code 0 when there is nothing to do. Additional Information: - dracut: 111-1.fc45 - Kernel: 7.2.0-0.rc6.260807gf9a2394a2348.52.fc45.aarch64 - Reproduced on: GNOME Workstation, KDE Plasma, Xfce, Minimal -- all Fedora 45 aarch64 spins on Raspberry Pi 4 - Not present in: dracut 109-7.fc45 (earlier boots did not show this error) - Impact: Cosmetic only -- boot continues normally. But it creates unnecessary noise in every boot log.
Created attachment 2154511 [details] Fedora 45 Branched 20260814.n.0 Minimal aarch64 boot log
Proposed as a Freeze Exception for 45-beta by Fedora user dustymabe using the blocker tracking app because: The dracut-crypt-generator failing seems harmless but it breaks CoreOS CI because we check that no generators fail during our boots. We have worked around this by pinning on older versions of dracut, but would like dracut-112 that has the fix.
This is fixed upstream https://github.com/dracut-ng/dracut/pull/2494 and is in dracut 112 so should get fixed when that is released to Fedora.
Accepted as a Beta freeze exception in https://forge.fedoraproject.org/quality/blocker-review/issues/2172
I don't believe that getting dracut 112 into Fedora 45 at this point in the cycle is realistic. You may want to submit a PR with the fix backported for the Fedora dracut package at: https://github.com/redhat-plumbers/dracut-fedora/ This uses a standard packit workflow.
In the end we signed off Beta-1.3 for release without this. Dropping FE status.