Ubuntu
friendly-recovery package

package friendly-recovery 0.2.41 [modified: lib/recovery-mode/recovery-menu] failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 1

Bug #1895211 reported by robert Newton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
friendly-recovery (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

changed disco to focal in /etc/apt/sources.list !!
1765 packages total in 3GB to update!!!

should I just wipe and new-install??? ;-)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: friendly-recovery 0.2.41
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 9 10:44:30 2020
ErrorMessage: installed friendly-recovery package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-02-01 (587 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190131)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: friendly-recovery
Title: package friendly-recovery 0.2.41 [modified: lib/recovery-mode/recovery-menu] failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-09-09 (1 days ago)

Revision history for this message
robert Newton (newtonsys-o) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in friendly-recovery (Ubuntu):
status: New → Confirmed
Revision history for this message
Pelam (pe78) wrote :

It seems that it could be related to the stuff mentioned in this post:
https://askubuntu.com/a/943425/117278

sudo update-grub gave a strange error that seems maybe related:

/usr/sbin/grub-probe: error: failed to get canonical path of `rpool/ROOT/ubuntu_3q4whe'.

However, doing as suggested in the linked post:
ZPOOL_VDEV_NAME_PATH=1 update-grub

succeeded. Afterwards update-grub works without the env variable... strange

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.