> So what is your question then? Your grub.cfg tries to unlock /. My question is, when it tries to unlock /, why does it accept an invalid password and just continue to the menu?
On Tue, Apr 2, 2024 at 5:56 AM Andrei Borzenkov <arvidj...@gmail.com> wrote: > > On 01.04.2024 23:48, Sotir Danailov wrote: > >> missing file is simply ignored > > > > What do you mean by "missing file"? > > > >> grub cannot ignore missing /boot > > > > /boot is fine and I don't need it to be ignored of course. I just > > wanted to know, why would it prompt for a second password, if the > > input doesn't matter for / (root)? Like I said, if I just press enter > > it continues to the menu directly, I haven't entered anything in that > > prompt. > > > > In grub.cfg I have a couple of cryptomount commands and all of them > > use the proper uuid for /boot and / (root). > > So what is your question then? Your grub.cfg tries to unlock /. > > > I don't see any invalid > > parameters. My PC boots fine, I'm only asking about the purpose of > > this second prompt and whether it's a mistake. >
