unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Guix System ext4 index full
Date: Thu, 04 Jun 2020 20:55:42 +0200	[thread overview]
Message-ID: <9ff8874bf170a90f1f0378881faae45931ba0b27.camel@gnu.org> (raw)
In-Reply-To: <87d06fc779.fsf@nckx>

Hi Tobias,

Thanks for your help.  Don't worry, I figured I had to reinstall it,
which is okay. :)

Unfortunately, after reinstalling Guix using Btrfs as the root
filesystem I cannot seem to boot either.  The last line printed on the
screen is:
[   10.830469 ] Error: Driver 'pcspkr' is already registered,
aborting...

I think it has something to do with the "compatibility support module"
option in the BIOS, because without it I couldn't boot the LiveUSB.  It
seems that booting and installing Fedora 32 works just fine with the
same hardware, so this is definitely an area where I'd like to see Guix
improve.

Kind regards,
Roel Janssen


On Thu, 2020-06-04 at 15:05 +0200, Tobias Geerinckx-Rice wrote:
> Roel,
> 
> Roel Janssen 写道:
> > Thanks for the suggestion.  So I did:
> > $ tune2fs -O large_dir /dev/sdd3
> > 
> > .. and after a reboot I get booted into a GRUB resque shell.
> 
> Shart.  It seems that GRUB still[0] can't read ext4 file systems 
> with features newer than 2017 :-/  I'll never recommend this again 
> (I use it myself…).
> 
> The flag can't be cleared once set:
> 
>   $ sudo tune2fs -O ^large_dir img
>   tune2fs 1.45.6 (20-Mar-2020)
>   Clearing filesystem feature 'large_dir' not supported.
> 
> Your data's perfectly safe.  This is just a GRUB limitation.
> 
> > So.. do you have a suggestion for how I could boot into the Guix 
> > system
> > again?
> 
> I think realistic options are:
> 
> - Migrate to any other file system like btrfs, then use the live 
>   USB's GRUB to bootstrap it using ‘configfile 
>   (hdX,Y)/your/grub.cfg’ so you don't have to reinstall anything, 
>   just copy.  This can even be done-in place[1], assuming you have 
>   back-ups.
> 
> - Use a separate /boot partition if you want to keep using ext4 
>   for large /gnus.  You'll have to manually copy each kernel & 
>   friends to /boot but this can be automated in your system .scm.
> 
> > After booting from a live USB, I chrooted into the Guix system 
> > and when
> > running the following command, I get the following error:
> > $ guix system reconfigure /etc/config.scm
> > ...
> > guix system: error: while setting up the build environment: 
> > cannot
> > pivot old root directory onto
> > '/gnu/store/4q1vpidsawmfhmqdwy4mxvjc720jxcjm-slim-
> > 1.3.6.drv.chroot/real-root': Invalid argument
> 
> I think your in-chroot guix is talking to the live system's 
> guix-daemon.  Perhaps stopping the out-of-chroot daemon and 
> starting a ‘guix-daemon --disable-chroot’ inside the chroot will 
> work.
> 
> Kind regards,
> 
> T G-R
> 
> [0]: https://savannah.gnu.org/bugs/?56897
> [1]: https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-convert



  parent reply	other threads:[~2020-06-04 18:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 20:21 Guix System ext4 index full Roel Janssen
2020-06-03 20:35 ` Tobias Geerinckx-Rice
2020-06-04  9:33   ` Roel Janssen
2020-06-04 13:05     ` Tobias Geerinckx-Rice
2020-06-04 13:27       ` Tobias Geerinckx-Rice
2020-06-04 18:55       ` Roel Janssen [this message]
2020-06-04 19:00         ` Vincent Legoll
2020-06-03 20:43 ` Vincent Legoll
2020-06-03 21:14   ` Tobias Geerinckx-Rice
2020-06-03 23:06     ` Leo Famulari
2020-06-04  9:27       ` Pierre Neidhardt

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=9ff8874bf170a90f1f0378881faae45931ba0b27.camel@gnu.org \
    --to=roel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).