Unable to reboot 2.4

[pfBasic]

Try giving it about 25 minutes to boot up.

The problem could be an issue connecting to the internet to reinstall your packages after a system upgrade. This is a known issue in some configurations (I don't remember specifically what). If this is the case it will eventually boot back up for you then you'll have to reinstall packages via the GUI.

What are you using for DNS and how is it configured?

[psulions5]

This happens during a normal reboot also - without actually installing anything.

My DNS is pulling from my ISP for my WAN, and 2 OpenVPN connections are static DNS for Private Internet Access.  The lockup happens during JUST the shutdown process, and not a clean boot.  A clean boot takes literally 15 seconds or so to complete, and completes perfectly every time.

[pfBasic]

Is there anything in the system logs at the time of shutdown?

Did anything change when this started happening?

[psulions5]

Logs didnt show much.  This was a fresh install of the latest snapshot for 2.4.  I run the same snapshot in a hyper-v container, and it has no issues rebooting.

So strange.

[psulions5]

Specs are:

7700K
Asrock H270M ITX
8GB Ram
Intel Pro/1000 4 port NIC.

Forgot to post them.

[pfBasic]

IDK then , maybe something got corrupted? I'd just do a fresh install then restore config.

If you aren't already maybe give a ZFS install a shot, it is generally less prone to corruption.

[psulions5]

I will try that tonight, thank you!

Someone on Reddit says he experiences something similar, and when he unplugs the WAN, it instantly finishes rebooting.  I haven't tried this yet though.

[psulions5]

@pfBasic:

IDK then , maybe something got corrupted? I'd just do a fresh install then restore config.

If you aren't already maybe give a ZFS install a shot, it is generally less prone to corruption.

Update:  Fresh install won't even reboot when it completes the installation.  I have to push the rest button on the front of the computer to force a reboot.  Everything works 100%, just cant reboot.  :(

[pfBasic]

Interesting, sounds like a hardware issue. What is your install media?

Also might want to check out your bios settings and turn off unneeded features. You'll have to search around the forums to pursue this, I have never had to adjust bios for pfsense.

[psulions5]

Yeah,  I have been going around disabling stuff.  I will search the forum looking for a possible cause with the BIOS.

[psulions5]

Is there a console command that I can use to force a reboot instead of the normal process?  In case of an emergency need to reboot or something?  Like if I am away from home etc.

Thanks.

[pfBasic]

https://www.freebsd.org/cgi/man.cgi?reboot(8)

[stephenw10]

You probably want:

shutdown -p now

If your box still doesn't shutdown using that there's probably some bad value being fed to the system about how to power down the board. BIOS up to date?

Steve

[kpa]

There are known problems on certain hardware where FreeBSD fails to reboot or powerdown properly. USB seems to be one of the common factors.

This is rather old bug but showcases the problem:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167685

Suggested workaround is a sysctl:

# sysctl hw.usb.no_shutdown_wait=1

[psulions5]

@kpa:

There are known problems on certain hardware where FreeBSD fails to reboot or powerdown properly. USB seems to be one of the common factors.

This is rather old bug but showcases the problem:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167685

Suggested workaround is a sysctl:

# sysctl hw.usb.no_shutdown_wait=1

Oh nice.  I moved my router to my Supermicro xeon server for the time being, and it works on that flawlessly (I had an issue with a NIC not showing up but it seems to be fixed).  I think I may just move my 7700K to my video encoding box, and keep the xeon as my router.

Where would I add that code if I wanted to test it out?  Not very familiar with that aspect of pfsense.  Thanks for all the help, this forum is great.

[kpa]

You can add any sysctl tunable at System->Advanced->System Tunables. Select new, enter hw.usb.no_shutdown_wait as the tunable and 1 as the value.

[psulions5]

Thank you!

[docBliny]

I'm seeing the same issue on a new ASRock H270M-ITX/ac P2.00 with the latest BIOS and the latest beta "built on Mon Apr 10 18:49:44 CDT 2017".

Applying the "hw.usb.no_shutdown_wait=1" did not seem to resolve the issue.

I've turned off most everything extra in the BIOS (except all the unused USB ports).

I do see the following in /var/log/system.log several times right at shutdown:
ACPI Exception: AE_ERROR, Thread 100762 could not acquire Mutex [0x0] (20160527/utmutex-345)
ACPI Error: Could not acquire AML Interpreter mutex (20160527/exutils-104)

Other info:
Intel Core i5-7600K @ 3.80GHz
8 GB RAM (2xCrucial 4GB DDR4-2133)
Samsung PM951 128GB M.2

Let me know what would be helpful to troubleshoot. (I am seeing packet loss from the LAN side with ping 8.8.8.8, but not from the pfSense machine or to the machine itself, and it seems php-fhm needs a restart pretty frequently, but those are for another post)

Thanks,

// Tomi B.

[stephenw10]

Hard to say exactly what that is. That ACPI error could be causing it to not pass the power functions correctly.

Can you power down with any manual command line?

Probably not much we can do there.

Steve

[Runenaldo]

@psulions5:

@pfBasic:

IDK then , maybe something got corrupted? I'd just do a fresh install then restore config.

If you aren't already maybe give a ZFS install a shot, it is generally less prone to corruption.

Update:  Fresh install won't even reboot when it completes the installation.  I have to push the rest button on the front of the computer to force a reboot.  Everything works 100%, just cant reboot.  :(

I'm having the excact same issue after installing ZFS 2 disk mirror onto two USB sticks.

Asrock J3455-ITX latest bios 1.20
2x4gb HyperX DDR3L 1866MHz RAM

Any updates?