Date: Sat, 07 Sep 2024 16:20:37 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Karl Vogel <vogelke@pobox.com> Cc: Ludovit Koren <ludovit.koren@gmail.com>, freebsd-questions@freebsd.org Subject: Re: ZFS boot devices specification Message-ID: <86h6ar1r62.fsf@ltc.des.dev> In-Reply-To: <ZtvYgD4RRUI349Q0@furbag.my.domain> (Karl Vogel's message of "Sat, 7 Sep 2024 00:37:20 -0400") References: <86y146zbef.fsf@gmail.com> <ZtqauS9lqXPBosBR@furbag.my.domain> <8634md11w4.fsf@gmail.com> <ZtvYgD4RRUI349Q0@furbag.my.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
Karl Vogel <vogelke@pobox.com> writes: > Ludovit Koren <ludovit.koren@gmail.com> writes: > > I already had in /boot/loader.conf. So these kernel variable > > settings do not solve the problem. > No, it's the "mountfrom=3D" line. You shouldn't need to specify `mountfrom` manually. The loader will check the `bootfs` property of all available pools, so just make sure your root pool has `bootfs` set correctly. But I don't think that's Ludovit's problem, anyway. It sounds like the kernel is somehow trying to mount the root filesystem before the disks are available (which shouldn't happen; the last thing the kernel does before mounting root is wait for all buses to settle), or maybe the pool can't be imported because it wasn't exported cleanly. We need more information, ideally a complete boot log. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86h6ar1r62.fsf>