From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 25AED61797 for ; Mon, 14 Sep 2020 12:10:11 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0DB58FB2C for ; Mon, 14 Sep 2020 12:10:11 +0200 (CEST) Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id DB866FB17 for ; Mon, 14 Sep 2020 12:10:08 +0200 (CEST) Received: by mail-yb1-xb35.google.com with SMTP id b142so2296669ybg.9 for ; Mon, 14 Sep 2020 03:10:08 -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=U7yOnlXDpYfYxATR1IEWGlpntGk7AiLD812QZMWnoHs=; b=u7Xn3C1aAdetQ4yInUpui8x8Lqlf9tx3J6ffI8QR/bdCiydzKV7vHA1Exi6uGnMcAF dAvEv3pfFzM1y590m5q909VgA0KZtXlGPEdbj1WuE2x9ZFbSspTWSTcuTnxSFHOcfedH T4YLxcUSeXrERIWehkToJXIPkz9n8znvUJJRR+87OFYAiJrB3SP4ARgl659jIa+gwyHr Hd21yi/vIlrsOfFPJJqVMsRToe0uAock90ReXMbt6uu4Olt1mPmS574I423NaTIIkHGH /XSUSpIbiD4kUOfHJb6TH4/GTspZWfuPwq4mYGVf4PMzEMTFqzMBmRIRutjlgN+9s3VS 0pFA== 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=U7yOnlXDpYfYxATR1IEWGlpntGk7AiLD812QZMWnoHs=; b=M/mtKW2pI/ypg1igD9Chqn8sGbhGLg1xF7Y0pgotQsNd1IBom0wwAPeTsVEJtqlo/K Tx/FHO8r2nP8ENeBfBsX2ZV3jpzvIZCXXVglGTwqZUfKaq8ldVierhQ5mWjSfSsYviLV PBWzIl5MT/KnGcH4moOaNe2me8A1C2JxcEuoqekNQn7i0CK9EiNn3hMXoRwGkzQCtQUH 3FfEIr6V3eLpilKWqdnMdSQNGfUgMPq2doQdEzGwwTrI7Lp3wRyzzlwXtNYT1NOZkbKM ju84LVuRmCqSzV09PybGySy/RIDJmZPuuGKA2qRnz34wGX5HiDMD8ImIgfqfCtdjhgAP LGfg== X-Gm-Message-State: AOAM531l+0615emX/z5NcL6mfZlipInxdGm4fA6/KCXwpTkYusENUDYT lGDs/nF0bftFOnrA7rfqbx46CkOcbWp0zuOSlNh9d9pC X-Google-Smtp-Source: ABdhPJyhU1WD+dQGwRIuAEe8KLVxoYbkiDLHc0C5WJoYpHDpF7G7mRzkOV43vLQtK0X1kF/eSpVmW75llFLHDipn4qg= X-Received: by 2002:a5b:3d2:: with SMTP id t18mr17576908ybp.333.1600078201348; Mon, 14 Sep 2020 03:10:01 -0700 (PDT) MIME-Version: 1.0 References: <35ff9a9f-60ba-5588-b5f7-d5c9b7483c84@it-functions.nl> <4c25b97a-507c-5ff9-effd-c04d39e848dc@proxmox.com> <5600ea98-0dca-6a27-e2ec-bb269660cf2e@proxmox.com> In-Reply-To: <5600ea98-0dca-6a27-e2ec-bb269660cf2e@proxmox.com> From: Gianni Milo Date: Mon, 14 Sep 2020 11:09:49 +0100 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_ENVFROM_END_DIGIT 0.25 Envelope-from freemail username ends in digit FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] zfs root after last update grub unknown filesystem X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2020 10:10:11 -0000 I was not aware of that tool as I'm not using UEFI boot mode at the moment. It looks like UEFI mode is the way to go from now on for root on zfs setups... Thanks, G. On Mon, 14 Sep 2020 at 10:34, Aaron Lauterer wrote= : > > > On 9/14/20 11:29 AM, Gianni Milo wrote: > > UEFI boot mode is indeed a good option, as it does not rely on the ZFS > pool > > for booting the system (it uses a separate VFAT partition for the > > bootloader). > > However, this method does not solve another problem which is the > redundancy > > of the bootloader, as the UEFI partition can be installed only on a > single > > (boot) drive. If that drive fails, then one must rebuild the UEFI > partition > > on a different or on the replacement drive. > > Have you read the documentation [0]? Especially chapter 3.11.4? > > We added and the pve-efiboot-tool and hooked it into the update-initramfs > to keep the EFI partition up to date on each disk used for the root pool = so > that if one disk fails, you can still boot from one of the remaining ones= . > The documentation on how to replace a failed boot drive takes into accoun= t > on how to get the bootloader set up as well. > > [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot > > > > > On Mon, 14 Sep 2020 at 09:14, Arjen via pve-user < > pve-user@lists.proxmox.com> > > wrote: > > > >> > >> > >> > >> ---------- Forwarded message ---------- > >> From: Arjen > >> To: Proxmox VE user list > >> Cc: > >> Bcc: > >> Date: Mon, 14 Sep 2020 08:04:03 +0000 > >> Subject: Re: [PVE-User] zfs root after last update grub unknown > filesystem > >> =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Origin= al Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 > >> On Monday, September 14, 2020 9:07 AM, Aaron Lauterer < > >> a.lauterer@proxmox.com> wrote: > >> > >>> Alternatively you can try to install the machine in UEFI mode. In UEF= I > >> mode with root ZFS the installer will set up systemd-boot instead of > grub. > >> This alleviates the problem with grubs limited ZFS compatibility. > >>> > >>> See the docs for more infos: > >> https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot > >>> > >>> HTH, > >>> Aaron > >> > >> I had the same problem with a zpool feature that could not be turned > off. > >> I used this work-around for a while in the hope that the bug would be > fixed > >> (GRUB patch existed for 5 years but it was never tested/reviewed): > >> Put a new Proxmox VE installation on USB and copy /boot from the hard > >> drives to the USB installation. > >> With that, it could boot from USB, after which it would pickup on the > >> rpool on the hard drives (probably by lucky chance). > >> Eventually, reinstalling with UEFI+GPT+ESP+systemd-boot (which did not > >> exists when I encountered the issue) fixed it. > >> > >> I would suggest taking the pain now, and reinstall using UEFI, to > prevent > >> such issues in the future. > >> > >>> On 9/14/20 12:16 AM, Gianni Milo wrote: > >>> > >>>> GRUB does not support all zfs features, so it's quite common for it = to > >> fail > >>>> to recognise the rpool during boot if it has a feature which is > >>>> incompatible with it. In your case, I believe that is the "encyption= " > >>>> feature. > >>>> Do you recall the issue starting after enabling encryption on > >> rpool/data > >>>> dataset? If so, you may have to rebuild the pool and leave rpool/dat= a > >>>> unencrypted. > >>>> Note that even though you enabled encryption only on rpool/data, the > >>>> feature will take effect at the pool level, hence the GRUB issue you > >>>> are facing. > >>>> Because of this issue, people have started using a separate boot poo= l > >>>> (bpool), with limited zfs features enabled and a different data pool > >>>> (rpool) for the OS and the data. I believe that the PVE installer > >> should be > >>>> modified to follow this approach (if it hasn't done it already) to > >> overcome > >>>> similar issues. > >>>> Gianni > >>>> On Sun, 13 Sep 2020 at 22:29, Stephan Leemburg > >> sleemburg@it-functions.nl > >>>> wrote: > >>>> > >>>>> Hi All, > >>>>> I have a proxmox system at netcup that was clean installed about tw= o > >>>>> weeks ago. > >>>>> It is full zfs, so root on zfs. I am migrating from one netcup syst= em > >>>>> with less storage to this system. > >>>>> This system is using the pve-no-subscription repository, but after > >>>>> migration I will move the subscription from the 'old' system to thi= s > >>>>> system. > >>>>> The rpool/data dataset is zfs encrypted. > >>>>> Today I did zfs send/recv from the 'old' system to this system to t= he > >>>>> rpool/data dataset. > >>>>> After that I did an apt update and noticed there where updates > >> available. > >>>>> After the upgrade and the mandatory reboot, the system does not com= e > >> up > >>>>> anymore. It is stuck in grub rescue. > >>>>> Grub mentions that it has a 'unknown filesystem'. > >>>>> Has anyone else experienced this same situation? > >>>>> If so and you could recover, what was the reason and fix? > >>>>> I am still researching what is causing this. If I boot a .iso then = I > >> can > >>>>> import the pool and see all datasets and subvolumes. > >>>>> So, it seems that the zpool itself and the datasets are ok, it is > >> just > >>>>> that grub is unable to recognize them for some reason. > >>>>> I have read about other situations like this where large_dnode > >> seemed to > >>>>> be the cause. I noticed that on the zpool large_dnode is enabled. > >> And it > >>>>> is a creation only setting. It cannot be changed to disabled > >> afterwards. > >>>>> This must have been done by the Proxmox installer. As booting is > >> about > >>>>> the root filesystem, I guess the zfs send / recv to the rpool/data > >>>>> dataset would have nothing to do with it, but I could be wrong. > >>>>> I will continue my research tomorrow evening after some other > >>>>> obligations, but if anyone has an idea, please share it. If it is > >> just > >>>>> how to get more debugging info out of the zfs module in grub. > >>>>> Because 'unknown filesystem', with the zfs module loaded is kind of > >> not > >>>>> helping enough.. > >>>>> Best regards, > >>>>> Stephan > >>>>> > >>>>> pve-user mailing list > >>>>> pve-user@lists.proxmox.com > >>>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >>>> > >>>> pve-user mailing list > >>>> pve-user@lists.proxmox.com > >>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >>> > >>> pve-user mailing list > >>> pve-user@lists.proxmox.com > >>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >> > >> > >> > >> > >> > >> > >> ---------- Forwarded message ---------- > >> From: Arjen via pve-user > >> To: Proxmox VE user list > >> Cc: Arjen > >> Bcc: > >> Date: Mon, 14 Sep 2020 08:04:03 +0000 > >> Subject: Re: [PVE-User] zfs root after last update grub unknown > filesystem > >> _______________________________________________ > >> pve-user mailing list > >> pve-user@lists.proxmox.com > >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >> > > _______________________________________________ > > pve-user mailing list > > pve-user@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >