From mboxrd@z Thu Jan  1 00:00:00 1970
From: ison <ison@airmail.cc>
Subject: bug#36942: Reconfigure broke GRUB
Date: Thu, 15 Aug 2019 05:20:40 -0600
Message-ID: <20190815112039.d5x4ondia6osghq5@cf0>
References: <20190806023517.uvf7ukp3qprsfvpv@cf0>
 <87tvauxvxo.fsf@sdf.lonestar.org> <87o912duoo.fsf@sdf.lonestar.org>
 <20190807191628.qm3mmpmkobumhsx4@cf0>
 <87imr8n4lc.fsf@sdf.lonestar.org>
 <20190807223655.heflhqiwjwfp7dr2@cf0>
 <87r25nr0gn.fsf@sdf.lonestar.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:59030)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hyDoV-0007l0-RF
 for bug-guix@gnu.org; Thu, 15 Aug 2019 07:21:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hyDoU-0003VW-Ju
 for bug-guix@gnu.org; Thu, 15 Aug 2019 07:21:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:41886)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1hyDoU-0003VF-GS
 for bug-guix@gnu.org; Thu, 15 Aug 2019 07:21:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hyDoU-00015L-A9
 for bug-guix@gnu.org; Thu, 15 Aug 2019 07:21:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.36942.B36942.15658680554137@debbugs.gnu.org>
Content-Disposition: inline
In-Reply-To: <87r25nr0gn.fsf@sdf.lonestar.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: 36942@debbugs.gnu.org

On Wed, Aug 14, 2019 at 03:50:00PM -0400, Jakob L. Kreuze wrote:
> However, I still cannot seem to reproduce this issue with the most
> recent master. Everything boots fine. I've extracted the bootloader
> installation "script", and everything appears to be normal to me.

Sorry it took me so long to reply, I didn't have access to the
broken machine until now. As you requested here is the partitions as
listed by parted:

Number  Start   End     Size    File system     Name    Flags
 1      1049kB  3046kB  2097kB                  grub    bios_grub
 2      3146kB  540MB   537MB   fat32           efi     boot, esp
 3      540MB   2588MB  2048MB  linux-swap(v1)  swap
 4      2588MB  750GB   748GB   ext4            guixsd

/boot/efi looks ok as far as I can tell at least. It's tree is:
/boot/efi/
└── EFI
    ├── grub
    │   └── grubx64.efi
    ├── Guix
    │   └── grubx64.efi
    └── GuixSD
        └── grubx64.efi
All 3 grubx64.efi files differ from each other and are around 120kb.

====================================================================
But considering you can't reproduce the issue would it be a good
idea for me to reinstall and see if I can even reproduce it?
Although I think this time I would leave off the bios_grub partition
I'm willing to keep testing the current bug if it's important or
indicative of a more serious problem. But please don't feel
obligated to keep working on this just for me, I'm perfectly fine
just reinstalling. The issue doesn't seem to affect my desktop
anyway, I was able to upgrade it smoothly.

It's always possible the issue was caused by some strange
combination involving the patched bug, from earlier in the
discussion, and my weird partition layout. Might not even be worth
investigating unless it happens to someone else
(or me again after a fresh install).