Date: Sat, 22 Aug 2020 23:39:45 +0000 From: marco <freebsd-current@lordsith.net> To: freebsd-current@freebsd.org Subject: Re: 13-CURRENT won't boot after switch to sysutils/openzfs Message-ID: <20200822233945.GA2522@freedom.nl> In-Reply-To: <20200822221014.GA1744@freedom.nl> References: <20200822114934.GB40844@lordsith.net> <bae620a6-1538-289c-8c14-b855d6cebca0@FreeBSD.org> <a2dd2f76-e726-b3e8-bc23-933be5eff3e5@FreeBSD.org> <20200822162743.GA64297@freedom.nl> <a97df6a8-1796-8978-f630-802589a897dc@FreeBSD.org> <20200822164848.GA71156@freedom.nl> <20200822221014.GA1744@freedom.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 22, 2020 at 10:10:14PM +0000, you (marco) sent the following to= [freebsd-current] : > On Sat, Aug 22, 2020 at 04:48:48PM +0000, you (marco) sent the following = to [freebsd-current] : > > On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent the f= ollowing to [freebsd-current] : > > > > > So besides not being able to boot= from the openzfs 2020080800 package install, I can't figure out why I can'= t upgrade the openzfs pkg to 2020081800 (which is the latest one in ports s= o I presume a package also exists of that same version) > >=20 > > If that won't work either I'll see if I can build sysutils/openzfs from= ports but I'd rather not mix packages and ports. >=20 > building and installing the GENERIC kernel did not do anything. > I can confirm BE r364030-OpenZFS booted with GENERIC but I got dropped > into the mountroot prompt again. > Before I got there I saw: >=20 > Trying to mount root from zfs:zroot/ROOT/r364030-OpenZFS failed with > error 2: unknown file system. >=20 > Guess I'll try to install sysutils/openzfs from ports next. Not happy with having to install the port but that worked. I removed openzfs and openzfs-kmod via pkg remove. Then did a 'make install clean' from sysutils/openzfs (2020081800) with r3= 64030 BE active. Once I confirmed the port installed a newer /boot/modules/openzfs.ko I destroyed r364030-OpenZFS and created it again so it would be in sync with r364030 and it would have the latest openzfs.ko. When I imported my backup pool (single drive, 1 vdev) /etc/zfs/zpool.cache was automatically created. So now I have 2 zpool cache files [~] ls -l /boot/zfs/zpool.cache /etc/zfs/zpool.cache -rw-r--r-- 1 root wheel 1456 Aug 22 22:04 /boot/zfs/zpool.cache -rw-r--r-- 1 root wheel 3088 Aug 22 22:54 /etc/zfs/zpool.cache [~] zpool get cachefile zroot backup NAME PROPERTY VALUE SOURCE backup cachefile - default zroot cachefile - default So the port does work even with running the GENERIC-NODEBUG kernel. Is it even possible to build a port only into a new BE and not the current one given how /usr is not mounted? Now I had to polute the active BE which could get me into trouble. I was hoping using BEs I could experiment by installing a port straight int= o the mounted BE. If that is possible I wouldn't mind getting some pointers on how to make th= at work. --=20 Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EAREKAB0WIQSgJdiqrBvS/DgNT8GOoAuohYDmywUCX0GsvgAKCRCOoAuohYDm y4WzAJwOCdiSWEDgywQ3OJo1YxWUN6CzLQCfTHqubd2hDoemyyEBh92swhKoZRM= =KpED -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200822233945.GA2522>