Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nixos-generate-config generates duplicate boot.initrd.luks.devices... entries which causes installation to fail #38564

Open
smaximov opened this issue Apr 7, 2018 · 2 comments
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md

Comments

@smaximov
Copy link
Contributor

smaximov commented Apr 7, 2018

Issue description

nixos-generate-config generates duplicate boot.initrd.luks.devices... entries in hardware-configuration.nix if a LUKS-encrypted Btrfs partition contains multiple subvolumes.

Steps to reproduce

  1. Encrypt a partition using LUKS and create a Btrfs filesystem, as described in the manual.

  2. Create two Btrfs subvolumes in the Btrfs filesystem, named root and home, and mount them as /mnt and /mnt/home, respectively.

  3. Run nixos-generate-config --root /mnt and inspect /mnt/etc/nixos/hardware-configuration.nix. There should be two identical entries which set boot.initrd.luks.devices."crypted".device.

  4. Run nixos-install. It should complain that boot.initrd.luks.devices."crypted".device is set multiple times and abort installation.

Workaround

Edit /mnt/etc/nixos/hardware-configuration.nix and remove duplicate entries.

Technical details

Graphical live CD, 64-bit Intel/AMD

@arianvp
Copy link
Member

arianvp commented Aug 21, 2018

Confirmed. I'll have a look this weekend if I can fix this.

@stale
Copy link

stale bot commented Jun 4, 2020

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
Projects
None yet
Development

No branches or pull requests

2 participants