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

    25.03-BETA won't install in SG-2100 (SG-1100 ok)

    Scheduled Pinned Locked Moved Plus 25.03 Develoment Snapshots
    6 Posts 3 Posters 211 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.
    • R
      robotox
      last edited by robotox

      Hi,
      I got 25.03-BETA to work in SG-1100 (from 24.11) a couples of days ago with no issues.
      Today I got 25.03.b.20250507.1611 and no issues.
      Using openvpn-client-export, Service_Watchdog and WireGuard.
      All good. Dashboard really really better, thank you for that!
      Only curious why I can't see the Stable branch listed anymore.
      I assume it is because Stable is not an upgrade anymore but rather a downgrade.
      [EDIT: In fact I found OPT at 100Mbps Half Duplex and I can't explain it. I changed it to 1Gbps today.]

      Tried to do the same in SG-2100 MAX (no hardware modifications) from 24.11 and never works.
      It completes the upgrade with success but then never boots with the new version until it falls back to a working boot environment after almost 30min of waiting.
      Space is not the problem as it reports 21% throughout the whole process.
      I cannot find a single log explaining the event.
      As the GUI has been getting slower and slower overtime, there are even steps I can't investigate without a dashboard crash at times. Reason why I really want to upgrade to beta the SG-2100 MAX as well.
      I tried by removing all packages in advance: openvpn-client-export, pfBlockerNG, Service_Watchdog.
      No joy.
      After some attempts it reports Messages ld-elf.so.1: Shared object "libmd.so.7" not found, required by "pfSense-repoc" which I was unable to sanitize with pkg-static upgrade -f -y pfSense-repoc.
      Also with pkg-static check -s -a I get a huge list of missing ones.
      I assume these are leftovers from the failed attempts as everything is running smoothly nonetheless.

      My next option would be to look at the console but I would need to find the cable and whatnot...

      I can just seat and wait for something new to come out, but I would like to be helpful.
      Please let me know if there is anything I could explore to support in case this is of any interest.

      Thank you all!

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @robotox
        last edited by

        @robotox 21% free space? That seems low for any install. Try deleting old boot environments.

        Though, first see if you can revert to a working 24.11 BE. An upgrade should create one, unless you’re saying it reverts to that.

        No, you can’t downgrade without reinstalling.

        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!

        R 1 Reply Last reply Reply Quote 0
        • R
          robotox @SteveITS
          last edited by robotox

          @SteveITS thanks.
          I meant 21% Used. Hence, not a problem from what I've experienced with the SG-1100 where I had to clean up quite a bit.

          Yes, once it fails to boot, after almost 30min, it always falls back to 24.11-RELEASE and goes back on with no issues apart from the normal slowness of pfBlockerNG coming up or Unbound needing a restart some times.

          Thank you for your reaction.

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

            I would be trying to upgrade at the console. Whatever is causing the boot verification check to fail should show there when it boot's into the new BE.

            Do you see am alert when it fails/ Anything beyond just showing that it failed and booted the last good BE?

            R 1 Reply Last reply Reply Quote 0
            • R
              robotox @stephenw10
              last edited by

              @stephenw10 I just see the bell alert mentioning the environments involved in the fall back process yes.

              I guess I will try to find the cable.
              Whatever might be breaking might still break in Stable one day...

              Thanks again.

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

                Indeed, I'm not aware of anything in beta that should present like that so it might well apply to any upgrade on that specific device. Somehow.

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