Date: Mon, 27 Dec 2021 22:02:13 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260628] FreeBSD 12.3-Release got stuck during the boot process after the update (maybe nsswitch issue?) Message-ID: <bug-260628-227-nx3gszPyyQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260628-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260628 --- Comment #2 from Yoshisato Yanagisawa <osho@pcc-software.org> --- > Which patch level? I hope you are asking patch level of 12.2R, then: # uname -v FreeBSD 12.2-RELEASE-p7 GENERIC # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 12.2-RELEASE from update2.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 12.2-RELEASE-p11. I am not sure why uname and freebsd-update show different values. Also, I use ZFS during the boot, and the root file system is also ZFS. # cat /boot/loader.conf kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" opensolaris_load="YES" zfs_load="YES" # grep zfs /etc/rc.conf zfs_enable="YES" Is there any special procedure I should do for updating such environment? As far as I understand from https://docs.freebsd.org/en/books/handbook/cutting-edge/#updating-upgrading-freebsdupdate, I should call nextboot only if I use a custom kernel, which I do not. I usually postpone `zfs upgrade` until I confirm the new version is stable enough because I do not know how to "downgrade" ZFS safely. Note that I assume there is no ZFS update between 12.2R and 12.3R. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260628-227-nx3gszPyyQ>
