Bug#856416: grub-efi-amd64: Updating grub-efi-amd64:amd64 to 2.02~beta3-5 is aborted with half-installed package and reboot
John Paul Adrian Glaubitz
glaubitz at physik.fu-berlin.de
Wed Mar 1 23:36:20 UTC 2017
Hi Reiner!
On 03/01/2017 07:46 PM, Reiner Nix wrote:
>> This looks more like a local configuration issue at first sight rather than
>> a bug in the grub2 package. Did you try to reproduce this issue on a freshly
>> installed system?
> Sorry, I did not try to reproduce this bug on another system.
That would be important though in this case.
>> I'm also not sure I understand how the configure process was interrupted? Did it
>> just abort on its own or did you hit "Ctrl+C" or did your machine crash?
>>
>> I'm tagging this "moreinfo" because it's currently not obvious how and when
>> the configure process for grub2 was interrupted.
>
> While running apt-get upgrade, and installing the package, the system crashed.
The crash could be completely unrelated to grub2 and possibly an issue with
your hardware. And if your machine crashes while dpkg is configuring packages,
it is virtually inevitable not to end up with half-broken packages.
> Before it did not display any other message than the usual apt-get / dpkg message to install X86-64-efi
> and in the next second it rebooted automatically not caused by any user activity or job.
> Before the reboot it did not execute the standard shutdown jobs.
> The reboot was just as if the system started with power on.
Could be an issue with your power supply maybe.
> Also there was no reasonable additional load, just my desktop environment (KDE) and email program were running idle
> indeed at the first time I was not present at the desk. When coming back I noticed that the system displayed the login screen while I did not logout.
>
> Some time later I tried to continue the update using 'dpkg --configure -a'.
> So I discovered that the update could not be completed but run into reboot.
>
> This was reproducible unless on the next day the configuration could be completed.
Reproducible in what way? Did the system crash-reboot once more when you tried
to run "dpkg --configure -a"?
> Hope this clarifies the situation a bit.
> Give me a note when I could provide any other details like log files etc.
I'm currently a bit reluctant to blame grub2 here. This should really be
tested with a fresh installation to try to reproduce it. It's unlikely
to be a bug if we cannot reproduce it.
> Please find below an extract from the dpkg.log showing the lines regarding grub-efi-amd64.
The log just indicates the fallout from the crash and is something to be
expected. The actual question is why your machine crashed while dpkg
was configuring packages and if it's actually reproducible.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz at debian.org
`. `' Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
More information about the Pkg-grub-devel
mailing list