Dpkg ошибка при обработке пакета grub pc

0

1

dpkg: ошибка при обработке пакета grub-pc (--configure):
 пакет абсолютно неработоспособен; перед настройкой его
 следует переустановить

root@alexrsk-desktop:~#  dpkg --configure -a
Настраивается пакет libapt-inst2.0:amd64 (1.6.8) …
Настраивается пакет deja-dup (37.1-2fakesync1ubuntu0.1) …
Настраивается пакет apt-transport-https (1.6.8) …
Обрабатываются триггеры для mime-support (3.60ubuntu1) …
Обрабатываются триггеры для ureadahead (0.100.0-20) …
ureadahead will be reprofiled on next reboot
Обрабатываются триггеры для desktop-file-utils (0.23-1ubuntu3.18.04.2) …
Настраивается пакет apt-utils (1.6.8) …
dpkg: ошибка при обработке пакета grub-pc (--configure):
 пакет абсолютно неработоспособен; перед настройкой его
 следует переустановить
Обрабатываются триггеры для libglib2.0-0:amd64 (2.56.3-0ubuntu0.18.04.1) …
Настраивается пакет opera-stable (58.0.3135.53) …
Обрабатываются триггеры для libc-bin (2.27-3ubuntu1) …
Обрабатываются триггеры для systemd (237-3ubuntu10.11) …
Обрабатываются триггеры для man-db (2.8.3-2ubuntu0.1) …
Обрабатываются триггеры для shared-mime-info (1.9-2) …
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Настраивается пакет avahi-autoipd (0.7-3.1ubuntu1.2) …
Обрабатываются триггеры для gnome-menus (3.13.3-11ubuntu1.1) …
Обрабатываются триггеры для dbus (1.12.2-1ubuntu1) …
Обрабатываются триггеры для hicolor-icon-theme (0.17-2) …
Настраивается пакет libavahi-common-data:amd64 (0.7-3.1ubuntu1.2) …
Настраивается пакет libavahi-common3:amd64 (0.7-3.1ubuntu1.2) …
Настраивается пакет libavahi-core7:amd64 (0.7-3.1ubuntu1.2) …
Настраивается пакет avahi-daemon (0.7-3.1ubuntu1.2) …
Настраивается пакет libavahi-client3:amd64 (0.7-3.1ubuntu1.2) …
Настраивается пакет avahi-utils (0.7-3.1ubuntu1.2) …
Настраивается пакет python3-distupgrade (1:18.04.30) …
Настраивается пакет python3-update-manager (1:18.04.11.9) …
Настраивается пакет ubuntu-release-upgrader-core (1:18.04.30) …
Устанавливается новая версия файла настройки /etc/update-manager/release-upgrades …
Настраивается пакет ubuntu-release-upgrader-qt (1:18.04.30) …
Настраивается пакет ubuntu-release-upgrader-gtk (1:18.04.30) …
Настраивается пакет update-manager-core (1:18.04.11.9) …
Настраивается пакет update-notifier-common (3.192.1.5) …
Настраивается пакет update-notifier (3.192.1.5) …
Настраивается пакет update-manager (1:18.04.11.9) …
Обрабатываются триггеры для libc-bin (2.27-3ubuntu1) …
При обработке следующих пакетов произошли ошибки:
 grub-pc

My problem begins with an upgrade from Ubuntu 12.04 LTS to 14.02 LTS. As part of this I received several error messages about not being able to remove old kernels.

When first booting into 14.02, I checked everything was ok by running sudo apt-get autoremove, the same errors appeared.

Following a guide online, I ran the following:

sudo apt-get purge grub-common
sudo apt-get install grub-pc

The first operation succeeded, removing grub from my pc. The second operation failed with the following:

