When reinstalling Ubuntu this error occur and installation got aborted. I have dual booted system but now grub don't ask for selecting OS,it directly boot into Ubuntu.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.9+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
shim:amd64: Install
shim-signed:amd64: Install
NULL: ConfigurePending
Architecture: amd64
BootEFIContents:
fw
fwupx64.efi
Date: Fri Jun 22 18:20:28 2018
Df:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda8 62695244 9727612 49753092 17% /
/dev/sdb1 7799276 1875436 5923840 25% /cdrom
udev 1943548 0 1943548 0% /dev
tmpfs 392948 1728 391220 1% /run
EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI variables are not supported on this system.
EFITables: Jun 22 18:26:11 Aditya-PC fwupd[2573]: disabling plugin because: failed to startup uefi: error listing variables: Function not implemented
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu2
apt 1.6.1
SourcePackage: shim-signed
Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
This particular error means that:
- your system supports UEFI
- your system was previously installed in BIOS mode
- the Ubuntu install image was booted in UEFI mode and tried to reinstall in UEFI mode, but this failed because you don't have an EFI system partition
- you had a previous BIOS bootloader present on disk, so the system still booted after installation.
That is bug #1766945.
If you were dual-booting and the other OS is not listed in your GRUB boot menu now, that is unfortunately unrelated to the above sequence that led to you being prompted to file this bug report.
It is possible that running 'sudo update-grub', now that the installation is finished, would be enough to restore your dual-boot option in the boot menu. If it does not, more information would be needed about your setup to understand why it's not being detected by os-prober.