Boot freezing after kernel load - root on zfs
Ben Woods
After shutting down to connect a new IP KVM switch (VGA and USB), my
FreeNAS mini hardware is no longer booting FreeBSD with root in zfs (no
encryption) - it is getting stuck after the kernel finishes loading and it
tries to mount root and start_init. It just stops printing any more output
to the screen, but I know the keyboard is working as ctrl+alt+delete works.
I wonder if this could be due to hard drives names being re-ordered (e.g.
what was ada0 is now ada1). I have 2 SATA3 SSDs in a zfs mirror for root
(showing as ada4 and ada5 during boot), and 4 SATA3 HDDs in a raidz2 with
geli for further storage (showing as ada0-3, but these are only mounted
during rc init - after the point the boot process is getting stuck). I have
no USB storage, although the IP KVM may present a virtual disk for loading
media remotely.
I am running 12-CURRENT, but know the recent upgrade is not the issue
because I can’t load from the previous boot environment either.
Is anyone able to recommend a fix or a way to troubleshoot further? Please
see below a link with screenshots at the end of the boot where it gets
stuck.
https://imgur.com/gallery/vhn7ScC
Thanks in advance for any help!
Regards,
Ben
--
From: Benjamin Woods
wood...@gmail.com
_______________________________________________
freebsd...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Allan Jude
If you just press shift a bunch of times, does it print the Mount root prompt?
--
Allan Jude
Ben Woods
> If you just press shift a bunch of times, does it print the Mount root
> prompt?
> --
> Allan Jude
>
coming!
I have tried booting with the KVM monitor and USB disconnected, with the
same result.
It is also worth noting I can successfully boot from a USB stick running
the latest 12-current snapshot
FreeBSD-12.0-CURRENT-amd64-20180618-r335317-memstick.img. From there I can
import both of my zpools (zroot and zstore), and then export them again
before rebooting - still can't boot from disk.
Warner Losh
UEFI or legacy BIOS booting?
Warner
Allan Jude
> There were some issues with legacy geely booting recently. What version?
> UEFI or legacy BIOS booting?
>
> Warner
>
> On Fri, Jun 22, 2018, 10:26 PM Ben Woods <wood...@gmail.com
> <mailto:wood...@gmail.com>> wrote:
>
> On 23 June 2018 at 12:08, Allan Jude <alla...@freebsd.org
>
> > If you just press shift a bunch of times, does it print the Mount root
> > prompt?
> > --
> > Allan Jude
> >
>
>
> No, unfortunately not. But please keep any troubleshooting suggestions
> coming!
>
> I have tried booting with the KVM monitor and USB disconnected, with the
> same result.
>
> It is also worth noting I can successfully boot from a USB stick running
> the latest 12-current snapshot
> FreeBSD-12.0-CURRENT-amd64-20180618-r335317-memstick.img. From there
> I can
> import both of my zpools (zroot and zstore), and then export them again
> before rebooting - still can't boot from disk.
>
> --
> From: Benjamin Woods
> _______________________________________________
> freebsd...@freebsd.org <mailto:freebsd...@freebsd.org>
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-curre...@freebsd.org
>
Warner: it is not that in this case, the screenshots show it getting
just past mountroot, so it is well into the kernel when it is stopping.
--
Allan Jude
Joe Maloney
do you by chance have multicons enabled with comconsole, vidconsole? This looks exactly like a race we encountered where the remaining output was actually being redirected to serial on some systems when multicons was being used. It appeared to be a lockup when it wasn’t because keyboard input would also break.
_______________________________________________
Ben Woods
> There were some issues with legacy geely booting recently. What version?
> UEFI or legacy BIOS booting?
>
> Warner
>
This was occurring with both my old and new beadm boot environments -
r330554 and r334554.
I am booting with legacy BIOS.
Regards,
Ben
Ben Woods
> Ben,
> do you by chance have multicons enabled with comconsole, vidconsole? This
> looks exactly like a race we encountered where the remaining output was
> actually being redirected to serial on some systems when multicons was
> being used. It appeared to be a lockup when it wasn’t because keyboard
> input would also break.
>
Hi Joe,
Indeed, you are right - I have now fixed the problem! Thanks very much for
your help!
I was previously using a serial console to boot the machine, whereas now I
have an IP KVM.
The lines I commented out in my /boot/loader.conf to fix this were:
boot_multicons="YES"
boot_serial="YES"
comconsole_speed="115200"
console="comconsole,vidconsole"
I would have thought that the boot should still complete regardless of
whether the serial console is connected or not?
Regards,
Ben
--
From: Benjamin Woods
wood...@gmail.com