New Netgate SG-1100 2.4.5-RELEASE-p1 Available Packages Empty

jwarmuth

Device: Netgate SG-1100
Software: 2.4.5-RELEASE-p1
DNS Servers: 9.9.9.9,1.1.1.1

I have a new SG-1100 that I installed about 3 days ago. Used the wizard to set up. This is my first official Netgate hardware, however have been running PFSense for years on PC hardware. The SG-1100 is mostly stock, again only configuration done was through the wizard for now. Tried to add some packages and the package list is blank. Running latest version. Rebooted device. Tried a few things on the google but nothing has worked. No active blocking on the network. I did a pkg update from command prompt and got this:
Updating pfSense-core repository catalogue...
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!

I see alot of "just reinstall" but this frustrates me. It is official hardware from Netgate running software installed by Netgate. It should not arrive broken. Thats my job.

stephenw10

The first thing to try there is a full power cycle rather than a reboot. Actually remove the power to reset the crypto chip.

If it still fails try running at the command line: pkg-static -d update
The output from that should show what's failing.

Steve

jgrantham

@stephenw10

Same issue with a brand new sg-1100 with image. Attached is the output of that command.

Edit1: Wanted to confirm I did the full halt and power cycle, with no change.

Thanks,

Justin

[2.4.5-RELEASE][admin@pfSense.localdomain]/root: pkg-static -d update
DBG(1)[15949]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[15949]> PkgRepo: verifying update for pfSense-core
DBG(1)[15949]> PkgRepo: need forced update of pfSense-core
DBG(1)[15949]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
DBG(1)[15949]> PkgRepo: verifying update for pfSense
DBG(1)[15949]> PkgRepo: need forced update of pfSense
DBG(1)[15949]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.conf with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.conf with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.conf with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo01.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz with opts "i"
DBG(1)[15949]> Fetch: fetching from: https://repo00.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz with opts "i"
pkg-static: https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-pfSense_factory-v2_4_5/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!
[2.4.5-RELEASE]admin@pfSense.localdomain]/root:

stephenw10

Is it able to resolve anything? In Diag > DNS Lookup for example?

jgrantham

@stephenw10
No, the packages still are not listed in the gui and can't install from shell.

What is the "Bad Request" result about?

stephenw10

Right but can it resolve any url?

jgrantham

@stephenw10
Ah, yes, it is able to resolve. Besides this package issue everythinf seems to be working okay. The update page for pfsense itself seems to contact update server okay as well.

I can also ping and traceroute by dns name from shell no problem.

DNS Lookup
www.netgate.com
Hostname
Results
Result Record type
199.60.103.30 A
199.60.103.226 A
2606:2c40::c73c:671e AAAA
2606:2c40::c73c:67e2 AAAA
1826203.group3.sites.hubspot.net CNAME
Timings
Name server Query time
127.0.0.1 1 msec
1.1.1.1 54 msec
66.185.96.3 15 msec
1.0.0.1 57 msec

Thanks for your help,

Justin

stephenw10

Hmm, those files are certainly present. Is the system date/time correct?

Since you're several versions behind you might opt to just install 21.05.2 clean. That's probably going to be the quickest way back to full function. Email tac@netgate.com to request the recovery image.

Steve

jgrantham

@stephenw10
Yes the time is correct. I will just plan on the re flashing soon.

Thanks for the quick responses.

Justin

jgrantham

@stephenw10
Just an update, I am all up and running from that latest recovery image. Thanks for your quick help.

Based on OP and my same experience, I guess the main issue was Netgate shipping the old 2020 firmware on the appliance, which seems unable to update to the modern versions through the normal updater? Similarly the pkg system fails to talk to current repos correctly is my guess from the "Bad Request" issues.

Justin

stephenw10

Hmm, that should still be updatable. In fact you should be able to update from any earlier version though in much older versions you may need to go in several steps.
Did that come directly from us? Recently?

Steve

jgrantham

@stephenw10
Yeah ordered straight from Netgate, arrived middle of last week. The update page would indicate that 2.4.5 was the latest and up to date, so not sure.

Justin

stephenw10

Hmm, well hard to say what might have caused that. That's not the expected behaviour though.

Quasaur

@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.

stephenw10

You can find the install instructions here too:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html

Though I just noted the support link needs to be updated there.

Steve

Quasaur

@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...???

stephenw10

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

Quasaur

@stephenw10 I was finally able to reach the Marvell prompt and the upgrade went PERFECTLY.
THANKS for all of your help and assistance!

stephenw10

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-errors

However you can always recover by installing clean form the recovery image.

Steve

SteveITS

@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.