Hi,
here below you can find the results of the script with set -x added right after
set -e.
cript started on 2023-05-07 10:10:40+02:00 [COMMAND="dpkg --configure
--pending" TERM="screen-256color" TTY="/dev/pts/3" COLUMNS="153" LINES="47"]
Setting up grub-efi-amd64 (2.06-12) ...
+ cached_available_ids=
+ case "$1" in
+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/grub-efi-amd64.postinst
configure 2.06-7
[1mdpkg:[0m error processing package grub-efi-amd64 (--configure):
installed grub-efi-amd64 package post-installation script subprocess returned
error exit status 128
[1mdpkg:[0m dependency problems prevent configuration of grub-efi:
grub-efi depends on grub-efi-amd64 (= 2.06-12); however:
Package grub-efi-amd64 is not configured yet.
[1mdpkg:[0m error processing package grub-efi (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
grub-efi-amd64
grub-efi
Script done on 2023-05-07 10:10:40+02:00 [COMMAND_EXIT_CODE="1"]
Hope this helps... BTW what does the exist status 128 means exactly?
ByeAndrea
Il giovedì 27 aprile 2023 15:50:10 CEST, Steve McIntyre <[email protected]>
ha scritto:
On Sat, Apr 22, 2023 at 11:05:14AM +0000, Andrea Palazzi wrote:
>>>Errors were encountered while processing:
>>> grub-efi-amd64
>>> grub-efi
>>>E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>>There's not a lot to see here so far. What happens if you run:
>>
>> "sudo grub-install -v"
>>
>> by hand please?
>
>Hi,
>
>not sure if it's relevant or not, but I'm running on a ZFS boot and root
>filesystem.
Ok, thanks for the extra info.
>Regarding the grub-install command, you can find attached the full output of
>LC_ALL=C grub-install -v .
Thanks. That's not showing anything unexpected, which surprises me.
Could you please edit /var/lib/dpkg/info/grub-efi-amd64.postinst and
add a line near the top saying
set -x
and then run
# script -c "dpkg --configure --pending" dpkg.log
please? That should capture whatever is failing in dpkg.log, I hope
--
Steve McIntyre, Cambridge, UK. [email protected]
We don't need no education.
We don't need no thought control.
