SG-5100 hangs durring reboot.
-
Do you have any USB devices attached to it?
We have seen one other case where here was a USB device that prevented it rebooting. -
The only usb devices that are connected would be the UPS (never had an issue with it before) and the mini-usb for console. I have tried with the the UPS instead unplugged.
Does the sata m.2 port use pcie or usb to connect?
-
It uses SATA. It's not a PCIe or USB device.
Try booting verbose to see if you get any more info. At the boot loader menu hit esc to reach the prompt then enter
boot -v
.Steve
-
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2023.02.22 17:53:44 =~=~=~=~=~=~=~=~=~=~=~= Netgate pfSense Plus will reboot. This may take a few minutes, depending on your hardware. Do you want to proceed? Y/y: Reboot normally R/r: Reroot (Stop processes, remount disks, re-run startup sequence) S: Reboot into Single User Mode (requires console access!) Enter: Abort Enter an option: y Netgate pfSense Plus is rebooting now. Stopping package nut...done. Stopping package suricata...done. Stopping package Avahi...done. Stopping package squid3...done. Stopping package Telegraf...done. Stopping /usr/local/etc/rc.d/haproxy.sh...done. Stopping /usr/local/etc/rc.d/pfb_dnsbl.sh...done. Stopping /usr/local/etc/rc.d/pfb_filter.sh...done. Stopping /usr/local/etc/rc.d/shutdown.nut.sh...done. Stopping /usr/local/etc/rc.d/sqp_monitor.sh...done. Stopping /usr/local/etc/rc.d/vnstatd.sh...done. pflog0: promiscuous mode disabled ovpns1: link state changed to DOWN Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining... 0 0 0 0 0 done All buffers synced. Swap device ada0p2 removed. Uptime: 3m56s (ada0:ahcich0:0:0:0): spin-down Khelp module "ertt" can't unload until its refcount drops from 37 to 0. ix1: Link is Down ix1: link state changed to DOWN ix0: Link is Down ix0: link state changed to DOWN lagg0: link state changed to DOWN lagg0.50: link state changed to DOWN lagg0.2: link state changed to DOWN lagg0.70: link state changed to DOWN lagg0.101: link state changed to DOWN lagg0.20: link state changed to DOWN lagg0.201: link state changed to DOWN lagg0.301: link state changed to DOWN uhub0: detached unknown: wake_prep disabled wake for \_SB_.PCI0.PEX0 (S5) unknown: wake_prep disabled wake for \_SB_.PCI0.PEX1 (S5) unknown: wake_prep disabled wake for \_SB_.PCI0.PEX2 (S5) unknown: wake_prep disabled wake for \_SB_.PCI0.PEX3 (S5) pcib2: wake_prep disabled wake for \_SB_.PCI0.PEX4 (S5) pcib3: wake_prep disabled wake for \_SB_.PCI0.PEX5 (S5) pcib4: wake_prep disabled wake for \_SB_.PCI0.PEX6 (S5) pcib5: wake_prep disabled wake for \_SB_.PCI0.PEX7 (S5) xhci0: wake_prep disabled wake for \_SB_.PCI0.XHC1 (S5) ix0: wake_prep disabled wake for \_SB_.PCI0.VRP0.LAN0 (S5) ix1: wake_prep disabled wake for \_SB_.PCI0.VRP0.LAN1 (S5) ix2: wake_prep disabled wake for \_SB_.PCI0.VRP1.LAN2 (S5) ix3: wake_prep disabled wake for \_SB_.PCI0.VRP1.LAN3 (S5)
It looks like its not related to the uhub0 as I originally though. I let it sit at this point for about 10 minutes
Pressing ctrl-t did nothing as well. -
Hmm, that looks like it might be Wake-on-LAN related.
Have you configured anything differently in the BIOS?
-
I have not, in fact I had never been in the bios until I was trying to troubleshoot this. I don’t think I changed anything but I can set it back to defaults and ensure WoL is disabled.
-
Seems unrelated in fact. My test 5100 also shows that in verbose mode but reboots as expected.
Hard to imagine it could be anything but a BIOS setting or actual hardware at that point.
-
When I have time for a longer downtime I’ll get the latest factory image, reset the bios and reflash the os. Maybe even get a new boot disk. I vaguely remember this one being a cheaper one I got for a project that fell through and got tossed in a drawer.
-
It's a possibility but it's hard to see what might have changed in 23.01 that could cause it.
The 5100 can be installed UEFI or legacy (BIOS). Try running:
sysctl machdep.bootmethod
to find out. My test box is currently BIOS.Steve
-
Mine is currently in BIOS mode as well. However I’m not sure it’s related to 23.01.
-
Ah, you think it may have also been hanging there in 22.05?
-
It was. I’m trying to remember when the last time I actually had to reboot was. I feel the rolling blackouts in December were fine but those also caused full power loss. But I vaguely remember having to pull the power for a reboot before then.
It started after replacing the drive but not immediately.
But it was most noticeable when I tried to install the 23.01 rc. Since it hung rebooting while still in 22.05.
After performing a nfs snapshot restore to 22.05 I had the same issue rebooting.
-
Ah, OK. That does start to seem like it might be the drive then.
I have experienced pretty much the same thing with a rogue drive in an MBT-4220. Not seen it in a 5100 but it could be possible.
-
Do you have any drives you would suggest or recommend?
-
I have the drive we fitted to various devices which unhelpfully shown as 'NT-32'.
There are a few threads here with other users reporting the drives they used in 5100s. I don't really have anything I can recommend personally.