Hi,
I’m using Aeon on my laptop for a month more or less without any problems.
Today I started it and instead of booting into Aeon it went straight to windows (which has is own ESP partition and is installed in a completely different disk) and searching a bit inside the BIOS not only the entry for Aeon is not present anymore but also the grub folder in boot is empty. How can I fix the grub due to the fact that Aeon is atomic instead of a “normal” system? Chroot seems to not work either giving my the error “unknown file system type 'crypto_LUKS”.
Is that from a “rescue system”?
When yes, you did not explain what that system is, but apparently it does not have to software to handle Luks encrypted file systems.
I’m not dual booting in the real sense of it. I’ve two SSD one with Windows 11 and one with Aeon. Both of them as their ESP partition on their disk and I boot windows only when needed by using a key on boot and entering the UEFI menu. If I disconnect the windows disks is like nothing change from Aeon perspective and vice versa.
Exactly, I really don’t understand what you mean, is on it’s disk and there is no way to boot windows from aeon grub, so no, I’m not dual booting. Is like if I was physically detaching one disk and attaching the other if I boot into windows. There is no overlap
@ParanoidNemo OK, If another operating system is present in the system UEFI nvram, it is not supported… By design it’s single boot, if your plugging and unplugging disks, it’s not supported…
Did you try pressing the spacebar at boot to get to the systemd-boot menu and boot from a previous snapshot?
Are you using TPM2? Are you using secure boot and fallback mode?
Ok now it’s a little bit clearer thanks. No I didn’t try, I’ll check if it gives me the opportunity to boot from another snapshot. I’m not using TPM2 because is not present in my laptop and no secure boot (I’d Nvidia problems with it). If doesn’t work I’ll reinstall tumbleweed at this point so at least the dual boot is supported.