Date: Tue, 28 Dec 2021 13:22:24 +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-JrSEE8UxFU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260628-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260628-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260628 Remco <freebsd@fam-vdberg.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@fam-vdberg.eu --- Comment #4 from Remco <freebsd@fam-vdberg.eu> --- I might have related, similar problems... I upgraded my FreeBSD VM from 12.2 to 12.3 by using freebsd-update. I think to remember it initially worked fine and survived the reboot after = the upgrade, but I'm not 100% sure. But a few weeks later after updating my packages it was stuck on boot with the last text visible on the console: "d= evd" ... Single user mode works, multi-user mode not. I gave up, as I couldn't fix it, and tried to install a complete new machine using FreeBSD 13.0-RELEASE ISO. But... it had the same issue !! Also stuck at "devd"=20 I figured out that using a traditional E1000 network adapter in VMWare (ESXi 5.5.0, yes rather old) I could install FreeBSD 13. But when using the VMXNE= T3 driver, it crashed. I went back to the other FreeBSD 12.3 server, changed the interface in VMwa= re in an E1000 (em0) interface, adjusted my rc.conf and ... voila... the whole machine worked again. ... if above is related, it might helping fixing the bug. Regards, Remco --=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-260628-227-JrSEE8UxFU>