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

    Crash nearly every day with 2.4.4

    Scheduled Pinned Locked Moved Off-Topic & Non-Support Discussion
    18 Posts 5 Posters 1.6k 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.
    • J
      jasonArloUser
      last edited by

      Ok, I brought the router upstairs and ran fsck /. Took about 3 times before all the errors went away so maybe that was indeed the issue. Will keep you posted.

      1 Reply Last reply Reply Quote 0
      • J
        jasonArloUser
        last edited by

        Well, after running fsck I've got uptime almost 3 days with no issues so I think that was the fix. Thanks for your help.

        1 Reply Last reply Reply Quote 1
        • J
          jasonArloUser
          last edited by

          The router lasted about 3 days, now it has crashed again:

          0_1550181856866_crashdump.tar.gz

          1 Reply Last reply Reply Quote 0
          • chrismacmahonC
            chrismacmahon
            last edited by

            2 crashes with different causes.... It's looking like hardware failure.

            Would do a memtest; perhaps replace the hard drive. At some point and time you will need to make the call, what's worth more, your time or purchasing a new device.

            Please let me know how this works out for you.

            Need help fast? Our support is available 24/7 https://www.netgate.com/support/

            Do Not PM For Help!

            1 Reply Last reply Reply Quote 0
            • J
              jasonArloUser
              last edited by

              This device is pretty new. :( It's an embedded PC Machines, basically a NIC with a CPU on it and an SSD drive.

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

                What you see is the result after the crash.
                Put an UPS up front to exclude any power issues. Set up a clean shut down - add a mail notification if a power.

                Also : start mall when using new hardware. No packages, nothing fancy.
                After some days / weeks, throlle up the load, and add a package, and retest.
                Finally, install : Squid.

                If you have hardware issues, problems will popup as soon as you start using the device for some time.
                If it concerns resource errors : when the load goes up : more errors.
                A faulty setup : as soon as you activate the pack

                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
                • boukeB
                  bouke @jasonArloUser
                  last edited by bouke

                  @jasonarlouser Make and model please? I am running several PC Engines APU boxes. For some versions it is required to upgrade the firmware (otherwise these will crash often).

                  1 Reply Last reply Reply Quote 0
                  • J
                    jasonArloUser
                    last edited by

                    PC Engines APU2
                    BIOS Vendor: coreboot

                    Not sure where to see more. Does that help? Running the disk clean up reduced reboots a lot. Now it's every couple of weeks instead of daily.

                    boukeB 2 Replies Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Try running kenv at the command line or Diag > Command Prompt. If it reports the BIOS version at all it will show there.

                      Steve

                      boukeB 1 Reply Last reply Reply Quote 0
                      • boukeB
                        bouke @jasonArloUser
                        last edited by

                        @jasonarlouser said in Crash nearly every day with 2.4.4:

                        PC Engines APU2
                        BIOS Vendor: coreboot

                        Not sure where to see more. Does that help? Running the disk clean up reduced reboots a lot. Now it's every couple of weeks instead of daily.

                        I am running quite a lot APU2/3/4 boxes. The APU4 (with 4 NICs) requires a BIOS upgrade for sure.

                        I recommend to check the current BIOS version. And you have to know which board you are using. Some identify an APU3 as an APU2...

                        1 Reply Last reply Reply Quote 0
                        • boukeB
                          bouke @jasonArloUser
                          last edited by bouke

                          @jasonarlouser

                          Please find the BIOS update here: https://pcengines.github.io/

                          Tip: when you login to your pfSense webUI, the BIOS version should be displayed.

                          For further testing you could enable SSH and SSH into your firewall.
                          Next start a shell and install Flashrom: pkg install flashrom

                          Once installed close the shell (by typing 'exit' and pressing <ENTER>). Next open the shell again.
                          Determine the board with this command: flashrom -p internal -V | grep DMI

                          Next download the matching ROM from pcengines.github.io. You could use curl. If curl isn't present, then install it "pkg install curl".

                          Next untar the file (tar xvfz apu?_v?.?.?.rom.tar.gz).

                          Next flash the BIOS: flashrom -w apu?_v?.?.?.rom -p internal:boardmismatch=force

                          Take note fo the detected mainboard. Mostly it doesn't match exactly - but that's a known issue. Just carry on when you are sure it is the correct ROM for your board.

                          After successfully flashing your BIOS you have to reboot (use the "reboot" command).

                          I am hoping this is helpful. Please only flash your board after a fresh reboot. You just don't want to brick your board. If you brick your board, you will need an unbricking tool (flash recovery board): https://www.pcengines.ch/spi1a.htm (I have one - but never had to use it).

                          1 Reply Last reply Reply Quote 0
                          • boukeB
                            bouke @stephenw10
                            last edited by

                            @stephenw10

                            kenv | grep smbios

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