From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id KHkHNHNIBWbl9wAAqHPOHw:P1 (envelope-from ) for ; Thu, 28 Mar 2024 11:37:39 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id KHkHNHNIBWbl9wAAqHPOHw (envelope-from ) for ; Thu, 28 Mar 2024 11:37:39 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=bluewin.ch header.s=fxzs-2048-20230414 header.b=DqiIET9f; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=bluewin.ch ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1711622259; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=fIImZS1d8+6SqnFNr/4EajwOMLRpAW87D4qKgpnebq0=; b=coGdV0unNO35VwHlR+VUueIqSO1T19jnkV0aGGOoc2AvKh1cHbc4N4uiyxLJetVBkGxnRQ fjyj1s2X3jD02RwE2adwUrOvonbaH2H5G4JmWmRpro5dF0z5e30BrHOfEWOAfHaDMjBlbq ef+rbAQfDULmXDG/FOh40Q9hiJ0kai4R/bgIDCeolu+KsbxWWalWvM96tCi+c5g/tMFOvS d8obUYEn1H691NksCdazyuBXLGSJkYiJPEjWKhWcPdXc92KTNwrjr9aA72OYSCcNtgjd/l eYGFiDrOOWZiukXM1lintssGHg+khdIvIuoMe3GMMA3NK1SfhwidLS+IHmVvog== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=bluewin.ch header.s=fxzs-2048-20230414 header.b=DqiIET9f; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=bluewin.ch ARC-Seal: i=1; s=key1; d=yhetil.org; t=1711622259; a=rsa-sha256; cv=none; b=I3S1Drcwgem7uQ+19RlwLbDFFVSmYzCiYq49DVmjAP0vl1wlMmeKotaIjOWGmM2LVNd+UQ LSAQKsVgNWvc7yb0Oq6ZE8RAL/DTERa+ADtv3iOEbeW9hDPGVCTIDVKhNeWSw+RMo/TbtJ 1wuynz5men4arPXLCWtX841YsYvAMF0SzfJyHjSy9rTzHiRDXtpuDCLGzscjrs8VhZvA/P AbSvWlIJKDJ29p4d8w9AdH1cwgDMzvbExKaSEmGJigZdHoJTWw41faM+3e+QI4Mh4aVvSS tA/puFQGzd3cHMkp6bhXrTResuCGyr7eYXZR/dxkwy6LSjkEa7jN2VM0m4jnTQ== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 8C18B60C37 for ; Thu, 28 Mar 2024 11:37:39 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rpn8O-0002ex-Fk; Thu, 28 Mar 2024 06:37:24 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rpn8L-0002di-7k for help-guix@gnu.org; Thu, 28 Mar 2024 06:37:21 -0400 Received: from vimdzmsp-sfwd01.bluewin.ch ([195.186.120.131]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rpn8F-00023o-F3 for help-guix@gnu.org; Thu, 28 Mar 2024 06:37:19 -0400 Received: from bluewin.ch ([213.55.245.153]) by vimdzmsp-sfwd01.bluewin.ch Swisscom AG with ESMTPA id pn88rnkcW5COZpn89roedC; Thu, 28 Mar 2024 11:37:09 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluewin.ch; s=fxzs-2048-20230414; t=1711622229; bh=fIImZS1d8+6SqnFNr/4EajwOMLRpAW87D4qKgpnebq0=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=DqiIET9fwtI6buc02X/v2uuALiLD8Pvbse9zKMpXgyqylo+qMGBqKD4+9z+MBr5HI UX/fWqwL2JRmtkMr424CDK0YTKGX3/ObeveX1w0zoj/i3w6MMn/wXFBLoTjBTmfB4f g91agpL6+s94Zo9+05eApfmb1gyphFO26f6sBpPfUjxWgWKKuxOoDwq0gZY9h9cO9r OmIGEruA8bep4aJDKxCTHUCQ3clIsYALdR85RubcIN561pYRH9Ya52KgRXbERpy+0B pFoJqcM8oAre5m3HoDgAuKbrsHsMmdmiK4jKIk/5dz0+UdbJBdg8WEsAdFuj4BkbfK NcdXF1D77xXwA== X-Bluewin-Spam-Analysis: v=2.4 cv=bY7IU/PB c=1 sm=1 tr=0 ts=66054855 a=/U1+rXC3EtFQ66MXwmYm5g==:117 a=IkcTkHD0fZMA:10 a=7-O4zLRhnmh2vj3v8owA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 X-Bluewin-Spam-Score: 0.00 X-FXIT-IP: IPv4[213.55.245.153] Epoch[1711622229] X-Bluewin-AuthAs: fulbert@bluewin.ch Date: Thu, 28 Mar 2024 11:37:08 +0100 From: Fulbert To: help-guix@gnu.org Subject: Re: system hangs at boot - LUKS /home/ problem(?) Message-ID: Mail-Followup-To: help-guix@gnu.org References: <932f7bd19906eee52f0f85f9915e283e4d57b1c9.camel@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <932f7bd19906eee52f0f85f9915e283e4d57b1c9.camel@gnu.org> X-CMAE-Envelope: MS4xfDslfH9v16oF+pbqD100qhOiOdvtpYjtSX9tdi7uXBYKEaM2chEPpp2MPglLpVh0dC+WThwD2+X4CWQA6wxQNh1hEpSEzIvpHjxuIWJcEdpYETXhe9MP RcETTmcHJT2Oj8YMsS0V5uyOlX3GwmMwIa1DuEgdWNfP4BEz0+zK6ArpNSS/o2r35V9SwdLl5IW7oA== Received-SPF: pass client-ip=195.186.120.131; envelope-from=fulbert@bluewin.ch; helo=vimdzmsp-sfwd01.bluewin.ch X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Spam-Score: -10.84 X-Migadu-Queue-Id: 8C18B60C37 X-Migadu-Scanner: mx13.migadu.com X-Migadu-Spam-Score: -10.84 X-TUID: H2Ct89pp5s82 Le Wed, Mar 27, 2024 at 10:39:36AM +0100, Adrien 'neox' Bourmault a écrit : > Le mardi 26 mars 2024 à 18:58 +0100, Fulbert a écrit : > > I forgot to mention : LUKS version 2 with PBKDF: argon2i. I remember reading > > that guix supported LUKS2 except for /boot… but I might be wrong. At > > least it > > has worked for month on my computer until guix d5f857a (22 mar 2024). > > > > So, new question, do I have to convert to LUKS1 ? > > > > Le 26.03.24 à 16:15, Fulbert a écrit : > > > > > Hello! Seeking some help/suggestions to solve a problem preventing > > > my system to boot up, which was working properly up to guix 9b84b36 > > > (21 mar 2024) (note: I confess that my system is not totally pure). > > > > > > Starting with guix d5f857a (22 mar 2024) up to my latest guix pull > > > with 1415ea7, the **system hangs during boot**, and it does before > > > anything is written to /var/log/messages. So, using a video capture > > > of the screen at boot, I was abble to catch : > > > > > > #+begin_src boot > > > shepherd[1]: Exception caught while while starting device-mapping-luks-homes: > > > (unbound-variable #f "Unbound variable: "S" (bytevector?) #f) > > > #+end_src > > > > > > … which appears to be the culprit ?! > > > > > > follows a long list of "shepherd[1]: Service XXX depends on YYY" and > > > then > > > #+begin_src boot > > > shepherd[1]: The following services could not be started in the background: > > > > > > #+end_src > > > > > >  From there : a blinking cursor and the only way out I found is > > > CTRL-ALT-DEL, which triggers shepherd to stop some services. After > > > that I have to shutdown using hardware button. > > > > > > My system and its config.scm have not changed and I see nothing > > > relevant, related to LUKS/dm-crypt, in `guix pull -l`. > > > > > > My LUKS is configured like so : > > > > > >    (mapped-devices > > >      (list > > >        (mapped-device > > >          (source (uuid "")) > > >          (target "luks-homes") > > >          (type luks-device-mapping)))) > > > > > >    (file-systems > > >      (append > > >        (list > > >          […] > > >          (file-system (mount-point "/home") > > >                       (device (file-system-label "luks-homes")) > > >                       (type "ext4") > > >                       (dependencies mapped-devices)) > > >          […] > > > > > > Any help would be appreciated. > > > > > > > Hi everyone, the exact same thing happens to me too since d5f857a. > > I'm using a pure GNU Guix installation with my /home as a LUKS partition. > > My fs configuration : > > (file-systems (cons* > (file-system > (mount-point "/home") > (device "/dev/mapper/crypthome") > (type "ext4") > (dependencies mapped-devices)) > (file-system > (mount-point "/boot/efi") > (device (uuid "A012-A17A" 'fat32)) > (type "vfat")) > (file-system > (mount-point "/") > (device (uuid "dfaec018-b99b-4d34-a206-eec25b833c45" 'ext4)) > (type "ext4")) %base-file-systems))) > > Happy hacking! > -- > Adrien Bourmault > Maintainer, GNU Boot project > Associate member, Free Software Foundation > GPG : 393D4CC68136F39799DA75F295F65F55F682A17A > > Hello Adrien and everyone, I have tried to transfer my /home data to a brand new LUKS1 partition, (as well as removing pointers to the old LUKS2 partition in my config.scm, of course) and the problem remains exactly the same, including those error messages (obtained with a video capture of the screen at boot, after removing 'quiet' from the kernel command line in grub) : #+begin_src boot shepherd[1]: Starting service device-mapping-luks-homes... shepherd[1]: Service device-mapping-luks-homes failed to start. shepherd[1]: Exception caught while starting device-mapping-luks-homes: (unbound-variable #f "Unbound variable: "S" (bytevector?) #f) #+end_src Maybe it's worth mentionning that I have tried one configuration of the 'mapped-device' with 'luks-device-mapping' and another one with 'luks-device-mapping-with-options #:keyfile "/…"'. I also tried one configuration with the 'source' declared in plain "/dev/..." and another one declared with the luks '(uuid "…")', just in case. So, although I have learned in the process that LUKS2 is not yet fully supported in guix, this problem also prevents booting using a LUKS1 /home partition… at least in my case… and I am surprised that we are only 2 to report about this, here. Transfering the /home data to a clear (unencrypted) partition is my current workaround to this problem. Any suggestion still welcome, but I suppose the next step should be to send a bug report, in due form.