Date: Tue, 2 Jul 2024 14:54:15 +0200 From: Jan Martin Mikkelsen <janm@transactionware.com> To: Rick Macklem <rick.macklem@gmail.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Booting in bhyve always sets currdev to ZFS Message-ID: <4988117B-1511-43DA-8B78-1BC007C037F2@transactionware.com> In-Reply-To: <CAM5tNy6rDBiV5j%2BnrAyHdnuLsPECs6JPvuUtk9svkBLEd7Wy-A@mail.gmail.com> References: <CAM5tNy6rDBiV5j%2BnrAyHdnuLsPECs6JPvuUtk9svkBLEd7Wy-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29. Jun 2024, at 03:26, Rick Macklem <rick.macklem@gmail.com> wrote: >=20 > Hi, >=20 > I've installed FreeBSD current in a bhvye instance. Everything > went ok, with UFS as a root partition. > Then I created a zpool in another partition... > - Now, every time I boot it I have to > OK set currdev=3Ddisk0s1a: > to get it to boot. >=20 > What is the trick to keep ZFS from messing up the boot variables? I remember having this problem a few years ago. I see I have in an old = startup file, =E2=80=98-e =E2=80=9Crootdev=3Ddisk0=E2=80=9D=E2=80=99 to = set a loader environment variable. I also recall needing different Bhyve = firmware, and I used gptboot. Some of these things might have been for = different reasons. Other details are fuzzy. Regards, Jan M.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4988117B-1511-43DA-8B78-1BC007C037F2>