unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Roman Riabenko via <help-guix@gnu.org>
To: Christophe Pisteur <christophe.pisteur@fsfe.org>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Could not prepare Boot variable
Date: Thu, 9 Jan 2025 22:05:17 +0200	[thread overview]
Message-ID: <20250109220517.f5b53504945220251dab649e@riabenko.com> (raw)
In-Reply-To: <b1fa2be7240a6b65575ec5ecb25903e4708531ec.camel@fsfe.org>

Hello Christophe

On Thu, 09 Jan 2025 20:01:55 +0100
Christophe Pisteur <christophe.pisteur@fsfe.org> wrote:
> Could not prepare Boot variable: No space left on device

I also had this issue recently. The device here is not the boot
partition. Instead, the device here is the EFI itself.

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 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.

To prevent dump files from filling up space, I disabled the pstore
backend which saves dump files to efi variables. I added the following
configuration in the operating-system declaration.

  ;; Prevent filling /sys/firmware/efi/efivars/ with dumps
  (kernel-arguments (cons* "efi_pstore.pstore_disable=1"
                           %default-kernel-arguments))

Hope this helps.

Roman


  parent reply	other threads:[~2025-01-09 20:05 UTC|newest]

Thread overview: 31+ 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 [this message]
2025-01-09 20:15   ` Christophe Pisteur
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
2025-01-10 13:51         ` Roman Riabenko via
2025-01-12 13:33           ` Roman Riabenko via
2025-01-13 17:43             ` Christophe Pisteur
2025-01-13 20:01               ` Roman Riabenko via
2025-01-21 18:58                 ` Leo Famulari
2025-01-21 20:17                   ` Roman Riabenko via
2025-01-21 20:26                     ` Leo Famulari
2025-01-22  7:18                       ` Roman Riabenko via
2025-01-22  8:06                         ` Efraim Flashner
2025-01-22 20:49                           ` Felix Lechner via
2025-01-24 16:18                             ` Roman Riabenko via
2025-01-10 16:53         ` Tobias Geerinckx-Rice
2025-01-10 17:22           ` Felix Lechner via
2025-01-11 10:26           ` Roman Riabenko 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=20250109220517.f5b53504945220251dab649e@riabenko.com \
    --to=help-guix@gnu.org \
    --cc=christophe.pisteur@fsfe.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).