Discussion:
Boot freezing after kernel load - root on zfs
(too old to reply)
Ben Woods
2018-06-23 02:13:31 UTC
Permalink
Hi everyone,

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
***@gmail.com
Allan Jude
2018-06-23 04:08:03 UTC
Permalink
Post by Ben Woods
Hi everyone,
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
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
If you just press shift a bunch of times, does it print the Mount root prompt?
--
Allan Jude
Ben Woods
2018-06-23 04:22:59 UTC
Permalink
Post by Allan Jude
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
***@gmail.com
Warner Losh
2018-06-23 04:37:23 UTC
Permalink
There were some issues with legacy geely booting recently. What version?
UEFI or legacy BIOS booting?

Warner
Post by Ben Woods
Post by Allan Jude
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
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
Allan Jude
2018-06-23 14:40:31 UTC
Permalink
Post by Warner Losh
There were some issues with legacy geely booting recently. What version?
UEFI or legacy BIOS booting?
Warner 
Post by Allan Jude
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
_______________________________________________
mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
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
2018-06-23 14:56:07 UTC
Permalink
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.
Post by Allan Jude
Post by Warner Losh
There were some issues with legacy geely booting recently. What version?
UEFI or legacy BIOS booting?
Warner
Post by Allan Jude
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
_______________________________________________
mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
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
Ben Woods
2018-06-23 17:13:29 UTC
Permalink
Post by Joe Maloney
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
***@gmail.com

Ben Woods
2018-06-23 17:10:27 UTC
Permalink
Post by Warner Losh
There were some issues with legacy geely booting recently. What version?
UEFI or legacy BIOS booting?
Warner
Hi Warner,

This was occurring with both my old and new beadm boot environments -
r330554 and r334554.

I am booting with legacy BIOS.

Regards,
Ben

--
From: Benjamin Woods
***@gmail.com
Loading...