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

    Can't load 'kernel' after 2.0.2 to 2.0.3 upgrade.

    Problems Installing or Upgrading pfSense Software
    4
    7
    2.6k
    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.
    • A
      awsiemieniec
      last edited by

      I upgraded via the web configurator page from version 2.0.2 to 2.0.3. After the system reboot I was left with:
      Can't load 'kernel'
      and just an OK prompt.

      What black magic can I do to repair and bring this back online?
      This is an AMD64 build

      Thanks
      IMAG0017-1.jpg
      IMAG0017-1.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • W
        witmore
        last edited by

        [EDIT]:I am removing my previous statement, It appears my issue may be a bad hard drive.

        1 Reply Last reply Reply Quote 0
        • A
          awsiemieniec
          last edited by

          Going to reload OS if there aren't any ideas.

          Can I take some shortcut in reloading to try and preserve the build or should I totally format and load from bare metal?

          Thx

          1 Reply Last reply Reply Quote 0
          • W
            witmore
            last edited by

            you could try, downloading the most recent cd, and boot from it, then chose recovery from the menu, it should look through your hard drive for your config.xml and then rebuild around those settings.

            I was using a SSD, and I guess it failed and it couldnt complete the rebuild, my last backup I could find was 2 years ago :-(

            1 Reply Last reply Reply Quote 0
            • A
              awsiemieniec
              last edited by

              I tried doing a "recovery" install (as outlined here: http://doc.pfsense.org/index.php/Automatically_Restore_During_Install) but it didn't work.  I did have a week old backup of everything so it's not a big deal, but it just seems like an overkill to completely have to wipe and reinstall for this.  I wish I knew more about the boot config file to have been able to make a fix.  I'm sure it would have been something quick and easy to do if I knew what I was doing.  :(  Oh well.

              Thx for looking.

              AWS

              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                @awsiemieniec:

                II wish I knew more about the boot config file to have been able to make a fix.  I'm sure it would have been something quick and easy to do if I knew what I was doing.

                If the disk developed a bad spot in a a "crucial" spot you could well have lost a lot more files than the kernel. I suspect it will generally be easier and much quicker to reinstall and restore your saved configuration file. (You do save your configuration file regularly, don't you?)

                1 Reply Last reply Reply Quote 0
                • L
                  languy
                  last edited by

                  I have this problem with the 4gb nanobsd-vga 2.0.3 image. I cannot get it to boot from USB. I have 3 identical Jetway JNF96 boards. All of them boot 2.0.2 fine. None of them will boot 2.0.3 either as a full install of 2.0.3 or an upgrade from 2.0.x. I get the same message as OP posted.  The system seems to enumerate the USB bus and crash. I can boot older versions and I can boot to SATA just fine.

                  When it crashed the keyboard is unresponsive and my only option is to reset/power down. What am I doing wrong. I built the image using phydiskwrite the same as 2.0.2. It starts to boot and then nothing.

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