Upgrade Netgate 6100-s from 23.09 to 24.03. not working

getcom

Hello all,

we tried to upgrade to 24.03 from WebUI with no success. We got different error messages.
We then decided to install it new with the Netgate online updater.

The install procedure hangs on partitioning:
"Committing the changes. (This can take a while)..."
It is unrelated if we use UFS or ZFS.

Additionally we cannot open a ticket at the moment. If we click on submit button, nothing happens.

Has anybody the same problems with the new installer?

Kind regards
Ralf

stephenw10

Any ideas what errors you saw when trying to upgrade?

In the installer you can check /var/log/daemon.log if it fails. That should show you where/why it did.

Steve

getcom

@stephenw10
Related to the error message in the WebUI: This was done by an employee . I will ask him if he is in the office next time.

This is the output of the log file:

Jul 8 07:59:33 pfSense-install pfSense-installer[1782]: uri: [POST] /installer/disk-add
Jul 8 07:59:33 pfSense-install pfSense-installer[1782]: POST: 9: [disk=nda0]
Jul 8 07:59:33 pfSense-install pfSense-installer[1782]: uri: [GET] /installer/disk-commit-pre-check
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: uri: [POST] /installer/disk-commit
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: POST: 8: [accept=1]
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[0]: /usr/local/libexec/installer/pfSense-disk-part
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[1]: -F
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[2]: ZFS
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[3]: -S
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[4]: GPT
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[5]: -s
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[6]: 1G
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[7]: -m
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[8]: /mnt
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[9]: -Z
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[10]: stripe
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[11]: -d
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec: argv[12]: nda0
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: Exporting ZFS pools...
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0 destroyed
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0 created
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0 destroyed
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0 created
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0p1 added
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: /dev/nda0p1: 532288 sectors in 16634 FAT16 clusters (16384 bytes/cluster) BytesPerSec=512 SecPerClust=32 ResSectors=1 FATs=2 RootDirEnts=512 Media=0xf0 FATsecs=65 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=532480
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0p2 added
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: partcode written to nda0p2 bootcode written to nda0
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0p3 added
Jul 8 07:59:40 pfSense-install pfSense-installer[1782]: exec output [1]: nda0p4 added
Jul 8 07:59:41 pfSense-install pfSense-installer[1782]: exec: /usr/local/libexec/installer/pfSense-disk-part exited with status: 0
Jul 8 07:59:41 pfSense-install pfSense-installer[1782]: exec: argv[0]: /usr/local/libexec/installer/pfSense-mount
Jul 8 07:59:41 pfSense-install pfSense-installer[1782]: exec: argv[1]: ZFS
Jul 8 07:59:41 pfSense-install pfSense-installer[1782]: exec: argv[2]: GPT
Jul 8 07:59:41 pfSense-install pfSense-installer[1782]: exec: argv[3]: /mnt
Jul 8 07:59:41 pfSense-install pfSense-installer[1782]: exec: /usr/local/libexec/installer/pfSense-mount exited with status: 0
Jul 8 07:59:41 pfSense-install pfSense-installer[1782]: uri: [GET] /installer/fetch-repos

Why it says "Partitioning...
Committing the changes. (This can take a while)..."
This seems to hang forever. After hours it did not change until I stop it.
In the log it seems to be finished with partitioning.

stephenw10

Hmm, yes the logs look like it finished partitioning and is actually failing at the repo connection. But no error is shown.

Anything shown in /tmp/bsdinstall_log or the output of dmesg?

getcom

@stephenw10
We connected the WAN port of the 6100 to a mobile LTE/G5 gateway for upgrade and new installation. The WAN address at this time was IPv6.
As we connected the 6100 to our office net we could install 24.03 without any issue. It seems to be related to the mobile gateway only.

Same problem while upgrading from 23.09.1 to 24.03.
My colleague told me that he got no answer from your server as he tried to update.

Everything was working over the mobile router, also for clients, except the updates and installation.
Again after reconnecting the 6100 to the mobile router we cannot get package information in the package manager even with an IPv4 WAN address.

We use mobile gateways sometimes as backup WAN connection or for new customers where internet is not available until the German Telekom has finished the installation.

We are using this device in passthrough mode: https://teltonika-networks.com/products/gateways/trb500
I assume that the 5g gateway is blocking the requests for whatever reason.
At this time I don`t believe that this has something to do with the new release or the new online installer.
We have to investigate to get the root cause.
If there is any update I will write a note here.

Ralf

stephenw10

Hmm, so it wasn't purely an IPv6 issue?

Do you know what the exact error was?

If you're able to retest I would try to ping ews.netgate.com from the installer CLI if it fails. I'd guess it's a DNS issue.

getcom

@stephenw10

As in the log above, no error message, only timeout.
Yeah, we also thought that it is maybe DNS related. This was the first thing we checked and so we tried different DNS servers without changing anything in the behavior.
Also IPv6 is not the problem. As said we also had no success with IPv4.
Maybe there is a hidden function in the gateway for whatever, e.g. geoip blacklisting or it is something related to the provider of the mobile network.
Is something different on Netgate side? We never had any problem to reach the servers in the past.

Ralf

getcom

@stephenw10
After upgrading the TRB500 to the latest firmware the system is working now. I could install packages on the pfSense which was not possible until now.
Maybe something APN related and 4 over 6 on the provider side.

stephenw10

Weird. Yeah nothing changed at the server end AFAIK.