I am running an EndeavourOS installation with an encrypted boot partition using LUKS and GRUB. Whenever I enter the wrong password to GRUB I am dumped into GRUB rescue mode. I end up rebooting my machine so that I can have another chance to enter my password. Of course this is not a big problem but instead merely a mild annoyance.
By searching on Google I found that other people had asked essentially the same question:
the solution you proposed, which was mentioned in a couple of the links I included in my first posting, is impractical because it is actually easier for me to manually reboot my machine so as to have another chance to enter the correct password than to enter the commands above.
Having only one chance to enter a correct password is, generally speaking, bizarre.
That is simply the way grub works, so it is not an EOS issue. Apart from entering those commands there is no other way on full disk encryption. The other solution is to use an unencrypted boot partition.
This could be an Ubuntu own solution, we are based on Arch and unlike Ubuntu, Arch isn’t funded by a major company behind it. They develop and maintain the scripts they specifically created and leave things like Systemd and Grub up to the development team of those projects.
Canonical has an army of paid developers who each are dedicated to their tasks. The vast majority of Arch developers are volunteers, who are doing this next to their regular jobs.
So, yes there’s a difference between Arch and Ubuntu but it isn’t fair to compare those two, because the infrastructure behind the two aren’t comparable.