From: "Ludovic Courtès" <ludo@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 40386@debbugs.gnu.org
Subject: bug#40386: guix system init can't find file system by UUID, workaround results in broken boot
Date: Thu, 02 Apr 2020 13:00:39 +0200 [thread overview]
Message-ID: <87tv22nodk.fsf@gnu.org> (raw)
In-Reply-To: <20200402084054.055a83f0@riseup.net> (raingloom@riseup.net's message of "Thu, 2 Apr 2020 08:40:54 +0200")
Hi,
raingloom <raingloom@riseup.net> skribis:
> Trying to install Guix System onto an SSD using an UltraBay dock.
> Config is the attached file (with slight variations in the obvious
> places)
>
> `readlink /dev/disk/by-uuid/643a215d-a30e-473b-826e-5c35de29e38f` gives
> me /dev/sdb1
>
> Yet using (uuid "643a215d-a30e-473b-826e-5c35de29e38f") results in:
>
> ```
> sudo -E guix system init --no-bootloader
> Configs/Guix/desktop-parametric.scm /mnt
> :( /home/raingloom/Configs/Guix/desktop-parametric.scm:50:26: error:
> file system with UUID '643a215d-a30e-473b-826e-5c35de29e38f' not found
> ```
>
> Switching the UUID to uppercase as in the example (thankfully) doesn't
> change anything, not even the error message.
>
> I tried using a label, same result.
What file system is on /dev/sdb1?
The code responsible for that is in (gnu build file-systems). It
currently recognizes only some file system types: ISO9660, ext2/3/4,
Btrfs, FAT32, FAT16, and JFS.
Can you try:
sudo guix repl
,use(gnu build file-systems)
(find-partition-by-uuid (uuid "643a215d-a30e-473b-826e-5c35de29e38f"))
?
> I ended up using the /dev/disk/by-uuid and /dev/disk/by-id paths for
> the root file system and the bootloader respectively, and that resulted
> in a succesful system init, but upon trying to boot the SSD with the
> other machine, I got thrown into a rescue shell, because it couldn't
> find the root using that path.
Yes, because /dev/disk is not accessible early on. That’s why the
manual recommends using ‘uuid’ or ‘file-system-label’.
> **(Quick aside: there really should be a guide for using that rescue
> shell. I can get around in a /bin/sh one, but this is nearly unusable.
> At least autocompletion should be supported.)**
Yes, that reminds me someone reported a serious Bournish bug on IRC.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-04-02 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 6:40 bug#40386: guix system init can't find file system by UUID, workaround results in broken boot raingloom
2020-04-02 11:00 ` Ludovic Courtès [this message]
2020-04-06 6:49 ` bug#40386: F2FS support Was: " raingloom
2020-05-21 5:09 ` raingloom
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=87tv22nodk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40386@debbugs.gnu.org \
--cc=raingloom@riseup.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).