Grub install failed during a recent Debian update

[fsociety3765]

Hi all,

I have Proxmox installed on a ZFS mirror. My server has been up and running for over one and a half years now and I have had no major issues.

I am current running:

pve-manager/7.2-7/d0dd0e85 (running kernel: 5.15.39-4-pve)

My zpool looks like this:

  pool: rpool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:56 with 0 errors on Sun Sep 11 00:24:58 2022
config:

    NAME                                               STATE     READ WRITE CKSUM
    rpool                                              ONLINE       0     0     0
      mirror-0                                         ONLINE       0     0     0
        ata-SuperMicro_SSD_SMCxxxxDxxxxxDQMxxxx-part3  ONLINE       0     0     0
        ata-SuperMicro_SSD_SMCxxxxDxxxxxDQMxxxx-part3  ONLINE       0     0     0

During the most recent update to Debian, carried out from the web interface...

Start-Date: 2022-09-10  23:55:53
Commandline: apt-get dist-upgrade
Upgrade: dpkg:amd64 (1.20.11, 1.20.12), libcurl4:amd64 (7.74.0-1.3+deb11u2, 7.74.0-1.3+deb11u3),
udev:amd64 (247.3-7, 247.3-7+deb11u1), krb5-locales:amd64 (1.18.3-6+deb11u1, 1.18.3-6+deb11u2),
libgssapi-krb5-2:amd64 (1.18.3-6+deb11u1, 1.18.3-6+deb11u2),
libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u2, 7.74.0-1.3+deb11u3),
systemd-timesyncd:amd64 (247.3-7, 247.3-7+deb11u1), libpam-systemd:amd64 (247.3-7, 247.3-7+deb11u1),
libavahi-common-data:amd64 (0.8-5, 0.8-5+deb11u1), grub-pc-bin:amd64 (2.04-20, 2.06-3~deb11u1),
libsystemd0:amd64 (247.3-7, 247.3-7+deb11u1), libnss-systemd:amd64 (247.3-7, 247.3-7+deb11u1),
libkrb5support0:amd64 (1.18.3-6+deb11u1, 1.18.3-6+deb11u2), systemd:amd64 (247.3-7, 247.3-7+deb11u1),
libudev1:amd64 (247.3-7, 247.3-7+deb11u1), libc6:amd64 (2.31-13+deb11u3, 2.31-13+deb11u4),
locales:amd64 (2.31-13+deb11u3, 2.31-13+deb11u4), libkrb5-3:amd64 (1.18.3-6+deb11u1, 1.18.3-6+deb11u2),
base-files:amd64 (11.1+deb11u4, 11.1+deb11u5), libk5crypto3:amd64 (1.18.3-6+deb11u1, 1.18.3-6+deb11u2),
libkrad0:amd64 (1.18.3-6+deb11u1, 1.18.3-6+deb11u2), libpcre2-8-0:amd64 (10.36-2, 10.36-2+deb11u1),
libavahi-common3:amd64 (0.8-5, 0.8-5+deb11u1), grub-efi-amd64-bin:amd64 (2.04-20, 2.06-3~deb11u1),
grub2-common:amd64 (2.04-20, 2.06-3~deb11u1), libc-dev-bin:amd64 (2.31-13+deb11u3, 2.31-13+deb11u4),
libc-l10n:amd64 (2.31-13+deb11u3, 2.31-13+deb11u4), grub-common:amd64 (2.04-20, 2.06-3~deb11u1),
libc-bin:amd64 (2.31-13+deb11u3, 2.31-13+deb11u4), libc-devtools:amd64 (2.31-13+deb11u3, 2.31-13+deb11u4),
libc6-dev:amd64 (2.31-13+deb11u3, 2.31-13+deb11u4), grub-efi-ia32-bin:amd64 (2.04-20, 2.06-3~deb11u1),
systemd-sysv:amd64 (247.3-7, 247.3-7+deb11u1), curl:amd64 (7.74.0-1.3+deb11u2, 7.74.0-1.3+deb11u3),
libgssrpc4:amd64 (1.18.3-6+deb11u1, 1.18.3-6+deb11u2), grub-pc:amd64 (2.04-20, 2.06-3~deb11u1),
libavahi-client3:amd64 (0.8-5, 0.8-5+deb11u1), libhttp-daemon-perl:amd64 (6.12-1, 6.12-1+deb11u1),
linux-libc-dev:amd64 (5.10.136-1, 5.10.140-1)

...a message appeared saying the grub-pc configuration failed to install grub. It asked me if I wanted to "continue anyway", with the options of "yes" or "no". I opted for "no". The "apt" process appeared to finish. It wasn't until a few days later that I realized that the process didn't complete when trying to carry out some further updates and being told the "lock could not be acquired as was in use by apt-get"

I killed the process and did a dpkg --configure -a, it picked up the upgrade back at the grub-install and again failed with the same message. This time I selected "yes".

I need to find out if grub is indeed installed correctly before I reboot. Perhaps just carry out a manual install.

The partition layout of the drives looks like this. The ZSF mirror from above is made up of partition 3 from each device.

sda           8:0     0  118G  0 disk
├─sda1        8:1     0 1007K  0 part
├─sda2        8:2     0  512M  0 part
├─sda3        8:3     0 59.5G  0 part
└─sda4        8:4     0   50G  0 part
sdb           8:16    0  118G  0 disk
├─sdb1        8:17    0 1007K  0 part
├─sdb2        8:18    0  512M  0 part
├─sdb3        8:19    0 59.5G  0 part
└─sdb4        8:20    0   50G  0 part

I can't remember now if I installed Proxmox using legacy BIOS or UEFI? I used the Proxmox GUI installer and I don't recall having a choice. What is the default? Is there a way to check if I'm legacy BIOS or UEFI?

If legacy BIOS, I think I just need to run grub-install /dev/sda /dev/sdb.

Any help or advice would be greatly appreciated.

FS

 

[leesteken]

According to this thread. it's already recently fixed in pve-kernel-helper and you just need to re-run apt-get update before apt-get dist-upgrade.

 

[fsociety3765]

According to this thread. it's already recently fixed in pve-kernel-helper and you just need to re-run apt-get update before apt-get dist-upgrade.

Awesome. I will have a look over that.

Thank you.

FS