unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Thomas Danckaert <post@thomasdanckaert.be>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: help-guix@gnu.org
Subject: Re: repair broken boot record
Date: Tue, 05 Oct 2021 11:28:50 +0200	[thread overview]
Message-ID: <2d6ff1739c954b939be941d34ef6c856@thomasdanckaert.be> (raw)
In-Reply-To: <20211001065344.3ofpdgnxusvgj4ac@pelzflorian.localdomain>

Hello Florian,

thank you for your help.  I managed to chroot into my system, and re-run 
'guix system reconfigure' (very useful mailing list discussion on 
chrooting, I also vote for including it in documentation :) ).  In one 
of the final steps, where guix tries to install the bootloader, I get 
the error:

/gnu/store/.../grub/i386-pc/modinfo.sh doesn't exist. Please specify 
--target or --directory.

Indeed my system uses grub-efi.  Could that be related?  Can you point 
me to some specific instructions on how to check/solve efivar issues?

Not sure if I need grub-efi, or if it might also work using grub-pc.  
Until now I've always used grub-efi.

(Another thing I noticed (maybe a side effect of chroot?): when I re-run 
'guix system reconfigure' it tries to rebuild derivations that are 
already there in the store from last time, I think.)

thank you!

Thomas

On 2021-10-01 08:53, pelzflorian (Florian Pelz) wrote:
> On Thu, Sep 30, 2021 at 09:43:18AM +0200, Thomas Danckaert wrote:
>> Hello guix-help,
>> 
>> my system does not boot anymore after a guix pull and system 
>> reconfigure
>> (which did show a warning, see below).  It does not even enter the 
>> GRUB
>> stage, I get a "Reboot and Select proper Boot device" instead.  I 
>> think the
>> MBR might not have been written correctly (just a hunch, I'm no 
>> expert...).
> 
> If this system uses no old grub-bootloader but instead EFI
> (grub-efi-bootloader), maybe writing the bootloader to the mainboard
> failed (it is not only written to disk), perhaps because the mainboard
> NVRAM is full and needs to be cleaned with efibootmgr/efivar/such
> utilities.
> 
> 
>> During reconfigure, I did get a warning that my bootloader 
>> configuration
>> used 'target', which is apparently deprecated in favor of 'targets'.  
>> I
>> wasn't paying too much attention, and ignored the warning.... I don't 
>> know
>> if that could be the cause of a missing or incorrect boot record?  (In 
>> that
>> case, I suggest this warning should be an ERROR ;-) )
> 
> No, the old target would fall back to targets.  The warning is only a
> warning that you should switch to (targets (list "…")).
> 
> 
> 
>> I checked using a live USB, and it seems the whole system is still 
>> there on
>> the hard drive.  Is there a way to restore my system, keeping the 
>> existing
>> /gnu/store?  Or do I have to reinstall from scratch, remove the 
>> existing
>> /gnu/store and rebuild everything (shouldn't be too much work using 
>> Guix,
>> but way less elegant :) )
>> 
>> Thank you!
>> 
>> Thomas
> 
> I search on Duckduckgo for “site:lists.gnu.org guix chroot”, you
> should read there how to chroot into your system so you can
> reconfigure.
> 
> Regards,
> Florian


  reply	other threads:[~2021-10-05  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  7:43 repair broken boot record Thomas Danckaert
2021-10-01  6:53 ` pelzflorian (Florian Pelz)
2021-10-05  9:28   ` Thomas Danckaert [this message]
2021-10-05 11:04     ` pelzflorian (Florian Pelz)
2021-10-06  8:23       ` Thomas Danckaert
2021-10-06  9:28         ` pelzflorian (Florian Pelz)
2021-12-13 14:16           ` Thomas Danckaert
2021-12-13 16:12             ` pelzflorian (Florian Pelz)

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=2d6ff1739c954b939be941d34ef6c856@thomasdanckaert.be \
    --to=post@thomasdanckaert.be \
    --cc=help-guix@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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.
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).