From nobody Tue Nov 29 05:51:57 2022 X-Original-To: freebsd-fs@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 4NLs0z065Hz4hrW3 for ; Tue, 29 Nov 2022 05:52:03 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 4NLs0y0q8Zz3FRM for ; Tue, 29 Nov 2022 05:52:02 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=n02hTfzI; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=Oo0otWgA; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id DFD493200063 for ; Tue, 29 Nov 2022 00:52:00 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 29 Nov 2022 00:52:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :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=1669701120; x=1669787520; bh=h7tLD9J+LN 6cIpbXd7zoTrNExicGwaAzBDS0dUOZnvc=; b=n02hTfzIVoHlvn0o44vMtqP3o+ GVnHGVeAYVqzeT62IYAGHvf1dGCTuz9XXBemU+5b3Wl18oRp139pOo9noPRI4XwG oUMY9fymt7gdgLVGxm8DO50DWsfxIson0CxcvKrw0XOe5d3VMNy2oe8BB/6k/m3L FKt15V7gyJhUV88s+J9XunkzllynLY6u7Kqv73rJn0PxHNwEGGljUnah2HO0Ll8s b7R8b361vOE6xURrGecymL+jjONJrNSVay3DHbRx9HkjY7Wn5Ke7UT+PgufgCcPr Zo2cpC7WrA/rQvq7eMb0bk3i6/f29DKXHLSAe425FL//vsMA+tpJQGv5qkhQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1669701120; x=1669787520; bh=h7tLD9J+LN6cIpbXd7zoTrNExicG waAzBDS0dUOZnvc=; b=Oo0otWgAilnDq8BJ9EPxFTqGgJ47LL/b+/JQq1XDDhAB fHbUN2T4XWBnM/pIXQr3S8EW0ul8nNeE1vxj/HECq0PqewcwnR3Aa5RMpgkjpLdN 2jREHo75arOtuYKbBImUndGOBeecU0XQMBVguk+xNEcbkAUysXx6H4OR0fSDnkNK pdF0iyvIoYPp4VrsPIRsqU2XxHeAN6UPRz/MGdNIwf2Jv2ViCkl6uR9hjmYHWhVm 0qmwHkZ+2s6TFTv/3/BOKHLcz5/M2CAA0wM3gcGIVadY7kXevcfwArsgN1I63r16 WSb4cPF2ykeb6MDquzzfvcgtNYZpPeYXKCu66FEsrg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrjeefgdeltdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertd dttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrght thgvrhhnpeekleduvdelhfeileefgffghfffkedtheellefgudfgvdegkeejjedutdehhe fgueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehv ohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 29 Nov 2022 00:51:59 -0500 (EST) Date: Tue, 29 Nov 2022 05:51:57 +0000 From: void To: freebsd-fs@freebsd.org Subject: Re: odd problems with zfs when installing latest stable snapshot Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org References: List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-4.93 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.83)[-0.832]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20:c]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4NLs0y0q8Zz3FRM X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Tue, Nov 29, 2022 at 05:37:03AM +0000, void wrote: > >The second thing is that it wasn't directly bootable. I had to wait till it got >past the bios screen and then plug in the usb stick again, and then the >prompt for the geli password came up. So I'm guessing the bootcode isn't >present on the new install SSDs. The above is slightly incorrect. The usb stick subsequently plugged in to make it boot was 13.1-RELEASE. timestamps on the files are dated May 12 2022. So for clarity, a newly installed 13-stable system zfs on root would not boot unless a 13-RELEASE installer img was plugged in *after* the bios screen (which flickered a cursor then went blank until the usb stick was plugged in) --