OPNsense Forum

Archive => 22.7 Legacy Series => Topic started by: agster27 on January 07, 2023, 07:45:17 pm

Title: OPNSense Halted and will not reboot. Help!
Post by: agster27 on January 07, 2023, 07:45:17 pm
OPNSense Version: 22.7 ( whatever the latest is )
Hardware: Protectli Vault 6 port

I did a search and not much came up.

OPNSense just stopped working literally. I was using ZenAmour to unblock a site and OPNSense halted.

When I plugged a monitor in to reboot I got the below. I do not where to start, except a fresh install.
When it reboots it gets to same spot and just turns off.

Any assistance would be wonderful

Last message when booting:

Code: [Select]
823.605958 [ 850] iflib_netmap_config  txr 4 rwr 4 txd 1024 rxd 1024 rbufsz 2048
823.880332 [ 850] iflib_netmap_config  txr 4 rwr 4 txd 1024 rxd 1024 rbufsz 2048
igb1: link state changed to DOWN

Screenshot attached.

** Update 1 ***
I tried to boot and set kern.vty=sc. IT doesn't get far just hangs.

Title: Re: OPNSense Halted and will not reboot. Help!
Post by: newsense on January 09, 2023, 03:55:23 am
The /dev/md43 and superblock entries at the bottom might be related to some data corruption, and in any case they're highly unusual for that moment in the boot up process.

I'd simply reinstall and restore the config or now.
Title: Re: OPNSense Halted and will not reboot. Help!
Post by: kpiq on April 08, 2023, 01:43:51 pm
My situation is similar, but it happens on a network appliance without video board.  Installation over serial port was performed.  The goal was to use a backup to restore the system to its previous state after a system crash.

The following unexpected situation resulted after restoring "ALL" sections from a OPNsense backup.  It seems to be affecting versions 21.7 thru 23.1.

After restore, the '<serialusb>1</serialusb>' line item was inserted into /conf/config.xml.   This was causing the system to look like it was hung after booting up, right before showing the login: prompt.  The system was still responding to ping, so it wasn't really hung, but was unresponsive and console access was lost.

Removing the '<serialusb>1</serialusb>' line from /conf/config.xml fixed the trouble.  Console access was regained, problem fixed.