OK so encrypted my system drive during install. So far so cool. It also prompts me to enter the password before loading the OS. However if I misstype it it kicks me in grub rescue mode instead of asking me to reenter it. Wtf D: Can I change this?

So I wanted a newer Linux OS for doing certain things at work. I went for Kubuntu 21.04 as it would have reasonably newer software and had the tools I needed for managing exfat partitions. I installed it on a second drive and everything went smoothly. I booted to the OS and it said it needed to do updates. Okay, lets do that. I started them and walked away.

I came back later and it had finished. I rebooted the machine because I needed to run windows. It came up to a prompt and a grub command line. WTF. I am like oh fuck, it didn't just fuck me out of my windows install. So I rebooted into the BIOS. I looked and it now had switched the drive I installed Linux on as the boot drive. That is weird. So I switched the M.2 drive to boot. It went right into Windows.

Kubuntu 21.04 installed on second drive as intended, switched the boot drive to the second drive, and then fucked itself on first update. And people wonder why non-techies don't run Linux. Its a pile of shit only a masochist would love. Because we are the only ones who can possibly sort out shit like this.

I know its probably a webpage away from fixing, but I needed to work in windows and could not be fucked to fix it. Its a distraction to actually getting my work done. Just disappointed in the entire ecosystem.

UGH.

I hate when I have to debug an issue and find out its somewhere entirely else, than I was looking.

>Installs a virtual server on the Proxmox VE platform
>Reboots and grub be like "No such device *UUID*"
Whut?

Okay, so... reinstall grub, maybe a bug in the automated install?
>Nop.exe, still an issue
Huh...
>Partition tables all good, drives all visible when booted from a live environment, grub is up to date
>Finally gives up and goes to mess in the (terrible) grub rescue environment
>Grub only sees (hd0) while root is on (hd2), what?
>A whole lot of cursing ensues, wtf?

Turns out it was a bug, but not in grub... Rather, in the QEMU-KVM agent daemon, wtf!

I never had to deal with a bug in the virtualization agent itself.

Downgrading from pve-qemu-kvm 5.0.x to 4.0.x solved the issue.

Now, maybe, I can finally go have my lunch...

Ok. Kill me now. WTF! This thing gets to 100% and starts all over again? Probably going to mess up Grub. I hate these updates. Restarted twice now!