Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - temporal-agent

#1
25.1, 25.4 Production Series / Re: rescue the config
February 25, 2025, 12:35:53 AM
i mounted it in a temp folder, ls -lah says that there is nothing in zroot.
#2
25.1, 25.4 Production Series / Re: rescue the config
February 25, 2025, 12:14:10 AM
FreeBSD was able to mount it, but i can't find it.


#3
25.1, 25.4 Production Series / Re: rescue the config
February 24, 2025, 11:25:26 PM
ubuntu 24.04:
failed to mount "zroot"
filesystem type zfs_member not configured in kernel
#4
25.1, 25.4 Production Series / rescue the config
February 24, 2025, 10:33:14 PM
i have a failed upgrade that won't finish booting.  i've tried to reinstall and import the config off the mirrored zfs array, but it can't seem to.  i can't seem to mount the zfs volume in another distro either.

is there any way to rescue the config?
#5
I had this exact problem:
/usr/local/etc/rc.bootup: The command `/sbin/ifconfig 'bxe0' -vlanhwtag' failed to execute
/usr/local/etc/rc.bootup: The command `/sbin/ifconfig 'bxe0' -vlanhwfilter' failed to execute
/usr/local/etc/rc.bootup: The command `/sbin/ifconfig 'bxe0' -vlanhwcsum' failed to execute
/usr/local/etc/rc.bootup: The command `/sbin/ifconfig 'bxe1' -vlanhwtag' failed to execute
/usr/local/etc/rc.bootup: The command `/sbin/ifconfig 'bxe1' -vlanhwfilter' failed to execute
/usr/local/etc/rc.bootup: The command `/sbin/ifconfig 'bxe1' -vlanhwcsum' failed to execute
bxe0: ERROR: Changing VLAN_HWTAGGING is not supported!
bxe0: ERROR: Changing VLAN_HWFILTER is not supported!
bxe0: ERROR: Changing VLAN_HWCSUM is not supported!
bxe1: ERROR: Changing VLAN_HWTAGGING is not supported!
bxe1: ERROR: Changing VLAN_HWFILTER is not supported!
bxe1: ERROR: Changing VLAN_HWCSUM is not supported!


Updating the firmware did not fix it.

Here's what did work: In Interfaces > Settings, I set "VLAN Hardware Filtering" to "Leave Default"

#6
I have FreeBSD 11.2-RELEASE-p9 amd64 running and patched.
I have running stress on it without incident.

Any ideas on how I can instigate a crash?

Perhaps running dtrace on the OPNsense install?
#7
Quote from: weust on April 25, 2019, 09:14:57 AM...  Have you tried installing FreeBSD itself, or perhaps HardenedBSD to see if any of those two plain installation will crash the system as well?

I haven't, but I will. I'll reply with results.

Quote from: franco on April 26, 2019, 05:35:11 AM
Shall we move this topic to hardware then? ...

Sounds fine to me.
#8
Quote from: weust on April 24, 2019, 01:48:02 PM
If the log doesn't report shutting down for a reboot, it crashes and boots. It's not rebooting.

You link to a Netgate page, is the hardware Netgate?

If it has replaceable memory, I would start there or run a memtest if you can.


  • Yes, technically it is not rebooting. It runs and then suddenly without warning or error, BIOS is booting up the system again.
  • I linked to the page as a reference on standard FreeBSD Troubleshooting of Unexpected Reboots (their phrase, not mine).  It is not NetGate hardware.  It's an ECS KBN-I2100 motherboard (see initial post for hardware details).
  • I have run Memtest 86 for 19+ hours without error.  I have run all the stress/burnin tests I can find, all without error.

I can find nothing wrong other than the symptom of seemingly random and sudden booting.  Using it seems to hasten the booting, i.e., SSH, WebGUI, or network traffic.  I have done everything I can think to do to find the cause.

Is there any additional debugging or logging I can do?
#9
Yea, nothing. 

I pulled all non-essential hardware out.
I replaced all the cables, inside and out.
I even swapped out the power supply and connected it to a UPS.

So that just leaves the RAM or the motherboard/CPU.
And it runs Linux & Windows fine...

Reference: https://docs.netgate.com/pfsense/en/latest/hardware/unexpected-reboot-troubleshooting.html
#10
Has anyone taken a look at the way FreeNAS installs to ZFS?
#11
I have a fresh install of OPNsense 19.1.6-amd64 that is rebooting repeatedly. Using SSH or webGUI seems to increase the frequency of the reboots.  The system.log doesn't show any problems, it just stops whatever it was doing and then records the bootup. 
No plugins installed and minimally configured.

Is there a way to enable more verbose logging?
Is this hardware incompatible?

System stats:
MB:  ECS KBN-I2100 v1.1
CPU: AMD E1-2100 APU with Radeon(TM) HD Graphics     (998.15-MHz K8-class CPU)
RAM: 8589934592 (8192 MB)

em0:  <Intel(R) PRO/1000 Network Connection 7.6.1-k>
em1:  <Intel(R) PRO/1000 Network Connection 7.6.1-k>
em2:  <Intel(R) PRO/1000 Network Connection 7.6.1-k>
em3:  <Intel(R) PRO/1000 Network Connection 7.6.1-k>
iwn0: <Intel Centrino Ultimate-N 6300>
re0:  <Realtek PCIe GBE Family Controller>

ada0:     <TEAML5Lite3D120G R0302A0> ACS-2 ATA SATA 3.x device
aesni0:   <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5
#12
19.1 Legacy Series / Re: Upgrade fail
February 02, 2019, 12:11:56 AM
Quote from: SecAficionado on February 01, 2019, 03:34:00 AM
There is one extra update before 19.1. You should go to 18.7.10_4 and then to 19.1.

Yea, it was 18.7.10_4 and not _3.

I was able to "rescue" the system from inside the 19.1 installer by loading the on-disk config.  I couldn't find a way to make the live system permanent. So I backed up the config (from the GUI) and did a fresh install.  This went fine until the reboot where it died before boot menu where it couldn't find the kernel.

I reverted to 18.7, loaded my config (which works despite being saved from 19.1), and it's up and running fine now.

Maybe it's because it's an i386 cpu...
QuoteVersions   OPNsense 18.7.10_4-i386
FreeBSD 11.1-RELEASE-p18
LibreSSL 2.7.5

sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu'
hw.machine: i386
hw.model: Intel(R) Pentium(R) 4 CPU 3.00GHz
hw.ncpu: 2
hw.machine_arch: i386


dmesg | grep -i cpu
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3014.55-MHz 686-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
SMP: AP CPU #1 Launched!
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0


Edit: It helps to SSH into the correct host...
#13
19.1 Legacy Series / Upgrade fail
February 01, 2019, 01:00:10 AM
Upgrading from 18.7.10_3 to 19.1 via GUI.
System halts at MOUNTROOT> prompt.
Not sure what to do next.
#14
Quote from: marjohn56 on May 03, 2018, 06:40:36 AM
Have you selected the theme in System->Settings->General ?
No... I couldn't find it.  But now it works, thanks.
#15
I have installed it on 18.1.6, but nothing changes:
***GOT REQUEST TO INSTALL: os-theme-rebellion***
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
os-theme-rebellion: 1.0

Number of packages to be installed: 1

The process will require 5 MiB more space.
[1/1] Installing os-theme-rebellion-1.0...
[1/1] Extracting os-theme-rebellion-1.0: .......... done
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***


is there something i need to change or configure?