all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: znavko@disroot.org
Cc: help-guix@gnu.org
Subject: Re: Cannot write to /boot directory No space left
Date: Thu, 10 Dec 2020 22:04:45 +0100	[thread overview]
Message-ID: <87im99l6du.fsf@nckx> (raw)
In-Reply-To: <2a5f407f8de6a67656b2889b5e61ffb3@disroot.org>

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

Hi,

znavko--- via 写道:
> Cannot write to /boot directory No space left

You got lost.  This has nothing to do with a ‘/boot directory’, or 
how it's mounted.  The bug is in your hardware.

>  Could not prepare Boot variable: No space left on device
>  /gnu/store/d1i6x7vwr83j1m0zms580mh2dqgx1s6m-grub-efi-2.04/sbin/grub-install: 
>  error: efibootmgr failed to register the boot entry: 
>  Input/output error.

Your UEFI NVRAM is full.

This happens on my ThinkPad X230T for unknown reasons.  The only 
‘solution’ I've found is to delete some unused default boot 
entries so GRUB can add one for Guix.

I have a script that deletes everything except ‘Guix’, ‘ATA‌ HDD0’, 
‘USB HDD’, and Important-Looking Things like ‘Setup’:

  $ efibootmgr
  [This will print them all, for example:]
  Boot0001 Lenovo Diagnostics
  Boot0002 ATAPI CD0
  ...
  $ sudo efibootmgr --delete-bootnum --bootnum 0001
  $ sudo efibootmgr --delete-bootnum --bootnum 0002
  ...

and then rerun grub-install (for example by running ‘guix system 
reconfigure’ again).

Kind regards,

T G-R

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

      reply	other threads:[~2020-12-10 21:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 20:33 Cannot write to /boot directory No space left znavko--- via
2020-12-10 21:04 ` Tobias Geerinckx-Rice [this message]

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

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

  git send-email \
    --in-reply-to=87im99l6du.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=znavko@disroot.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.