Hello, I am a proxmox and linux n00b so please excuse my poor explanations and also please remember to explain things like you would to a child.
I had a healthy running version of proxmox and tried to update to a newer version of proxmox and somewhere along the way I really screwed things up. while running the `pveXtoY` tool I got a message that `grub-efi-amd64` was not installed. So I ran `apt install grub-efi-amd64` and it then next time I booted it stopped working. Anytime I turn it on after it gets to the screen with
Then it just stays there...
I am able to boot to the recovery mode where I immediately tried to uninstall `grub-efi-amd64` and re-install `grub-pc`. I had hoped this would work and fix things, but that was not the case. I tried a few other things I found googling around like running `update-grub` and then `grub-install /dev/xxx` but still I get stuck on the same screen.
I also looked through the `journalctl -xb` and googled all the errors, most seemed to be "normal, just ignore it" except there was one issue with the network interface names which I think I fixed by editing the `/etc/network/interfaces` file because those errors are no longer showing up in the journal.
I don't have anything "important" saved on the proxmox disk other than the VMs- unless there is a way to save the config and data of the TrueNAS VM I have on there. Basically I only care about the TrueNAS VM because I don't want to have to setup the permissions and shares all over again and potentially lose the data (which is stored on totally different drives than the one running proxmox).
Other background info- I didn't do any special modifications to my setup at all except for following the walkthrough to get PCI-passthrough for an nvidia graphics card to do hardware acceleration for Plex on one of my VMs... I know that had some updates to the "grub".
I had a healthy running version of proxmox and tried to update to a newer version of proxmox and somewhere along the way I really screwed things up. while running the `pveXtoY` tool I got a message that `grub-efi-amd64` was not installed. So I ran `apt install grub-efi-amd64` and it then next time I booted it stopped working. Anytime I turn it on after it gets to the screen with
Code:
Found volume group "pve" using metadata type lvm2
5 logical volume(s) in volume group "pve" now active
/dev/mapper/pve-root: recovering journal
/dev/mapper/pve-root: clean, 74313/6291456 files, 12254815/25165824 blocksThen it just stays there...
I am able to boot to the recovery mode where I immediately tried to uninstall `grub-efi-amd64` and re-install `grub-pc`. I had hoped this would work and fix things, but that was not the case. I tried a few other things I found googling around like running `update-grub` and then `grub-install /dev/xxx` but still I get stuck on the same screen.
I also looked through the `journalctl -xb` and googled all the errors, most seemed to be "normal, just ignore it" except there was one issue with the network interface names which I think I fixed by editing the `/etc/network/interfaces` file because those errors are no longer showing up in the journal.
I don't have anything "important" saved on the proxmox disk other than the VMs- unless there is a way to save the config and data of the TrueNAS VM I have on there. Basically I only care about the TrueNAS VM because I don't want to have to setup the permissions and shares all over again and potentially lose the data (which is stored on totally different drives than the one running proxmox).
Other background info- I didn't do any special modifications to my setup at all except for following the walkthrough to get PCI-passthrough for an nvidia graphics card to do hardware acceleration for Plex on one of my VMs... I know that had some updates to the "grub".