On Thu, May 13, 2021 at 09:21:22PM -, Bill McGonigle wrote:
> Fast forwarding eight months, this still breaks a fully-updated xubuntu
> LTS 16 to LTS 18 release upgrade
Because you have a misconfigured grub package on your system which is not
writing to the correct MBR. That is impossible
Fast forwarding eight months, this still breaks a fully-updated xubuntu
LTS 16 to LTS 18 release upgrade, at least. Does this need to be pushed
to LTS 16 (or 18 if the new package is run)?
Mounting the disks on the host (error was in a VM guest), chrooting, and
running grub-install /dev/sda
To see the error on the VGA console of an AWS EC2 instance:
apt-get install netpbm gocr
aws --output=text ec2 get-console-screenshot --instance-id $InstanceId --query
ImageData | base64 -d | jpegtopnm | gocr -
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello halfgaar, our knowledge base article includes some instructions
for Amazon ec2 instances on how to recover from this situation:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass#Cloud_instances_.28e.g._AWS_EC2.29
If the virtual console support provides a mechanism to
I had an amazon EC2 Ubuntu 18.04 instance fail to boot. Grub was updated
to the fixed version on aug 3 (2.02-2ubuntu8.17). A fix for this bug
that prevents this in the future may have been released, but the broken
state the machine is in, is not recovered.
Amazon AWS is especially tricky, because
This bug was fixed in the package grub2 - 2.04-1ubuntu26.2
---
grub2 (2.04-1ubuntu26.2) focal; urgency=medium
* debian/postinst.in: Avoid calling grub-install on upgrade of the grub-pc
package, since we cannot be certain that it will install to the correct
disk and a
This bug was fixed in the package grub2 - 2.02-2ubuntu8.17
---
grub2 (2.02-2ubuntu8.17) bionic; urgency=medium
* debian/postinst.in: Avoid calling grub-install on upgrade of the grub-pc
package, since we cannot be certain that it will install to the correct
disk and a
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.27
---
grub2 (2.02~beta2-36ubuntu3.27) xenial; urgency=medium
* debian/postinst.in: Avoid calling grub-install on upgrade of the grub-pc
package, since we cannot be certain that it will install to the correct
** Changed in: grub2 (Ubuntu Groovy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not fail package upgrade (and
This bug was fixed in the package grub2 - 2.04-1ubuntu26.2
---
grub2 (2.04-1ubuntu26.2) focal; urgency=medium
* debian/postinst.in: Avoid calling grub-install on upgrade of the grub-pc
package, since we cannot be certain that it will install to the correct
disk and a
I have run some additional tests on bionic and focal desktop VMs with
lvm (and lvm+luks) - no boot issues were observed with the -proposed
builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
xenial verification:
Tested with 1.66.27+2.02_beta2-36ubuntu3.27 from -proposed.
Boots successfully in BIOS mode.
Timestamps updated in EFI mode.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Tags removed: verification-needed
** Tags added:
I have also attempted to verify xenial (using version
1.66.27+2.02_beta2-36ubuntu3.27), however grub-efi-
amd64-signed_1.66.27+2.02_beta2-36ubuntu3.27 still seems to be
unavailable in -proposed (http://archive.ubuntu.com).
I have manually downloaded it and tested from here [1], however I'll
focal verification:
Tested with version 1.142.4+2.04-1ubuntu26.2 from -proposed using the above
test case.
Boots successfully in BIOS mode.
Timestamps updated in EFI mode.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification
bionic-verification:
Tested with version 1.93.19+2.02-2ubuntu8.17 from -proposed using the test case
in the description.
Boots successfully in BIOS mode.
Timestamps were updated in EFI mode.
** Tags removed: sts verification-needed-bionic
** Tags added: verification-done-bionic
--
You
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not fail package upgrade (and does not roll
back to matching modules)
To manage
** Description changed:
[SRU Justification]
SRU regression triggered by latent misconfiguration of grub on the host
system, leading to a failure to boot due to ABI mismatch between
/boot/grub/i386-pc which is updated, and the grub image in the MBR which is not
[Test case]
1. Boot a
Hello Robert, or anyone else affected,
Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.27 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Robert, or anyone else affected,
Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.17
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- [Justification]
+ [SRU Justification]
SRU regression triggered by latent misconfiguration of grub on the host
system, leading to a failure to boot due to ABI mismatch between
/boot/grub/i386-pc which is updated, and the grub image in the MBR which is not
+ [Test
Hello Robert, or anyone else affected,
Accepted grub2 into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu26.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Justification]
+ SRU regression triggered by latent misconfiguration of grub on the host
system, leading to a failure to boot due to ABI mismatch between
/boot/grub/i386-pc which is updated, and the grub image in the MBR which is not
+
+
Failure to install new
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388437
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388432
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388423
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not
** Attachment added: "grub-pc.0.crash"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+attachment/5397267/+files/grub-pc.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Installing for i386-pc platform.
grub-install: error: cannot find a GRUB drive for /dev/sda. Check your
device.map.
dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 1
...
Errors were encountered while processing:
** Tags removed: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not fail package upgrade (and does not roll
back to matching modules)
We had this problem yesterday on only one of two Ubuntu 18.04 instance
on AWS. We had to rollback to a previous snapshot to make the instance
bootable again.
So we did a quick test with these two AMI:
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200408 -
ami-0edd51cc29813e254
My recreate is with an AWS EC2 instance with an NVMe root device as that
is one known way to trigger an error in cloud-init cc_grub_dpkg so that
it does not write a valid debconf for grub-pc install_devices, however
this is broader than NVMe root with cloud-init.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
** Merge proposal linked:
https://code.launchpad.net/~xnox/grub/+git/grub/+merge/388383
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not fail package
Hm, I wonder if in postinst, in grub-pc case,
else
break # noninteractive
fi
Should actually be
exit 1, like it is in the UPGRADE_FROM_GRUB_LEGACY case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm attaching a full log from the recreate that shows additional details
** Attachment added: "grub_bug_log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+attachment/5397176/+files/grub_bug_log
** Description changed:
Failure to install new grub core to the specified
** Tags added: regression-release
** Tags added: regression-update
** Also affects: grub2 (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Xenial)
Importance:
38 matches
Mail list logo
