From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, nixd@tuta.io
Subject: Re: GuixSD installation issues (missing commands and build errors)
Date: Thu, 12 Jul 2018 10:07:38 +0200 [thread overview]
Message-ID: <5A30E394-7E5D-47DA-9BB2-700896336AE1@lepiller.eu> (raw)
In-Reply-To: <LHAX3JP--B-0@tuta.io>
This looks like the kind of error that occurrs when your RAM is corrupted. You should run a memtest I think.
Le 12 juillet 2018 00:48:41 GMT+02:00, nixd@tuta.io a écrit :
>I've encountered a problem with installing GuixSD 0.15 (from the latest
>ISO image
>(https://alpha.gnu.org/gnu/guix/guixsd-install-0.15.0.x86_64-linux.iso.xz
><https://alpha.gnu.org/gnu/guix/guixsd-install-0.15.0.x86_64-linux.iso.xz>)
>burnt to a DVD). I followed the manual as well as I could.
>The first, no-so-important issue is that I get an error message about
>some tools not beeing found by bash. These include mkfs.ext4, mkfs.fat,
>parted, cfdisk. These are the only ones I really used and noticed it
>on. This doesn't always happen. Whenever I reboot from the DVD again,
>the commands on which I get the error change. Sometimes for example
>mkfs.ext4 doesn't work, something else might work, you reboot and
>something else might break while mkfs.ext4 might work again, it seems
>completely random. You can workaround this by executing these tools
>directly from their directory (they are present!) such as going to
>e2fsprogs directory and manually executing mkfs.ext4.
>However, the real problem for is this:
>First of all, I partitioned and mounted as follows:/dev/sda1 is the ESP
>(I use EFI), mounted to /mnt/boot/efi/dev/sda2 is the main FS, label is
>"my-root" like in the manual, ext4, mounted to /mnt/dev/sda3 is swap
>I use the desktop.scm template as config.scm, minus the part for mapped
>devices and I replaced "my-root" with (file-system-label "my-root")
>because guix system init told me to do so., rest is left default.
>On the first run of "guix system init /mnt/etc/config.scm /mnt" I get a
>huge error message, its too big to even see all of it (lists many many
>packages though). The end says that the "builder for
>/gnu/store/*-profile.drv failed with exit code 1" and that it "cannot
>build derivation "/gnu/store/*-system.drv: 1 dependencies couldn't be
>built". I am unsure which dependency could not be built.
>When I run "guix system init /mnt/etc/config.scm /mnt" a second time I
>get 5 package collision warnings (for wayland-egl.pc, giomodule.cache,
>libwayland-egl.la, mimeinfo.cache, ifconfig), but it does get to the
>copying to /mnt stage.
>I then, at some point in the copying to /mnt stage, get the following
>error:
>"guix system: error: lstat: No such file or directory: " followed by a
>package directory
>I've tried this several times and the packages I got the errors on so
>far were:guile-ssh 2 or 3 timesfuse 2 or 3 timesguile 1 time
>It seems random on which of these packages I get the error.
>I can't make any sense of these problems, and if further information is
>needed I will of course provide it. Does anyone have an idea?
next prev parent reply other threads:[~2018-07-12 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 22:48 GuixSD installation issues (missing commands and build errors) nixd
2018-07-12 8:07 ` Julien Lepiller [this message]
2018-07-12 8:10 ` Ricardo Wurmus
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=5A30E394-7E5D-47DA-9BB2-700896336AE1@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=nixd@tuta.io \
/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).