That Super Grub2 Disk Beta might also not work as it is an older version which doesn’t has the dashes support. That got added in December 2022 to a more modern grub version which is not released. Those changes will be included in 2.08 version of grub. So people simply call the pacman cmd as I compiled grub against stable branch anyway. I simply didn’t upload it there yet …
I’m not affected, so I just skimmed over this long thread and am sorry, if this has been mentioned before:
If you get dropped into grub recovery console because cryptomount failed, you can execute it manually. For example, /boot is on the second partition of the first disk: cryptomount (hd0,gpt2) or alternatively cryptomount -u <uuid>
it should ask for the pass again. Once that succeeds to unlock, execute:
@boustanihani well. You may want to post the content of your /etc/fstab file and compare it with the cryptomount llines of your /boot/grub/grub.cfg file. If you have dashes in the grub.cfg file for the UUID remove them in all the lines you find the word cryptomount and save the file. That is what the updated /usr/bin/update-grub does. You can re-read my more lengthy posts, as I explained the issue in rich details. Only updating the grub packages won’t update the grub install on you MBR/EFI. So you have to call grub-install ... at some point to fix it properly.
nearly same thing ; since the “crypto bug” last day of march
I did several things but my computer was able to mount finaly (Sorry for my english language. Media items -screenshots- can’t be uploaded) :
Now at boot my PC prompts 2 times hd1, gpt2 UUID without dashes…
sparse file not allowed…” error.
452: out of range pointer: 0x95d67020
Aborted. Press any key to exit
the third time, it prompts hd1,gpt2, UUID with dashes
and it’s OK
NB : no such a crypto disk message disappear with Philm command (sudo pacman etc Great Thanks to Philm !)
For information :
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=0118-AEE6 /boot/efi vfat umask=0077 0 2
/dev/mapper/luks-bab359ae-44e6-42f6-89ec-7d25913c7c37 / ext4 defaults,noatime 0 1
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
I dare not to delete dashes from cfg (because I get impression system is mounting when it prompts UUID with dashes)
I dare not make this change (I had seen before boustanihani post) because He still has to put 2 times the PW (me 3)
I noticed I have two Boot Priorities in my Bios on my Manjaro SSD.
I switched to the other boot option, simply named “manjaro” (not UEFI).
This magically solved all issues, the “452: out of range pointer” error is gone, and I no longer need to enter the password twice.
Is it the non UEFI mode that solved the problem?
Below are some screenshots for my BIOS and my partition on the SSD.