I did not use cryptsetup + mount + manjaro-chroot because I was able to boot into my OS with some tricks.
update-grub seems to work
But mkinitcpio throws some errors. How can I remove the preset for 6.0? The kernel application and mhwd-kernel do not list it as installed (I think because the kernel was removed) EDIT: I will move /etc/mkinitcpio.d/linux60.present to my desktop
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux60.preset: 'default'
-> -k /boot/vmlinuz-6.0-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.0-x86_64.img
==> ERROR: specified kernel image does not exist: '/boot/vmlinuz-6.0-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux60.preset: 'fallback'
-> -k /boot/vmlinuz-6.0-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.0-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: '/boot/vmlinuz-6.0-x86_64'
Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: error: disk `hostdisk//dev/nvme0n1p1' not found.
What can I fix this error?
I’m currently to afraid to reboot just for testing
@Zesko grub-install have worked in chroot (and I forget to execute and write down the result of df -H /boot/efi - but I think this is no longer necessary). So I guess I have successfully reinstalled grub.
@Zesko Can you fix the typo in sudo mkinicpio -P to sudo mkinitcpio -P for the next person who will execute this command?
The current situation is, that my mainboard detects two possible boot methods.
I had the same error trying to boot an encrypted system & followed the steps to reinstall Grub. Unfortunately, now I am just in some weird loop where it keeps taking me to the boot menu where all I can do is select my main SSD & it starts all over again.
I am trying to find a solution online but finding it very confusing. I think I need to some how mount my encrypted disk & chroot into it. I’m lost currently! I do have a Timeshift restore point but don’t know how to get to it.
@Tobiwan Thanks! Okay, so I’m into my system. I’m just unsure how to fix my system from here. There seem to be several approaches suggested. When I followed the “sudo mkinitcpio -P” and then updated Grub, that’s when my problems got worse. Before that, I could at least boot into my system. I have a Timeshift restore point. Should I apply that & try the update again? Thanks a lot for your help. Ruziel…
I assumed maybe grub got my disks mixed up or something, so at the “error: no such cryptodisk found…” error message, I unplugged my external USB drive. This allowed the system to continue booting to the grub menu, where I selected to fall back to an old kernel (5.19).
So the system is running now but I am afraid to reboot.
I am looking into restoring a Timeshift snapshot to fix this, however other post on this forum indicate that Timeshift does not support restoring of full disk encrypted drives.
I was able to follow the wiki article (after I first fsck’d my LUKS partitions via gnome-disk-utility) until I got to the command grub-mkconfig -o /boot/grub/grub.cfg, at which point I get the following errors:
grub-mkconfig errors
[manjaro /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done
Same problem afterwards: I enter the password, it says “Slot 0 Opened,” then after a couple seconds, the system powers off, then powers itself back on and goes into the BIOS screen
Sorry to say it, but it is this type of issue that drives users away from Manjaro.
Update your system = boot failure. This should never happen. If it is due to an update to the way grub works (or doesn’t) with encrypted disks, then the update scripts should check for disk encryption on the host system and take appropriate action to avoid a non-bootable system.
Currently, this thread is chock full of different solutions that may or may not work to fix the problem, leaving less adept users stuck with a broken system and no idea what to do next.
I just went from being a big Manjaro fan (seriously, I own a T-shirt ) to fairly disillusioned, in a matter of 5 minutes.
I’ve just done another complete backup of my home folder. Trying to work up the courage to roll the dice on a reboot after making some of the changes mentioned in this thread.
I just rebooted, and I still get the same error message but then it proceeds to boot anyway.
I don’t understand. It feels like it is only a matter of time before it breaks again.
Yeah, I’m downloading images to my Ventoy disk.
If I can’t get it going again, I don’t want to use a rolling release for my work machine.
This has cost me a day.
It’s a shame. There is so much to love about Manjaro, but this type of thing is simply unacceptable for a machine that I rely on every day. My daughter also runs Manjaro on her main workstation (which she uses to run her business) so now I have to warn her not to update and think about migrating her to a different distro. What a headache.
At least I have discovered that Timeshift is useless if you are using full disk encryption. I need to go back to the drawing board and figure out something that actually works.
OOF. What about timeshift + btrfs + FDE?
Or if not Timeshift, what about OpenSUSE’s Snapper utility, which manages btrfs snapshots? That should be worth trying.
I was using it for a little while, but got off of OpenSUSE Tumbleweed because it was frustrating to use the root password everywhere (They’re not a fan of PolKit/gksudo?!?!)
) to fairly disillusioned, in a matter of 5 minutes.
