Machine requires 2 boots before it asks for LUKS passwd (Rocky 9.2)
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Machine requires 2 boots before it asks for LUKS passwd (Rocky 9.2)
Hi Guys,
here's a weird one.
I recently created a new Rocky 9.2 build (bare metal) on my Dell Latitude 5500.
I opted for LUKS for security, but mostly took the default options.
I've discovered that when I first boot it, I just get the DELL sign appearing and it stops there..
However, if I then power down (using the power button) and power on again, it will show the DELL sign, swiftly followed by a prompt for the LUKS passwd, and then it's fine from there.
Oddly, it seems to be related to how long the machine has been powered off+disconnected from mains power.
I only have room for one machine at a time, so when I'm WFH, I take the personal machine off.
If I'm WFO, i usually leave it connected to power.
iirc over the last week, it does seem that if it's been off for a day (like today), then it won't reach the decrypt prompt.
I timed it and waited 2 mins, but nothing. I then powered off and on and I got the disk boot after ~ 14 secs and Decrypt prompt after ~ 24 secs (from boot).
I've added rootdelay=10 to grub's "GRUB_CMDLINE_LINUX=... " and we'll see what happens tomorrow if I disconnect before bed tonight.
Sounds very like one of my old machines. After months I concluded it must have a dry joint(s) somewhere or similar. So I just went with the flow. Power it on, go make a coffee, reset the box. Bingo.
Yeah - it's cold in Syddo, but I'm due for a break in Top End soon - warmth, sunshine & Salties
PS I do seem to be able to force it by powering on twice fairly quickly, but I'll try to post back about the 10 sec delay for anyone else who comes across this.
For anyone playing along at home, yesterday it seemed the rootdelay thing did the trick, but conversely this morning, I had to revert to a 2nd boot to get the prompt to appear.
It was cold last night, so maybe syg00 is onto something...
At least atm I've generally found that I don't need to wait too long before hitting the 2nd boot, but it is annoying.
I guess I need a reputable(!) HW shop in Sydney to look into it...
Any suggestions ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.