search

nix-community / disko

Declarative disk partitioning and formatting using nix [maintainers=@Lassulus @Enzime @iFreilicht]
MIT License
1.85k stars 196 forks source link

passwordFile unlocking immediately fails after providing a password #872

Closed JimmJam closed 1 day ago

JimmJam commented 1 day ago

I've had good success in creating a disk with all the partitions I would need for a working system using this config. However, when attempting to boot into the config, I am immediately faced with this error stating that Cryptography Setup failed for my disk, leaving the system unable to find the subsequent LVM partitions. image

I am using disko-install to set up the drive, attached via USB. The LUKS partition is created successfully, and I am able to successfully use the partuuid to unlock, mount, chroot into, interact, and rebuild the system. The password works as intended everywhere except right here, where the password inexplicably fails and I have no clue why.

Removing and adding a new password from the partition also does not solve the problem. This does NOT occur on an identically partitioned, subpartitioned and labeled drive that was migrated into disko rather than being created with it.

Any ideas?

Mic92 commented 1 day ago

Please try including the all-hardware.nix profile and check if this solves your problem. My current suspicions is that your hardware-configuration.nix doesn't contain the usb driver for your external drive.

JimmJam commented 1 day ago

Was worth a shot, but no dice. I'm running this under QEMU to test, and while I think that solves an issue I was having on my laptop when testing the drive directly (not being prompted for a password at all), I'm still being prompted for the password, and being notified that the drive was found, leaving me very confused.

hardware.nix

image

JimmJam commented 1 day ago

Amendment: problem.. solved? You were right, on bare metal the USB driver was not being loaded, and now boots and recognizes the device. When booting to bare metal, it DOES boot! Now I'm confused but less concerned about why it immediately fails via QEMU, but I suppose that can be dismissed. Unless you have any theories for why it might be failing in QEMU, I suppose that's case closed!

Mic92 commented 1 day ago

It's definitely a sharp edge present only in NixOS.