unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: ison <ison@airmail.cc>
Cc: 36942@debbugs.gnu.org
Subject: bug#36942: Reconfigure broke GRUB
Date: Tue, 06 Aug 2019 09:30:59 -0400	[thread overview]
Message-ID: <87tvauxvxo.fsf@sdf.lonestar.org> (raw)
In-Reply-To: <20190806023517.uvf7ukp3qprsfvpv@cf0> (ison@airmail.cc's message of "Mon, 5 Aug 2019 20:35:18 -0600")

[-- Attachment #1: Type: text/plain, Size: 2487 bytes --]

Hi ison,

Thanks for opening a new ticket for tracking this.

ison <ison@airmail.cc> writes:

> Continuing this issue from https://issues.guix.gnu.org/issue/36878
>
> guix reconfigure recently broke GRUB for me. When rebooting I get
> dropped to a "grub rescue>" shell with an error about
> "grub_file_filters" being an unknown symbol.
> If I try doing the usual commands to tell GRUB how to boot I just
> see the above error repeated, or "unknown command" when I run
> things such as insmod or "configfile".
>
> So to fix the problem I can boot to a Guix install disk and do
> "guix init" which rebuilds the system using older package
> definitions from the disk.
> That allows me to get a working system, but if I do another
> "guix pull" and reconfigure using the same config file it breaks
> GRUB again when I reboot. "guix describe" shows that my latest
> attempt was with commit 35600cd.
>
> Here is the bootloader and filesystem sections of my config:
>   (bootloader (bootloader-configuration
>                 (bootloader grub-efi-bootloader)
>                 (target "/boot/efi")))
>   (file-systems (cons* (file-system
>                          (device "/dev/sda2")
>                          (mount-point "/boot/efi")
>                          (type "vfat"))
>                        (file-system
>                          (device (file-system-label "guixsd-root"))
>                          (mount-point "/")
>                          (type "ext4"))
>                        %base-file-systems))

This narrows it down quite a bit -- I suspect that we're broken for
'grub-efi-bootloader', since I've been able to successfully reconfigure
with 'grub-bootloader' on both of my machines.

> I should make a note that I usually don't use efi, and I'm not
> completely confident it's all set up properly. I do have a
> "BIOS boot" partition on /dev/sda1 too, is that even needed with
> efi?

I don't believe so. I think the ESP partition on /dev/sda2 is all you
need.

> Although, I have been using this setup, and the above
> definitions, for about 6 months now without any bootloader or
> filesystem issues. And the same config is being used to fix the
> system when GRUB breaks as well as to reconfigure afterward
> (causing the breakage). So my guess is some new update is the
> culprit.

It certainly sounds like it, and I'm the last person to have touched the
bootloader installation code :)

I'll look into this ASAP. Thanks again for the bug report!

Regards,
Jakob

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-08-06 13:35 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 [this message]
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
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=87tvauxvxo.fsf@sdf.lonestar.org \
    --to=zerodaysfordays@sdf.lonestar.org \
    --cc=36942@debbugs.gnu.org \
    --cc=ison@airmail.cc \
    /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).