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

    Online Network Installer SG-1100 "Cannot Reach the Netgate Servers, Please verify your network Settings"

    Scheduled Pinned Locked Moved
    Official Netgate® Hardware
    2
    15
    636
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Mmm, that doesn't look good. However that wouldn't prevent the installer connecting.

      It shows '1 disk found' so it must have removed most of the formatting. I assume you ran usbrecovery at some point?

      G 1 Reply Last reply Reply Quote 0
      • G
        gdb @stephenw10
        last edited by gdb

        @stephenw10 Yes on usbrecovery.

        The sequence of events was:
        I saw I was a release behind on the device, so I installed the update. When that was complete, I had the device reboot itself. It did not come back up.

        I connected to the console and it booted, (But was not responding) so I pressed the reset button to reset to factory defaults.

        After another reboot all that I received on the console was a repeating series of:

        FreeBSD/arm64 (Amnesiac) (ttyu0)
        -sh: /etc/rc.initial: not found

        And it was unresponsive to any keys.

        I then downloaded and tried the usbrecovery and hit the "Cannot reach the Netgate servers" error and posted this message, and powered the device down and went to bed.

        This morning when I received your reply, I powered it up to change the LAN subnet as you suggested and when I ran usbrecovery, I captured the above logging output.

        I later opened a TAC case and the response was to follow these instructions:

        https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html#emmc

        But the device will not boot beyond outputting those errors above.

        Thanks again for your responses!

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

          The log output above doesn't look like it tried to boot from USB I don't see where you ran usbrecoery.

          I assume it can boot from the USB image though as it would have had to to reach the netgate servers error message.

          You need to set the LAN IP in the installer. It defaults there to 192.168.1.1 and that conflicts with the WAN IP/subnet passed by DHCP.

          Alternatively you could setup a different internal subnet on the 4100, on a separate interface perhaps, and connect the 1100 there. That would also remove the conflict.

          G 1 Reply Last reply Reply Quote 0
          • G
            gdb @stephenw10
            last edited by

            @stephenw10 Sorry, the console output seems to overwrite some of the previous output.

            I just restarted the process and here is the console output from power-up to the marvell>> prompt before I enter the run command:

            TIM-1.0
            WTMI-devel-18.12.1-1a13f2f
            WTMI: system early-init
            SVC REV: 5, CPU VDD voltage: 1.248V
            NOTICE: Booting Trusted Firmware
            NOTICE: BL1: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
            NOTICE: BL1: Built : 10:16:46, Oct 13 2021
            NOTICE: BL1: Booting BL2
            NOTICE: BL2: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
            NOTICE: BL2: Built : 10:16:50, Oct 13 2021
            NOTICE: BL1: Booting BL31
            NOTICE: BL31: v1.5(release):1f8ca7e-dirty (Marvell-devel-18.12.2)
            NOTICE: BL31: Built : 10

            U-Boot 2018.03-devel-18.12.3-gc9aa92c-dirty (Oct 13 2021 - 10:14:54 -0300)

            Model: Netgate 1100
            CPU 1200 [MHz]
            L2 800 [MHz]
            TClock 200 [MHz]
            DDR 750 [MHz]
            DRAM: 1 GiB
            Comphy chip #0:
            Comphy-0: USB3 5 Gbps
            Comphy-1: PEX0 2.5 Gbps
            Comphy-2: SATA0 6 Gbps
            SATA link 0 timeout.
            AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
            flags: ncq led only pmp fbss pio slum part sxs
            PCIE-0: Link down
            MMC: sdhci@d0000: 0, sdhci@d8000: 1
            Loading Environment from SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 64 KiB, total 4 MiB
            OK
            Model: Netgate 1100
            Net: eth0: neta@30000 [PRIME]
            Hit any key to stop autoboot: 0
            Card did not respond to voltage select!
            ** No partition table - mmc 1 **

            Reset SCSI
            scanning bus for devices...
            ** Bad device scsi 0 **
            BOOTP broadcast 1
            DHCP client bound to address 192.168.1.226 (0 ms)
            *** Warning: no boot file name; using 'C0A801E2.img'
            Using neta@30000 device
            TFTP from server 0.0.0.0; our IP address is 192.168.1.226; sending through gateway 192.168.1.1
            Filename 'C0A801E2.img'.
            Load address: 0x7000000
            Loading: *
            TFTP error: 'illegal (unrecognized) tftp operation' (4)
            Starting again

            TFTP error: 'illegal (unrecognized) tftp operation' (4)
            Starting again

            *** ERROR: serverip' not set *** ERROR: serverip' not set
            libfdt fdt_check_header(): FDT_ERR_BADMAGIC
            libfdt fdt_check_header(): FDT_ERR_BADMAGIC
            No FDT memory address configured. Please configure
            the FDT address via "fdt addr <address>" command.
            Aborting!
            No FDT memory address configured. Please configure
            the FDT address via "fdt addr <address>" command.
            Aborting!

            Starting EFI application at 07000000 ...

            Card did not respond to voltage select!
            Scanning disk sdhci@d0000.blk...
            Disk sdhci@d0000.blk not ready
            Scanning disk sdhci@d8000.blk...
            Found 1 disks
            WARNING: Invalid device tree, expect boot to fail
            efi_load_pe: Invalid DOS Signature

            Application terminated, r = 9223372036854775806

            Marvell>>

            Then enter the command and:

            Marvell>> run usbrecovery
            switch to partitions #0, OK
            mmc1(part 0) is current device

            MMC erase: dev # 1, block # 0, count 4194304 ...

            Then it looks like a screen clear is issued and the output jumps to the top of the screen and starts overwriting and this is what I can copy from the scrollback buffer at that point:

            Consoles: EFI console
            Reading loader env vars from /efi/freebsd/loader.env
            Setting currdev to disk0:
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            FreeBSD/arm64 EFI loader, Revision 1.1
            (Tue Mar 12 06:35:53 UTC 2024 root@freebsd)
            Marvell>>
            Command line arguments: loader.efi
            Image base: 0x7000000
            EFI version: 2.70
            EFI Firmware: Das U-Boot (rev 0.00)
            Console: efi,comconsole (0)
            Load Path: /\armada-3720-sg1100.dtb
            Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/eMMC(1)/eMMC(0)
            Setting currdev to disk0:
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273600 size=1 status=7304 blocks erased: OK
            MMC: block number 0xe90e81 exceeds max(0xe90e80)
            efipart_readwrite: rw=1, blk=15273593 size=8 status=7
            Setting currdev to net0:
            net0: cannot set rx. filters (status=3)

            The device is not responding to the console at that point, but it will eventually reboot and display this, although it looks like the screen clears again:

            "Synchronous Abort" handler, esr 0x96000004
            elr: fffffffffe6745f0 lr : fffffffffe6745a4 (reloc)
            elr: 000000003e5b45f0 lr : 000000003e5b45a4s) found
            x0 : 0000000000000000 x1 : 00000000000000001 Storage Device(s) found
            x2 : 0000000000000000 x3 : 000000000000ff01
            x4 : 000000003c7fae82 x5 : 00000000000000d1
            x6 : 000000000000000f x7 : 0000000000000000
            x8 : 383533003e610570 x9 : 000000003e61282c
            x10: 000000003c7fa990 x11: 0000000000000000
            Consoles: EFI console 13: 000000000000000a
            Reading loader env vars from /efi/freebsd/loader.env
            FreeBSD/arm64 EFI loader, Revision 1.100000
            (Tue Mar 12 06:35:53 UTC 2024 root@freebsd)
            x20: 000000003e612bf0 x21: 000000003e610154
            Command line arguments: loader.efi000008
            Image base: 0x70000005: 0000000000000003
            EFI version: 2.705 x27: 00000000a5860100
            EFI Firmware: Das U-Boot (rev 0.00)10080
            Console: efi,comconsole (0)
            Load Path: /C0A801E2.img
            Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/MAC(f0ad4e2f4bd4,0x1)/
            Setting currdev to net0:
            net0: cannot set rx. filters (status=3)

            I never get to the initial Freebsd boot screen where you can pause the boot, set parameters, and then continue to boot to single or multi-user

            G 1 Reply Last reply Reply Quote 0
            • G
              gdb @gdb
              last edited by

              To be clear, I never get any of the normal installation prompts or the choices to set the interfaces.

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

                Hmm, but you did yesterday when you hit the connectivity error? So something has changed since then?

                G 1 Reply Last reply Reply Quote 0
                • G
                  gdb @stephenw10
                  last edited by gdb

                  @stephenw10 Yes, It was progressing through the boot process yesterday and presented the dialog about the Interfaces then.

                  The only thing that happened after I posted the message you responded to today is that I powered it down overnight.

                  I powered it back on when I got your message/suggestion this morning and it had these errors at that point.

                  Could the eMMC errors have caused the initial failed reboot after upgrade? This device has been running flawlessly for 8-9 months, then I upgraded it and rebooted afterwards and it did not come back up successfully.

                  The 1100 is only 10 months old.

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

                    Then if the eMMC really is bad it should be replaced.

                    But it appears as though it's not booting the USB drive. Try moving the USB stick to the other socket. Try re-writing the image to the USB drive.

                    G 1 Reply Last reply Reply Quote 0
                    • G
                      gdb @stephenw10
                      last edited by

                      @stephenw10 Thank you. I had rewritten the thumbdrive earlier that day (New PNY thumbdrive) and was seeing the activity light on the thumbdrive flicker after run usbrecovery so I assumed it was reading the drive.

                      In any case, strangely today, after powering on the netgate, usbrecovery worked and I managed to the the eMMC utilities installed:

                      eMMC Firmware Version: 18203b19
                      eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x06
                      eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x0b
                      eMMC Pre EOL information [EXT_CSD_PRE_EOL_INFO]: 0x01

                      So not great, but ok.

                      The device is running, so I am going to put it back online for now.

                      Thinking about when I will need to replace it: Is the eMMC replaceable or can the SG-2100 run entirely off the M.2 and just not use the eMMC?

                      Thanks again for your help, and your patience!

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

                        @gdb said in Online Network Installer SG-1100 "Cannot Reach the Netgate Servers, Please verify your network Settings":

                        Is the eMMC replaceable or can the SG-2100 run entirely off the M.2 and just not use the eMMC?

                        A 2100 can run from m.2 SSD yes. However I thought this was an 1100 which has no SSD capability.

                        G 1 Reply Last reply Reply Quote 0
                        • G
                          gdb @stephenw10
                          last edited by

                          @stephenw10 It is, My wording was not clear, I meant :When I need to replace the 1100, Is the eMMC in the 2100 replaceable, or can I run the 2100 entirely off of the M.2 drive? (just to avoid being in the total replacement situation again!)

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

                            Ah, OK. The eMMC is fixed and non-replacable in both. The 2100 can boot and run from an m.2 SSD at any time including if the emmc fails.

                            1 Reply Last reply Reply Quote 1
                            • N nachorobot referenced this topic on
                            • First post
                              Last post