Recovering from the grub2 update issue

Due to the latest grub2 update, there may be some instances when updating a Proxmox node through the GUI causes issues, breaking packages. This is specifically true for an earlier release such as Proxmox 3.4. All the newer versions of Proxmox seem to have this issue fixed. To prevent this issue from happening, it is best to upgrade a node, through SSH, or console by logging in directly on the node and not through the GUI. If the upgrade has already been applied through the GUI and there are unconfigured packages due to issues, perform the following steps to fix the issue:

• Check package status with:

  # pveversion –v
  

• Before configuring grub, we need to know the device where Proxmox is installed. We can find the device by running the following command:

  # parted -l 
  

• If there are incorrect packages, run the following commands to kill the background dpkg process and configure all the packages, including the new grub2:

  # killall dpkg
  # dpkg --configure –a
  

• Select...