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

    It was not possible to identify which pfSense kernel is installed

    Scheduled Pinned Locked Moved Virtualization
    6 Posts 3 Posters 581 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.
    • P
      padhi
      last edited by

      Hello,

      I am using pfSense 2.6.0 in a virtual machine (QNAP TVS-872 NAS, QTS 5). It worked like a charm since years.
      Today I am facing this error message : "It was not possible to identify which pfSense kernel is installed" shown via the console.
      From this console, a password is requested.
      I cannot access the webgui. I did not ask for any pfSense update. Other posts with same error did not help me or I did not catch what to do.
      My usual password is rejected by the console.
      Trying to access the terminal with Boot Single user option : this user seems to not have rights to use scp command in order to allow me to save the config.xml file to an external storage.

      May be other useful messages could help but they quickly go outside the console window.
      I am totally stuck there with my network down.
      I wonder if someone would kindly help to recover normal pfSense running or at least a way to save the config.xml file on a distant volume.
      Thank you for your help.

      S GertjanG 2 Replies Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @padhi
        last edited by

        @padhi if the disk is readable you can try during install: https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html
        Always save backups…

        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
        • P
          padhi
          last edited by

          Thank you for reading.

          That did not help because pfSense is run from an img file (not directly from a disk).

          Under Ubuntu, I tried to mount the ufs filesystem using losetup -P and mount -t ufs -o ufstype=ufs2 but that failed because loop<n>p1 is not created.

          Of course I have a backup of config.xml file but it is not the very last.

          I understand that the current pfSense img file I have is not working anymore and I get no evidence in logs that an event could explain this situation.

          If you see something else, do not hesitate. Thank you.

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

            @padhi said in It was not possible to identify which pfSense kernel is installed:

            in a virtual machine

            The VM manager doesn't permit you to 'browse' the file system offline ?

            @padhi said in It was not possible to identify which pfSense kernel is installed:

            but they quickly go outside the console window

            Even the dumb 'free' Hyper-V permits to log the console. For easy analysis afterwards. Yours ?

            edit :
            Example : as I'm using this one : https://github.com/KoenZomers/pfSenseBackup/blob/master/README.md

            So all you need is a Windows PC. Set it up so that every day a xx h it grabs a backup.
            Or have it backup when you start (boot) it.
            Now your taking the advantage of the fact that if you have a very recent backup, you'll never need it 😊

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

            P 1 Reply Last reply Reply Quote 1
            • P
              padhi @Gertjan
              last edited by

              Thank you for your ideas. Finally I was able to recover the last config.xml file using a FAT USB key attached to the faulty pfSense VM.

              From the early pfSense menu in console: Boot Single user
              I entered these commands:

              mount -o rw /
              mount_msdosfs /dev/da0s1 /media
              cp /cf/conf/config.xml /media
              

              I used the same ISO pfSense image version as the pfSense VM version that crashed to build a new default pfSense VM, then I imported the config.xml.

              That worked for me.

              Thank you for the pfSenseBackup solution. The author also provides a Linux version I will try for sure.

              P 1 Reply Last reply Reply Quote 1
              • P
                padhi @padhi
                last edited by

                I am new here so, a moderator may kindly mark this thread as solved.
                Thank you.

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