Trying to figure out why a few of my Bullseye VM's are still booting from grub 2.02 ....... beta3-5 when the latest grub 2.04 is installed. These systems were updated from Buster and again I verified and even tried to re-install grub 2.04, but the terminal showed the latest 2.04 is already there. Maybe I selected or clicked an incorrect button during the upgrade to Bullesye. Many of my other Bullseye systems are correctly booting from 2.04. Lets assume I made an operator error during upgrade. NOW ---- how to I go about getting these systems to boot grub 2.04 since its already good to go according to Debian's apt-get and the terminal. Booting these systems on grub 2.02 leaves them working fine and everything. I would appreciate direction here.
You did a « sudo grub-install \dev\sda » followed by a « sudo update-grub » ? (Replacing \dev\sda with your own drive choice)
I will look at this when I get back home in a day or two. I did notice that for some reason my bare metal Bullseye systems are all running 2.04X, BUT the VM's are booting 2.02X. I am curious if this has anything to do with the VirtualBox config's. Never heard of such a thing but just making note of an observation in case anyone else see it on their systems.
I recreated the issue by upgrading a saved Buster VM again just to watch it. At one point you have the option to keep the grub the same OR to update to the new one. I clicked to keep the grub since it appeared to be the default recommendation. That is where the issue came from on my end. Once I realized what I did, I manually updated Grub. A "bone head" move during the update.
