从17.10升级到18.04时出错(shim签名和grub-efi-amd64签名)


13

sudo do-release-upgrade今天早上运行将系统从Ubtunu 17.10升级到18.04 LTS后,我在升级过程中遇到错误。跟踪太长,无法完整地发布,但是这对我来说似乎是问题所在:

Rebuilding /usr/share/applications/bamf-2.index...
Errors were encountered while processing:
 shim-signed
 grub-efi-amd64-signed
Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an error code (1)

Could not install the upgrades 

The upgrade has aborted. Your system could be in an unusable state. A 
recovery will run now (dpkg --configure -a). 

Setting up shim-signed (1.34.9+13-0ubuntu2) ...
Installing for x86_64-efi platform.
Could not add entry to BootOrder: Interrupted system call
grub-install: error: efibootmgr failed to register the boot entry: No such device or address.
dpkg: error processing package shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned error exit status 1
Setting up grub-efi-amd64-signed (1.93+2.02-2ubuntu8) ...
Installing for x86_64-efi platform.
Could not add entry to BootOrder: Interrupted system call
grub-install: error: efibootmgr failed to register the boot entry: No such device or address.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script     subprocess returned error exit status 1
Errors were encountered while processing:
 shim-signed
 grub-efi-amd64-signed

Upgrade complete

The upgrade has completed but there were errors during the upgrade process.

我浏览论坛的解决方案,并能抢先确认中的条目/etc/fstab没有注释掉cat /etc/fstab输出以下内容:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda9 during installation
UUID=a2f91309-dc7e-4456-b3ef-89900b145365 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda2 during installation
UUID=90EA-4FB8  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/sda6 during installation
UUID=2f80d8f4-5609-45e1-854d-578ab25836c3 none            swap    sw              0       0

该系统是Windows 10双重引导系统。通过lsb_release -a我可以确认我的Ubuntu分区确实更新为18.04 LTS,但是这些错误使我感到不安,并且我不希望它们长期引起问题。谢谢。


您的系统启动进入Ubuntu了吗?
有机大理石'18

2
是的,系统启动正常。
巴雷特

有趣的问题。我认为您还可以,但希望一些专家会提供实际答案。
有机大理石

Answers:


18

我有完全一样的错误。我找到的用于升级剩余的最后两个软件包的解决方案是:

sudo su -
cd /boot/efi/EFI
mv ubuntu ubuntu-old
apt install -f
mv ubuntu-old ubuntu
update-grub2
exit

希望对您有所帮助。


有趣的解决方案。您能解释一下为什么mv ubuntu ubuntu-old和之后恢复apt install -f吗?
WinEunuuchs2Unix

1
@ WinEunuuchs2Unix似乎由于某种原因,较新的grub无法访问/ boot / efi / EFI / ubuntu目录。因此,由于我的系统正常启动,因此我每次使用apt时都希望摆脱该错误。因此,我认为该变通方法只是为了检查安装是否完成,并且似乎可行。最后,我恢复了ubuntu目录名,但又不会影响系统的启动能力。看来,我忘了提事了update-grub2
乔治·塔万佐波洛斯

似乎奏效了。非常感谢你!
巴雷特

1
它对我有用,
Rqomey

这为我工作在Ubuntu 18.04与二次SSD驱动器(Linux的斯特凡-N56VM 4.15.0-50泛型#54,Ubuntu的SMP周一5月6日18时46分08秒UTC 2019 x86_64的x86_64的x86_64的GNU / Linux)的安装Uuntu
斯特凡V
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.