Ubuntu
grub2-signed package

package grub-efi-amd64-signed 1.66.3+2.02~beta2-36ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1627584 reported by Mike Schaefer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

i was installing an update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-efi-amd64-signed 1.66.3+2.02~beta2-36ubuntu3.3
ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10
Uname: Linux 4.2.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Sep 25 20:55:40 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-04-27 (152 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.14
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.66.3+2.02~beta2-36ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-09-26 (0 days ago)

Revision history for this message
Mike Schaefer (arizona6) wrote :
Revision history for this message
Mike Schaefer (arizona6) wrote :

I was installing an update

Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

The error in your log is:

> grub-install: error: attempt to install to encrypted disk without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file `/etc/default/grub'..

However, this is being installed for UEFI, which means the target disk must be an EFI System Partition and can't be encrypted. And this is an upgrade, which means you previously had grub2-signed installed, and we have not reduced the set of grub modules included in grub2-signed; /neither/ the new /nor/ the old version of grub-efi-amd64-signed that you had installed on your system has support for loading kernels from encrypted partitions.

Did you reconfigure your system to use encryption after installation? Did you manually install a version of grub with cryptodisk support, or is your /boot partition not properly mounted? Please attach /etc/fstab and the output of 'mount' from the affected system.

Changed in grub2-signed (Ubuntu):
status: New → Incomplete
Steve Langasek (vorlon)
tags: added: bot-stop-nagging
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2-signed (Ubuntu) because there has been no activity for 60 days.]

Changed in grub2-signed (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.