Regression #15387
closed
Boot failure detection tripping on config reset button during boot
100%
Description
When booting the 4200, if you follow the instructions outlined here to press the reset button when the appliance starts to flash the black diamond light, the unit hangs at the smbus0 prompt for a while while it waits for the three red lights to begin flashing:
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-4200/factory-reset.html
This seems to be tripping up the boot failure detection that was introduced in 24.03, as it's then power cycling the appliance with the following message in the console output:
ig4iic3: Using MSI iicbus3: <Philips I2C bus (ACPI-hinted)> on ig4iic3 driver bug: Unable to set devclass (class: uart devname: (unknown)) driver bug: Unable to set devclass (class: atkbdc devname: (unknown)) ichsmb0: <Intel Alder Lake SMBus controller> port 0xefa0-0xefbf mem 0x4000064000-0x40000640ff at device 31.4 on pci0 smbus0: <System Management Bus> on ichsmb0 Terminated *** SYSTEM BOOT FAILURE *** Failed Boot Environment: default R/r: Enter a recovery shell Any: Shutdown immediately Enter an option: 2024-04-07T02:10:58.583524+00:00 - init 1 - - /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: 2024-04-07T02:11:00.708967+00:00 - init 1 - - single user shell terminated.
Updated by Kris Phillips 23 days ago
Appears to have the same boot failure detection on the 4100. Likely not the only devices to have this issue.
Short press detected, entering the factory-defaults recovery mode.
Waiting for the long press to confirm.
- Reset button pressed - resetting configuration to factory defaults. *
- All additional packages installed will be removed *
- The system will reboot after this completes. * ***************************************************************
Terminated
- SYSTEM BOOT FAILURE ***
Failed Boot Environment: default
R/r: Enter a recovery shell
Any: Shutdown immediately
Updated by Kris Phillips 23 days ago
This also affected the SG-2440. This appears to not be smbus related, but simply a result of the reset button causing a non-full boot up.
Initializing.................... done.
- Reset button pressed - resetting configuration to factory defaults. *
- All additional packages installed will be removed *
- The system will reboot after this completes. * ***************************************************************
Terminated
- SYSTEM BOOT FAILURE ***
Failed Boot Environment: default
R/r: Enter a recovery shell
Any: Shutdown immediately
Updated by Kris Phillips 23 days ago
Testing multiple times on these units, they still will factory reset just fine, so this appears to not be a critical stoppage, but it might cause issues depending on how many times the boot failure counter is tripped.
Updated by
Updated by Steve Wheeler 21 days ago
- Subject changed from Boot Failure Detection Tripping on 4200 Reset Button During Boot to Boot Failure Detection Tripping on Config Reset Button During Boot
This applies to all devices that have a hardware config reset button. The 4200 can be reset at any time which means it can be after boot to avoid this. All other devices can only reset during boot.
Updated by Steve Wheeler 21 days ago
- Priority changed from Normal to High
- Target version set to 24.03
This prevents the hardware config reset working on anything that has multiple ZFS BE snapshots present to roll back to.
Updated by Jim Pingle 20 days ago
- Status changed from New to In Progress
- Assignee set to Jim Pingle
Working with Steve, we have identified a method to work around this. Commit coming shortly.
Updated by Jim Pingle 20 days ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Updated by Jim Pingle 17 days ago
- Subject changed from Boot Failure Detection Tripping on Config Reset Button During Boot to Boot failure detection tripping on config reset button during boot
- Release Notes changed from Default to Force Exclusion
Updated by Christopher Cope 16 days ago
On the 4100 & 4200 as of
24.03-RC (amd64) built on Wed Apr 10 17:29:00 UTC 2024 FreeBSD 15.0-CURRENT
I am no longer seeing this error. Leaving this open until a couple of other models are confirmed working as well.