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

    Netgate 3100 failure after house power outage

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    9 Posts 5 Posters 551 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.
    • D
      DaveM
      last edited by

      Some time ago my house took a power hit in a storm and I cannot access my Netgate 3100.

      I recently pressed the reset button trying to factory reset with no luck.
      The operating systems seems to load. I get errors on the pfSense loading.
      Connecting via the LAN port is not working.
      Consoling in gives the menu but the following error no matter which option I chose:

      
      0) Logout (SSH only)                  9) pfTop
       1) Assign Interfaces                 10) Filter Logs
       2) Set interface(s) IP address       11) Restart webConfigurator
       3) Reset webConfigurator password    12) PHP shell + Netgate pfSense Plus tools
       4) Reset to factory defaults         13) Update from console
       5) Reboot system                     14) Enable Secure Shell (sshd)
       6) Halt system                       15) Restore recent configuration
       7) Ping host                         16) Restart PHP-FPM
       8) Shell
      
      Enter an option: 5
      
      
      Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(95): file_notice('config.xml', 'No config.xml f...', 'pfSenseConfigur...', '')
      #2 /etc/inc/config.gui.inc(53): parse_config()
      #3 /etc/inc/auth.inc(34): require_once('/etc/inc/config...')
      #4 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...')
      #5 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...')
      #6 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...')
      #7 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....')
      #8 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
      #9 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
      #10 /etc/inc/config.inc(37): require_once('/etc/inc/notice...')
      #11 /etc/rc.initial.reboot(30): require_once('/etc/inc/config...')
      #12 {main}
        thrown in /etc/inc/notices.inc on line 135
      PHP ERROR: Type: 1, File: /etc/inc/notices.inc, Line: 135, Message: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(95): file_notice('config.xml', 'No config.xml f...', 'pfSenseConfigur...', '')
      #2 /etc/inc/config.gui.inc(53): parse_config()
      #3 /etc/inc/auth.inc(34): require_once('/etc/inc/config...')
      #4 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...')
      #5 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...')
      #6 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...')
      #7 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....')
      #8 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
      #9 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
      #10 /etc/inc/config.inc(37): require_once('/etc/inc/notice...')
      #11 /etc/rc.initial.reboot(30): require_once('/etc/inc/config...')
      #12 {main}
        thrown
      Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(1168): file_notice('phperror', 'PHP ERROR: Type...', 'PHP errors')
      #2 [internal function]: pfSense_clear_globals()
      #3 {main}
        thrown in /etc/inc/notices.inc on line 135
      
      Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(95): file_notice('config.xml', 'No config.xml f...', 'pfSenseConfigur...', '')
      #2 /etc/inc/config.gui.inc(53): parse_config()
      #3 /etc/inc/auth.inc(34): require_once('/etc/inc/config...')
      #4 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...')
      #5 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...')
      #6 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...')
      #7 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....')
      #8 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
      #9 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
      #10 /etc/inc/config.inc(37): require_once('/etc/inc/notice...')
      #11 /etc/rc.banner(27): require_once('/etc/inc/config...')
      #12 {main}
        thrown in /etc/inc/notices.inc on line 135
      PHP ERROR: Type: 1, File: /etc/inc/notices.inc, Line: 135, Message: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(95): file_notice('config.xml', 'No config.xml f...', 'pfSenseConfigur...', '')
      #2 /etc/inc/config.gui.inc(53): parse_config()
      #3 /etc/inc/auth.inc(34): require_once('/etc/inc/config...')
      #4 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...')
      #5 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...')
      #6 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...')
      #7 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....')
      #8 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
      #9 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
      #10 /etc/inc/config.inc(37): require_once('/etc/inc/notice...')
      #11 /etc/rc.banner(27): require_once('/etc/inc/config...')
      #12 {main}
        thrown
      Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(1168): file_notice('phperror', 'PHP ERROR: Type...', 'PHP errors')
      #2 [internal function]: pfSense_clear_globals()
      #3 {main}
        thrown in /etc/inc/notices.inc on line 135
      
      

      Thanks in advance for any assistance.

      S GertjanG 2 Replies Last reply Reply Quote 0
      • MaxK 0M
        MaxK 0
        last edited by MaxK 0

        Have you tried reinstalling the pfSense Software as per these instructions?

        https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/reinstall-pfsense.html

        D 1 Reply Last reply Reply Quote 0
        • D
          DaveM @MaxK 0
          last edited by

          @MaxK-0 I have not. I will open the TAC ticket soonest.
          Thank you for the reply.

          1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @DaveM
            last edited by

            @DaveM said in Netgate 3100 failure after house power outage:

            pressed the reset button trying to factory reset

            That's not what that does on this model, it just hard resets.
            https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/io-ports.html#other-ports

            You could look in directory /cf/conf/backup and see if there's a file you can recover/copy up to /cf/conf.

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote 👍 helpful posts!

            1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan @DaveM
              last edited by

              @DaveM said in Netgate 3100 failure after house power outage:

              #0 /etc/inc/notices.inc(135): fopen('', 'w')
              #1 /etc/inc/config.lib.inc(95): file_notice('config.xml', 'No config.xml f...', 'pfSenseConfigur...', '')

              pfSense can't write a file.
              Known reason : no more place avaible - disk full.
              Another reason, especially after a power outage (stands for : no clean shutdown) : file system is 'dirty'. And while the system reboots, the file system is marked as 'read only'. hence the write error.
              Netgate made a movie about it..

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 0
              • MaxK 0M
                MaxK 0
                last edited by

                A properly configured UPS will help prevent this type of file corruption.

                Fault tolerance on return of power

                1 Reply Last reply Reply Quote 1
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by stephenw10

                  Yes you may be able to recover that by running fsck a few times. But if you have a config backup I would probably just reinstall clean to be sure.

                  If you have frequent power outages at that location you might consider enabling RAM disks to prevent filesystem issues.

                  Steve

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    DaveM @stephenw10
                    last edited by

                    @stephenw10 Thanks purchased and installed an UPS yesterday. Did a fresh install. Having trouble configuring the WAN to internet rule now.

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      SteveITS Galactic Empire @DaveM
                      last edited by

                      @DaveM WAN is already the Internet. Rules are incoming not outgoing. So LAN needs a rule “to any.”

                      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                      Upvote 👍 helpful posts!

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