From mboxrd@z Thu Jan 1 00:00:00 1970 From: Divan Santana Subject: Re: guixsd install questions Date: Fri, 30 Jun 2017 22:49:55 +0200 Message-ID: <87d19l9p58.fsf@santanas.co.za> References: <87tw8kkisf.fsf@santanas.co.za> <878tpu22mu.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50404) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dR3QI-0001O2-FX for help-guix@gnu.org; Fri, 30 Jun 2017 17:25:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dR3QD-0006wa-5K for help-guix@gnu.org; Fri, 30 Jun 2017 17:25:54 -0400 In-reply-to: <878tpu22mu.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?Q?Court=C3=A8s?= , help-guix Hi Ludo, Ludovic Court=C3=A8s writes: > Hello! > > Divan Santana skribis: > >> Then do the install with this guile code: >> >> #+BEGIN_SRC scheme >> ;; two devices in raid0 striped with LUKS full disk encryption. >> (bootloader (grub-configuration (device "/dev/vdb"))) >> (mapped-devices (list >> (mapped-device >> (source (list "/dev/vdb1" "/dev/vdc1")) >> (target "/dev/md0") >> (type raid-device-mapping)) >> (mapped-device >> (source (uuid "fb29c6f6-b2c0-4c87-8651-4962b7125dc= 0")) >> (target "crypt") >> (type luks-device-mapping)))) >> #+END_SRC >> >> >> And this too: >> >> #+BEGIN_SRC scheme >> (file-systems (cons (file-system >> (device "root") >> (title 'label) >> (mount-point "/") >> (type "ext4")) >> %base-file-systems)) >> #+END_SRC >> >> >> The above fails. So tried another install with device like so > > Do you know how it fails? I don't have exact details of how it fails. > My guess is that you=E2=80=99d need to explicitly mark one of the mappe= d device > as depending on the other; this cannot be guessed. > > If you run =E2=80=9Cguix system shepherd-graph=E2=80=9D on your config = you=E2=80=99ll probably > see that there=E2=80=99s no such dependency. > > Currently dependencies among mapped devices cannot be expressed, but > that=E2=80=99s easy to fix (by providing a =E2=80=98dependencies=E2=80=99= field as in > =E2=80=98file-system=E2=80=99.) So I've tried altering the code and asked on IRC a while back too. I tried some of the suggestions that were given but none of them worked. Would you be able to "spell out" for someone clueless what the code should look like to express the dependencies. Currently the code looks like this (bootloader (grub-configuration (device "/dev/vdb"))) (mapped-devices (list (mapped-device (source (list "/dev/vdb1" "/dev/vdc1")) (target "/dev/md0") (type raid-device-mapping)) (mapped-device (source (uuid "1c0f1601-97f4-4a3d-9528-cd76130ff919")= ) (target "crypt") (type luks-device-mapping)))) (file-systems (cons (file-system (device "/dev/mapper/crypt") (title 'device) (mount-point "/") (type "ext4")) %base-file-systems)) Pre-install I configured the disks like so: #+BEGIN_EXAMPLE fdisk, one partition of each only marked as fd mdadm --create --level=3D0 --raid-devices=3D2 /dev/md0 /dev/vd[bc]1 cryptsetup luksFormat /dev/md0 cryptsetup luksOpen /dev/md0 crypt mkfs.ext4 -L root -m2 /dev/mapper/crypt mount /dev/mapper/crypt /mnt #+END_EXAMPLE