From: Christophe Pisteur <christophe.pisteur@fsfe.org>
To: Roman Riabenko <roman@riabenko.com>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Could not prepare Boot variable
Date: Thu, 09 Jan 2025 21:15:22 +0100 [thread overview]
Message-ID: <c3e2be55b3edb324458d08e4a91a08c7a67d5ff4.camel@fsfe.org> (raw)
In-Reply-To: <20250109220517.f5b53504945220251dab649e@riabenko.com>
Hello Roman,
Thank you very much for your help.
Le jeudi 09 janvier 2025 à 22:05 +0200, Roman Riabenko a écrit :
> Hello Christophe
> >
> > I also had this issue recently. The device here is not the boot
> partition. Instead, the device here is the EFI itself.
Ah ok
>
> Check whether you have any files begninning with "dump"
> in /sys/firmware/efi/efivars/
>
> Those are dump files saved by the pstore kernel module. They should
> be
> safe to remove. Removing them frees up space for a new boot variable.
I have 218 (!) files begninning with "dump": do I delete them all
without distinction?
>
> I do not recommend rebooting until you complete the failed system
> reconfiguration. Otherwise, the boot may fail. GRUB did not show up
> for me at all.
Ok , Thanks for the advice!
Kind Regards
Christophe
next prev parent reply other threads:[~2025-01-09 20:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 19:01 Could not prepare Boot variable Christophe Pisteur
2025-01-09 19:19 ` Felix Lechner via
2025-01-09 19:33 ` Christophe Pisteur
2025-01-09 19:38 ` Felix Lechner via
2025-01-09 20:04 ` Christophe Pisteur
2025-01-09 20:05 ` Roman Riabenko via
2025-01-09 20:15 ` Christophe Pisteur [this message]
2025-01-09 20:24 ` Roman Riabenko via
2025-01-09 20:42 ` Christophe Pisteur
2025-01-09 20:49 ` Roman Riabenko via
2025-01-09 21:10 ` Christophe Pisteur
2025-01-09 21:34 ` Roman Riabenko via
2025-01-09 22:04 ` Christophe Pisteur
2025-01-09 22:34 ` Roman Riabenko via
2025-01-09 20:16 ` Felix Lechner via
2025-01-09 20:35 ` Roman Riabenko via
2025-01-09 21:45 ` Felix Lechner via
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=c3e2be55b3edb324458d08e4a91a08c7a67d5ff4.camel@fsfe.org \
--to=christophe.pisteur@fsfe.org \
--cc=help-guix@gnu.org \
--cc=roman@riabenko.com \
/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).