From nobody Mon Jan 01 04:27:41 2024 X-Original-To: questions@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 4T3NJJ0P8Tz55s9y for ; Mon, 1 Jan 2024 04:28:00 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 4T3NJH2Jn0z3Lr4 for ; Mon, 1 Jan 2024 04:27:59 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-io1-xd31.google.com with SMTP id ca18e2360f4ac-7bb87ff6144so47375139f.2 for ; Sun, 31 Dec 2023 20:27:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704083278; x=1704688078; 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=PMvKsz5a6gsDk4erQj8sqwIZPjzvc36NgIPG2L5+iBo=; b=Oq3N+LB941xZQ/Xr9mgVCN1G1ZDCne41oGteHp2IqL4NRVbzQd3YVh1/1bdfXvsMH8 N1sheCMH6xzLMJKE+0Ge5ijXYaZ6ndwRiXkYeTjddt72GuYcmX/pvhhjK8v/cBQzN/SW /sYke59Cu2fsw1MlNPflaCieuuQgPKsd1nsg9A2IK4NMg9MrcMMMJiycmFQbh1+Gevaj sdcaTiHLyn0wo2ZsAQ1Ln+SmGpuMin9P0cPfTSH6WBXivYncFoFsvoBGEDw23Foy6gFx wpSB1Yeo+yLbLR3TE8iUcnbB2ZEHT7HFKwUst/LyjD0CB5g0Kd57leJVbpmoy4S7l48B mnIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704083278; x=1704688078; 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=PMvKsz5a6gsDk4erQj8sqwIZPjzvc36NgIPG2L5+iBo=; b=oe46O5pKIjSMF1kIZDTKL3evWnoPhwUxKM7fBSyPdkFsf0AqF7KYfEcLDQ9/bN/eU6 cHoc8rxY6ipPcCZ9/D9g5Wvi90ZSNDDY4yCXhTqjXgrpYPn+EBge3qhgkexVDN7PEhml D5euaaJEHWyjfV4u5gBSdnXfY1ROg8SMbbMEVuNcSKVp5ROVloslVqmhKXhYWykjpTtT IkJbeJGzeUPYw8BQ4Jrp/rXckBP2phNHgo4SzgmkVOJ+uH2U4U43oFyY1ajWgRlfp/oP D92qGb0IJyUdO7dCmZWi9AzSk/ScylMrSkP7RFmW4Vjj45PuQWfNrRFtT1QjI5DBrxnK DdFw== X-Gm-Message-State: AOJu0YxFDxMvClJHESSyCDH7BRSjaxQd9kppx05ywM6QhMzYrs3LvODF xlXAuDgHJzxP6BZyfvunbMWACuo4sBgmxaEZTBdZeuGg X-Google-Smtp-Source: AGHT+IG55RULChXH3BmEgz5IsEVyJ6VUmKnCjlmOmBkQowyire+FY5zwvWJdDDiWXydmDus27lZyFPpY1FxEhDp4CsY= X-Received: by 2002:a92:cda6:0:b0:35f:f007:e904 with SMTP id g6-20020a92cda6000000b0035ff007e904mr13667170ild.50.1704083277958; Sun, 31 Dec 2023 20:27:57 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: <65aac66f-0d06-4668-9632-9a6701047a84@holgerdanske.com> In-Reply-To: <65aac66f-0d06-4668-9632-9a6701047a84@holgerdanske.com> From: Kevin Oberman Date: Sun, 31 Dec 2023 20:27:41 -0800 Message-ID: Subject: Re: VirtualBox 7.0, FreeBSD 12.4-RELEASE-amd64, ZFS, and bootpool To: David Christensen Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="0000000000007353ba060ddacec4" 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:2607:f8b0::/32, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4T3NJH2Jn0z3Lr4 --0000000000007353ba060ddacec4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Dec 31, 2023 at 3:11=E2=80=AFPM David Christensen wrote: > On 12/31/23 00:34, Alexander Burke wrote: > > Dec 31, 2023 04:36:42 David Christensen wrote: > >> freebsd-questions: > >> > >> If I use VirtualBox 7.0 (on Debian 11.8 amd64) to create a > FreeBSD-12.4-RELEASE-amd64 virtual machine with BIOS (MBR), ZFS boot, > encrypted swap, and encrypted ZFS root, the boot pool is not imported > automatically when the system boots: > >> > >> root@geneweb:~ # freebsd-version ; uname -a > >> 12.4-RELEASE-p9 > >> FreeBSD geneweb 12.4-RELEASE-p9 FreeBSD 12.4-RELEASE-p9 GENERIC amd64 > >> > >> root@geneweb:~ # zpool import > >> pool: bootpool > >> id: 16038363864467226171 > >> state: ONLINE > >> action: The pool can be imported using its name or numeric > identifier. > >> config: > >> > >> bootpool ONLINE > >> ada0s1a ONLINE > >> > >> > >> Why? > >> > >> > >> I have seen the defect since FreeBSD-12.1-RELEASE-amd64. I do not kno= w > if it was present earlier. > >> > >> > >> How do I arrange for bootpool to be imported automatically at boot? > > > > FreeBSD 11 is deprecated and out of support. Have you tried with a > > newer version? Quite a few changes to ZFS have happened since then, > > including the switch to OpenZFS. > > > Regarding FreeBSD versions, please re-read my post (above). > > > Regarding FreeBSD ZFS changes, I am reminded of the recent OpenZFS data > destruction bug. And, I recall issues when I evaluated FreeBSD 13/ > OpenZFS in the past. I am not inclined to trust my data to OpenZFS > unless and until I see improvements in their processes, validation of > their processes and code by reputable entities, and no defects > discovered for "long enough". This means FreeBSD 13 is not an option > for me at this time. > > > But the major problem is that FreeBSD EoL'd 12.4R today: > > https://www.freebsd.org/security/#sup > > > I am screwed. > > > I think the 12.xR line should have continued until OpenZFS is proven and > until the FreeBSD 12->13 upgrade boot loader OpenZFS bug is fixed. > It's not like zfs is mandatory. I run FreeBSD 15-CURRENT on my system with UFS and no boot issues. No requirement for ZFS. The installer gives you the option of either file system. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --0000000000007353ba060ddacec4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Dec 31, 2023 at 3:11=E2= =80=AFPM David Christensen <dpchrist@holgerdanske.com> wrote:
On 12/31/23 00:34, A= lexander Burke wrote:
> Dec 31, 2023 04:36:42 David Christensen wrote:
>> freebsd-questions:
>>
>> If I use VirtualBox 7.0 (on Debian 11.8 amd64) to create a FreeBSD= -12.4-RELEASE-amd64 virtual machine with BIOS (MBR), ZFS boot, encrypted sw= ap, and encrypted ZFS root, the boot pool is not imported automatically whe= n the system boots:
>>
>> root@geneweb:~ # freebsd-version ; uname -a
>> 12.4-RELEASE-p9
>> FreeBSD geneweb 12.4-RELEASE-p9 FreeBSD 12.4-RELEASE-p9 GENERIC=C2= =A0 amd64
>>
>> root@geneweb:~ # zpool import
>>=C2=A0 =C2=A0=C2=A0=C2=A0 pool: bootpool
>>=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 id: 16038363864467226171
>>=C2=A0 =C2=A0=C2=A0 state: ONLINE
>>=C2=A0 =C2=A0 action: The pool can be imported using its name or nu= meric identifier.
>>=C2=A0 =C2=A0 config:
>>
>>=C2=A0 =C2=A0=C2=A0=C2=A0 bootpool=C2=A0=C2=A0=C2=A0 ONLINE
>>=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ada0s1a=C2=A0=C2=A0 ONLINE >>
>>
>> Why?
>>
>>
>> I have seen the defect since FreeBSD-12.1-RELEASE-amd64.=C2=A0 I d= o not know if it was present earlier.
>>
>>
>> How do I arrange for bootpool to be imported automatically at boot= ?


