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

    Pfsense has detected a crash report. Got this error on my dashboard

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 3 Posters 905 Views 3 Watching
    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.
    • S Offline
      Speck1970
      last edited by

      Since the error no users on the network can access the internet. Only when I restart then the internet works for a while then it drops again.
      Can anyone assist.

      b85ab72a-67f0-463d-a884-dc31f4dccca7-WhatsApp Image 2021-10-14 at 7.41.52 AM.jpeg

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

        @speck1970 said in Pfsense has detected a crash report. Got this error on my dashboard:

        Can anyone assist.

        You can help yourself !
        Newer versions came out. They contain bug fixes. What about upgrading ?

        The crash rapport(s) page gives you the possibility to download them. You can then publish them on this forum for analysis.
        That is, post them somewhere, and post the link here.

        See how others post crash reports.

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

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          Speck1970 @Gertjan
          last edited by

          @gertjan ok thanks i did upgrade to the latest version buit the bug report reappears

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

            2.5.2, the latest version, is still built on the RELENG_2_5_0 branch so that's probably fine.

            The panic string there 'ffs_alloc: dupe alloc' indicates a filesystem error. It likely crashed at some point due to some other reason or lost power and that caused the error that could not be recovered.
            You should run a manual filesystem check to rules that out as the on-going cause:
            https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check

            Steve

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              Speck1970 @stephenw10
              last edited by

              @stephenw10 if i do a system restore to default settings would that remove the error or would i have to do a fresh install

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

                A system default only loads the default config, it does not replace any damaged files etc.

                I would start out running the manual filesystem check.

                If you're still seeing issues then you could re-install.

                Steve

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

                  @speck1970

                  When pfSEnse boots, you can see if the disk is 'clean' : it will log a line if the disk is 'dirty' when it gets mounted.
                  Just follow the boot process on the console.

                  When pfSense crashes, this can leave the disk in a dirty state.

                  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
                  • stephenw10S Offline
                    stephenw10 Netgate Administrator
                    last edited by

                    The actual issue here is that fsck (which runs at every boot) can mark the filesystem as clean when in fact it is not. That's why when you run it manually you must run it at least 3 times. It will always come back after the first pass with 'file system marked clean' but it may not be and that's when you get panics at mount.

                    Steve

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