From debbugs-submit-bounces@debbugs.gnu.org Tue Jun 20 15:45:36 2023 Received: (at submit) by debbugs.gnu.org; 20 Jun 2023 19:45:36 +0000 Received: from localhost ([127.0.0.1]:59799 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qBhIG-0003gn-Dq for submit@debbugs.gnu.org; Tue, 20 Jun 2023 15:45:36 -0400 Received: from lists.gnu.org ([209.51.188.17]:47614) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qBhIE-0003ga-9X for submit@debbugs.gnu.org; Tue, 20 Jun 2023 15:45:34 -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 1qBhHv-0007cn-Ht for bug-guix@gnu.org; Tue, 20 Jun 2023 15:45:18 -0400 Received: from mx0.riseup.net ([198.252.153.6]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qBhHr-00019o-RQ for bug-guix@gnu.org; Tue, 20 Jun 2023 15:45:14 -0400 Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4QlxtV5jBmz9tJb for ; Tue, 20 Jun 2023 19:45:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1687290306; bh=OjHuLrMzIC6wmBn9HHYkuiHGU1Hy0L2nfnum9W0DZ40=; h=From:To:Subject:Date:From; b=Xa2YeaHBUqVxE5PTzHIMffC54Y9/I5XO7zB1PEs2naAzKBlI0wAXmtaWasystA6T4 L4xMbTAXUhbYwAboeMKUtmG+cgfYoxVvV8Bb1ATJERzUDAGxKTcU7LpbmQFvYgHgyN A/idRepMp0xNyinitrvGLSsZY/SSt1QSFs8xmESU= X-Riseup-User-ID: 44327C4729F980C664E1A3E6A5DE12DA045914230AD144193088DB54DA7485DE Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4QlxtV2FTCzFryn for ; Tue, 20 Jun 2023 19:45:06 +0000 (UTC) From: Csepp To: bug-guix@gnu.org Subject: Can't boot due to discrepancy between reconfigure and init Date: Tue, 20 Jun 2023 20:38:58 +0200 Message-ID: <87jzvxrk94.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=198.252.153.6; envelope-from=raingloom@riseup.net; helo=mx0.riseup.net 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -1.4 (-) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.4 (--) I'm trying to move my installation from /dev/sda to /dev/sdb, I created the file system and changed the bootloader config in my operating-system definition to point to /dev/sdb and the file-system to use the correct UUID (previously it was using a label). First I tried to simply reconfigure my running system and then taking a BTRFS snapshot and copying that over the /dev/sdb1, but that failed. The exact error was GRUB not being able to find a file system with a given UUID, which matched the UUID of /dev/sda1. This error happened before GRUB loaded any of its modules, so I was dropped into a rescue shell. I thought this might be related to subvolumes, maybe I originally used the wrong config and the updated config was written to a different subvolume and GRUB doesn't recognize the default subvolume ID option on the BTRFS partition. I think this is a fairly critical error. The error doesn't manifest when I run guix system init with the same config, so there is some (possibly un(der)documented) difference between guix system reconfigure and guix system init that makes the former rely on the state of the running system in a way that doesn't take into account the new configuration. Is this intended behaviour for some reason? From debbugs-submit-bounces@debbugs.gnu.org Wed Jun 21 03:45:37 2023 Received: (at 64196) by debbugs.gnu.org; 21 Jun 2023 07:45:37 +0000 Received: from localhost ([127.0.0.1]:60544 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qBsX2-0001DV-Iq for submit@debbugs.gnu.org; Wed, 21 Jun 2023 03:45:36 -0400 Received: from jpoiret.xyz ([206.189.101.64]:43030) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qBsX1-0001DN-5j for 64196@debbugs.gnu.org; Wed, 21 Jun 2023 03:45:35 -0400 Received: from authenticated-user (jpoiret.xyz [206.189.101.64]) by jpoiret.xyz (Postfix) with ESMTPA id B3A05185420; Wed, 21 Jun 2023 07:45:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jpoiret.xyz; s=dkim; t=1687333532; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=iJp8zH0ZXJDdxyag3m4HRfpC2UlCUhSIwLz4TPY1BCU=; b=MNHW5rTlKeyrxStMh4sx8EDFyFox6lIPL9v0mxOwAn2I3kku6Tqd/qSkKlCnn9tzMbNXej CjlWwR4FSMzb1zSJ6GunDZo8DfIhhj4JHv9Zl4RXKGA6jTtA+fkD5VzjY4hx880rN85y5o M1FCspDFOwo40U6WQ5mDm5dXr3TBiqBHz/CD260VmkXCqXnHRiuJjeeXoMvKnChxxeFTV/ f+ksE5RYWqQZkOIpq+dU6RlqNv4hLSc0KyxaWs5CaKVWauFe4tVDS7yNrCyD8MydCk37+L /65qm3ck7WCIH07MqrfbgYVdeX5lptulXDttGJrtigzWoasdtTFr6Y8THL8qag== From: Josselin Poiret To: Csepp , 64196@debbugs.gnu.org Subject: Re: bug#64196: Can't boot due to discrepancy between reconfigure and init In-Reply-To: <87jzvxrk94.fsf@riseup.net> References: <87jzvxrk94.fsf@riseup.net> Date: Wed, 21 Jun 2023 09:45:30 +0200 Message-ID: <87legd45t1.fsf@jpoiret.xyz> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spamd-Bar: / Authentication-Results: jpoiret.xyz; auth=pass smtp.auth=jpoiret@jpoiret.xyz smtp.mailfrom=dev@jpoiret.xyz X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 64196 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Csepp, Csepp writes: > I'm trying to move my installation from /dev/sda to /dev/sdb, I created > the file system and changed the bootloader config in my operating-system > definition to point to /dev/sdb and the file-system to use the correct > UUID (previously it was using a label). > First I tried to simply reconfigure my running system and then taking a > BTRFS snapshot and copying that over the /dev/sdb1, but that failed. Any reason you didn't try in the reverse order? This seems prone to error. > The exact error was GRUB not being able to find a file system with a > given UUID, which matched the UUID of /dev/sda1. This error happened > before GRUB loaded any of its modules, so I was dropped into a rescue > shell. > I thought this might be related to subvolumes, maybe I originally used > the wrong config and the updated config was written to a different > subvolume and GRUB doesn't recognize the default subvolume ID option on > the BTRFS partition. > I think this is a fairly critical error. This is too fuzzy to be actionable, but if you manage to reproduce reliably then I would gladly take a look at it. > The error doesn't manifest when I run guix system init with the same > config, so there is some (possibly un(der)documented) difference between > guix system reconfigure and guix system init that makes the former rely > on the state of the running system in a way that doesn't take into > account the new configuration. I don't think there is, the biggest difference is that `guix system init` will copy stuff into the target store and initialize the basic directories for Guix, whereas reconfigure will just build everything in the current store. Best, =2D-=20 Josselin Poiret --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmSSqpoQHGRldkBqcG9p cmV0Lnh5egAKCRBQXkC5Fhcaiq7RDAC5MHCJVgd3EzvWy4HusWs2ywThOU4trY21 lTmz78YbOhq3JT7GYq1xw/lxIY+UDvQ5e3tGT6v7cDSytR3f8EAYI9sTAcJdVTpN pKXKLoql80nxxsoZyzwjVyv5xNr4mo3J4wRQaMdy8XxR5oOOZjhLwWPe3RI6qfdY yDPfRJd1G96ChBth1Z5D5rE6a86lGqW1HaiC1unE2m+XQZfeOZI7FClVSDqN72zT hQcspVbbdl5mMOlKCH4sDBACsnnU94LiYNWifFV6k9S+zmZ3lG5ewEm9PULxwor0 Jt5WTqvdAR80K9T8kK3g1i0uHUw1dQoljHjLyt7eeUibW5YORTMRx9p5EznTofXe 7QqebhQRIV0lgNNxmcWUz/lh1N7jJvmrHwjvaLN5rRBcyANevkt7EYV7z9sA0GLz oTNusl4mEPS8VFvZJFr0gyoISzUg8Ut3svaydCi19rCntsuuGAICM13rTNNDaGWh 1wLUqHejcjirzx9k35OvUmkmWpyo0+o= =fhIA -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Wed Jun 21 18:13:39 2023 Received: (at 64196) by debbugs.gnu.org; 21 Jun 2023 22:13:39 +0000 Received: from localhost ([127.0.0.1]:34341 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qC655-0005EG-CW for submit@debbugs.gnu.org; Wed, 21 Jun 2023 18:13:39 -0400 Received: from mx1.riseup.net ([198.252.153.129]:39840) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qC653-0005E1-7z for 64196@debbugs.gnu.org; Wed, 21 Jun 2023 18:13:38 -0400 Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4Qmd7H5yGJzDqnV; Wed, 21 Jun 2023 22:13:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1687385611; bh=bOsXTzbi5TXOhvXWr62JGBCEYDtzOX73atiQDYCd/z0=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=LiBiJcrqEtqveFyMLGoeCtu5kqFjPc2E5n2H5suJvoN7ugSiggixDdVOHGULLN3az onyo+eEf6Wf3OUhIcIZUhRb/ndsnSUiquFos6kup6LnzXHcVXIssinDYdA8wHmKZsc EU4uk6aoszX6mtXipbm3UAfRAggXnoyJ4kZYROKg= X-Riseup-User-ID: 057C01909C0D8E8E1344828B877DC0E5E82C6CAB5606CABAC6F4A7B8E8512C3B Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4Qmd740TgpzFrx9; Wed, 21 Jun 2023 22:13:19 +0000 (UTC) References: <87jzvxrk94.fsf@riseup.net> <87legd45t1.fsf@jpoiret.xyz> From: Csepp To: Josselin Poiret Subject: Re: bug#64196: Can't boot due to discrepancy between reconfigure and init Date: Thu, 22 Jun 2023 00:08:36 +0200 In-reply-to: <87legd45t1.fsf@jpoiret.xyz> Message-ID: <877crwmpl1.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 64196 Cc: 64196@debbugs.gnu.org, Csepp X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Josselin Poiret writes: > [[PGP Signed Part:Undecided]] > Hi Csepp, > > Csepp writes: > >> I'm trying to move my installation from /dev/sda to /dev/sdb, I created >> the file system and changed the bootloader config in my operating-system >> definition to point to /dev/sdb and the file-system to use the correct >> UUID (previously it was using a label). >> First I tried to simply reconfigure my running system and then taking a >> BTRFS snapshot and copying that over the /dev/sdb1, but that failed. > > Any reason you didn't try in the reverse order? This seems prone to error. Since reconfigure overwrites /dev/sdb, I don't see how reversing the order would fix things?? Maybe copying the file system over and *then* running init would make sense. >> The exact error was GRUB not being able to find a file system with a >> given UUID, which matched the UUID of /dev/sda1. This error happened >> before GRUB loaded any of its modules, so I was dropped into a rescue >> shell. >> I thought this might be related to subvolumes, maybe I originally used >> the wrong config and the updated config was written to a different >> subvolume and GRUB doesn't recognize the default subvolume ID option on >> the BTRFS partition. >> I think this is a fairly critical error. > > This is too fuzzy to be actionable, but if you manage to reproduce > reliably then I would gladly take a look at it. I tried reproducing it, it seems to happen every time, but I can try to create a more minimal test case. >> The error doesn't manifest when I run guix system init with the same >> config, so there is some (possibly un(der)documented) difference between >> guix system reconfigure and guix system init that makes the former rely >> on the state of the running system in a way that doesn't take into >> account the new configuration. > > I don't think there is, the biggest difference is that `guix system > init` will copy stuff into the target store and initialize the basic > directories for Guix, whereas reconfigure will just build everything in > the current store. > > Best, I mean, that's the theory, but either Guix or GRUB seems to get the incorrect UUID from *somewhere*. From debbugs-submit-bounces@debbugs.gnu.org Thu Jun 22 03:35:27 2023 Received: (at 64196) by debbugs.gnu.org; 22 Jun 2023 07:35:27 +0000 Received: from localhost ([127.0.0.1]:34724 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qCEql-0007Ac-As for submit@debbugs.gnu.org; Thu, 22 Jun 2023 03:35:27 -0400 Received: from jpoiret.xyz ([206.189.101.64]:42824) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qCEqi-0007AS-MH for 64196@debbugs.gnu.org; Thu, 22 Jun 2023 03:35:25 -0400 Received: from authenticated-user (jpoiret.xyz [206.189.101.64]) by jpoiret.xyz (Postfix) with ESMTPA id EDC51185420; Thu, 22 Jun 2023 07:35:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jpoiret.xyz; s=dkim; t=1687419323; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5g1JPaW4NW7qvyQHkHgV4idIVi76NT+84tyzN8kcI4c=; b=BmuMP7wo7EOYOn7Hig9MW+ddHJSVBAwUYt1NqayQFmvKz3vJGbj+lLykCm3t21xcw8TuiU tEbe+WuOSp/YjFwRuiBNtK7Xpq0VR7YCoQnGyfrYHrysUvEFdBgBKpYsoq05Dpp/s+TrJD t3FLgd+ve2KqA6esX9CLEnrhmFjb6KuSx5wB8wF2phSLlyfmlYuDW+FUUYSH6b49qPJJVA NFZXST/e/Z8Zbf5wtalEgexO6YZWfjZGEsh6FoygkT1skecCy/erX1atGch6DVojiafLbU 0QAhbQxZIp1Ip9ZnIORVgEtEKhQjQkEuc412CLKGB+pW53LZqxYr3dPpfV9Hjw== From: Josselin Poiret To: Csepp Subject: Re: bug#64196: Can't boot due to discrepancy between reconfigure and init In-Reply-To: <877crwmpl1.fsf@riseup.net> References: <87jzvxrk94.fsf@riseup.net> <87legd45t1.fsf@jpoiret.xyz> <877crwmpl1.fsf@riseup.net> Date: Thu, 22 Jun 2023 09:35:08 +0200 Message-ID: <87h6r0rlub.fsf@jpoiret.xyz> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spamd-Bar: / Authentication-Results: jpoiret.xyz; auth=pass smtp.auth=jpoiret@jpoiret.xyz smtp.mailfrom=dev@jpoiret.xyz X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 64196 Cc: 64196@debbugs.gnu.org, Csepp X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.0 (/) --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, Csepp writes: >> I don't think there is, the biggest difference is that `guix system >> init` will copy stuff into the target store and initialize the basic >> directories for Guix, whereas reconfigure will just build everything in >> the current store. >> >> Best, > > I mean, that's the theory, but either Guix or GRUB seems to get the > incorrect UUID from *somewhere*. You can manually check that the generated grub.cfg file contains the expected UUID after the reconfigure, it should be in /boot/grub/grub.cfg. Best, =2D-=20 Josselin Poiret --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmST+awQHGRldkBqcG9p cmV0Lnh5egAKCRBQXkC5FhcailvgC/4iFN3XijbRtC1ED/4S18XvNwJaHUyX8+Dg sil+wPlwuynkTfJvbQh4l+q0DkOyDXOy0prd1ZIStP6yghVg3Ormq12L2O9Zx/Yv LlC6/e67VILUINo/ULpogcRFKwWj64OqEsURnhkH3+ohXiWnRK6+pJdOSTZxLf2E HlZFflftUt6NDm7dwbI0jQ022bMIAQxpncOCgOHyi2ZG94dwznDblr3GlHJxyBy1 sOmn71t8fZNuZnQsfKw6nQqRxxcQHIgLcgtGuo51nSxhpPQ5lSsJhB9iACFg7jn4 DI+dUtIPu/NDJDem44K7MfBzWaburg+b7bQtoqR6W0r0I1mKMKYtKOuKIz+eD9Bt JtZh18F5/14NTtbI3F2LvDLZWPfwSJBEmNeLqlwtr2XR6NvEvXbTdnaVy0SKLqB4 wj0DpmBGgtn9ek2G5m1sXxUkjcWUmOLyAXUI+1JL3r3yOZvEOPIK//2EjVOwuR0t fz8USFsLsR2ktLNt0fjt4xGLD8v5vpU= =45Yn -----END PGP SIGNATURE----- --=-=-=-- From debbugs-submit-bounces@debbugs.gnu.org Sat Jun 24 14:03:50 2023 Received: (at 64196) by debbugs.gnu.org; 24 Jun 2023 18:03:50 +0000 Received: from localhost ([127.0.0.1]:41481 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qD7by-0000lx-97 for submit@debbugs.gnu.org; Sat, 24 Jun 2023 14:03:50 -0400 Received: from mx0.riseup.net ([198.252.153.6]:49988) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qD7bt-0000lg-OU for 64196@debbugs.gnu.org; Sat, 24 Jun 2023 14:03:48 -0400 Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4QpMRc2XtBz9t5v; Sat, 24 Jun 2023 18:03:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1687629820; bh=sesIipPZXU05cAk5IoJsgC5V7BedRLVjwuc54AQkbp4=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=g3yokrv11MKpyxYBLHbxZc79kI5FWPIAaf1dYRSWt9meWWA/olv6pOc28BamYI/D8 jr6leyP01789adRhBY9tvSem+PkNoUgSCFxA19PadOYFXN2dt+a6tK4Thjp22NQ09U ML939or0296kyb4MoJTukJNoRdCGtALPGyK1uPhQ= X-Riseup-User-ID: 2FB34D2500941496E99BF1C6CC2B9CD3C8A4B5628A8D845299A0AAB6A89AB524 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4QpMRb3zjxzJn7m; Sat, 24 Jun 2023 18:03:39 +0000 (UTC) References: <87jzvxrk94.fsf@riseup.net> <87legd45t1.fsf@jpoiret.xyz> <877crwmpl1.fsf@riseup.net> <87h6r0rlub.fsf@jpoiret.xyz> From: Csepp To: Josselin Poiret Subject: Re: bug#64196: Can't boot due to discrepancy between reconfigure and init Date: Sat, 24 Jun 2023 20:01:12 +0200 In-reply-to: <87h6r0rlub.fsf@jpoiret.xyz> Message-ID: <874jmwzqiy.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 64196 Cc: 64196@debbugs.gnu.org, Csepp X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Josselin Poiret writes: > [[PGP Signed Part:Undecided]] > Hi, > > Csepp writes: >>> I don't think there is, the biggest difference is that `guix system >>> init` will copy stuff into the target store and initialize the basic >>> directories for Guix, whereas reconfigure will just build everything in >>> the current store. >>> >>> Best, >> >> I mean, that's the theory, but either Guix or GRUB seems to get the >> incorrect UUID from *somewhere*. > > You can manually check that the generated grub.cfg file contains the > expected UUID after the reconfigure, it should be in > /boot/grub/grub.cfg. > > Best, I did, I think I already wrote that it wasn't coming from there, but I'll check again when I next try it. From debbugs-submit-bounces@debbugs.gnu.org Wed Jul 26 18:46:03 2023 Received: (at 64196) by debbugs.gnu.org; 26 Jul 2023 22:46:03 +0000 Received: from localhost ([127.0.0.1]:40139 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qOnGd-00039o-EH for submit@debbugs.gnu.org; Wed, 26 Jul 2023 18:46:03 -0400 Received: from mx0.riseup.net ([198.252.153.6]:57360) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qOnGb-000399-R8 for 64196@debbugs.gnu.org; Wed, 26 Jul 2023 18:46:02 -0400 Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4RB8BW6nx5z9sNy; Wed, 26 Jul 2023 22:45:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1690411556; bh=9OngYrpYnbxuJY0+r+UXSDjbHmNiXGqfslxRXWDcoOE=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=e90tbuqmmxUkT6St+ZvZRBCWpEjhEKjfaJWVzNrpJsh3qKV0ovApMROgCXZf6q+p6 3YjvuwcjyTmqq+VAma93zM6SWswM3iHXwLwRREujLNA3A+TvuZLAJzuBH/H655/2KR Bo2NwS5eqVV5WMPbbhFhGzPp+OLKxcm2UoS5+bIc= X-Riseup-User-ID: F3C68F59599BDCF9ED5B3124F576D06FE366F4196EACCD61059B6AD33D3083E8 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4RB8BW1bNFzFrwk; Wed, 26 Jul 2023 22:45:55 +0000 (UTC) References: <87jzvxrk94.fsf@riseup.net> <87legd45t1.fsf@jpoiret.xyz> <877crwmpl1.fsf@riseup.net> <87h6r0rlub.fsf@jpoiret.xyz> <874jmwzqiy.fsf@riseup.net> From: Csepp To: Csepp Subject: Re: bug#64196: Can't boot due to discrepancy between reconfigure and init Date: Thu, 27 Jul 2023 00:42:45 +0200 In-reply-to: <874jmwzqiy.fsf@riseup.net> Message-ID: <87o7jy9tra.fsf@riseup.net> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 64196 Cc: 64196@debbugs.gnu.org, Josselin Poiret X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) Csepp writes: > Josselin Poiret writes: > >> [[PGP Signed Part:Undecided]] >> Hi, >> >> Csepp writes: >>>> I don't think there is, the biggest difference is that `guix system >>>> init` will copy stuff into the target store and initialize the basic >>>> directories for Guix, whereas reconfigure will just build everything in >>>> the current store. >>>> >>>> Best, >>> >>> I mean, that's the theory, but either Guix or GRUB seems to get the >>> incorrect UUID from *somewhere*. >> >> You can manually check that the generated grub.cfg file contains the >> expected UUID after the reconfigure, it should be in >> /boot/grub/grub.cfg. >> >> Best, > > I did, I think I already wrote that it wasn't coming from there, but > I'll check again when I next try it. This is still happening. Couldn't figure out a decent way to transfer my system with btrfs send. I checked the generated bootloader installer script that gets run, it seems to refer to the correct device, but somehow the UUID of the booted partition still gets accessed. I guess I'll have to strace it.