=C2=A0> FreeBSD 11 is deprecated and out of support. Have you tried with= a
=C2=A0> newer version? Quite a few changes to ZFS have happened since th= en,
=C2=A0> including the switch to OpenZFS.


Regarding FreeBSD versions, please re-read my post (above).


Regarding FreeBSD ZFS changes, I am reminded of the recent OpenZFS data destruction bug.=C2=A0 And, I recall issues when I evaluated FreeBSD 13/ OpenZFS in the past.=C2=A0 I am not inclined to trust my data to OpenZFS unless and until I see improvements in their processes, validation of
their processes and code by reputable entities, and no defects
discovered for "long enough".=C2=A0 This means FreeBSD 13 is not = an option
for me at this time.


But the major problem is that FreeBSD EoL'd 12.4R today:

=C2=A0 =C2=A0 =C2=A0https://www.freebsd.org/security/#sup=


I am screwed.


I think the 12.xR line should have continued until OpenZFS is proven and until the FreeBSD 12->13 upgrade boot loader OpenZFS bug is fixed.

It's not like zfs is mandatory. I r= un FreeBSD 15-CURRENT on my system with UFS and no boot issues. No requirem= ent for ZFS. The installer gives you the option of either file system.
<= /div>
--
<= /div>
Kevin Oberman, Part= time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--0000000000007353ba060ddacec4--