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

Update from 2.4.1 to 2.4.2 dev failed

Scheduled Pinned Locked Moved 2.4 Development Snapshots
6 Posts 4 Posters 1.4k 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.
  • B
    bimmerdriver
    last edited by Oct 26, 2017, 3:54 AM

    I was running 2.4.1 since it was released and tried to switch over to 2.4.2 dev. The update failed. Below is a screen capture of the console. freebsd boots, but pfsense is non-functional. I was going to download a snapshot and reinstall, but I thought I'd ask if anyone wants me to look at any files that may indicate what happened before I blow it away.
    ![pfsense 2.4.1 to 2.4.2 dev failed update.PNG](/public/imported_attachments/1/pfsense 2.4.1 to 2.4.2 dev failed update.PNG)
    ![pfsense 2.4.1 to 2.4.2 dev failed update.PNG_thumb](/public/imported_attachments/1/pfsense 2.4.1 to 2.4.2 dev failed update.PNG_thumb)

    1 Reply Last reply Reply Quote 0
    • D
      doktornotor Banned
      last edited by Oct 26, 2017, 11:19 AM

      Try reinstalling with next snapshot. Or fix the buggy line yourself - https://github.com/pfsense/pfsense/commit/b0b70737ba38c5b7daca2ba779c5d71159e0ce05#diff-c3916603d3e9accb83275e3ccbddf6e6

      Then there's another bug introduced and fixed: https://github.com/pfsense/pfsense/commit/c48651648ceea6bfa4cd83af815af26cabc7d8e1#diff-c3916603d3e9accb83275e3ccbddf6e6

      And then there are probably other bugs, and you'll be better off leaving the 2.4.2 thing alone until someone does some QA actually, because this is getting absurd. Not sure which snapshot has both of these fixed, and similar issues would be avoided if someone actually at least tried to load the GUI after making the above broken code changes.

      1 Reply Last reply Reply Quote 0
      • I
        ivor
        last edited by Oct 26, 2017, 5:55 PM

        @doktornotor:

        And then there are probably other bugs, and you'll be better off leaving the 2.4.2 thing alone until someone does some QA actually, because this is getting absurd. Not sure which snapshot has both of these fixed, and similar issues would be avoided if someone actually at least tried to load the GUI after making the above broken code changes.

        You're welcome to help with testing.

        Need help fast? Our support is available 24/7 https://www.netgate.com/support/

        1 Reply Last reply Reply Quote 0
        • B
          bimmerdriver
          last edited by Oct 28, 2017, 12:36 AM Oct 28, 2017, 12:33 AM

          I downloaded and installed the 2.4.1 release. I'll try updating to the 2.4.2 snapshot later.

          1 Reply Last reply Reply Quote 0
          • B
            bullet92
            last edited by Nov 4, 2017, 9:08 AM

            My firewall failed to update drom 2.4.1 to 2.4.2.
            My setup is a physical machine with SSD and intel sata controller. It hangs at boot, says it can't start the kernel. Installation came from an upgrade 2.3.4 –> 2.4.1 Trying to boot the 2.4.0 memstick (i need 2.4.0 or 2.4.2 for PPP VLAN support) and i riceive the same (almost) error. I have an old HP server board (SE316M1) with 2 E5620 and 24G RAM. Now i'm testing my RAM machine,

            1 Reply Last reply Reply Quote 0
            • B
              bimmerdriver
              last edited by Nov 4, 2017, 4:11 PM

              @bullet92:

              My firewall failed to update drom 2.4.1 to 2.4.2.
              My setup is a physical machine with SSD and intel sata controller. It hangs at boot, says it can't start the kernel. Installation came from an upgrade 2.3.4 –> 2.4.1 Trying to boot the 2.4.0 memstick (i need 2.4.0 or 2.4.2 for PPP VLAN support) and i riceive the same (almost) error. I have an old HP server board (SE316M1) with 2 E5620 and 24G RAM. Now i'm testing my RAM machine,

              That's a different problem than I had. I since successfully updated to 2.4.2. Not sure how much success you will have going directly from 2.3.4 to 2.4.1. If your RAM checks out, you might want to try installing freebsd 11.1 (not pfsense) to see if it's a compatibility issue.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                [[user:consent.lead]]
                [[user:consent.not_received]]