# Recovery Mode after Failed Decryption

**URL:** <https://forum.endeavouros.com/t/recovery-mode-after-failed-decryption/61094>\
**Category:** Newbie\
**Created:** [September 30, 2024, 6:43pm UTC](https://forum.endeavouros.com/t/recovery-mode-after-failed-decryption/61094 "2024-09-30T18:43:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![badamkulfi](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/ac91a4/32.png) [@badamkulfi](https://forum.endeavouros.com/u/badamkulfi)\
**Post date:** [September 30, 2024, 6:43pm UTC](https://forum.endeavouros.com/t/recovery-mode-after-failed-decryption/61094/1 "2024-09-30T18:43:42Z")

</div>

Hello,

I’ve installed EndeavourOS with encryption twice on two different systems (also with GRUB and hibernate). In both cases, if I make a typo entering the decryption password, it takes me to GRUB recovery mode, whereas previous installations of Arch that I’ve done give me unlimited (or at least more than one) chances to attempt to decrypt.

My question: Is there a way to configure the system to give you multiple chances to enter the passphrase? Also, is there a way to get out of recovery mode to attempt to decrypt again?

Or maybe it is a security feature to only give one chance and make you turn the computer off and on again to attempt to decrypt.

---

<div class="post-metadata">

**Author:** ![eso](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/eso/32/36767_2.png) [@eso](https://forum.endeavouros.com/u/eso)\
**Post date:** [October 1, 2024, 6:45am UTC](https://forum.endeavouros.com/t/recovery-mode-after-failed-decryption/61094/2 "2024-10-01T06:45:43Z")

</div>

Edit: [consider unencrypted /boot](https://forum.endeavouros.com/t/allow-multiple-luks-password-attempts/4749)  
There was a [case](https://forum.endeavouros.com/t/luks-keyboard-layout-max-password-tries-show-asterisks-while-typing/58559) here.  
If no other constrains, systemd-boot seems to be better for LUKS.