Creating config file /etc/default/grub with new version
Installing for i386-pc platform.
Installation finished. No error reported.
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-3.13.0-54-generic
Found initrd image: /boot/initrd.img-3.13.0-54-generic
Found linux image: /boot/vmlinuz-3.13.0-44-generic
Found initrd image: /boot/initrd.img-3.13.0-44-generic
Found linux image: /boot/vmlinuz-3.13.0-40-generic
Found initrd image: /boot/initrd.img-3.13.0-40-generic
Adding boot menu entry for EFI firmware configuration
cat: /video.lst: No such file or directory
/usr/sbin/grub-probe: error: failed to get canonical path of `'.
No path or device is specified.
Usage: grub-probe [OPTION...] [OPTION]... [PATH|DEVICE]
Try 'grub-probe --help' or 'grub-probe --usage' for more information.
dpkg: error processing package grub-pc (--configure):
 subprocess installed post-installation script returned error exit status 64
Errors were encountered while processing:
 grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have tried numerous fixes for this, most of which are documented here. I created a LiveCD before removing grub-common, so I have access to my old partition and can mount and chroot into it.

But when running update-grub the same error appears, I also cannot run dpkg --configure -a without this occurring.

I used boot-repair to get a boot summary for my machine, which is a 2 HDD rig with dual boot on the first drive (/dev/sda). With Windows on /dev/sda1 and my Ubuntu partition (also boot) on /dev/sda2.

Please help me fix this and I promise I won’t touch my Ubuntu install ever again.

Во время настройки GRUB в среде OpenStack на ВМ с носителями вида /dev/vda возникают ошибки вида:

Настраивается пакет grub-pc (2.02+dfsg1-20+deb10u4+ci202109241449+astra3) …
/dev/sda does not exist, so cannot grub-install to it!

dpkg: ошибка при обработке пакета grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error exit status 1
При обработке следующих пакетов произошли ошибки:
grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)

Диагностика

Возможные причины

On one of my machines dpkg is unable to finish installing/configuring grub, only giving the error message:

subprocess installed post-installation script returned error exit status 255

Full output:

# dpkg --configure grub-pc
Setting up grub-pc (1.99-27+deb7u3) ...
device node not found
device node not found
device node not found
device node not found
Installation finished. No error reported.
Installation finished. No error reported.
dpkg: error processing grub-pc (--configure):
 subprocess installed post-installation script returned error exit status 255
Errors were encountered while processing:
 grub-pc

There is nothing in the log files that would shed any more light.

Running dpkg with some debug options reveals a little more:

# dpkg -D10113 --configure grub-pc
Setting up grub-pc (1.99-27+deb7u3) ...
D000002: fork/exec /var/lib/dpkg/info/grub-pc.postinst ( configure  )
device node not found
device node not found
device node not found
device node not found
Installation finished. No error reported.
Installation finished. No error reported.
dpkg: error processing grub-pc (--configure):
 subprocess installed post-installation script returned error exit status 255
D010000: trigproc_run_deferred
Errors were encountered while processing:
 grub-pc

Now I know the problem is someplace in /var/lib/dpkg/info/grub-pc.postinst configure, but that script doesn’t seem to have any verbosity or debug options and is just to large to read through with nearly 700 lines. The script also doesn’t have any exit 255 calls, so I tend to believe the problem isn’t even in there but in some other script that is called.

The configure task also fails for the kernel processes:

# dpkg --configure linux-image-3.16.0-0.bpo.4-amd64
Setting up linux-image-3.16.0-0.bpo.4-amd64 (3.16.39-1+deb8u1~bpo70+1) ...
vmlinuz(/boot/vmlinuz-3.16.0-0.bpo.4-amd64
) points to /boot/vmlinuz-3.16.0-0.bpo.4-amd64
 (/boot/vmlinuz-3.16.0-0.bpo.4-amd64) -- doing nothing at /var/lib/dpkg/info/linux-image-3.16.0-0.bpo.4-amd64.postinst line 263.
initrd.img(/boot/initrd.img-3.16.0-0.bpo.4-amd64
) points to /boot/initrd.img-3.16.0-0.bpo.4-amd64
 (/boot/initrd.img-3.16.0-0.bpo.4-amd64) -- doing nothing at /var/lib/dpkg/info/linux-image-3.16.0-0.bpo.4-amd64.postinst line 263.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-0.bpo.4-amd64
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 255
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.16.0-0.bpo.4-amd64.postinst line 634.
dpkg: error processing linux-image-3.16.0-0.bpo.4-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-3.16.0-0.bpo.4-amd64

Line 634 in /var/lib/dpkg/info/linux-image-3.16.0-0.bpo.4-amd64.postinst boils down to this command:

run-parts --report --exit-on-error --arg=3.16.0-0.bpo.4-amd64 --arg=/boot/vmlinuz-3.16.0-0.bpo.4-amd64 /etc/kernel/postinst.d

Running this command manually results in:

run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 255

This script is, as far as I can tell, only a wrapper that does a check and then calls update-grub, which works without error.

update-grub just runs grub-mkconfig, so I ran this command and checked the return value:

# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.16.0-0.bpo.4-amd64
Found initrd image: /boot/initrd.img-3.16.0-0.bpo.4-amd64
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
# echo $?
255

This seems to be the culprit. The script works, finds all kernels, generates a valid grub config (saves it as /boot/grub/grub.cfg.new though) and then exits with return code 255. And of course it doesn’t have any debug options.

How can I go on debugging the problem?

Additional information that might or might not be helpful:

• the system is running debian wheezy
• GRUB is version 1.99-27+deb7u3
• the system has an mdraid
• the system has been running for years, it’s not a new installation. The error appeared only recently
• not quite sure, but I believe the error started to appear after a faulty hard drive was replaced
• the configure task only fails for grub and the kernel packages. All other packages can be installed without error

More information from questions that came up later

zulu668:~# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda4[2] sdb4[1]
      1456504640 blocks super 1.2 [2/2] [UU]

md1 : active raid1 sda3[2] sdb3[1]
      7996352 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sda2[2] sdb2[1]
      499392 blocks super 1.2 [2/2] [UU]

unused devices: <none>
zulu668:~# sudo mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Wed Oct 29 12:40:33 2014
     Raid Level : raid1
     Array Size : 499392 (487.77 MiB 511.38 MB)
  Used Dev Size : 499392 (487.77 MiB 511.38 MB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Wed Mar 15 14:51:01 2017
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : zulu668:0  (local to host zulu668)
           UUID : 22e14818:7754cf01:67287402:c31a3328
         Events : 217

    Number   Major   Minor   RaidDevice State
       2       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2