You are not logged in.
Pages: 1
Hi,
I am running Arch Linux on a Dell XPS 13 7490 with luks disc encryption and everything was fine until yesterday evening. This morning I tried to boot and I am stuck at the "a password is required to access" prompt. I type in the password and press enter, but nothing at all seems to happen.
I used a rescue Arch installation on a USB stick to arch-chroot into my system (so my password seems to work) and downgraded linux to a previous version. After rebooting the machine, I noticed this did not help, in fact, I did not update the linux version yesterday as I noticed afterwards, so this was bound to fail.
I have timeshift installed on my system and I then did a restore using a backup I did on 2020-04-17, but that did not help either.
Before trying to remove the encryption and re-encrypt, which seems to be quite a hassle, I wanted to ask if you have any idea why the encryption login prompt could be unresponsive and what to try to fix it. As I can arch-chroot into my system I hope there is a chance I can fix this somehow.
Last edited by jose_67 (2020-05-16 10:41:53)
Offline
Are the hooks correct in /etc/mkinitcpio.conf?
Offline
Try pressing ctrl + alt + f2 to see if you you do have access to a virtual console. Could
be that your system has booted but Xorg crashed or something like that.
Last edited by f33dm3bits (2020-05-17 06:45:30)
Offline
Thanks for your replies, I am sorry to reply so late, the notification about your replies went to the spam folder.
For security reasons I had disabled opening virtual consoles, so I would not have been able to switch, but good point.
It may well have been that there was something wrong in /etc/mkinitcpio.conf, i.e. maybe something had corrupted the file because it was working before (encrypt hook before filesystem hook etc.).
I decided to setup my system from scratch anew, which took me some hours, maybe I gave up too soon, but this is my work machine and I wanted to make sure I could use it again on Monday. Thanks a lot for your good suggestions, I will keep them in mind in case it happens again (I hope not...) and dig a bit more then if I have the time.
Offline
This comes up in google so..
I stuck a USB keyboard in and that worked. Was considering a re-install.
Seems archinstall puts `keyboard` after `autodetect` in `/etc/mkinitcpio.conf` (rebuild with `mkinitcpio -P`), which caused the problem.
Offline
Thanks for the tip! I will definitely remember to try this out next time.
Offline
Pages: 1