From nobody Thu Jun 8 16:28:14 2023 X-Original-To: freebsd-current@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 4QcV4y68kfz4bxln for ; Thu, 8 Jun 2023 16:28:18 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QcV4y34h5z3Dws for ; Thu, 8 Jun 2023 16:28:18 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm1 header.b=wRli7BvT; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="J INtNZ+"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.19 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 03709320096B for ; Thu, 8 Jun 2023 12:28:16 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 08 Jun 2023 12:28:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1686241696; x=1686328096; bh=UFdbI9e3xbnJ/nz23SzjKIJ87cdC/CTyDej RoXYrnAk=; b=wRli7BvTA2JfYlfUcd10lI5MnivLlatCTJHgZJbQbHxtW9Mbxj5 menh08oF1x+XiAuPs8aneHVhDNtNW09HPMnsODGWCVQ55p1gJyxNxUvFS7oIEO6d NVMjWAyJhG2LlmnCl/Vwj20aBxWkQE0jJf85etypT5s28jtIQkorIgsnf1hJ4Yuq pBjxrdJIItgCFKI2hhDD5fzlRHMHHjF9pvbOlJ9MVrOF/740U+TaxgBtATZuXkaG 0VIrhA3Oz4Jkw2IprOf0Vm+xrTSh9e3gC7R30sfnPtOHgDB5Bj6P+LEGX+F6SRRk cwwvYJOVT9fiKZ9DtDNFTJVi8nmWIn2/ESA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1686241696; x= 1686328096; bh=UFdbI9e3xbnJ/nz23SzjKIJ87cdC/CTyDejRoXYrnAk=; b=J INtNZ+O9LCV2t5X529F9zcc734P2JeDsRTNH2vIEq/PgZkxkaMw3O7MSGOpzLTRI JaBoOeisaMg9B8ZlNHitJ+7itbE9UW0NogjXlyoymoQ89eDMUuVcrxpcXjEsvPj3 OKbEyotUoCY2NyiClrF+RoGWY80DsfwnTmEfhle5u5F5pyelfHkjnelpnrsfHffo J+s/uf/toBNUNWuQgdxaC4ufIzbbtW8mUlKCCdFRmMcWy6xtDa4EghAk1KfD+A13 jdKDb9OoxHicQK5wvdsW6Pl6XSj6cmfoTvZUt6u5YHVLd9QrWh54Wz9niO15XtAV f+RlhqHvIIdrsExSQqGKw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedtiedguddtudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ejredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhepvedvgeeltdevkeduhfejgeegffetheeujeelhfekgeffte ehveevjeefhffgffdtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhephihurhhisegrvghtvghrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 8 Jun 2023 12:28:15 -0400 (EDT) Message-ID: <46816dca-c4a9-6e12-6057-f7fcd642eafd@aetern.org> Date: Thu, 8 Jun 2023 18:28:14 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.2 Subject: Re: CURRRENT snapshot won't boot due missing ZFS feature Content-Language: en-US To: freebsd-current@freebsd.org References: <20230608181115.7c97ea19.grembo@freebsd.org> From: Yuri In-Reply-To: <20230608181115.7c97ea19.grembo@freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QcV4y34h5z3Dws X-Spamd-Bar: / X-Spamd-Result: default: False [-0.40 / 15.00]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-ThisMailContainsUnwantedMimeParts: N Michael Gmelin wrote: > Hi, > > I didn't dig into this yet. > > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I > get this on boot: > > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > > (booting stops at this point) > > Seems like the boot loader is missing this recently added feature. Are you sure it was June 1's? I saw this problem on: FreeBSD-14.0-CURRENT-amd64-20230427-60167184abd5-262599-disc1.iso ...but it was fixed since (for me, at least): FreeBSD-14.0-CURRENT-amd64-20230504-4194bbb34c60-262746-disc1.iso