Date: Tue, 04 Jul 2023 17:23:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 272365] sysutils/openzfs & sysutils/openzfs-kmod do not boot Message-ID: <bug-272365-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272365 Bug ID: 272365 Summary: sysutils/openzfs & sysutils/openzfs-kmod do not boot Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freqlabs@FreeBSD.org Reporter: michael.hmich@gmail.com Flags: maintainer-feedback?(freqlabs@FreeBSD.org) Assignee: freqlabs@FreeBSD.org since the kmod port does not compile I pulled from openzfs github which compiles well and works with stock zfs.ko, I think that is because the vers= ion number is newer=20 it does not really boot with openzfs_load=3DYES as instructed, the kernel is found and booted, but stops at mountroot trying to boot from zroot/ROOT/default, and stops then because there is no suitable filesystem, even if it just booted the kernel from zroot, in other words, we are on zro= ot but it says it can not find zroot ... if PATH is also corrected to give search preference to sbin, openzfs works = like expected, but that is far from being enough, also setting the path in earli= er relevant scripts, it does not work the problem at this point, at least for me, verbose_boot does not help and failing at mounting root there are no other options as typing a valid boot device=20 bectl is not a solution for this case, we're using just another kmod and th= at's all when you look into rc.d at zfs, zpool, zvol and zfsbe they have all the same limitation, they expect required_modules=3D"zfs", not openzfs at this point normally is endpoint, there's not so much to do but guessing I created openzfs scripts as openzfs, openzpool, openzfsbe including not on= ly the search path corrected but also added a fullpath prefix as DIR=3D"/usr/local/sbin" to be sure that the openzfs binaries will be used accordingly, each script is working correctly integrated with the others wh= en needed, adding openzfs_enable var to rc.conf, means I can easily switch bet= ween zfs and openzfs zfsd I've ignored so far, because I don't need it but, unfortunately it is still hanging at mounting root and I'm back at the beginning please don't ask why I want to use openzfs, then I must answer why it is th= ere? but seriously, I have some zpools running on linux and after last zfs upgra= de I answered without thinking yes to upgrade the pools, since then I have no ac= cess from Freebsd workstations any more because of two new feature=20=20 completing my box FreeBSD hm-fbsd 13.2-STABLE FreeBSD 13.2-STABLE #0 stable/13-a86b5f4f06-dir= ty: Mon Jul 3 18:13:27 -03 2023=20=20=20=20 root@hm-fbsd:/usr/obj/usr/src/amd64.amd64/sys/HMichZ amd64 hm@hm-fbsd:~ % which zfs /usr/local/sbin/zfs hm@hm-fbsd:~ % zfs -V zfs-2.2.99-1 zfs-kmod-2.1.12-FreeBSD_g86783d7d9 so now what can I do? I might not have enough knowledge of the little secrets,if somebody know, please tell me what to do the problem is not only openzfs ports, but pkg also, both give the same description and that is uncomplete if not wrong, but who knows I'm just bli= nd or too stupid :)=20 thanks in advance --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272365-7788>