From nobody Thu Nov 02 16:39:37 2023 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SLqNS2Bknz4yrRG for ; Thu, 2 Nov 2023 16:39:52 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SLqNR4n2Kz4s3y for ; Thu, 2 Nov 2023 16:39:51 +0000 (UTC) (envelope-from delphij@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-53e751aeb3cso1842479a12.2 for ; Thu, 02 Nov 2023 09:39:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698943190; x=1699547990; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fFBsHEoExvRlebM2CK7X398d1+w5bU5AjdGfmc//Tu4=; b=KqCF0RO0njk6pe4nZtNT8Y+3fHySYLviMWbLwjjzd7XHWFtHYlAOYfOAgyiumSjW8b kZVWbuADfApA+4NNYbX0fxVltX0ZMEEbeOXP4TB6X7itzN7E9RXlhR43qfT99O5/J6cA axtFP6xWborR15TYRiUKprWWJnl9Cqh7r/PmQ2+8khsnCxAVpf0mojJFbsVoetqmf1Ug Dqz3Yqx/ujO9p8PXVlmkRZ6vft9mNUmtFe5cOQZmnpZAjLMlSmT+88VkVQve4Tr9di4p 9q4ZBVGeAtzSMs5bAhY3NwnhheFxlmIuCJF9kNZGvk2KlROMD2P8xiEF+pjOGNCgkKxI ZpcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698943190; x=1699547990; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fFBsHEoExvRlebM2CK7X398d1+w5bU5AjdGfmc//Tu4=; b=wiKGmLaNq/UqTYuAWP7vqwA6ZOq0zb5YVBuFwS3InB4Q4PQNBdF/Y0CLP8/tylmcE8 0YQ4VqMyoCMitjHkvKRC6WetlgxC6J8Vb3mEPEabdCNTz2JZFb6Sk6VYNgzd8Eip3Sqf 64UcGcO6LGX6FXeiRsbVkBFV0Nty563vJVLVsXcBV6Kvdkpimq+Atd2thow7G4hpfPmF T6VVfGon54NKgDCTBYQSon9ahO/hkFlalwEoIc7n2R2x4A6PD8eETGUVdNfacPJqzWJj pHoS/qij4rJw/aTWuTVH+vV3yuBE6QmkZBNhYvWX2Ui1z41sPNkpfWFdULPt+xLOrDS1 q9hg== X-Gm-Message-State: AOJu0Yzx3HxrDqsiurfeAvGxL8H2ekQI77LTu1cvgyZBcnhaRANaf0gH O6OU8iARaY6ilooGNks3HerojtMUzrDceucB6bY= X-Google-Smtp-Source: AGHT+IHnktXYugNsMlEEpNqV3JxfSUskYx3ApTV5uhHQeJiX/byCQJ4+yOTdlq2zul0+dLWQnaVIYtEPHsgWZ5qKUtE= X-Received: by 2002:a50:9f83:0:b0:53e:bb41:7506 with SMTP id c3-20020a509f83000000b0053ebb417506mr3999648edf.33.1698943189358; Thu, 02 Nov 2023 09:39:49 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <0c19b8a6-119c-4f5d-af26-d625afc7afec@sentex.net> In-Reply-To: <0c19b8a6-119c-4f5d-af26-d625afc7afec@sentex.net> From: Xin LI Date: Thu, 2 Nov 2023 09:39:37 -0700 Message-ID: Subject: Re: RELENG_13 to 14 upgrade fail To: mike tancsa Cc: FreeBSD-STABLE Mailing List Content-Type: multipart/alternative; boundary="0000000000004b9cee06092e09a4" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4SLqNR4n2Kz4s3y --0000000000004b9cee06092e09a4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Nov 2, 2023 at 9:28=E2=80=AFAM mike tancsa wrote: > On one of my VMs that I upgraded from RELENG_13 to RELENG_14, I forgot > to update the boot loader so now at bootup, I have > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > > Can't find /boot/zfsloader > > What is the best way to recover from this ? Its a raw vm image. gpart is > p1=3Dfreebsd-boot, p2=3Dfreebsd-swap,p3=3Dfreebsd-zfs > > I was thinking perhaps start up a second vm thats RELENG_14, mdconfig > the image, and then what do I need to do ? Just > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 md0 ? > Yes, note that if the host is running FreeBSD you can mdconfig the image on the host directly and do it on the host too. BTW. pmbr is very simple and doesn't change that often, updating gptzfsboot should be sufficient. Cheers, --0000000000004b9cee06092e09a4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Nov 2, 2023 at 9:28=E2=80= =AFAM mike tancsa <mike@sentex.net> wrote:
On = one of my VMs that I upgraded from RELENG_13 to RELENG_14, I forgot
to update the boot loader so now at bootup, I have
ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2

Can't find /boot/zfsloader

What is the best way to recover from this ? Its a raw vm image. gpart is p1=3Dfreebsd-boot, p2=3Dfreebsd-swap,p3=3Dfreebsd-zfs

I was thinking perhaps start up a second vm thats RELENG_14, mdconfig
the image, and then what do I need to do ? Just

gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 md0 ?

--0000000000004b9cee06092e09a4--