• Boot errors efter upgrade ?

    7
    0 Votes
    7 Posts
    2k Views
    J

    update,
    i found solution how to eliminate boot up errors regarding ahcich xx.
    on installed PFS add
    "hint.ahci.0.msi=0"
    to /boot/loader.conf

    if you have problems during fresh install
    hit "3" escape to loader prompt and type
    "set hint.ahci.0.msi=0
    boot"

    however i had no success adding nvidia raid controller to pfs 2.2.5 installer (attached)

    while pfs 2.0 installer sees it (attached)

    I tried with set kern.geom.raid.enable=1,
    add drive and mirror drive with no errors, but geom raid does not appear as option in disk selection to instal PFS.

    do you have any suggestions?

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

    ![pfs 2.0 installer.JPG](/public/imported_attachments/1/pfs 2.0 installer.JPG)
    ![pfs 2.0 installer.JPG_thumb](/public/imported_attachments/1/pfs 2.0 installer.JPG_thumb)

  • High CPU Usage (100%)

    4
    0 Votes
    4 Posts
    4k Views
    D

    I saw that error in system > routing (it kept coming back every few seconds):

    radvd[31817]: prefix length should be 64 for vr0

    I googled it and found things like that: http://superuser.com/questions/662851/radvd-wont-accept-non-64-subnets

    So I manually set the prefix length to 60 (in the WAN interface config). That took care of this message.

    Then it seemed like the processor usage dropped a bit, but still had frequent 100% peaks. Plus other services kept logging (things like reload…)

    So I disabled IPv6 on WAN and LAN interfaces and the constant logging stopped, and the processor usage dropped and is now oscillating between 0 and 50%.

    I would prefer to have IPv6 on, but at least now I've got a more healthy situation for my firewall...

    Here's a chunk of the log before turning off IPv6, if anyone can tell me what's wrong with IPv6 on my firewall...

    Dec 5 17:29:23 kernel: arpresolve: can't allocate llinfo for 192.168.0.1 on vr1
    Dec 5 17:29:23 check_reload_status: rc.newwanip starting vr1
    Dec 5 17:29:23 php-fpm[62205]: /interfaces.php: ROUTING: setting default route to 192.168.0.1
    Dec 5 17:29:24 check_reload_status: Restarting ipsec tunnels
    Dec 5 17:29:29 php-fpm[4112]: /rc.newwanip: rc.newwanip: Info: starting on vr1.
    Dec 5 17:29:29 php-fpm[4112]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.0.10) (interface: WAN[wan]) (real interface: vr1).
    Dec 5 17:29:31 php-fpm[62205]: /interfaces.php: Shutting down Router Advertisment daemon cleanly
    Dec 5 17:29:31 check_reload_status: updating dyndns wan
    Dec 5 17:29:31 check_reload_status: Restarting ipsec tunnels
    Dec 5 17:29:36 php-fpm[4112]: /rc.newwanip: ROUTING: setting default route to 192.168.0.1
    Dec 5 17:29:39 check_reload_status: updating dyndns lan
    Dec 5 17:29:41 check_reload_status: Reloading filter
    Dec 5 17:29:41 php-fpm[62205]: /interfaces.php: Creating rrd update script
    Dec 5 17:29:44 php-fpm[4112]: /rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1449332984] unbound[48401:0] error: bind: address already in use [1449332984] unbound[48401:0] fatal error: could not open ports'
    Dec 5 17:29:46 php-fpm[4112]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
    Dec 5 17:29:46 php-fpm[4112]: /rc.newwanip: Creating rrd update script
    Dec 5 17:29:48 php-fpm[4112]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 192.168.0.10 -> 192.168.0.10 - Restarting packages.
    Dec 5 17:29:48 check_reload_status: Starting packages
    Dec 5 17:29:51 php-fpm[4112]: /rc.start_packages: Restarting/Starting all packages.

  • Installed Pfsense but doesn't work

    22
    0 Votes
    22 Posts
    5k Views
    B

    Your solution was…?

    Inquiring minds want to know.

  • [solved] pfSense 2.2.5 Soekris net6501 MemStick i386 fail to boot

    6
    0 Votes
    6 Posts
    3k Views
    T

    Dear sirs,

    Here some news:

    I am unable to boot with SATA DVDROM with the 2.2.5 iso.

    So I decided to go with PXE.

    I set up mem stick serial.img on my tftp server and boot with MEMDISK from SYSLINUX.

    This time I have something booting but not yet functionnal.

    I got this error:
    full log:

    comBIOS ver. 1.41c  20121115  Copyright (C) 2000-2011 Soekris Engineering. net6501 2048 Mbyte Memory                        CPU Atom E6xx 1600 Mhz SATA AHCI BIOS ver. 0.61 20121115  Copyright (C) 2003-2011 Intel Corporation Controller Bus#02, Device#06, Function#00: 02 Ports, 01 Devices   Port-00: No device detected   Port-01: Hard Disk, KINGSTON SMS200S330G Soekris USB Expansion ROM ver. 1.01  20111203 Initializing Intel(R) Boot Agent GE v1.3.72 PXE 2.1 Build 089 (WfM 2.0) Slot  Vend Dev  ClassRev Cmd  Stat CL LT HT  Base1    Base2  Int -------------------------------------------------------------------- 00:00:0 8086 4114 06000005 0007 0000 00 00 00 00000000 00000000 00:23:0 8086 8184 06040000 0107 0010 08 00 01 1FFF1000 A0FFA000 10 00:24:0 8086 8185 06040000 0107 0010 08 00 01 3FFF2000 A2FFA100 11 00:25:0 8086 8180 06040000 0107 0010 08 00 01 5FFF4000 A4FFA300 05 00:26:0 8086 8181 06040000 0107 0010 08 00 01 0FFF1000 00FFA000 09 00:31:0 8086 8186 06010000 0003 0000 00 00 80 00000000 00000000 02:02:0 8086 8804 0C031002 0106 0010 00 00 80 A0000B00 00000000 09 02:02:1 8086 8805 0C031002 0106 0010 00 00 80 A0000C00 00000000 09 02:02:2 8086 8806 0C031002 0106 0010 00 00 80 A0000D00 00000000 09 02:02:3 8086 8807 0C032002 0106 0010 00 00 80 A0000E00 00000000 09 02:06:0 8086 880B 01060102 0107 0010 00 00 00 00000000 00000000 11 02:08:0 8086 880C 0C031002 0106 0010 00 00 80 A0004800 00000000 10 02:08:1 8086 880D 0C031002 0106 0010 00 00 80 A0004900 00000000 10 02:08:2 8086 880E 0C031002 0106 0010 00 00 80 A0004A00 00000000 10 02:08:3 8086 880F 0C032002 0106 0010 00 00 80 A0004B00 00000000 10 02:10:1 8086 8811 07000201 0107 0010 00 00 80 00001041 A0004D00 09 02:10:2 8086 8812 07000200 0107 0010 00 00 80 00001049 A0004D10 09 02:12:2 8086 8817 0C800000 0106 0010 00 00 80 00000000 A0005000 05 02:12:3 8086 8818 0C090000 0106 0010 00 00 80 00000000 A0005200 05 03:00:0 111D 803A 0604000E 0107 0010 08 00 01 3FFF2000 A2FFA100 05:00:0 8086 10D3 02000000 0107 0010 08 00 00 A1000000 00000000 09 06:00:0 8086 10D3 02000000 0107 0010 08 00 00 A2000000 00000000 10 08:00:0 111D 803A 0604000E 0107 0010 08 00 01 5FFF4000 A4FFA300 10:00:0 8086 10D3 02000000 0107 0010 08 00 00 A3000000 00000000 10 11:00:0 8086 10D3 02000000 0107 0010 08 00 00 A4000000 00000000 11 1 Seconds to automatic boot.  Press Ctrl-P for entering Monitor. Intel(R) Boot Agent GE v1.3.72 Copyright (C) 1997-2010, Intel Corporation   ▒                                        ▒   ▒                                        ▒   ▒                                        ▒   ▒                                        ▒   ▒                            !            ▒   ▒                                        ▒   ▒                                        ▒   ▒                          ]              ▒   ▒                                  d      ▒   ▒                                e      ▒   ▒                            e          ▒   ▒                                    e    ▒   ▒                                    g  ▒   ▒                          t            ▒   ▒          t                              ▒   ▒                                        ▒   ▒                                        ▒   ▒                                        ▒   ▒                                  t    ▒   ▒                                        ▒   ▒                                        ▒ KDB: debugger backends: ddb KDB: current backend: ddb (map says 0x9b000), loading at 0x9a000 Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 leve prThe Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.3-RELEASE-p16 #0: Mon Aug 25 08:25:41 EDT 2014b     root@pf2_1_1_i386.pfsense.org:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Genuine Intel(R) CPU        @ 1.60GHz (1600.01-MHz 686-class CPU)   Origin = "GenuineIntel"  Id = 0x20661  Family = 6  Model = 26  Stepping = 1   Features=0xbfe9fbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x40e3bd <sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,movbe>AMD Features=0x20100000 <nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant real memory  = 2147352576 (2047 MB) avail memory = 1888325632 (1800 MB) ACPI Error: A valid RSDP was not found (20101013/tbxfroot-309) MPTable: <soekris  net6501 =""  ="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID:  0 cpu1 (AP/HT): APIC ID:  1 ioapic0: Assuming intbase of 0 ioapic0 <version 2.0="">irqs 0-23 on motherboard wlan: mac acl policy registered ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_bss_fw, 0xc07c1560, 0) error 1 ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc07c1600, 0) error 1 ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc07c16a0, 0) error 1 kbd0 at kbdmux0 ACPI Error: A valid RSDP was not found (20101013/tbxfroot-309) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. cryptosoft0: <software crypto="">on motherboard padlock0: No ACE support. pcib0: <mptable host-pci="" bridge="">pcibus 0 on motherboard pci0: <pci bus="">on pcib0 pcib1: <pci-pci bridge="">irq 16 at device 23.0 on pci0 pci1: <pci bus="">on pcib1 pcib2: <pci-pci bridge="">irq 16 at device 0.0 on pci1 pci2: <pci bus="">on pcib2 pci2: <unknown>at device 0.0 (no driver attached) pci2: <network, ethernet="">at device 0.1 (no driver attached) pci2: <unknown>at device 0.2 (no driver attached) ohci0: <ohci (generic)="" usb="" controller="">mem 0xa0000b00-0xa0000bff irq 19 at device 2.0 on pci2 ohci0: [ITHREAD] usbus0: <ohci (generic)="" usb="" controller="">on ohci0 ohci1: <ohci (generic)="" usb="" controller="">mem 0xa0000c00-0xa0000cff irq 19 at device 2.1 on pci2 ohci1: [ITHREAD] usbus1: <ohci (generic)="" usb="" controller="">on ohci1 ohci2: <ohci (generic)="" usb="" controller="">mem 0xa0000d00-0xa0000dff irq 19 at device 2.2 on pci2 ohci2: [ITHREAD] usbus2: <ohci (generic)="" usb="" controller="">on ohci2 ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xa0000e00-0xa0000eff irq 19 at device 2.3 on pci2 ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: <ehci (generic)="" usb="" 2.0="" controller="">on ehci0 pci2: <serial bus,="" usb="">at device 2.4 (no driver attached) pci2: <base peripheral,="" sd="" host="" controller=""> at device 4.0 (no driver attached) pci2: <base peripheral,="" sd="" host="" controller=""> at device 4.1 (no driver attached) atapci0: <intel ahci="" controller="">port 0x1020-0x103f mem 0xa0004400-0xa00047ff irq 17 at device 6.0 on pci2 atapci0: [ITHREAD] atapci0: AHCI v1.10 controller with 2 3Gbps ports, PM supported ata2: <ata channel="">at channel 0 on atapci0 ata2: [ITHREAD] ata3: <ata channel="">at channel 1 on atapci0 ata3: [ITHREAD] ohci3: <ohci (generic)="" usb="" controller="">mem 0xa0004800-0xa00048ff irq 16 at device 8.0 on pci2 ohci3: [ITHREAD] usbus4: <ohci (generic)="" usb="" controller="">on ohci3 ohci4: <ohci (generic)="" usb="" controller="">mem 0xa0004900-0xa00049ff irq 16 at device 8.1 on pci2 ohci4: [ITHREAD] usbus5: <ohci (generic)="" usb="" controller="">on ohci4 ohci5: <ohci (generic)="" usb="" controller="">mem 0xa0004a00-0xa0004aff irq 16 at device 8.2 on pci2 ohci5: [ITHREAD] usbus6: <ohci (generic)="" usb="" controller="">on ohci5 ehci1: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xa0004b00-0xa0004bff irq 16 at device 8.3 on pci2 ehci1: [ITHREAD] usbus7: EHCI version 1.0 usbus7: <ehci (generic)="" usb="" 2.0="" controller="">on ehci1 pci2: <unknown>at device 10.0 (no driver attached) pci2: <simple comms,="" uart="">at device 10.1 (no driver attached) pci2: <simple comms,="" uart="">at device 10.2 (no driver attached) pci2: <simple comms,="" uart="">at device 10.3 (no driver attached) pci2: <simple comms,="" uart="">at device 10.4 (no driver attached) pci2: <unknown>at device 12.0 (no driver attached) pci2: <serial bus="">at device 12.1 (no driver attached) pci2: <serial bus="">at device 12.2 (no driver attached) pci2: <serial bus="">at device 12.3 (no driver attached) pci2: <unknown>at device 12.4 (no driver attached) pcib3: <pci-pci bridge="">irq 17 at device 24.0 on pci0 pci3: <pci bus="">on pcib3 pcib4: <pci-pci bridge="">at device 0.0 on pci3 pci4: <pci bus="">on pcib4 pcib5: <pci-pci bridge="">at device 2.0 on pci4 pci5: <pci bus="">on pcib5 em0: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0x2000-0x201f mem 0xa1000000-0xa101ffff,0xa1020000-0xa1023fff irq 19 at device 0.0 on pci5 em0: Using MSIX interrupts with 3 vectors em0: [ITHREAD] em0: [ITHREAD] em0: [ITHREAD] pcib6: <pci-pci bridge="">at device 3.0 on pci4 pci6: <pci bus="">on pcib6 em1: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0x3000-0x301f mem 0xa2000000-0xa201ffff,0xa2020000-0xa2023fff irq 16 at device 0.0 on pci6 em1: Using MSIX interrupts with 3 vectors em1: [ITHREAD] em1: [ITHREAD] em1: [ITHREAD] pcib7: <pci-pci bridge="">at device 4.0 on pci4 pci7: <pci bus="">on pcib7 pcib8: <pci-pci bridge="">irq 18 at device 25.0 on pci0 pci8: <pci bus="">on pcib8 pcib9: <pci-pci bridge="">at device 0.0 on pci8 pci9: <pci bus="">on pcib9 pcib10: <pci-pci bridge="">at device 2.0 on pci9 pci10: <pci bus="">on pcib10 em2: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0x4000-0x401f mem 0xa3000000-0xa301ffff,0xa3020000-0xa3023fff irq 16 at device 0.0 on pci10 em2: Using MSIX interrupts with 3 vectors em2: [ITHREAD] em2: [ITHREAD] em2: [ITHREAD] pcib11: <pci-pci bridge="">at device 3.0 on pci9 pci11: <pci bus="">on pcib11 em3: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0x5000-0x501f mem 0xa4000000-0xa401ffff,0xa4020000-0xa4023fff irq 17 at device 0.0 on pci11 em3: Using MSIX interrupts with 3 vectors em3: [ITHREAD] em3: [ITHREAD] em3: [ITHREAD] pcib12: <pci-pci bridge="">at device 4.0 on pci9 pci12: <pci bus="">on pcib12 pcib13: <pci-pci bridge="">irq 19 at device 26.0 on pci0 pci13: <pci bus="">on pcib13 isab0: <pci-isa bridge="">at device 31.0 on pci0 isa0: <isa bus="">on isab0 cpu0 on motherboard est0: <enhanced speedstep="" frequency="" control="">on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 612101906001019 device_attach: est0 attach returned 6 p4tcc0: <cpu frequency="" thermal="" control="">on cpu0 cpu1 on motherboard est1: <enhanced speedstep="" frequency="" control="">on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 612101906001019 device_attach: est1 attach returned 6 p4tcc1: <cpu frequency="" thermal="" control="">on cpu1 pmtimer0 on isa0 ata0: <ata channel="">at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata0: [ITHREAD] ata1: <ata channel="">at port 0x170-0x177,0x376 irq 15 on isa0 ata1: [ITHREAD] atrtc0: <at real="" time="" clock="">at port 0x70 irq 8 on isa0 ppc0: parallel port not found. uart0: <non-standard ns8250="" class="" uart="" with="" fifos="">at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 uart0: [FILTER] uart0: console (9600,n,8,1) est0: <enhanced speedstep="" frequency="" control="">on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 612101906001019 device_attach: est0 attach returned 6 est1: <enhanced speedstep="" frequency="" control="">on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 612101906001019 device_attach: est1 attach returned 6 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 12Mbps Full Speed USB v1.0 usbus7: 480Mbps High Speed USB v2.0 ugen0.1: <0x8086> at usbus0 uhub0: <0x8086 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 ugen1.1: <0x8086> at usbus1 uhub1: <0x8086 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1 ugen2.1: <0x8086> at usbus2 uhub2: <0x8086 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2 ugen3.1: <intel>at usbus3 uhub3: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus3 ugen4.1: <0x8086> at usbus4 uhub4: <0x8086 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4 ugen5.1: <0x8086> at usbus5 uhub5: <0x8086 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5 ugen6.1: <0x8086> at usbus6 uhub6: <0x8086 OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6 ugen7.1: <intel>at usbus7 uhub7: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus7 ad6: 28626MB <kingston sms200s330g="" 600abbf0="">at ata3-master UDMA100 SATA 3Gb/s uhub0: 1 port with 1 removable, self powered uhub1: 1 port with 1 removable, self powered uhub2: 1 port with 1 removable, self powered uhub4: 1 port with 1 removable, self powered uhub5: 1 port with 1 removable, self powered uhub6: 1 port with 1 removable, self powered uhub3: 3 ports with 3 removable, self powered uhub7: 3 ports with 3 removable, self powered SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ufs/pfSense ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt:     set vfs.root.mountfrom.options=rw and then remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/pfSense vfs.root.mountfrom.options=ro Manual root filesystem specification:   <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a                       eg. cd9660:/dev/acd0                       This is equivalent to: mount -t cd9660 /dev/acd0 /   ?                  List valid disk boot devices   <empty line="">Abort manual input mountroot></empty></fstype></device></device></fstype></kingston></intel></intel></intel></intel></enhanced></enhanced></non-standard></at></ata></ata></cpu></enhanced></cpu></enhanced></isa></pci-isa></pci></pci-pci></pci></pci-pci></intel(r)></pci></pci-pci></intel(r)></pci></pci-pci></pci></pci-pci></pci></pci-pci></pci></pci-pci></intel(r)></pci></pci-pci></intel(r)></pci></pci-pci></pci></pci-pci></pci></pci-pci></unknown></serial></serial></serial></unknown></simple></simple></simple></simple></unknown></ehci></ehci></ohci></ohci></ohci></ohci></ohci></ohci></ata></ata></intel></serial></ehci></ehci></ohci></ohci></ohci></ohci></ohci></ohci></unknown></network,></unknown></pci></pci-pci></pci></pci-pci></pci></mptable></software></version></soekris ></lahf></nx,lm></sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,movbe></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

    And i reach a prompt.
    I decide to press Enter without writing anything and got this:

    mountroot> panic: Root mount failed, startup aborted. cpuid = 1 KDB: enter: panic [thread] Stopped at      kdb_enter+0x3b: movl    $0,kdb_why db> To fix this, I plug my Usb stick with the 2.2.5 image writed on it and boot via PXE This time, system is booting nice and I reach the setup menu. I use the Quick and easy install. It detect successfully my primary Hard drive and install pfsense and bootloader on it. But on the first reboot (booting from internal hard drive, USB stick unplug) I fail to boot and reset just after the menu "Pfsense: F1 PXE: F6 Boot: F1" I read some post about soekris board bios is not ACPI and it doesnt work well with nanobsd v10 maybe develloppers can do something about this ? Digging the forum I reach this post https://forum.pfsense.org/index.php?topic=93642.0 According to this, I try to install 2.1.5 the same way : Copy pfsense2.1.5memstickserial.img in tftp, write image on usb stick and boot via PXE. Reach install menu and perform full installation. This time, installation goes right and i am able to boot after installation. Then I go to the main page and upgrade from 2.1.5 to 2.2.5 and reboot. and this time everything work. I will put more details on How to do on my first post. Hope next version will be easier to install from scratch because it is really painfull to install old version only to be able to upgrade. Thank you.[/thread]
  • Clean install with automatically restored configuration

    5
    0 Votes
    5 Posts
    1k Views
    jimpJ

    Try putting your file in /conf.default on the CD

  • PDFSense boot failing after install

    4
    0 Votes
    4 Posts
    1k Views
    KOMK

    Glad to hear you got it working.

    attach.png
    attach.png_thumb

  • MOVED: Sarg Could not find report index file

    Locked
    1
    0 Votes
    1 Posts
    333 Views
    No one has replied
  • Backup/Restore - SNORT settings missing?

    8
    0 Votes
    8 Posts
    3k Views
    A

    Restore worked this time, so it was the above setting and/or something else that prevented a proper restore last time.  All good!

    Also, the original crash may have been to a failed/failing USB stick; CAM error today.  :(  Went with hdd this time.  Hopefully no problems for a while.

  • "Unable to check for updates" again

    29
    0 Votes
    29 Posts
    14k Views
    A

    @stephenw10:

    Hmm, OK. We've tried the usual suspects here.
    You can see this behaviour in a multiwan setup with gateway groups. The clients on LAN use the gateway group to access the internet, in your case you have a failover setup. If you have firewall rules on LAN that catch all traffic and specify the gateway group then you are never using the system routing table to select a gateway. The pfSense box itself cannot use a gateway group it always uses the system routing table. Thus if it's default gateway is set incorrectly it will not be able to access the internet.
    Using the ping test in the diagnostics menu will fail to find this since you have to specify which interface you want to ping from.

    Go to System: Routing: Gateways: make sure the default gateway is set to something sensible, like your primary WAN connection.

    Steve

    Steve, thanks a lot for this. It makes sense now why as I'm testing my failover setup, once off my "default gateway" which is set to the "primary" wan connection, pfSense refuses to check updates or download from the available Package list. If I swap the default gateway to the (2nd) wan connection, it immediately works.

    Shouldl this behaviour affect my client workstations (DHCP) at all? Or would it just affect the web configurator from accessing the internet when the primary wan is down. Is there a way to add a firewall rule ahead of the failover gateway group "catch all", so that pfSense web configurator traffic is captured first? Hmmm

    Andrew

  • Hide process pfsense after reboot

    8
    0 Votes
    8 Posts
    2k Views
    D

    Sounds like some lame rebranding attempt to me…  ::)

  • Upgraded from 2.1.5 to 2.2.4 on CARP Backup, never came back up…

    8
    0 Votes
    8 Posts
    2k Views
    J

    Opened a support ticket.  Turns out that the issue was related to pfBlocker not being properly uninstalled during the upgrade and leaving behind a broken alias/rules.  Once the config was cleaned up the Firewall/NAT rules loaded properly and the box worked.  I am now in the process of upgrading the primary as well.

    No idea on the ix interfaces with vLANs though.  That is still broken for me.

  • MOVED: WAN interface issues

    Locked
    1
    0 Votes
    1 Posts
    430 Views
    No one has replied
  • Restore to Dissimilar Hardware/Interfaces?

    3
    0 Votes
    3 Posts
    881 Views
    M

    @divsys:

    [What version of pfSense are you running?
    [/quote]

    2.2.5.

    Thanks for the autoreplace tip, that's probably what I would have done. I'll make sure to do it manually.

  • 2.1.5->2.2.2 system does not reboot after upgrade, requires power cycle

    17
    0 Votes
    17 Posts
    4k Views
    A

    Newbie here.  Working through all things pfSense.  This was one of them.

    I put an old Dell laptop to use with pfSense for routing and radius functions.  Had problem where, from the main console menu, when I choose reboot (option 5) it goes until it stops the system and the last message is the "Uptime…"  then it just hangs.  I have to force a hard power off.

    Googled everything I could find, most folks suggested ACPI, so I went looking for it in the BIOS, but it's not there.  While I was there I noticed that this system had AHCI enabled for the HD controller, which is fine for windows and intel parties, but I dont' think it helps in pfSense under freeBSD!  Or am I wrong here ?

    Anyway, I changed the HD controller function back to the Dell default of ATA, not thinking it was connected.  When I booted and did a reboot, it worked.

    For what it's worth, something about AHCI seems to mess with the reboot process.  I'm running 2.2.5

  • Basic pfsense/vlan/network question

    15
    0 Votes
    15 Posts
    4k Views
    johnpozJ

    Once u get vlans they are not that difficult understanding native and tagged vs untagged and different switch makers use terms a bit different but if you understand the basics just need to know what switch your dealing with

  • Internet Speed Slow when connected to router at 1000mbps

    11
    0 Votes
    11 Posts
    4k Views
    D

    @Seif:

    I was hoping to find a way to make them work.

    The only way to make them "work" is the one you mentioned in the OP. I.e., force the ports to 100Mbit.

  • Mounting from ufs:/dev/ufs/pfsense0 failed with error 19

    2
    0 Votes
    2 Posts
    2k Views
    S

    After following article i was able to boot pfsense but it wont survive reboot .. it will be at that screen requiring me to input ufs:/dev/da0s1a

    http://mundofreebsd.blogspot.com/2012/09/mounting-from-ufsdevadaxs1a-failed-with.html

    here is my fstab contents
    /dev/ufs/pfsense0 / ufs ro,sync,noatime 1 1
    /dev/ufs/cf /cf ufs ro,sync,noatime 1 1

    how to set them to make ..
    below are pictures after i entered above command .. (ufs:/dev/da0s1a)

    ![usb boot error 0.PNG](/public/imported_attachments/1/usb boot error 0.PNG)
    ![usb boot error 0.PNG_thumb](/public/imported_attachments/1/usb boot error 0.PNG_thumb)
    ![usb boot error 01.PNG](/public/imported_attachments/1/usb boot error 01.PNG)
    ![usb boot error 01.PNG_thumb](/public/imported_attachments/1/usb boot error 01.PNG_thumb)
    ![usb boot error 03.PNG](/public/imported_attachments/1/usb boot error 03.PNG)
    ![usb boot error 03.PNG_thumb](/public/imported_attachments/1/usb boot error 03.PNG_thumb)

  • Watchguard X1000 Boot Error

    7
    0 Votes
    7 Posts
    1k Views
    P

    I am using one of these, and used it to talk to an X1000 console last week: http://www.amazon.com/gp/product/B000067SCH
    I bought a bunch of them a few years ago for each site.
    Any similar spec cable should do the same.

  • 0 Votes
    2 Posts
    646 Views
    KOMK

    See my reply in your other post about this same issue.

  • Install packages through LAN proxy

    12
    0 Votes
    12 Posts
    6k Views
    N

    Hello i am new to this too . I have as a project to make a Computer work as DHCP ,  Firewall , DNS , http(s) proxy and L3 routing  and route traffic from trusted and DMZ to and the outside network of the school that has internet connection threw another proxy.  (Proxy support isn't working for me either) Is there any way to install the packages manually (even the pkg is not installed)?I can download any packages from my trusted network but i have no internet connection on pfsense.I posted here as its similar problem .

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.