I’m having this annoying issue:
When I start the computer,it goes as follow:
1 - Ask for the LUKS key
2 - Boot menu appears
3 - after selection of any entry (all Majaro): “452 out of range pointer…” error
4 - Ask for LUKS key again
5 - Boot menu appear again
6 - After selection of any entry: It starts normally
It’s been about a month I’m having this issue. It came after the install of new grub package. I tryied pretty much all the tricks mentioned on the forum and I can’t find a way to fix it. Maybe somebody has a clu?
My install is straight forward: 1 drive, 1 OS, and partition is encrypted
Reinstall grub boot loader from
@j8a thanks, it worked!
But since I did not need to follow all those steps, I just wanted to leave the differences on this thread so people who stumble upon it in the future know. In my case there is no need to chroot as my Manjaro install is booting normally, I just couldn’t use my grub install to boot another arch linux installation, so in my case all I needed to do was reinstall grub:
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro
Before running sud…
For future visitors, this is how you succesfully chroot an encrypted uefi system
cryptsetup luksOpen /dev/sda2 ssd ( here > name of the drive )
cryptsetup luksOpen /dev/sda3 swap
mount /dev/mapper/ssd /mnt
mount /dev/sda1 /mnt/boot/efi
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -t devpts pts /mnt/dev/pts/
Ok. Lets do that like at the second link.
Start again with your live usb.
Start with (i will replace the drives with the one from your blkid. If it says /directory doesnt exist, then you have to mkdir)
root # mount /dev/nvme0n1p8 /mnt
root # mount /dev/nvme0n1p6 /mnt/boot
root # mount /dev/nvme0n1p5 /mnt/boot/efi
"Create the chroot environment and use bash as shell "
root # manjaro-chroot /mnt /bin/bash
He suggests Reinstall Grub
"One possible cause why yo…
@bogdancovaciu for the links
I was hoping to avoid a reinstall, but I guess I’ll have to
So reinstalling grub didn’t change a thing.
Re-installing grub like
@bogdancovaciu suggested, solved this problem for me. Reinstall grub like this.
Edit: A reboot later I was back to where it started like
@Cigalon said. I saw somewhere else that having linux 515 and 610 together can be problematic. Deleted 515 and everything is fixed.