unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ison <ison@airmail.cc>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: 36942@debbugs.gnu.org
Subject: bug#36942: Reconfigure broke GRUB
Date: Thu, 15 Aug 2019 05:20:40 -0600	[thread overview]
Message-ID: <20190815112039.d5x4ondia6osghq5@cf0> (raw)
In-Reply-To: <87r25nr0gn.fsf@sdf.lonestar.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).

  reply	other threads:[~2019-08-15 11:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  2:35 bug#36942: Reconfigure broke GRUB ison
2019-08-06 13:30 ` Jakob L. Kreuze
2019-08-06 18:18   ` Jakob L. Kreuze
2019-08-06 19:44     ` Danny Milosavljevic
2019-08-06 19:48       ` Jakob L. Kreuze
2019-08-06 21:53         ` Danny Milosavljevic
2019-08-26 10:20           ` Ludovic Courtès
2019-08-27  3:16             ` ison
2019-08-07 19:16     ` ison
2019-08-07 19:43       ` Jakob L. Kreuze
     [not found]         ` <20190807223655.heflhqiwjwfp7dr2@cf0>
2019-08-14 19:50           ` Jakob L. Kreuze
2019-08-15 11:20             ` ison [this message]
2019-08-16 14:36               ` Jakob L. Kreuze
2019-08-16 23:34                 ` ison
2019-08-17 12:49                   ` Jakob L. Kreuze
2019-08-20 14:27                     ` ison
2019-08-20 16:51                       ` Jakob L. Kreuze
2019-08-20 21:52                         ` ison
2019-08-26 10:17                       ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190815112039.d5x4ondia6osghq5@cf0 \
    --to=ison@airmail.cc \
    --cc=36942@debbugs.gnu.org \
    --cc=zerodaysfordays@sdf.lonestar.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).