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

    [Solved] Upgrade failed

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    6 Posts 2 Posters 8.8k 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.
    • W Offline
      wallabybob
      last edited by

      On a pfSense 2.0.1 system I upgraded firmware using http://iserv.nl/files/pfsense/releng83/pfSense-Full-Update-2.1-DEVELOPMENT-i386-20120227-2226.tgz.

      On reboot the boot loader reported:

      Unable to load a kernel!
      –
      Can't load 'kernel'

      The boot loader command ls /boot/kernel shows only the file pfsense_kernel.txt whereas the same (shell) command on a pSense 2.0.1 shows kernel.gz and a bunch of .ko files.

      I did wonder that the 2.1 i386 Update is 70MB while the 2.0 i386 Release Full Update is 88MB and the 2.1 i386 memstick is 80MB while the 2.0.1 i386 Release memstick is 98MB. Some of the snapshots are a few sandwiches short of a full picnic?

      1 Reply Last reply Reply Quote 0
      • E Offline
        Efonnes
        last edited by

        Was it using either the uniprocessor kernel or the dev kernel?  Both of those were removed semi-recently.

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

          @Efonne:

          Was it using either the uniprocessor kernel or the dev kernel?  Both of those were removed semi-recently.

          If  recall correctly, when I installed pfSense 2.0.1 a few weeks I selected Advanced install and was asked to select uniprocessor, SMP or developers' kernel and I selected developers' kernel.

          This is a path of no upgrade?

          How do I recover? Change /boot/kernel/pfsense_kernel.txt to SMP and Upgrade again?

          1 Reply Last reply Reply Quote 0
          • E Offline
            Efonnes
            last edited by

            If you boot from the LiveCD it should be possible to fix it by mounting your root filesystem and running this command that comes from /tmp/post_upgrade_command, adding to the paths as appropriate for where you mounted it:

            tar xzpf /kernels/kernel_SMP.gz –exclude loader.conf -C /boot/

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

              Thanks. Is this a generic problem with upgrades or a problem with upgrading from the "wrong" kernel?

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

                Before I aw this suggestion @Efonne:

                If you boot from the LiveCD it should be possible to fix it by mounting your root filesystem and running this command that comes from /tmp/post_upgrade_command, adding to the paths as appropriate for where you mounted it:

                tar xzpf /kernels/kernel_SMP.gz –exclude loader.conf -C /boot/

                I had reinstalled 2.0.1.

                I decided to try changing /boot/kernel/pfsense_kernel.txt to SMP and then upgrade to 2.1. If the upgrade didn't work I could try booting the LiveCD and issuing the tar command. The firmware upgrade completed successfully and the subsequent reboot successfully booted FreeBSD 8.3-PRERELEASE.

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