Pop OS 22.04 LTS Grub bootloader not working

Forum home -> General Chat -> View topic

Post

Posted
Rating:
#1048 (In Topic #468)
Liy
Avatar
Standard member

Stuck at troubleshooting LUKS volume name.

Hey I am at this step on the "Repair the bootloader" process. I have also watched your video- jacobgkau and followed all the steps you went through.
Repair the Bootloader - System76 Support   (I am stuck at the last part of this page - LUKS Volume name under troubleshooting)
This is my specific setup:

Grub Bootloader on Pop OS that was installed in Legacy BIOS mode and I am unable to reach the log in screen, so my bootloader may be the cause.
My main device is a LUKS Device on sda2 which I decrypted 1st and then tried to mount. However, terminal showed an error while mounting sda2. -mount: /mnt: unknown filesystem type 'crypto_LUKS'.

I overlooked the above error and moved on to mounting my boot sda1 partition which was successful. Since I do not have an efi file, I only typed sudo mount /dev/sda1 /mnt/boot/.

I found no issues after following all the steps after sudo chroot /mnt. The terminal upgraded the grub-efi-amd64, the -bin and the -signed.

Then i reinstalled grub-efi-amd64, linux-generic and linux-headers-generic. This completed successfully as well.

On typing update-initramfs -c -k all i came across an issue where the target 'cryptdata' was not found in /etc/crypttab.
When i opened /mnt/etc/crypttab, i found that the cryptdata UUID did not have 'luks-' but the remaining UUID of the cryptdata was intact.

Also, unlike what is decribed on the support.system76 site under troubleshooting LUKS volume name, in my crypttab file, there is not string of characters after cryptdata.

After confirming this I reran the update- initramfs -c -k all command but the result did not change, showing the same error:
cryptsetup: WARNING: target 'luks-<cryptdata>' not found in /etc/crypttab.

Please help me out, I will be grateful!
Thank you!
Online now: No Back to the top

Post

Posted
Rating:
#1049
Avatar
NOTS Staff
You can't just "overlook" failing to mount your root partition. I can't tell for sure because of how disjointed your post is, but I'd suspect you didn't get the chroot set up correctly.

Please copy/paste the exact, complete terminal history for the commands that you're running when trying to follow the steps on the webpage. That's the only way to see what you're actually doing and what might be wrong.
Online now: No Back to the top

Post

Posted
Rating:
#1051
Liy
Avatar
Standard member
Thank you for replying!
I have decided to reinstall linux as I have spent too much time trying to figure out what went wrong.
Online now: No Back to the top
1 guest and 0 members have just viewed this.