You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using a nixpkgs commit of a1c4f0a or later, boot.initrd.systemd.enable = true for me triggers a boot errorwarning with 2min wait 'Timed out waiting for device'.
Steps To Reproduce
Steps to reproduce the behavior:
follow nixos manual to partition/install with default config
add boot.initrd.systemd.enable = true;
rebuild
reboot
find error 'Timed out waiting for device'
Expected behavior
either boot successfully or use assertions to warn users the config should change
Additional context
this issue started for me from a1c4f0a (#282022). canceling out its addition using boot.blacklistedKernelModules = ["efivarfs"]; fixes the boot for me.
i'm not sure:
what this means i messed up on my set-up that caused this
how i might use boot.initrd.systemd.package.withEfi (or lib.mkForce on boot.initrd.availableKernelModules) to circumvent this
This may be due to the fact that you had a failed resume from hibernation at boot, so you had a hibernate entry in your efivarfs.
Try: ls /sys/firmware/efi/efivars/ | grep HibernateLocation. You should see something like HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67 (the uuid should be different, but may not be similar to the device waited for)
Yea, this was a systemd issue that has been (mostly) fixed in systemd/systemd#32043. It clears the efi variable on boot so the issue only happens once. Not perfect, but it's hard to imagine any way to do better, since there's no reason to disbelieve the efi variable in the first place.
Describe the bug
Using a nixpkgs commit of a1c4f0a or later,
boot.initrd.systemd.enable = true
for me triggers a booterrorwarning with 2min wait 'Timed out waiting for device'.Steps To Reproduce
Steps to reproduce the behavior:
boot.initrd.systemd.enable = true;
Expected behavior
either boot successfully or use assertions to warn users the config should change
Additional context
this issue started for me from a1c4f0a (#282022). canceling out its addition using
boot.blacklistedKernelModules = ["efivarfs"];
fixes the boot for me.i'm not sure:
boot.initrd.systemd.package.withEfi
(orlib.mkForce
onboot.initrd.availableKernelModules
) to circumvent thisNotify maintainers
@ElvishJerricco @flokli @kloenk
Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.Metadata
log
The text was updated successfully, but these errors were encountered: