"Recent posts
#1
High availability / Automatic XMLRPC Sync not trig...
Last post by Luke - Today at 04:51:01 AMHello all,
This is my first post, so I'll apologise in advance if I am being dumb.
I have searched the forums but I haven't found anything related (just people with no sync at all).
I'm in the process of prepping a new HA pair of OPNsense firewalls in my home network. Each is running on an identical Proxmox host with PCI-passthrough for the 2 NICs (WAN/LAN). They are currently not live as the plan is to replace my existing firewall when they are ready.
I've just reinstalled both firewalls from scratch using the 26.1 ISO, and applied updates to 26.1_4, and the problem persists.
Both have been set up with minimal configuration:
- WAN, LAN, and a few vlans configured (including one for PFSYNC) and attached to new interfaces; these are identical on each firewall.
- A floating firewall rule allowing ICMP on all interfaces for testing
- An any/any rule on the PFSYNC interface to allow PFSYNC and XMLRPC sync
I've checked the firewalls can ping each other on each interface (including the PFSYNC one).
Finally, I have set up the high-availability settings according to the documentation:
- PFSYNC interface for the sync
- Peer IP is the PFSYNC IP of the other firewall
- XMLRPC Sync configured only on the master
- Username and password are still default, just in case it was a complex password typo issue
- All services selected for sync
If I use the synchronise and reconfigure all button on the status page, the sync works beautifully as expected; I can see this in the log files on both firewalls:
Master:
Backup:
However, if I change anything on the master firewall (a new firewall rule, a new Virtual IP), I can see the configuration change in the log, but it does not trigger a sync to the backup firewall
As I understand it, this configctl event should trigger an automatic sync to the backup, but I do not see that in the logs and the changes are not synchronised. If I run another manual sync from the high-availability status page, any changes since the last manual sync are successfully synced as expected.
Am I doing something wrong? Is this a Layer8 issue?
How do I go about diagnosing this further to see why the sync is not triggering on a configuration change?
Any assistance would be greatly appreciated.
This is my first post, so I'll apologise in advance if I am being dumb.
I have searched the forums but I haven't found anything related (just people with no sync at all).
I'm in the process of prepping a new HA pair of OPNsense firewalls in my home network. Each is running on an identical Proxmox host with PCI-passthrough for the 2 NICs (WAN/LAN). They are currently not live as the plan is to replace my existing firewall when they are ready.
I've just reinstalled both firewalls from scratch using the 26.1 ISO, and applied updates to 26.1_4, and the problem persists.
Both have been set up with minimal configuration:
- WAN, LAN, and a few vlans configured (including one for PFSYNC) and attached to new interfaces; these are identical on each firewall.
- A floating firewall rule allowing ICMP on all interfaces for testing
- An any/any rule on the PFSYNC interface to allow PFSYNC and XMLRPC sync
I've checked the firewalls can ping each other on each interface (including the PFSYNC one).
Finally, I have set up the high-availability settings according to the documentation:
- PFSYNC interface for the sync
- Peer IP is the PFSYNC IP of the other firewall
- XMLRPC Sync configured only on the master
- Username and password are still default, just in case it was a complex password typo issue
- All services selected for sync
If I use the synchronise and reconfigure all button on the status page, the sync works beautifully as expected; I can see this in the log files on both firewalls:
Master:
Code Select
Notice opnsense /usr/local/etc/rc.filter_synchronize: Filter sync successfully completed with https://172.16.0.3/xmlrpc.php.Backup:
Code Select
Notice syslog-ng Configuration reload finished;
Notice syslog-ng Configuration reload request received, reloading configuration;
Notice opnsense /xmlrpc.php: plugins_configure monitor (execute task : dpinger_configure_do(,null))
Notice opnsense /xmlrpc.php: plugins_configure monitor (,null)
Notice opnsense /xmlrpc.php: ROUTING: keeping inet default route to 192.168.1.1
Notice opnsense /xmlrpc.php: ROUTING: configuring inet default gateway on lan
Notice opnsense /xmlrpc.php: ROUTING: entering configure using defaults
Notice configctl event @ 1770003384.80 exec: system event config_changed response: OK
Notice configctl event @ 1770003384.80 msg: Feb 2 03:36:24 OPNsense02.internal config[51995]: config-event: new_config /conf/backup/config-1770003384.7952.xml
Notice opnsense /xmlrpc.php: plugins_configure monitor (execute task : dpinger_configure_do(,null))
Notice opnsense /xmlrpc.php: plugins_configure monitor (,null)
Notice opnsense /xmlrpc.php: ROUTING: keeping inet default route to 192.168.1.1
Notice opnsense /xmlrpc.php: ROUTING: configuring inet default gateway on lan
Notice kernel <6>[1613] carp: demoted by 240 to 240 (pfsync bulk start)
Notice kernel <6>[1613] carp: 1@ixl0: INIT -> BACKUP (initialization complete)
Notice kernel <6>[1613] ixl0: promiscuous mode enabled
Notice opnsense /usr/local/sbin/pluginctl: plugins_configure crl (execute task : openvpn_refresh_crls(1))
Notice opnsense /usr/local/sbin/pluginctl: plugins_configure crl (execute task : core_trust_crl(1))
Notice opnsense /usr/local/sbin/pluginctl: plugins_configure crl (1)
Notice opnsense /xmlrpc.php: ROUTING: entering configure using defaults
Notice opnsense /usr/local/etc/rc.syshook.d/carp/20-openvpn: Carp cluster member "VIP - LAN (192.168.1.250) (1@ixl0)" has resumed the state "BACKUP" for vhid 1However, if I change anything on the master firewall (a new firewall rule, a new Virtual IP), I can see the configuration change in the log, but it does not trigger a sync to the backup firewall
Code Select
Notice configctl event @ 1770003822.21 exec: system event config_changed response: OK
Notice configctl event @ 1770003822.21 msg: Feb 2 03:43:42 OPNsense01.internal config[80873]: config-event: new_config /conf/backup/config-1770003822.2062.xmlAs I understand it, this configctl event should trigger an automatic sync to the backup, but I do not see that in the logs and the changes are not synchronised. If I run another manual sync from the high-availability status page, any changes since the last manual sync are successfully synced as expected.
Am I doing something wrong? Is this a Layer8 issue?
How do I go about diagnosing this further to see why the sync is not triggering on a configuration change?
Any assistance would be greatly appreciated.
#2
26.1 Series / Possible issue importing old r...
Last post by awshirley - Today at 04:47:32 AMI'm getting this error message when I tried to import my old rules csv:
e1e633f9-c53c-4391-b640-adc9c7b82d65,1,keep,,451,pass,1,0,lo0,in,inet,any,,,,,0,0,0,0,0,,,,,,,,,,,,,,,,,,,,,,,,0,any,,0,any,
[interface] Option [lo0] not in list.
It looks like the other rules imported expect this one. I'm not exactly sure what the problem is. I've reviewed all the old rules and I don't have an lo0 interface.
Thanks!
e1e633f9-c53c-4391-b640-adc9c7b82d65,1,keep,,451,pass,1,0,lo0,in,inet,any,,,,,0,0,0,0,0,,,,,,,,,,,,,,,,,,,,,,,,0,any,,0,any,
[interface] Option [lo0] not in list.
It looks like the other rules imported expect this one. I'm not exactly sure what the problem is. I've reviewed all the old rules and I don't have an lo0 interface.
Thanks!
#3
General Discussion / btop install?
Last post by Lucid1010 - Today at 04:08:19 AMhttps://github.com/aristocratos/btop
Do I need to compile and install it myself?
Pre binary for opnsense?
Code Select
# pkg install btop
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating mimugmail repository catalogue...
Fetching meta.conf: 100% 179 B 0.2kB/s 00:01
mimugmail repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'btop' have been found in the repositoriesDo I need to compile and install it myself?
Pre binary for opnsense?
#4
26.1 Series / Re: Suricata - Divert (IPS)
Last post by agh1701 - Today at 03:37:31 AMif Suricata should fail. will the anti-lockout rules let me in?
#5
26.1 Series / Re: udpbroadcastrelay do not s...
Last post by nelox - Today at 02:08:27 AMQuote from: nero355 on January 30, 2026, 03:32:01 PMeven tho this isn't a CISCO device their 'Best Practice Guides' do advise to skip VLAN 0 to 5 when setting up your network
Cisco/CCNA best practices do not say to "skip VLAN 0-5." VLAN 0 is a special 802.1Q priority-tag concept and the common guidance is to avoid VLAN 1 for production/management and to change the native VLAN to an unused VLAN. VLANs 2–5 are valid and routinely used.
#6
German - Deutsch / Re: Bootreihenfolge geändert n...
Last post by Patrick M. Hausen - Today at 12:19:41 AMAuf die Ausgabe bekommst du von mir, dass der eMMC kaputt ist und du ihn austauschen solltest, wenn das bei deinem Gerät möglich ist. Und wenn man statt eMMC auch eine richtige SSD verbauen kann, evtl. mSATA oder M.2 2242, dann eher das.
#7
26.1 Series / KEA DHCP issue in logs but no...
Last post by liteucantresist - Today at 12:10:51 AMI have attached log file.
DHCP seems to be behaving both IPV4 and 6. Just raising this for information.
I am very new to this so if this is not what the forum is for then please let me know and remove the post.
DHCP seems to be behaving both IPV4 and 6. Just raising this for information.
I am very new to this so if this is not what the forum is for then please let me know and remove the post.
#8
German - Deutsch / Re: Bootreihenfolge geändert n...
Last post by cottec - Today at 12:02:19 AMich dachte dmesg ist das gleiche wie das syslog das ich vorher angehängt hatte.
Das mit der "KI" war nur auf den Teil des defekten eMMCs bezogen
Das mit der "KI" war nur auf den Teil des defekten eMMCs bezogen
Code Select
---<<BOOT>>---
Copyright (c) 1992-2023 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 14.3-RELEASE-p7 stable/26.1-n271965-1bab7230df71 SMP amd64
FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
[1] VT(vga): resolution 640x480
[1] CPU: Intel(R) Celeron(R) N5105 @ 2.00GHz (1996.80-MHz K8-class CPU)
[1] Origin="GenuineIntel" Id=0x906c0 Family=0x6 Model=0x9c Stepping=0
[1] Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
[1] Features2=0x4ff8ebbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,RDRAND>
[1] AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
[1] AMD Features2=0x101<LAHF,Prefetch>
[1] Structured Extended Features=0x2394a2c3<FSGSBASE,TSCADJ,FDPEXC,SMEP,ERMS,NFPUSG,PQE,RDSEED,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,SHA>
[1] Structured Extended Features2=0x18400124<UMIP,WAITPKG,GFNI,RDPID,MOVDIRI,MOVDIR64B>
[1] Structured Extended Features3=0xfc000400<MD_CLEAR,IBPB,STIBP,L1DFL,ARCH_CAP,CORE_CAP,SSBD>
[1] XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
[1] IA32_ARCH_CAPS=0x14020c6b<RDCL_NO,IBRS_ALL,SKIP_L1DFL_VME,MDS_NO>
[1] VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
[1] TSC: P-state invariant, performance statistics
[1] real memory = 8589934592 (8192 MB)
[1] avail memory = 8120631296 (7744 MB)
[1] Event timer "LAPIC" quality 600
[1] ACPI APIC Table: <COREv4 COREBOOT>
[1] WARNING: L1 data cache covers fewer APIC IDs than a core (0 < 1)
[1] FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
[1] FreeBSD/SMP: 1 package(s) x 4 core(s)
[1] random: registering fast source Intel Secure Key RNG
[1] random: fast provider: "Intel Secure Key RNG"
[1] random: unblocking device.
[1] ioapic0 <Version 2.0> irqs 0-119
[1] Launching APs: 1 3 2
[1] random: entropy device external interface
[1] wlan: mac acl policy registered
[1] kbd0 at kbdmux0
[1] WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 15.0.
[1] efirtc0: <EFI Realtime Clock>
[1] efirtc0: registered as a time-of-day clock, resolution 1.000000s
[1] smbios0: <System Management BIOS> at iomem 0x78332000-0x78332017
[1] smbios0: Entry point: v3 (64-bit), Version: 3.3
[1] aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS,SHA1,SHA256>
[1] acpi0: <COREv4 COREBOOT>
[1] acpi0: Power Button (fixed)
[1] hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
[1] Timecounter "HPET" frequency 19200000 Hz quality 950
[1] Event timer "HPET" frequency 19200000 Hz quality 550
[1] Event timer "HPET1" frequency 19200000 Hz quality 440
[1] Event timer "HPET2" frequency 19200000 Hz quality 440
[1] Event timer "HPET3" frequency 19200000 Hz quality 440
[1] Event timer "HPET4" frequency 19200000 Hz quality 440
[1] atrtc0: <AT realtime clock> port 0x70-0x77 on acpi0
[1] atrtc0: registered as a time-of-day clock, resolution 1.000000s
[1] Event timer "RTC" frequency 32768 Hz quality 0
[1] attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
[1] Timecounter "i8254" frequency 1193182 Hz quality 0
[1] Event timer "i8254" frequency 1193182 Hz quality 100
[1] Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
[1] acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
[1] pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
[1] pci0: <ACPI PCI bus> on pcib0
[1] vgapci0: <VGA-compatible display> port 0x1000-0x103f mem 0x90000000-0x90ffffff,0x80000000-0x8fffffff at device 2.0 on pci0
[1] vgapci0: Boot video device
[1] xhci0: <XHCI (generic) USB 3.0 controller> mem 0x91500000-0x9150ffff at device 20.0 on pci0
[1] xhci0: 32 bytes context size, 64-bit DMA
[1] usbus0 on xhci0
[1] usbus0: 5.0Gbps Super Speed USB v3.0
[1] pci0: <memory, RAM> at device 20.2 (no driver attached)
[1] pci0: <simple comms> at device 22.0 (no driver attached)
[1] sdhci_pci0: <Generic SD HCI> mem 0x91518000-0x91518fff at device 26.0 on pci0
[1] sdhci_pci0: 1 slot(s) allocated
[1] mmc0: <MMC/SD bus> on sdhci_pci0
[1] pcib1: <ACPI PCI-PCI bridge> at device 28.0 on pci0
[1] pci1: <ACPI PCI bus> on pcib1
[1] igc0: <Intel(R) Ethernet Controller I226-V> mem 0x7fc00000-0x7fcfffff,0x7fd00000-0x7fd03fff at device 0.0 on pci1
[1] igc0: EEPROM V2.13-0 eTrack 0x80000286
[1] igc0: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc0: Using 4 RX queues 4 TX queues
[1] igc0: Using MSI-X interrupts with 5 vectors
[1] igc0: Ethernet address: 64:62:66:2f:0f:0a
[1] igc0: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib2: <ACPI PCI-PCI bridge> at device 28.1 on pci0
[1] pci2: <ACPI PCI bus> on pcib2
[1] igc1: <Intel(R) Ethernet Controller I226-V> mem 0x7fe00000-0x7fefffff,0x7ff00000-0x7ff03fff at device 0.0 on pci2
[1] igc1: EEPROM V2.13-0 eTrack 0x80000286
[1] igc1: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc1: Using 4 RX queues 4 TX queues
[1] igc1: Using MSI-X interrupts with 5 vectors
[1] igc1: Ethernet address: 64:62:66:2f:0f:0b
[1] igc1: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib3: <ACPI PCI-PCI bridge> at device 28.5 on pci0
[1] pci3: <ACPI PCI bus> on pcib3
[1] igc2: <Intel(R) Ethernet Controller I226-V> mem 0x91000000-0x910fffff,0x91100000-0x91103fff at device 0.0 on pci3
[1] igc2: EEPROM V2.13-0 eTrack 0x80000286
[1] igc2: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc2: Using 4 RX queues 4 TX queues
[1] igc2: Using MSI-X interrupts with 5 vectors
[1] igc2: Ethernet address: 64:62:66:2f:0f:0c
[1] igc2: netmap queues/slots: TX 4/1024, RX 4/1024
[1] pcib4: <ACPI PCI-PCI bridge> at device 28.6 on pci0
[1] pci4: <ACPI PCI bus> on pcib4
[1] igc3: <Intel(R) Ethernet Controller I226-V> mem 0x91200000-0x912fffff,0x91300000-0x91303fff at device 0.0 on pci4
[1] igc3: EEPROM V2.13-0 eTrack 0x80000286
[1] igc3: Using 1024 TX descriptors and 1024 RX descriptors
[1] igc3: Using 4 RX queues 4 TX queues
[1] igc3: Using MSI-X interrupts with 5 vectors
[1] igc3: Ethernet address: 64:62:66:2f:0f:0d
[1] igc3: netmap queues/slots: TX 4/1024, RX 4/1024
[1] isab0: <PCI-ISA bridge> at device 31.0 on pci0
[1] isa0: <ISA bus> on isab0
[1] hdac0: <Intel Jasper Lake HDA Controller> mem 0x91510000-0x91513fff,0x91400000-0x914fffff at device 31.3 on pci0
[1] pci0: <serial bus> at device 31.5 (no driver attached)
[1] cpu0: <ACPI CPU> on acpi0
[1] ns8250: UART FCR is broken
[1] ns8250: UART FCR is broken
[1] uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
[1] ns8250: UART FCR is broken
[1] uart0: console (115200,n,8,1)
[1] est0: <Enhanced SpeedStep Frequency Control> on cpu0
[1] cpufreq0: <CPU frequency control> on cpu0
[1] cpufreq1: <CPU frequency control> on cpu1
[1] cpufreq2: <CPU frequency control> on cpu2
[1] cpufreq3: <CPU frequency control> on cpu3
[1] Timecounter "TSC" frequency 1996804504 Hz quality 1000
[1] Timecounters tick every 1.000 msec
[1] ugen0.1: <Intel XHCI root HUB> at usbus0
[1] uhub0 on usbus0
[1] uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
[1] mmcsd0: 31GB <MMCHC BJTD4R 0.3 SN 78F5FEBD MFG 08/2023 by 21 0x0000> at mmc0 200.0MHz/8bit/8192-block
[1] mmcsd0boot0: 4MB partition 1 at mmcsd0
[1] mmcsd0boot1: 4MB partition 2 at mmcsd0
[1] mmcsd0rpmb: 4MB partition 3 at mmcsd0
[1] hdacc0: <Intel Jasper Lake HDA CODEC> at cad 2 on hdac0
[1] hdaa0: <Intel Jasper Lake Audio Function Group> at nid 1 on hdacc0
[1] pcm0: <Intel Jasper Lake (HDMI/DP 8ch)> at nid 4 on hdaa0
[1] Trying to mount root from ufs:/dev/gpt/rootfs [rw,noatime]...
[1] WARNING: / was not properly dismounted
[1] WARNING: /: mount pending error: blocks 72 files 3
[1] Dual Console: Serial Primary, Video Secondary
[1] uhub0: 14 ports with 14 removable, self powered
[2] ugen0.2: <VIA Labs, Inc. USB2.0 Hub> at usbus0
[2] uhub1 on uhub0
[2] uhub1: <VIA Labs, Inc. USB2.0 Hub, class 9/0, rev 2.10/0.50, addr 1> on usbus0
[2] uhub1: MTT enabled
[4] uhub1: 4 ports with 4 removable, self powered
[4] ugen0.3: <VIA Labs, Inc. USB3.0 Hub> at usbus0
[4] uhub2 on uhub0
[4] uhub2: <VIA Labs, Inc. USB3.0 Hub, class 9/0, rev 3.10/0.50, addr 2> on usbus0
[6] uhub2: 4 ports with 4 removable, self powered
[9] igc1: link state changed to UP
[9] igc2: link state changed to UP
[9] igc3: link state changed to UP
[12] lo0: link state changed to UP
[12] coretemp0: <CPU On-Die Thermal Sensors> on cpu0
[14] igc2: link state changed to DOWN
[14] lagg0: link state changed to DOWN
[14] igc3: link state changed to DOWN
[14] vlan0: changing name to 'vlan01'
[14] vlan1: changing name to 'vlan02'
[14] igc1: link state changed to DOWN
[14] wg0: link state changed to UP
[15] ng0: changing name to 'pppoe0'
[17] igc3: link state changed to UP
[17] igc2: link state changed to UP
[17] igc1: link state changed to UP
[22] lagg0: link state changed to UP
[22] vlan02: link state changed to UP
[22] vlan01: link state changed to UP
[127] igc1: promiscuous mode enabled
[127] igc2: promiscuous mode enabled
[127] igc3: promiscuous mode enabled
[127] lagg0: promiscuous mode enabled
[127] vlan02: promiscuous mode enabled
[127] pppoe0: promiscuous mode enabled
[127] vlan01: promiscuous mode enabled
[127] wg0: promiscuous mode enabled
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15666479104, length=19660mmcsd0: Setting erase start position failed Timeout
[14100] 80)]error = 5
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15669100544, length=49152mmcsd0: Setting erase start position failed Timeout
[14100] 0)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15671099392, length=10485mmcsd0: Setting erase start position failed Timeout
[14100] 76)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15673655296, length=91750mmcsd0: Setting erase start position failed Timeout
[14100] 4)]error = 5
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15681388544, length=52428mmcsd0: Setting erase start position failed Timeout
[14100] 8)]error = 5
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15682797568, length=52428mmcsd0: Setting erase start position failed Timeout
[14100] 8)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15692169216, length=10485mmcsd0: Setting erase start position failed Timeout
[14100] 76)]error = 5
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15698984960, length=52428mmcsd0: Setting erase start position failed Timeout
[14100] 8)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15703736320, length=10485mmcsd0: Setting erase start position failed Timeout
[14100] 76)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15705341952, length=62259mmcsd0: Setting erase start position failed Timeout
[14100] 2)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15706652672, length=19988mmcsd0: Setting erase start position failed Timeout
[14100] 48)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15714222080, length=1048576)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15722348544, length=524288)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15723495424, length=1048576)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15726673920, length=884736)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15729721344, length=10485mmcsd0: Setting erase start position failed Timeout
[14100] 76)]error = 5
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15806758912, length=52428mmcsd0: Setting erase start position failed Timeout
[14100] 8)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15840706560, length=72089mmcsd0: Setting erase start position failed Timeout
[14100] 6)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15877603328, length=58982mmcsd0: Setting erase start position failed Timeout
[14100] 4)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15883763712, length=72089mmcsd0: Setting erase start position failed Timeout
[14100] 6)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15888875520, length=81920mmcsd0: Setting erase start position failed Timeout
[14100] 0)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15919546368, length=20971mmcsd0: Setting erase start position failed Timeout
[14100] 52)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15975776256, length=85196mmcsd0: Setting erase start position failed Timeout
[14100] 8)]error = 5
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15978102784, length=52428mmcsd0: Setting erase start position failed Timeout
[14100] 8)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=15988817920, length=10485mmcsd0: Setting erase start position failed Timeout
[14100] 76)]error = 5
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=16042426368, length=52428mmcsd0: Setting erase start position failed Timeout
[14100] 8)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=16044654592, length=10485mmcsd0: Setting erase start position failed Timeout
[14100] 76)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] g_vfs_done():gpt/rootfs[DELETE(offset=16048226304, length=12451mmcsd0: Setting erase start position failed Timeout
[14100] 84)]error = 5
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14100] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=16069853184, length=55771mmcsd0: Setting erase start position failed Timeout
[14101] 136)]error = 5
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=23345561600, length=41615mmcsd0: Setting erase start position failed Timeout
[14101] 36)]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789429760, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789528064, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789593600, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789659136, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789757440, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789822976, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789855744, length=32768)]error = 5
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13789986816, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13790019584, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13790085120, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13874397184, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13875085312, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13900021760, length=16384mmcsd0: Setting erase start position failed Timeout
[14101] 0)]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13911523328, length=32768)]error = 5
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13914210304, length=32768)]error = 5
[14101] mmcsd0: Setting erase start position failed Timeout
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=13918404608, length=32768mmcsd0: Setting erase start position failed Timeout
[14101] )]error = 5
[14101] g_vfs_done():gpt/rootfs[DELETE(offset=14132641792, length=196608)]error = 5
[14103] mmcsd0: Error indicated: 1 Timeout
[14103] g_vfs_done(): gpt/rootfs converting all errors to ENXIO
[14103] mmcsd0: Error indicated: 1 Timeout
[14103] g_vfs_done():gpt/rootfs[WRITE(offset=32621568, length=512)]error = 6 supressing further ENXIO
[14103] panic: UFS: root fs would be forcibly unmounted
[14103] cpuid = 1
[14103] time = 1769979720
[14103] KDB: stack backtrace:
[14103] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0085059c20
[14103] vpanic() at vpanic+0x161/frame 0xfffffe0085059d50
[14103] panic() at panic+0x43/frame 0xfffffe0085059db0
[14103] ffs_fsfail_cleanup() at ffs_fsfail_cleanup+0x11e/frame 0xfffffe0085059de0
[14103] softdep_disk_write_complete() at softdep_disk_write_complete+0x45/frame 0xfffffe0085059e40
[14103] bufdone() at bufdone+0x1f2/frame 0xfffffe0085059ea0
[14103] g_io_schedule_up() at g_io_schedule_up+0xea/frame 0xfffffe0085059ee0
[14103] g_up_procbody() at g_up_procbody+0x6c/frame 0xfffffe0085059ef0
[14103] fork_exit() at fork_exit+0x81/frame 0xfffffe0085059f30
[14103] fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0085059f30
[14103] --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
[14103] KDB: enter: panic
#9
26.1 Series / Re: udpbroadcastrelay do not s...
Last post by letic - February 01, 2026, 11:35:50 PMI only get this if I try to run it manually. The daemon seems up and running now.
#10
