package grub-legacy-ec2 1:1 failed to install/upgrade: installed grub-legacy-ec2 package post-installation script subprocess returned error exit status 10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub-legacy-ec2 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
not upgrade system
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-legacy-ec2 1:1
Uname: Linux 3.18.14-
ApportVersion: 2.20.9-0ubuntu7
Architecture: arm64
Date: Sat Nov 28 16:12:38 2020
Df:
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 24604780 18139636 6372984 75% /
tmpfs 1434188 1020 1433168 1% /dev
Dmesg:
ErrorMessage: installed grub-legacy-ec2 package post-installation script subprocess returned error exit status 10
PackageArchitec
Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.1
SourcePackage: grub-legacy-ec2
Title: package grub-legacy-ec2 1:1 failed to install/upgrade: installed grub-legacy-ec2 package post-installation script subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)
information type: | Private Security → Public |
Thank you for taking the time to file a bug report.
I have tried to reproduce this problem here, but did not succeed. Here's what I did:
1) Launched a Bionic VM using lxd
2) apt update && apt upgrade
3) apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -q -y -o APT::Install- Recommends= true -o APT::Get: :AutomaticRemov e=true -o APT::Acquire: :Retries= 3 install server^
This last command is what triggered the problem; I don't think the previous commands from the log are too important.
Everything went fine, including the configuration process of grub-legacy-ec2. In my test system, here is what I saw:
Setting up grub-legacy-ec2 (1:1) ...
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... Generating /boot/grub/default file and setting the default boot entry to 0
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.lst file ...
Could not find /boot/grub/menu.lst file. 4.15.0- 126-generic 4.15.0- 124-generic
Generating /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
Updating /boot/grub/menu.lst ... done
As you can see, I did not get an error about dpkg not being able to determine the root device. I have also gotten the full log, whereas in your case it appears that the log has been cut. Do you have access to the full output of the "apt-get" command you executed?
It is hard to say for certain, but it seems to me that there might be a local configuration error in your system that is preventing the package from completing its setup.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://