failed during xubuntu upgrade from 17.04 to 17.10 package shim-signed 1.32+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shim-signed (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I have no idea what the problem was. just got the error during distribution upgrade from xubuntu 17.04 to 17.10
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: shim-signed 1.32+0.
ProcVersionSign
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelMo
.proc.sys.
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sun Jan 14 23:07:36 2018
EFITables:
jan. 14 23:12:06 zrg kernel: efi: EFI v2.40 by American Megatrends
jan. 14 23:12:06 zrg kernel: efi: ACPI=0x78821000 ACPI 2.0=0x78821000 SMBIOS=0xf0000 SMBIOS 3.0=0xf0020 ESRT=0x792d2018 MEMATTR=0x75dfe018
jan. 14 23:12:06 zrg kernel: esrt: Reserving ESRT space from 0x00000000792d2018 to 0x00000000792d2050.
jan. 14 23:12:06 zrg kernel: Secure boot could not be determined
ErrorMessage: subprocess installed post-installation script returned error exit status 1
GrubDiff: Binary files /boot/efi/
InstallationDate: Installed on 2018-01-03 (11 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageV
dpkg 1.18.24ubuntu1
apt 1.5.1
SecureBoot: 6 0 0 0 0
SourcePackage: shim-signed
Title: package shim-signed 1.32+0.
UpgradeStatus: Upgraded to artful on 2018-01-14 (0 days ago)
tags: | removed: need-duplicate-check |
The error in your log is:
Installing for x86_64-efi platform. grub/x86_ 64-efi/ core.efi' : Operation not permitted.
grub-install: error: cannot open `/boot/
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
This looks like filesystem corruption. What filesystem do you have mounted at /boot? Please show the output of 'mount | grep /boot'.