Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Power outage then pfsense not working

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 2 Posters 3.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      Bill48105
      last edited by

      Hewdy,
      I've been testing out pfsense 2.0. In this case embedded/nano.  I am not sure of the exact build but could figure it out if needed although not sure this problem is specific to a certain build. I do know it was from the last few weeks for sure as I've only been testing pfsense for that long.

      The power went out here for about 5 seconds & I had not yet plugged my pfsense box into a UPS battery backup so it powered off. It was set to power back on automatically so when power came back on I assume it did so.  A few minutes later the power went out again for like 5 seconds so I assume the pfsense box went down again.  After the power came back on I waited & waited & waited for my desktop to have internet access but after 10 minutes or more I tried pinging the pfsense box but no response.  Grabbed my lappy & headed to the basement. Plugged in the serial cable, opened up hyperterminal & hit enter. I got a # prompt not the normal menu. Pressed the power button briefly & it said pfsense was shutting down & it did.  Powered it back on & let it boot, watching the serial console output. It booted to the menu but one of my PPPoE WAN's showed no connection.  I checked & I could not ping the pfsense box.  I chose assign interfaces & it showed only 3 of my 4 NIC's! For some reason one of the 3 NIC's on the daughterboard was MIA..  So I chose the reboot menu option & watched it boot again. To my dismay it said interfaces had changed or something along those lines as if it forgot which NIC's I had even though I had changed nothing. GRRR.  I powered it off & back on & chose the backup slice & let it boot. I got an error about using a newer config but it did assign all 4 NIC's properly & everything was up & running again. Could ping the box, all 3 WAN's came up, could access internet again. PHEW!  But WTH is going on?!?  Can I trust pfsense??

      My hardware is a Jetway JNC92-330-LF (Atom 330) with 1 onboard RTL8111C NIC + Jetway AD3INLANG 3 port daugherboard with "Intel 82541PI Gigabit Ethernet Controller".  I am using a 4GB Kingston CF card in IDE->CF adapter with DMA/UDMA disabled and I believe pfSense-2.0-RC1-2g-i386-20110226-1633-nanobsd.img.gz although I am not 100% certain I believe I had done at least 1 upgrade from the web admin.

      If helpful this is how I have the interfaces assigned:
      WAN em1 (static IP)
      LAN em0 (10. range)
      OPT1 em2 (PPPoE static)
      OPT2 re0 (PPPoE dynamic)

      Any input on this would be appreciated. I'd really like to use pfsense but stuff like this is scary to say the least. Luckily I was able to boot to the backup slice or I would have been SOL. Luckily I was here when it happened & not off somewhere else or I wold have been SOL with no access from the outside.  I got the pfsense box plugged into a UPS now and would like to backup the working slice to the other area but didn't want overwrite logs/config files that might be useful to track down wth happened.
      Thanks,
      Bill

      1 Reply Last reply Reply Quote 0
      • B
        Bill48105
        last edited by

        Nadda? Was hoping for some input.. Should I consider it a 1 in 1,000,000 fluke that might never happen again? Do I need to take closer look at my hardware?  Is something like this normal when using pfsense? This specific to nano build in how things are not written right away?  Could it be a bug in pfsense?

        I can't imagine this is super common/likely or I wouldn't be alone here on this but then again I find it hard to believe pfsense is that unreliable/unstable that it'd no longer boot after a power outage either.. Power is not 100% anywhere. :D

        Anyway, if the developers want/need any info off the bad/crashed slice please let me know soon or i'll be backing up the working one over top of it in case it happens again I don't want to be SOL. (I've been making backups of the config so I suppose I could always install 2.0RC fresh & restore but I'd end up being down longer than I'd really like)
        Thx
        Bill

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG
          GruensFroeschli
          last edited by

          I just had the same.
          This is the log from bootup:

          
          BIOS drive C: is disk0
          BIOS 640kB/261120kB available memory
          
          FreeBSD/i386 bootstrap loader, Revision 1.1
          (sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Fri Apr 15 15:02:47 EDT 201                                                                                                                                                             1)
          Loading /boot/defaults/loader.conf
          /boot/kernel/kernel text=0x89a110 data=0x3c9c54+0x9b6a0 syms=[0x4+0x93b80+0x4+0x                                                                                                                                                             ca86f]
          /
          Hit [Enter] to boot immediately, or any other key for command prompt.
          Booting [/boot/kernel/kernel]...
          Copyright (c) 1992-2010 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 8.1-RELEASE-p2 #0: Fri Apr 15 15:18:24 EDT 2011
              sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSe                                                                                                                                                             nsesrc/src/sys/pfSense_wrap.8.i386 i386
          Timecounter "i8254" frequency 1193182 Hz quality 0
          CPU: Geode(TM) Integrated Processor by AMD PCS (498.05-MHz 586-class CPU)
            Origin = "AuthenticAMD"  Id = 0x5a2  Family = 5  Model = a  Stepping = 2
            Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>AMD Features=0xc0400000 <mmx+,3dnow!+,3dnow!>real memory  = 268435456 (256 MB)
          avail memory = 243433472 (232 MB)
          pnpbios: Bad PnP BIOS data checksum
          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 /bo                                                                                                                                                             ot/loader.conf.
          module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0708960, 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 /b                                                                                                                                                             oot/loader.conf.
          module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0708a00, 0) error 1
          wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
          wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/l                                                                                                                                                             oader.conf.
          module_register_init: MOD_LOAD (wpi_fw, 0xc087b6b0, 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, 0xc0708aa0, 0) error 1
          K6-family MTRR support enabled (2 registers)
          ACPI Error: A valid RSDP was not found (20100331/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: <host to="" pci="" bridge=""> pcibus 0 on motherboard
          pci0: <pci bus=""> on pcib0
          Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007
          pci0: <encrypt decrypt,="" entertainment="" crypto=""> at device 1.2 (no driver attached)
          vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1000-0x10ff mem 0xe0000000-0xe0                                                                                                                                                             0000ff irq 10 at device 9.0 on pci0
          vr0: Quirks: 0x2
          vr0: Revision: 0x96
          miibus0: <mii bus=""> on vr0
          ukphy0: <generic ieee="" 802.3u="" media="" interface=""> PHY 1 on miibus0
          ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
          vr0: [ITHREAD]
          vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx=""> port 0x1400-0x14ff mem 0xe0040000-0xe0                                                                                                                                                             0400ff irq 11 at device 10.0 on pci0
          vr1: Quirks: 0x2
          vr1: Revision: 0x96
          miibus1: <mii bus=""> on vr1
          ukphy1: <generic ieee="" 802.3u="" media="" interface=""> PHY 1 on miibus1
          ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
          vr1: [ITHREAD]
          ath0: <atheros 2413=""> mem 0xe0080000-0xe008ffff irq 9 at device 12.0 on pci0
          ath0: [ITHREAD]
          ath0: AR2413 mac 7.8 RF2413 phy 4.5
          isab0: <pci-isa bridge=""> port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x                                                                                                                                                             9d7f,0x9c00-0x9c3f at device 15.0 on pci0
          isa0: <isa bus=""> on isab0
          atapci0: <amd cs5536="" udma100="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x37                                                                                                                                                             6,0xff00-0xff0f at device 15.2 on pci0
          ata0: <ata 0="" channel=""> on atapci0
          ata0: [ITHREAD]
          ata1: <ata 1="" channel=""> on atapci0
          ata1: [ITHREAD]
          ohci0: <ohci (generic)="" usb="" controller=""> mem 0xefffe000-0xefffefff irq 12 at devic                                                                                                                                                             e 15.4 on pci0
          ohci0: [ITHREAD]
          usbus0: <ohci (generic)="" usb="" controller=""> on ohci0
          ehci0: <amd cs5536="" (geode)="" usb="" 2.0="" controller=""> mem 0xefffd000-0xefffdfff irq 12                                                                                                                                                              at device 15.5 on pci0
          ehci0: [ITHREAD]
          usbus1: EHCI version 1.0
          usbus1: <amd cs5536="" (geode)="" usb="" 2.0="" controller=""> on ehci0
          cpu0 on motherboard
          orm0: <isa option="" rom=""> at iomem 0xe0000-0xea7ff pnpid ORM0000 on isa0
          atrtc0: <at real="" time="" clock=""> at port 0x70 irq 8 on isa0
          ppc0: parallel port not found.
          uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
          uart0: [FILTER]
          uart0: console (9600,n,8,1)
          uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
          uart1: [FILTER]
          RTC BIOS diagnostic error 80 <clock_battery>Timecounter "TSC" frequency 498052753 Hz quality 800
          Timecounters tick every 10.000 msec
          IPsec: Initialized Security Association Processing.
          usbus0: 12Mbps Full Speed USB v1.0
          usbus1: 480Mbps High Speed USB v2.0
          ugen0.1: <amd> at usbus0
          uhub0: <amd 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
          ugen1.1: <amd> at usbus1
          uhub1: <amd 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus1
          ad0: 967MB <cf 20090819="" 1gb=""> at ata0-master PIO4
          Root mount waiting for: usbus1 usbus0
          uhub0: 4 ports with 4 removable, self powered
          Root mount waiting for: usbus1
          uhub1: 4 ports with 4 removable, self powered
          Trying to mount root from ufs:/dev/ufs/pfsense1
          WARNING: / was not properly dismounted
          Configuring crash dumps...
          Mounting filesystems...
          Setting up embedded specific environment... done.
          WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck
          mount: /dev/ufs/pfsense1 : Operation not permitted
          ** /dev/ufs/pfsense1
          ** Last Mounted on /
          ** Root file system
          ** Phase 1 - Check Blocks and Sizes
          ** Phase 2 - Check Pathnames
          ** Phase 3 - Check Connectivity
          ** Phase 4 - Check Reference Counts
          ** Phase 5 - Check Cyl groups
          6054 files, 308406 used, 598249 free (561 frags, 74711 blocks, 0.1% fragmentatio                                                                                                                                                             n)
          
          ***** FILE SYSTEM MARKED CLEAN *****
          ** /dev/ufs/cf
          ** Last Mounted on /cf
          ** Phase 1 - Check Blocks and Sizes
          ** Phase 2 - Check Pathnames
          ** Phase 3 - Check Connectivity
          ** Phase 4 - Check Reference Counts
          ** Phase 5 - Check Cyl groups
          20 files, 2988 used, 98067 free (43 frags, 12253 blocks, 0.0% fragmentation)
          
          ***** FILE SYSTEM MARKED CLEAN *****
          
               ___
           ___/ f \
          / p \___/ Sense
          \___/   \
              \___/
          
          Welcome to pfSense 2.0-RC1  ...
          
          Creating symlinks......done.
          PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20                                                                                                                                                             060613/pcre.so' - /usr/local/lib/php/20060613/pcre.so: Undefined symbol "pcre_fr                                                                                                                                                             ee" in Unknown on line 0
          External config loader 1.0 is now starting... ad0s3
          appending output to nohup.out
          Launching the init system... done.
          Initializing............................
          Fatal error: Call to undefined function preg_match_all() in /etc/inc/util.inc on                                                                                                                                                              line 1203
          Starting CRON... done.
          Syncing packages: Avahi
          Fatal error: Call to undefined function preg_match() in /etc/inc/interfaces.inc                                                                                                                                                              on line 3517
          Executing rc.d items...
           Starting /usr/local/etc/rc.d/avahi-daemon.sh...done.
          Bootup complete
          grep: /var/log/dmesg.boot: No such file or directory
          [: -gt: unexpected operator
          
          FreeBSD/i386 (Amnesiac) (console)
          
          *** Welcome to pfSense 2.0-RC1-nanobsd (i386) on pfsense ***
          
          Fatal error: Call to undefined function preg_match() in /etc/inc/interfaces.inc                                                                                                                                                              on line 3517
          
           0) Logout (SSH only)                  8) Shell
           1) Assign Interfaces                  9) pfTop
           2) Set interface(s) IP address       10) Filter Logs
           3) Reset webConfigurator password    11) Restart webConfigurator
           4) Reset to factory defaults         12) pfSense Developer Shell
           5) Reboot system                     13) Upgrade from console
           6) Halt system                       14) Enable Secure Shell (sshd)
           7) Ping host
          
          Enter an option:
          [/code]
          
          I switched slice back to working state.</cf></amd></amd></amd></amd></clock_battery></at></isa></amd></amd></ohci></ohci></ata></ata></amd></isa></pci-isa></atheros></generic></mii></via></generic></mii></via></encrypt></pci></host></software></mmx+,3dnow!+,3dnow!></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>
          

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • B
            Bill48105
            last edited by

            Hey GruensFroeschli,
            Wow stinks you had it happen but good as means I might not be crazy. lol  I scanned thru your log to compare to my memory of when it happened to me & do recall various errors but not sure exactly. I might have to see if I can get to the log files on the disabled slice to compare..
            Thx,
            Bill

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.