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

    SG-1100 upgrade horror, now brick

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    15 Posts 5 Posters 1.5k 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.
    • keyserK
      keyser Rebel Alliance @Rico
      last edited by

      @Rico …… Sorry for your loss.

      However - I had a bit of an issue with a 1100 as well - it is a rather fragile device in my experience, and I could not for the life of me get it to boot on 23.01 from USB. In the end I found a 22.05 recovery image I had stored, and I could install that just fine (with ZFS).
      AFter that I just upgraded inline to 23.01 (and now 23.05.1), so….. Maybe give it a shot?

      Love the no fuss of using the official appliances :-)

      1 Reply Last reply Reply Quote 1
      • RicoR
        Rico LAYER 8 Rebel Alliance
        last edited by

        Thanks for your input keyser. I already tried to reflash 22.05 yesterday but no chance.
        Do you remember what your error was?

        -Rico

        keyserK 2 Replies Last reply Reply Quote 0
        • keyserK
          keyser Rebel Alliance @Rico
          last edited by

          @Rico Sorry to hear that.

          No, I can’t remember where it stalled, but I think it was related to some missing U-boot update or something.

          Love the no fuss of using the official appliances :-)

          R 1 Reply Last reply Reply Quote 0
          • keyserK
            keyser Rebel Alliance @Rico
            last edited by

            @Rico Just from the back of my head…. Wasn’t there something with the SG-1100 where it could get the hardware into a non functioning state that required you to power it off completely and wait a while before it would work properly again? I’m sure you have tried that, but just in case….

            Love the no fuss of using the official appliances :-)

            1 Reply Last reply Reply Quote 0
            • RicoR
              Rico LAYER 8 Rebel Alliance
              last edited by

              Yeah wasnt this after U-Boot upgrade? I unplugged the device like 100 times since yesterday and left it with no power over night.
              Now I also tried to boot into pfSense-plus-SG-1100-recovery-21.02-RELEASE-aarch64.img.gz and pfSense-netgate-SG-1100-recovery-2.4.5-RELEASE-p1-aarch64.img.gz but get always the same error 'No valid device tree blob found!'.

              -Rico

              keyserK 2 Replies Last reply Reply Quote 0
              • keyserK
                keyser Rebel Alliance @Rico
                last edited by

                @Rico Well, then it probably is a dead device… Sorry :-(

                Love the no fuss of using the official appliances :-)

                1 Reply Last reply Reply Quote 0
                • keyserK
                  keyser Rebel Alliance @Rico
                  last edited by

                  @Rico I’m sure you tried this as well. Stephen really knows the in’s and out’s of Netgate hardware:

                  https://forum.netgate.com/topic/165397/sg-1100-no-valid-tree-blob-found-after-power-cut

                  Love the no fuss of using the official appliances :-)

                  1 Reply Last reply Reply Quote 0
                  • RicoR
                    Rico LAYER 8 Rebel Alliance
                    last edited by

                    Well the problem is I get this error when booting the installer from USB thumb. The local MMC is empty anyway because it gets erased after 'run usbrecovery' command.

                    -Rico

                    1 Reply Last reply Reply Quote 0
                    • R
                      rcoleman-netgate Netgate @keyser
                      last edited by

                      @keyser said in SG-1100 upgrade horror, now brick:

                      No, I can’t remember where it stalled, but I think it was related to some missing U-boot update or something.

                      Did you open a ticket with TAC>

                      Ryan
                      Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                      Requesting firmware for your Netgate device? https://go.netgate.com
                      Switching: Mikrotik, Netgear, Extreme
                      Wireless: Aruba, Ubiquiti

                      1 Reply Last reply Reply Quote 0
                      • RicoR
                        Rico LAYER 8 Rebel Alliance
                        last edited by

                        Yes, #1746268942 if you like to check.

                        -Rico

                        R 1 Reply Last reply Reply Quote 0
                        • R
                          rcoleman-netgate Netgate @Rico
                          last edited by

                          @Rico Yep, Let's keep digging into the ticket and see what we can come up with.

                          Ryan
                          Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                          Requesting firmware for your Netgate device? https://go.netgate.com
                          Switching: Mikrotik, Netgear, Extreme
                          Wireless: Aruba, Ubiquiti

                          1 Reply Last reply Reply Quote 1
                          • RicoR
                            Rico LAYER 8 Rebel Alliance
                            last edited by

                            My SG-1100 is up and running again after a few more setenv commands 👍
                            Thanks to all supporters!

                            -Rico

                            S 1 Reply Last reply Reply Quote 2
                            • S
                              SteveITS Galactic Empire @Rico
                              last edited by SteveITS

                              @Rico Glad to hear you got it fixed. For posterity I was going to ask if you tried a different and/or smaller USB. This thread is for a 3100 but that worked for this person:

                              MordyT said in After upgrade to 23.05.1, pfSense on Netgate 3100 basically dead:

                              Of note, you can't use just any flash drive - a 5 year old 64GB Kingston USB3.0 drive would crash during the run recovery stage and I had to dig out a 8GB USB2.0 drive for it to work.

                              and...
                              @keyser said in SG-1100 upgrade horror, now brick:

                              Wasn’t there something with the SG-1100 where it could get the hardware into a non functioning state that required you to power it off completely

                              You may be thinking of https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#segmentation-fault-in-pkg ? IIRC that was a one time thing and fixed in later updates. (edit: the driver/condition was fixed so it didn't get into that state)

                              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
                              • stephenw10S
                                stephenw10 Netgate Administrator @Rico
                                last edited by

                                @Rico said in SG-1100 upgrade horror, now brick:

                                No valid device tree blob found!
                                WARNING! Trying to fire up the kernel, but no device tree blob found!

                                That error implies it has failed to load the dtb file at boot. That means the file it tried to load wasn't present. So either it failed to access the file because it couldn't see the media or the file wasn't on the media. Or that the file it was trying to load was incorrect. The latter was the case here, the uboot env that contains the file name was wrong.

                                Steve

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