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

    keeps on rebooting

    Scheduled Pinned Locked Moved General pfSense Questions
    15 Posts 4 Posters 1.0k 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.
    • O
      ozlecz
      last edited by

      ver=2.4.4 p3
      apps installed=snort, squid, pfblocker

      it works for a week then the system keeps rebooting..

      please see attached file...it scrolls lots of pages and it will stop on this page before rebooting itself...rebooting 2.4.4p3.jpg

      done sentinel check on the SSD but helath is 100%

      1 Reply Last reply Reply Quote 0
      • O
        ozlecz
        last edited by

        Note: this same SSD when transferred to another identical box will behave the same.

        1 Reply Last reply Reply Quote 0
        • NollipfSenseN
          NollipfSense
          last edited by NollipfSense

          If a reboot didn't fix the issue, I would just reinstall pfSense.

          pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
          pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

          1 Reply Last reply Reply Quote 0
          • O
            ozlecz
            last edited by

            re installation will surely stop the problem but i guess it wont be fixed.

            =transferred the same ssd to an identical hardware and the same rebooting issue was duplicated
            =pls see attached capture, i wanna see the root cause as we want to prevent the same error happening again

            7360 issue.txt

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

              I would bet on these two :

              ufs_makeinode() at ufs_makeinode+0xa3/frame 0xfffffe0235e86580
              ufs_create() at ufs_create+0x34/frame 0xfffffe0235e865a0
              

              which means to me : troubles making a file ...

              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
              • O
                ozlecz
                last edited by

                troubles making a file? means?

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

                  That info isn't included in the dump.

                  It could be a file on a ram disk, or more common : a file on your 'hard' disk.
                  It could be as simple as : no more space or more usual : file system hosed (repair with fsck on boot) up until disk-starts-to-die.

                  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 1
                  • O
                    ozlecz
                    last edited by

                    its a new system with 128gb transcend 370 series ssd. health was chcked via sentinal and it was 100% healthy

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

                      Yeah that looks like a filesystem issue. You should be able to recover that by manually running fsck -y / a few times (at least 3) from single user mode.

                      Steve

                      O 1 Reply Last reply Reply Quote 0
                      • O
                        ozlecz @stephenw10
                        last edited by

                        @stephenw10 weve replaced the SSD meantime but what if the problem comes back again

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

                          Easy !

                          1 ) if needed, shut down system properly. No power line ripping.
                          2) use an UPS and set it up so rule 1 applies when power goes away.

                          edit : Your SSD isn't probably physically damaged, only logically.
                          Never heard or saw of 'chkdsk' before ?
                          Some command line commands are needed to put things in place again, as @stephenw10 mentioned.

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

                            Yeah I doubt there is a problem with your SSD. The real question is what was causing the filesystem issue. It's almost always because the system lost power during writing the drive.

                            Steve

                            1 Reply Last reply Reply Quote 1
                            • O
                              ozlecz
                              last edited by

                              if its not a power issue, would there be a chance of a hardware issue?

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

                                How, according to you, could we know if something is wrong with your hardware ?

                                Bad sata cables, bad power supplies, all is possible.

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

                                  Yes, it could be something else causing the drive write to fail mid-write. Bad SSD. Bad internal power. Bad cable.
                                  I have seen bad SATA cables do some truly weird stuff, I would swap that out first if you have not already.

                                  Steve

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