New Netgate SG-1100 2.4.5-RELEASE-p1 Available Packages Empty
-
@stephenw10 Having the exact same problem with an SG-1100 I purchased directly from NetGate...will request the recovery image (and installation instructions) by email.
-
You can find the install instructions here too:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.htmlThough I just noted the support link needs to be updated there.
Steve
-
@stephenw10 I've followed your instructions and have a live console displayed on my MacBook.
i cant get to the Marvell prompt and i can't figure out how to boot from the usb flash drive.
This is what i am getting:Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 1 second... Type '?' for a list of commands, 'help' for more detailed help. OK
..."run" is NOT one of the commands; there is a boot command, but i don't know how to boot from the USB flash...???
-
That is the FreeBSD loader prompt. The uboot prompt (Marvell>) is accessed before that.
You need to interrupt the boot when it shows:
Hit any key to stop autoboot:
You will then be at the Marvell prompt and you can enter:
run usbrecovery
Steve
-
@stephenw10 I was finally able to reach the Marvell prompt and the upgrade went PERFECTLY.
THANKS for all of your help and assistance! -
I've been trying to replicate this issue and cannot do so directly. A clean install on 2.4.5p1 sees the update to 21.05.2 available and can upgrade to it correctly.
What I think must have happened here is that some bad pkgs were pulled in by attempting to install a package before either upgrading or setting the pkg repo.
If that is the case it can probably be recovered using this procedure:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errorsHowever you can always recover by installing clean form the recovery image.
Steve
-
@jgrantham said in New Netgate SG-1100 2.4.5-RELEASE-p1 Available Packages Empty:
old 2020 firmware on the appliance, which seems unable to update
It definitely should update, I've updated older versions. Though as Steve noted you might need to skip...once or twice to get from 2.4.4 to 21.05 I had to go to either 2.4.5 or 21.02 first, though that's not always necessary (don't recall which, exactly). See https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors notably changing Branch to "Previous stable version" and update that way. That should (right now) make it detect/offer an older version, and you can change the Branch to current and upgrade to 21.05 afterwards.
-
I have this exact issue. Brand new Netgate device from Netgate and 2.4.5-p1 and no updates available and no packages to install. Am I understanding that I need to reload the Firewall to get this to work?
-
You can probably resolve it using the procedure I linked to above.
However having a copy of the firmware is always a good idea.
Steve
-
@stephenw10 - Yeah I tried all those no luck. I submitted a support ticket to get the latest version.
-
Exact same issue with a SG-1100 I received today 1/5/2021 direct from Netgate has the 2020 software.
2.4.5-RELEASE-p1 (arm64)
built on Tue Sep 15 10:30:40 EDT 2020
FreeBSD 11.3-STABLEFiled a support ticket, need that upgraded image.
-
Hmm, I tried to replicate this and couldn't. So to be clear this a was new 1100 dircelty from us that arrived with 2.4.5p1 installed.
You tried to update it during the initial deployment and it was unable to see the firmware update?
Like using the check for updates button in the setup wizard?Steve
-
Correct.
I’ve also tried from SSH using pkg-static (from link in your troubleshooting upgrade docs), it complains that the Repository pfsense-core missing. ‘pkg update’ required.
-
Using
pkg-static -d update
?Hmm it should pull in the updates if the meta file is missing. Can you get the output from that command?
Steve
-
[2.4.5-RELEASE][admin@iotfirewall.localdomain]/root: pkg-static -d update
DBG(1)[28836]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[28836]> PkgRepo: verifying update for pfSense-core
DBG(1)[28836]> PkgRepo: need forced update of pfSense-core
DBG(1)[28836]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
DBG(1)[28836]> PkgRepo: verifying update for pfSense
DBG(1)[28836]> PkgRepo: need forced update of pfSense
DBG(1)[28836]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.conf with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz with opts "i"
DBG(1)[28836]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!
[2.4.5-RELEASE][admin@iotfirewall.localdomain]/root: -
Ok, thanks. Same error then.
Re-installing 21.05.2 clean will certainly get you to it fastest.
We are still looking into this.
Steve
-
One more detail. I am running the device inside of a LAN to create a secure subnet. In order to get access to the device on its default IP I disconnected the WAN port before going through the wizard and gave it a different subnet 192.168.20.0/24 - since the 192.168.1.0 subnet is already in use.
Perhaps that initial step of running the wizard when not connected to the WAN is the variation causing this issue? I’ll do the reinstall tomorrow with some fresh coffee.
-
Hmm, well it would certainly fail the check at that point but as long as the WAN was then connected and the subnets didn't conflict it should be OK.
-
I am up and running on the new firmware and all seems well. Thank you!
A couple of notes:
- Running Etcher on Windows 10. There is a known issue that causes it to fail validation of writing the flash drive. If you encounter that follow these steps.
https://superuser.com/questions/1199823/how-to-prevent-creation-of-system-volume-information-folder-in-windows-10-for/1199824#1199824
Burned an hour trying to check my stick for writing problems.
-
Had to manually install the Prolific USB serial driver for windows.
-
Install Instructions. Between Steps 6 and 7 there is ALOT of console output and reboots, this would be worth mentioning, that you should be patient (and not worry!) while it runs through these steps.
-
@stephenw10 said in New Netgate SG-1100 2.4.5-RELEASE-p1 Available Packages Empty:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html
I am experiencing the exact same issue with a SG-1100 pfSense 2.4.5-RELEASE-p1 (arm64) ordered directly from Netgate. Received my unit about 14 days ago.
DNS is working properly for all domains except repo.netgate.com. DNS cannot resolve repo.netgate.com
*** Can't find repo.netgate.com: No answer