Bug#990867: shim-helpers-arm64-signed: post-install script fails with 'error exit status 1'
Steve McIntyre
steve at einval.com
Thu Aug 11 20:59:07 BST 2022
Hey Diederik!
On Wed, Jul 27, 2022 at 12:12:41AM +0200, Diederik de Haas wrote:
>On Sunday, 11 July 2021 17:42:27 CEST Steve McIntyre wrote:
>> >If an error is detected, a message like "Look at this wiki page <URL> for
>> >possible solutions", with the solution you just provided me (among others),
>> >would be really helpful.
>> >I've made/attached screenshots which could be used for that.
>>
>> I'm adding an extra section to https://wiki.debian.org/UEFI right now,
>> at least.
>
>I just ran into this issue again and your solution worked again :-)
>But I ran a search in my mail folder(s) to find it again, so a pointer to
>that wiki page would still be useful I'd guess.
>
>I didn't get the error message I initially got (not a post-install script
>failure), but I can understand if people get scared when seeing:
>"system may not be bootable"
Nod. :-( If you'd like to help, patches would be *very* welcome
here.
I'm swamped with other issues and I don't have the time or the
equipment any more to be able to do this alone.
>I've learned to ignore that warning, which may not be the response
>we'd want to teach our users ;-)
>I _think_ that even without the "dpkg-reconfigure" call the system would
>still boot, but I didn't verify it (at least this time).
>
>Here's the output I got this time, again on a Rock64 device, but another
>one with a recent fresh system install:
>
>root at cs21:~# aptitude safe-upgrade
>Resolving dependencies...
>The following NEW packages will be installed:
> linux-image-5.18.0-3-arm64{a}
>The following packages will be upgraded:
> ... shim-helpers-arm64-signed ...
>Preparing to unpack .../22-shim-helpers-arm64-signed_1+15.6+1_arm64.deb ...
>Unpacking shim-helpers-arm64-signed (1+15.6+1) over (1+15.4+7) ...
>Setting up libdouble-conversion3:arm64 (3.2.0-1) ...
>Setting up libapparmor1:arm64 (3.0.5-1) ...
>Setting up libnewt0.52:arm64 (0.52.21-5+b2) ...
>Setting up apt-utils (2.5.2) ...
>Setting up shim-helpers-arm64-signed (1+15.6+1) ...
>Installing for arm64-efi platform.
>grub-install: warning: Cannot set EFI variable Boot0000.
>grub-install: warning: efivarfs_set_variable: failed to create /sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c for writing: Read-only file system.
>grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Read-only file system.
>grub-install: error: failed to register the EFI boot entry: Read-only file system.
>Failed: grub-install --target=arm64-efi
>WARNING: Bootloader is not properly installed, system may not be bootable
ACK.
--
Steve McIntyre, Cambridge, UK. steve at einval.com
The two hard things in computing:
* naming things
* cache invalidation
* off-by-one errors -- Stig Sandbeck Mathisen
More information about the Pkg-grub-devel
mailing list