[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#954134: marked as done ([d-i bullseye alpha2 i386] Configuring 'grub-installer' failed with error code 134)

Your message dated Sun, 28 Mar 2021 14:43:14 +0200
with message-id <[🔎] 20210328144314.8b91254a7d0d5b35dfe9152f@mailbox.org>
and subject line Re: Bug#954134: [d-i bullseye alpha2] installing grub fails
has caused the Debian Bug report #954134,
regarding [d-i bullseye alpha2 i386] Configuring 'grub-installer' failed with error code 134
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
954134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954134
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Severity: grave


While testing the alpha2 netinst image on a spare Thinkpad, I found that grub
cannot be installed successfully (and rebooting into the new installation
fails as well). This was ok in alpha1.

This might look like an grub-installer issue, however there were only trivial
installation update releases since alpha1, so I suspect it's not in issue
in grub-installer. Therefore I file this against debian-installer.

I will sent installation logs shortly.


Holger


-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

--- End Message ---
--- Begin Message --- 
Hi,

Holger Wansing <hwansing@mailbox.org> wrote (Sun, 28 Mar 2021 14:39:41 +0200):
> Hi,
> 
> Steve McIntyre <steve@einval.com> wrote (Sat, 21 Mar 2020 17:00:59 +0000):
> >Hmm, this is getting annoying:
> >while doing several test installs, I thought I had a path how to reproduce
> >the issue, but then suddenly it looked completely different than before.
> >So, that's something between "some portion of coincidence involved" and
> >"wow, not it looks like a hardware failure".
> >
> >And since I was never able to reproduce the issue on amd64, it seems at
> >least to be a i386-only issue, and thus could be considered as a corner 
> >case...

Since I cannot reproduce this for a long time now, I'm closing this report.


Holger


-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

--- End Message ---
Reply to: