From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 4NH3NxVkL2EiXAAAgWs5BA (envelope-from ) for ; Wed, 01 Sep 2021 13:29:25 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 4KGaMxVkL2E9IQAA1q6Kng (envelope-from ) for ; Wed, 01 Sep 2021 11:29:25 +0000 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 15041D505 for ; Wed, 1 Sep 2021 13:29:25 +0200 (CEST) Received: from localhost ([::1]:51356 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLOQl-0005RX-CU for larch@yhetil.org; Wed, 01 Sep 2021 07:29:23 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:47918) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLO3H-00062v-4Y for help-guix@gnu.org; Wed, 01 Sep 2021 07:05:08 -0400 Received: from mail-0201.mail-europe.com ([51.77.79.158]:55238) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLO3E-0002Yh-3s for help-guix@gnu.org; Wed, 01 Sep 2021 07:05:06 -0400 Date: Wed, 01 Sep 2021 11:04:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1630494260; bh=P3FpgeSE4UAIftjtY/ht8BFEn/oXUDbO0NVXtMG2BrU=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=RkL45f+EZ6azUzf9/YqeMNxvhh0xxcAoar3BiPBr1g4S791vibKshSkqOAvkSY3Dj aYpaszTVg4tqUyopyIqoliEgK4txRPHgSd6fpQsP6OcVsYZFfVSHvyeD9L+6hYCPaC lH2pgeWcXodv62bsqN9raoBGJiZ8Jiy3hkVKYhuw= To: Thiago Jung Bauermann From: Roland Everaert Cc: "help-guix@gnu.org" Subject: Re : Re: Librem Mini with pureboot/head don't boot GuixSD Message-ID: In-Reply-To: <1661974.YvECvzcvlD@popigai> References: <6aSjg7iYcJWpR7Q-nXpsq5dPo9ffUzh5f9l_jm-ZjoJYtCqXhRTs4Ln-Cgd6FCcP4nr48P7A3jmI0H-dkpuwYLnt1wTSTziwwKjJNNqBMCU=@protonmail.com> <125682436.G5Nuijvvs6@popigai> <1661974.YvECvzcvlD@popigai> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=51.77.79.158; envelope-from=r.everaert@protonmail.com; helo=mail-0201.mail-europe.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-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.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Roland Everaert Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1630495765; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc: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=P3FpgeSE4UAIftjtY/ht8BFEn/oXUDbO0NVXtMG2BrU=; b=b2+WZHMGtHKV2kyjYG8nfrDkAcsIA37a91wjoCUAKbfhKihttLUhZlk3N9ki9eTxNumGTO 1lRyp2L+/5B9elLISV47xfQ7mvI3In7qgzZU2Jp0nN4Nfna5VkLIN3EipaIXpYtxtkLhO6 bgnyvmJUOEQ/cwKsCshAQGMtp2tdUHN9WFfZwrLtSiCRkU+MInPHd1nzbDLbGxVnGbIxNM C3w9oGADfoREUHOadkzPJ8XR/FWLsPDxvFJrN50r+kiwHziUXYPWmpCFTiKiam4QruFjm2 BZF3Ekx0jTzWa4gmXuBGrYyteS9zZQWHf33Ba6ftBVWFF1GBpcybVC0O9laM2A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1630495765; a=rsa-sha256; cv=none; b=A0V77UJe/U9x2kkc+bbrdub2ea5FsgMsVXgYNnHgaNRx5O6TzXsOm/Bh0cr/c8UfUDEvth 2K6AoFu88RLZjGU2WZpZp5awzfRJCpISE4BrJdxOF15g8OE0YTvNEKwknnIQfp3e45WxgN Lmc6Uf9BWMhjjLHqs+0nAX64EiOPY40bifWpLUO25Kd8wCd2CnUMfT5pDZVjzaekuG/MzZ bXHbQfF3F109Y71GVcbLyzbJIR3jYufCgzqf1kIww66sUKBT11ETAsLbqH4URYbYKrkMcm 5ilPFSxFPk0YXCfSXZHq354WaqxPph+PlbsmwvN5GzkUgre1gY8MZRLPa41uTA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail header.b=RkL45f+E; dmarc=pass (policy=quarantine) header.from=protonmail.com; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Spam-Score: -3.12 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail header.b=RkL45f+E; dmarc=pass (policy=quarantine) header.from=protonmail.com; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Queue-Id: 15041D505 X-Spam-Score: -3.12 X-Migadu-Scanner: scn1.migadu.com X-TUID: ehyqHG/LliM1 Hello again, I am slowly moving forward with this topic. I manage to reinstall GuixSD on the librem Mini. But, now I am having issue= s with configuring GuixSD to add an entry to the bootloader menu, so, I can= tell HEADS to actually use the kernel in the separate partition mounted to= /boot. I discover that HEADS, actually, read the content of grub.cfg to pr= opose a list of system to boot on. Without the form (menu-entries), in the bootloader definition, 'reconfigure= ' runs fine. So what am I doning wrong? When the form (menu-entries) is not present, the only notable thing is that= the system does not mount the partition ("15dd9d6b-801b-4c57-b2dd-8712405d= 54e1") to /boot, as a part of the reconfigure operation and the fact that t= he copy of the kernel files should happen after the reconfigure. However, a= fter rebooting the system, the partition is mounted properly, so it is only= during the reconfigure that the partition has not been mounted. Is this in= tentional? When executing reconfigure with the file pasted below, I got a huge backtra= ce. Below is the head of the backtrace. Backtrace: 16 (primitive-load "/root/.config/guix/current/bin/guix") In guix/ui.scm: 2185:7 15 (run-guix . _) 2148:10 14 (run-guix-command _ . _) In ice-9/boot-9.scm: 1752:10 13 (with-exception-handler _ _ #:unwind? _ # _) In guix/status.scm: 820:3 12 (_) 800:4 11 (call-with-status-report _ _) In guix/scripts/system.scm: 1228:4 10 (_) In ice-9/boot-9.scm: 1752:10 9 (with-exception-handler _ _ #:unwind? _ # _) In guix/store.scm: 658:37 8 (thunk) 1320:8 7 (call-with-build-handler # =E2=80=A6) 2108:24 6 (run-with-store # = =E2=80=A6) In guix/scripts/system.scm: 1252:15 5 (_ _) 807:9 4 (perform-action reconfigure #< name: #f format:= =E2=80=A6> =E2=80=A6) In gnu/bootloader/grub.scm: 496:13 3 (grub-configuration-file #< = =E2=80=A6> =E2=80=A6) In srfi/srfi-1.scm: 241:2 2 (map _ _) In ice-9/boot-9.scm: 1685:16 1 (raise-exception _ #:continuable? _) 1685:16 0 (raise-exception _ #:continuable? _) ice-9/boot-9.scm:1685:16: In procedure raise-exception: In procedure map: Wrong type argument: (#< label: "GNU with Lin= ux-Libre 5.13.12" device: #< type: ext4 bv: #vu8(141 147 13 97 214 10= 1 77 110 183 1 83 125 191 171 22 162)> device-mount-point: "/" linux: # "/ bzImage"> linux-arguments: ("--root=3D8d930d61-d665-4d6e-b701-537db= fab16a2" # kernel: # kernel-loadable-modules: () kernel-arguments: ("modprobe.blacklist= =3Dusbmouse,usbkbd" "quiet") hurd: #f bootloader: #< bootloader: #< name: grub package: # installer: #package '("nss-certs" "restic" "gnupg")) %base-packages)) (services (append (list (service xfce-desktop-service-type) (service openssh-service-type) (set-xorg-configuration (xorg-configuration (keyboard-layout keyboard-layout)))) %desktop-services)) (bootloader (bootloader-configuration (bootloader grub-bootloader) (targets '("/dev/sdb")) (keyboard-layout keyboard-layout) (menu-entries (menu-entry (label "Guix for Pureboot") (device (uuid "15dd9d6b-801b-4c57-b2dd-8712405d54e1")))))) (swap-devices (list (uuid "22be707b-6a27-4f14-81cb-6a1a9c6d2c12"))) (file-systems (append (list (file-system =09=09 (mount-point "/") =09=09 (device =09=09 (uuid "8d930d61-d665-4d6e-b701-537dbfab16a2" =09=09=09'ext4)) =09=09 (type "ext4")) =09=09(file-system =09=09 (mount-point "/boot") =09=09 (dependencies (list "/")) =09=09 (device =09=09 (uuid "15dd9d6b-801b-4c57-b2dd-8712405d54e1" =09=09=09'ext4)) =09=09 (type "ext4"))) =09 %base-file-systems) )) Roland Everaert --- Use the F.O.S.S., Luke Sent with ProtonMail Secure Email. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Le vendredi 20 ao=C3=BBt 2021 =C3=A0 00:39, Thiago Jung Bauermann a =C3=A9crit : > Hello Roland, > > Em quinta-feira, 19 de agosto de 2021, =C3=A0s 11:57:45 -03, Roland Evera= ert > > escreveu: > > > I manage to successfuly copy the needed files to /boot using the `for e= ach` loop from =E2=80=98%copy-kernel-and-initrd=E2=80=99, Thank You. > > That=E2=80=99s great! > > > However, I need to resize (i.e. reduce) the root filesystem so /boot ca= n > > > > live in its own one. Currently, copying the kernel files too /boot is > > > > useless, as HEAD will scan and sign all the files in /, anyway. > > > > Did you have any article discussing such process? > > > > I find plenty of articles about increasing the root partition, but, non= e > > > > to reduce it. > > > > As the root partition cannot be unmounted online, I need to know if the= re > > > > is a simple way to "switch to an offline mode of sort". For example, I > > > > could map a minimal root FS in memory and chroot to it. An other > > > > possibility is to copy a guix system to a USB drive and boot from it. > > > > The USB option seems the easiest, but the one with the RAMFS seems neat= . > > > > What are the recommandations of the fine folks on this ML, for such > > > > operation? > > I don=E2=80=99t have any resource about how to shrink a partition and its > > filesystem. I would boot into some distro=E2=80=99s live image and do it = from > > there. > > Shrinking a partition is dangerous and error-prone because there are two > > steps: > > 1. Shrink the filesystem > 2. Shrink the partition > > If you get the size calculation wrong in step 2 you=E2=80=99ll end up= cutting off > > the end of your filesystem and thus corrupt it. > > So I believe the recommended practice is to always shrink the partiti= on to > > be slightly bigger than the filesystem to make sure you don=E2=80= =99t take that > > risk. You can then optionally grow back the filesystem to fill the sl= ack > > space (filesystem resizing tools can automatically calculate the corr= ect > > size to fill the partition). > > Since this is a risky operation, you have to make sure you have backu= ps of > > everything. And since you need to do that, to be honest what I would > > really do is wipe everything out, repartition the disk to the new lay= out > > and then restore from backups... > > -- > > Thanks, > > Thiago >