From: Kete Foy <kete@ninthfloor.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Failed to start service 'device-mapping
Date: Sun, 26 Jun 2016 23:17:45 +0000 [thread overview]
Message-ID: <8d14e970-8505-0cb5-b6b7-ffad1622071e@ninthfloor.org> (raw)
In-Reply-To: <8737nzll7k.fsf@gnu.org>
Ludovic Courtès:
> Are you sure the UUID is correct? It must be a LUKS UUID, as returned
> by “cryptsetup luksUUID /dev/sdXXYY”, not an ext2 UUID.
No, that's probably what's wrong, Ludó, and thanks for the suggested
command.
>
> Also, the ability to use LUKS UUIDs like this was not available in
> 0.10.0. So if you’re installing from the 0.10.0 USB image, you must
> first ‘guix pull’.
>
Ok, I better do that, too.
> Apart from that the config looks OK.
>
Thanks, I might respond with results.
--
https://emailselfdefense.fsf.org
gpg --recv-key 'D7E9 5431 9C95 097F C314 C2A2 DD8C 15BD 0168 5E3A'
next prev parent reply other threads:[~2016-06-26 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 19:49 Failed to start service 'device-mapping Kete Foy
2016-06-26 21:00 ` Ludovic Courtès
2016-06-26 23:17 ` Kete Foy [this message]
2016-06-27 7:14 ` Kete Foy
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=8d14e970-8505-0cb5-b6b7-ffad1622071e@ninthfloor.org \
--to=kete@ninthfloor.org \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.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.
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).