package grub-pc 2.04-1ubuntu26.4 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1

[Scott Talbert]

This happened when upgrading my machine from 18.04 -> 20.4.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-pc 2.04-1ubuntu26.4
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Oct 6 14:38:07 2020
DuplicateSignature:
 package:grub-pc:2.04-1ubuntu26.4
 Setting up grub-pc (2.04-1ubuntu26.4) ...
 dpkg: error processing package grub-pc (--configure):
  installed grub-pc package post-installation script subprocess returned error exit status 1
ErrorMessage: installed grub-pc package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2013-11-04 (2527 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=08068afd-7442-4bb5-b53a-76f24196407d ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: grub2
Title: package grub-pc 2.04-1ubuntu26.4 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-06 (0 days ago)

[Scott Talbert (swt-techie)]

Here's running dpkg --configure grub-pc with "set -x" in grub-pc.postinst.

[Scott Talbert (swt-techie)]

I have two hard drives in an MD RAID configuration as my boot device(s).

[Scott Talbert (swt-techie)]

Seems possibly related to bug #1896608, but I don't have grub-efi-* installed.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Julian Andres Klode (juliank)]

Same bug nonetheless, the log tells us it skipped the question and this was accidentally treated as a failure.