From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:bcc0::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id CB7wEexecGCr6QAAgWs5BA (envelope-from ) for ; Fri, 09 Apr 2021 16:04:28 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id iEHaC+xecGAWagAAB5/wlQ (envelope-from ) for ; Fri, 09 Apr 2021 14:04:28 +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 B307D231DC for ; Fri, 9 Apr 2021 16:04:27 +0200 (CEST) Received: from localhost ([::1]:37768 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lUrkI-0006sI-Er for larch@yhetil.org; Fri, 09 Apr 2021 10:04:26 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40250) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lUphh-0002lw-1u for help-guix@gnu.org; Fri, 09 Apr 2021 07:53:37 -0400 Received: from mail-il1-x12a.google.com ([2607:f8b0:4864:20::12a]:33718) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lUphb-0001kp-6e for help-guix@gnu.org; Fri, 09 Apr 2021 07:53:36 -0400 Received: by mail-il1-x12a.google.com with SMTP id 7so2811379ilz.0 for ; Fri, 09 Apr 2021 04:53:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=wvdFcajdQ1D0mTkNatW2ZtJUi6TC66Oh6Hw9KS9Z6LM=; b=nSkarvsxQERRhQiCynJkh/5dI3OLoUEmy/GvU9u64QgymuKR25Nbk+KIH/df9T1C2K JNxCkJYAm/UT+XdVeKyoHhlydmIxQvekPCLBqKjhd+DfBQB1JFIcwIHuLd78yb32lNyf 4FPufCE1bgyDS3s+8EdqPY/QTGcykQGn85z0vVOOHnB9ioEtQbryNMXITqfgEN2BmTCE t6gd2YXitssYqDFxloh4MhDAxe7bH48yi3891ThVpF4OzRa6tEmsueyzl8KJM6Driw2s h91HOcRRvR3Yjgq/cPQ9+vMnqsWVGLmBoCOhRz4iIRj6x+kHOI5NJQuGBoaZ+qCtJDlo onAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=wvdFcajdQ1D0mTkNatW2ZtJUi6TC66Oh6Hw9KS9Z6LM=; b=fvEzDqX1xOLeWr0HRkZQd/1WRZo2SMXWdDKXtlKsGJkO8HPdyYD2CysGlH42FouuOS dFMCCcO+YTjVVKbeZDTPrBOUGQSbAe3lX5T+tlcLjDtskdS8mznDz1Hm6dj4o/Vee8Ha iDX1xNwu+AudJcKzkMg/p/rpkWJMLfkjFUydo0rrtUO3r8ii1OQorabbZFltAqGSU0MO pPjDLNE4dRcYAhFbo2F1JuIEOjirrxYLHcqNAgywOEdHGBnsvIXugtq+CDMxwU4gxH/b cbNc6Aa9dqj+dIaKmllgzv1KkDm6l7y33985gRIv7UBgIXOnG4Udcu2+iQgULqoDK4W7 Ee7A== X-Gm-Message-State: AOAM531QS9Cejc/SXuiS0TEmH/t4NckA+8C+FTwyVrwWY3CpctytMrN0 /fN5GPiWlT3gyJJCMibR+FrT4+SzrnfUisZNsjcjv5WnewE= X-Google-Smtp-Source: ABdhPJwkaiMVS51ZdIU34QMIaDW0iq3fTGLMDUQXOnASx7tvfWfGAtk/VYv02OldOAmavZd9pKC7sqbSdSyS0LT/TOM= X-Received: by 2002:a05:6e02:80b:: with SMTP id u11mr2368111ilm.153.1617969208673; Fri, 09 Apr 2021 04:53:28 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Vladilen Kozin Date: Fri, 9 Apr 2021 12:53:16 +0100 Message-ID: Subject: Re: How to debug failed boot after successful reconfigure? To: help-guix@gnu.org Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=2607:f8b0:4864:20::12a; envelope-from=vladilen.kozin@gmail.com; helo=mail-il1-x12a.google.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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Fri, 09 Apr 2021 10:03:18 -0400 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: , 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=1617977067; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=wvdFcajdQ1D0mTkNatW2ZtJUi6TC66Oh6Hw9KS9Z6LM=; b=QpuAqnaJMZjAWUqlq0tsdip0//FZX/mGDwjgkMdfU80enTCBH1FyI/DNs/gVB6e/dEob1Z 5v1ukFUxcFdxvOCpYmPm4hfS/WLQoGiwM/cC1G958A7xoMRNUKs7vUx0196+NuvC27WjRe TrzevCAEWuL7NSuhQKLgxkYJBIIQp+jA+fsaMGEHsQDjzfIbaCdNhk05iw+/o23M6RmluK QxyFTtbIIrv00cRPt8XshpeuqdM0rnLSa4fiVbCsah86y+U2bpxruV2Cn3TmkSCtVX+S1f zyE8QnWZ9rbEcKxcCmcntKfvHjw8iucbhy9XUw/rsxJAFHjhjHxTvm/DaQcUyw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1617977067; a=rsa-sha256; cv=none; b=Cfj5If8SfPn4y3NnbP7mpBIzjm3EBpdMj4g/kYCmN2EHmjqJxx5NRBFwLj8ez4LogfsCYd Q3l4FL2stMDpRvZHOS6LmV5E2UUBulmrbhZOUm88fcLbN6wOg7ryFESIQ6TQNkur8UBuGr C2L40JDxVBRD/Roj980DcWSlc0DsBL9GpEQiihn5426120Rl1hMgHL2Wqmt+W8OPckhNkk O9SHGIeeDHeBQFeFVUB0HylBz2/zhRU/Di+mKOy1aTvqnP3H1Rho4f0BzdGLwlj9N9h5l/ HgkuFS8F4mBSwwL11GAM7ilGcFYSk76LUxf61S2SNvVKk9v1TD3Gcpz6afLgVA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=nSkarvsx; dmarc=pass (policy=none) header.from=gmail.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: -2.14 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=nSkarvsx; dmarc=pass (policy=none) header.from=gmail.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: B307D231DC X-Spam-Score: -2.14 X-Migadu-Scanner: scn0.migadu.com X-TUID: 1MeOcVnKSCuK Hm, bit puzzled. Noone ever encountered boot failures with Guix? Should I've sent it to guix-devel? I'm going to try my luck in a separate thread with a much narrower question. FWIW for the issue at hand I ended up leveraging the fact that I'm running on a server with out-of-band ethernet and IPMI on board. Essentially, I ended up configuring that server to communicate Serial over Lan, then reconfigured Guix with Grub and Kernel both doing IO to serial console, then connected over SSH while running inside a Tmux session ... so now I can scroll up if boot fails and see exactly what happened. This would probably only work on an actual enterprise hw that lets you do IPMI SOL. For anyone interested here're relevant parts of my config.scm: ;; make sure kernel IO to serial both com1 and com2 (kernel-arguments '("console=tty1 console=ttyS0,115200n8 console=ttyS1,115200n8")) ;; make sure grub IO goes over serial both com1 and com2 (bootloader (bootloader-configuration (bootloader grub-bootloader) ;; TODO well that's nuts given that plugging in USB drive changes ;; order of block devices (target "/dev/sda") (keyboard-layout keyboard-layout) (terminal-inputs '(console serial_0 serial_1)) (terminal-outputs '(console serial_0 serial_1)))) Seriously, noone knows where to find dmesg and contents of /etc that pertain to the last attempt to boot specific generation? Pretty please? On Thu, 8 Apr 2021 at 16:58, Vladilen Kozin wrote: > > Hi list. > > I'm trying to wrap my head around running guix. While question in subj > is general it was prompted by a real failure, so really I am > interested both in "general approach" as well as solving the actual > problem I ran into. > > having updated with `guix pull` I run `sudo guix system reconfigure > config.scm` which succeeds. I reboot and the boot fails attempting to > mount the new file-systems I've introduced in that config. This being > guix I reboot into older generation. However, now I am unsure how to > debug what'd happened. E.g. I would like to: > - look at failed dmesg or equivalent log, > - look at files that reconfigure produced in /etc, e.g. /etc/fstab > > IIUC when I boot even from an older generation, the failed one will be > marked as "current" (that is the newest reconfigured) but everything > in /etc appears to belong to the older generation - hardly surprising. > Following link shown by `guix system describe` in my case > /var/guix/profiles/system-2-link I don't see e.g. /etc/fstab I'm > interested in. Where are those files? > > So, the questions above (maybe others I should've asked?) amount to my > asking, how to debug the failure. > > My specific case was adding these files-systems to my os declaration: > (file-system > (mount-point "/mnt/tempb") > (device (file-system-label "tempb")) > (type "ext4") > #;(flags '(no-atime)) > (options "defaults,noatime,discard,user") > (create-mount-point? #t)) > > At boot time I got multiple errors from mount unable to figure the > options supplied. This in itself is puzzling seeing how I did check > /etc/fstab after reconfigure and was able to manually mount as per > that generated /etc/fstab without issue. One note is that I think the > (create-mount-point? #t) had not been honored, but I did create those > mount points manually. Dunno, might be a bug in guix proper. But > that's minor. > > Thanks > > -- > Best regards > Vlad Kozin -- Best regards Vlad Kozin