| brocashelm | i reinstalled beowulf and still want as new as possible within that arch. what are good pin values for backports, proposed-updates, updates, and security? | 00:15 |
|---|---|---|
| tom | hello | 00:17 |
| tom | can I please have some help? I rebooted my machine to update to the latest kernel patches and now my machine won't turn on | 00:17 |
| tom | here are the last few lines displayed on screen | 00:17 |
| tom | caching passphrase for crypt_swap: | 00:18 |
| tom | cryptsetup: crypt_swap: set up successfully | 00:18 |
| Guest3500 | using cached passphrase for bigssd. | 00:18 |
| Guest3500 | Device /dev/nvme0n1p1 is not a valid LUKS device. | 00:18 |
| Guest3500 | cryptsetup: ERROR: bigssd: cryptsetup failed, bad password or options? | 00:19 |
| Guest3500 | Caching passphrase for bigssd: Device /dev/nvme0n1p1 is not a valid LUKS device. | 00:19 |
| Guest3500 | then it just blinks a underscore cursor forever, going on at least 30 minutes so far | 00:19 |
| Guest3500 | it looks similar to the black screen of death from Windows 3.1 | 00:20 |
| Guest3500 | https://upload.wikimedia.org/wikipedia/commons/e/e0/Win3x_Black_Screen_of_Death.gif | 00:20 |
| Guest3500 | i think it's stuck in the ramdisk, but it's not giving me a shell to fix things manually | 00:21 |
| gnarface | eh, some issues keep coming up for common reasons, first one i can think of is you might be missing the crypsetup-initramfs package | 00:21 |
| Guest3500 | that's possible, but why isn't it dropping to an emergency shell when it can't figure out how to boot so i can fix it? | 00:23 |
| Guest3500 | is there a key combo to force it? | 00:23 |
| gnarface | i think you might need something to use as a rescue disk | 00:23 |
| gnarface | rescue mode from the installer, or a live image or something | 00:24 |
| gnarface | something to chroot into the install to add the missing package | 00:24 |
| gnarface | i would assume this is because the on-disk "rescue mode" is part of what it can't decrypt, but maybe i'm wrong about that if you can see a rescue mode option somewhere in the grub menu before this error.... | 00:25 |
| gnarface | worth looking anyway | 00:25 |
| Guest3500 | it's refind | 00:29 |
| Guest3500 | the problem is /dev/nvme0n1p1 IS a luks ... container | 00:29 |
| Guest3500 | i don't know why it would think it isn't, or why it's using the device name instead of the uuid | 00:30 |
| Guest3500 | also, I have my disk replicated to a completely seperate array to prevent this exact kind of an issue, but I can't access a ramdisk shell so I can't switch over to it | 00:30 |
| gnarface | oh, that rings a bell, are you using LVM? you might need to tell it the device of the LVM container or something like that | 00:32 |
| gnarface | stick around, people here know more about it than me and can help | 00:33 |
| Guest3500 | no i'm not using lvm | 00:33 |
| gnarface | there's only a couple common problems with encryption that keep coming up and they always have pretty easy fixes, i just don't know them well enough to repeat them without direct experience, sorry | 00:35 |
| gnarface | but people here do know, just stick around | 00:35 |
| Guest3500 | hmm | 00:37 |
| Guest3500 | break=mount worked | 00:37 |
| Guest3500 | fixed it | 00:46 |
| Guest3500 | somehow, using LUKS, the data generated randomly in such a way as to trick the kernel into thinkinga luks container was 2 partitions | 00:46 |
| Guest3500 | igh | 01:02 |
| Guest3500 | ugh | 01:02 |
| Guest3500 | for some reason despite the uuid not belonging to a partition | 01:02 |
| Guest3500 | despite there not actually being a partition | 01:02 |
| Guest3500 | it tries to boot a partition from the nvme | 01:02 |
| golinux100 | rrq | 06:57 |
| rwp | gnarface, I have myself tripped over the cryptsetup-initramfs having been split out of cryptsetup but not being a Depends to ensure it was brought in twice now. | 08:00 |
| rwp | And IRL a friend in another city also just tripped over that yesterday too. | 08:01 |
| Guest3500 | it turns out that the initramfs module that handles luks there's a bug | 12:55 |
| Guest3500 | that also interacted with a kernel bug that cause phantom partitions to show | 12:56 |
| Guest3500 | so now despite manually specifying the uuid or device /dev/nvme0n1 | 12:56 |
| Guest3500 | it tries to mount the phantom partition instead | 12:56 |
| hagbard | Guest3500: It's very odd and unusual to specify an entire device for luks. Usually you'd encrypt a partition e.g. /dev/nvme0n1p1, not the whole disk, like /dev/nvme0n1. | 13:12 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
