I have Leap 15.1 on a SSD encrypted. it was loading and booting pretty fast. All of the sudden, lately, after Grub dissapears, the option to type the password appears, but it does not allow me to type anything. I have to wait about 45 seconds. after that, I can type normally, the password works fine, and leap loads pretty fast.
That 45 second halt is so annoying and I have not been able to figure it out.
Any help is appreciated
“lately” is a bit vague. Did you anything to try to remember if you did an update, or installed additional software, or changed a configuration just before this happened?
Yes,
I installed new Nvidia drivers, and encrypted an external disk that is no longer connected.
I had an additional 1m30s delay because of that, so I had that disk removed from crypttab.
other than that, nothing has changed.
I am no expert here, but are you sure that other disk is removed everywhere and not waited for somewhere? E.g. /etc/fatab?
That is the issue. I don’t know anywhere else to look for.
So you already suspected that encrypted and removed disk being somewhere in play, but you did not mention that in your first post?
And now, did you check /etc/fstab or not?
-
I did not think that the encryption had anything to do, since I have done that multiple times and never had an issue besides the crypttab extra line.
Also, i’m not sure if the issue started before the encryption. Can’t remember what was first. -
I don’t see anything wrong with fstab, but I dont understand everything on it. here it is just in case.
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 / btrfs defaults 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /.snapshots btrfs subvol=/@/.snapshots 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /var btrfs subvol=/@/var 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /usr/local btrfs subvol=/@/usr/local 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /tmp btrfs subvol=/@/tmp 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /srv btrfs subvol=/@/srv 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /root btrfs subvol=/@/root 0 0
UUID=4594b0c6-9001-425d-a2c7-4cae5f8b66f0 /opt btrfs subvol=/@/opt 0 0
UUID=02302c83-3c7e-4312-a76c-1bcafc390ddf /home ext4 data=ordered,acl,user_xattr 0 2
UUID=be917f0d-345a-442b-affd-3f64f6d9a15e swap swap defaults 0 0
UUID=c913ca3d-347a-44ab-a06c-07a98e418339 /home/cepiolidus/Storage ext4 defaults 0 2
And that /home/cepiolidus/Storage was not the file system you were talking about?
After removing that entry from “crypttab”, did you run “mkinitrd”?
If not, then do that now. There may be a copy of the old “crypttab” sitting in the “initrd”.
And that /home/cepiolidus/Storage was not the file system you were talking about?
No
After removing that entry from “crypttab”, did you run “mkinitrd”?
did that. nothing changed.
Still halts in the “please enter paraphrase for disk…” for about a minute before I can start typing.
I once had that problem with a computer here. But there were also messages about USB ports. Apparently the kernel was having trouble finding the right driver to read the USB keyboard. It was a BIOS problem. When the computer was new, it was fine. After a BIOS update, it started this misbehavior. A later fixed BIOS update solved the problem.
You may have a different, but analogous problem.
No Bios update. This i pretty weird and annoying. any suggestions?
Sorry, I don’t have any good ideas on this.
Maybe a google search will turn up others with the same hardware and similar problems. But I guess most people don’t use encryption, and so won’t run into this.
Are you also prompted for the encryption key at the start of grub (before the menu shows)?
What exactly “type normally” means? What happens during these 45 seconds? What happens after? May be you actually “type normally” all the time but just nothing acts on what you have typed?
Boot with “systemd.log_level=debug printk.devkmsg=on” and deleted “quiet” on kernel command line and upload “journalctl -b” output to http://susepaste.org/. Booting without plymouth may also provide some additional hints.
Are you also prompted for the encryption key at the start of grub (before the menu shows)?
Yes, and I can imput the password without an issue, then it goes into the GRUB menu. when I select Opensuse then the screen where I have to type the password again appears, and it is when it halts.
- during the first 45 seconds the keyboard does nor work. No matter what you type, it does not do anything.
- here is the link for the journalctl -b SUSE Paste
- please explain “Booting without plymouth”. my apologies, but I do not know what plymouth is.
Okay, then I do have a suggestion for you.
Take a look at this page:
SDB:Encrypted root file system
Scroll down to the heading “Avoiding to type the passphrase twice”.
That suggests a way of avoiding the second password prompt, and that’s the one that is giving you problems.
Assuming you are at Plymouth splash screen, it does not take any input, so what reaction do you expect? Did you try Alt-F1?
- here is the link for the journalctl -b SUSE Paste
It is truncated to just several lines. Provide full output, please.
- please explain “Booting without plymouth”. my apologies, but I do not know what plymouth is.
Add “plymouth.enable=0” to kernel command line.