23.09.1 → 24.11: GUI Selects 24.11 but Active Repo Remains 23.09.1

stephenw10

Hmm, so it appears to have the 24.11 repo configured already. I assume pfSense-upgrade -d still fails with errors?

stephenw10

24.11 is still ancient you could just reinstall to 26.07 directly. Your NDI will be valid in the installer.

DobbsRx

Thanks. Since this is currently 23.09.1 on ZFS, are you recommending a clean install of 26.07 using the installer's Configuration Restore to recover the existing config from disk? And is a direct restore of the complete 23.09.1 config to 26.07 supported/recommended in this case?

stephenw10

Yes I would do that. Though I would also be sure to have a local backup too!

Yes the config from 23.09.1 will import directly into 26.07 either during the install or after.

It should be pretty seamless.

DobbsRx

@stephenw10

Done and done thanks for the help. Successfully updated to 26.07 with everything imported appropriately! Only issue was figuring out why dpinger was unhappy and not wanting to work and finding a stale VIP causing the issue.

edit: and this hint.acpi_spmc.0.disabled=1 kernel panic I just fixed as well lol

rainer_d

I have the same problem. I cannot update beyond 23.09.1.

And I actually have a Netgate 2100 device.

I was able to update from 23.09 to 23.09.1 but that's it.

Then I click on that reload button:

and it shows:

When I switch to the other option:

I have no idea how to do a full re-install on a 2100 (and I want to avoid that very much, TBH). As I have that "device only detects the GBIC when it's inserted after it has cold-booted"-problem, I am not even keen on rebooting....

stephenw10

Try upgrading from the command line to see what error it's showing: pfSense-upgrade -d

And by that I mean the real command line not the gui command prompt.

rainer_d

@stephenw10

OK, I did that and then it ran out of disk-space.
Then I removed some old BEs and then it worked.
Now on 24.11.

However, when I try to update, it says another instance is already running.

There's a notification about
"
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2026-10-04 01:53:26
"

But I'm happy it booted up again....

[24.11-RELEASE][root@pfSense.example.org]/root: bectl list
BE                                    Active Mountpoint Space Created
auto-default-20261003232725           -      -          573M  2026-10-03 23:27
default                               -      -          2.94M 2026-10-04 01:21
default_20261004012041                NR     /          3.48G 2026-10-04 01:34
default_20261004012041_20261004013331 -      -          952K  2022-06-22 21:27
[24.11-RELEASE][root@pfSense.example.org]/root: df -h
Filesystem                                           Size    Used   Avail Capacity  Mounted on
pfSense/ROOT/default_20261004012041                  3.7G    1.1G    2.6G    31%    /
devfs                                                1.0K      0B    1.0K     0%    /dev
pfSense/var                                          2.6G     12M    2.6G     0%    /var
pfSense/tmp                                          2.6G    256K    2.6G     0%    /tmp
pfSense/home                                         2.6G     96K    2.6G     0%    /home
pfSense/var/log                                      2.6G    4.6M    2.6G     0%    /var/log
pfSense/var/db                                       2.6G    6.1M    2.6G     0%    /var/db
pfSense/var/cache                                    2.6G    104K    2.6G     0%    /var/cache
pfSense/var/tmp                                      2.6G    120K    2.6G     0%    /var/tmp
pfSense/ROOT/default_20261004012041/cf               2.6G    1.5M    2.6G     0%    /cf
pfSense/ROOT/default_20261004012041/var_cache_pkg    2.9G    318M    2.6G    11%    /var/cache/pkg
pfSense/ROOT/default_20261004012041/var_db_pkg       2.6G     10M    2.6G     0%    /var/db/pkg
tmpfs                                                4.0M    128K    3.9M     3%    /var/run
devfs                                                1.0K      0B    1.0K     0%    /var/dhcpd/dev

stephenw10

@rainer_d said in 23.09.1 → 24.11: GUI Selects 24.11 but Active Repo Remains 23.09.1:

when I try to update, it says another instance is already running.

That should resolve itself after a minute. Unless it really can't check for some reason.

When you connect to the dashboard it initiates a check so it can display available upgrades in the widget. That can take some time to complete in the background.

SteveITS

It may take longer on a 2100 in my experience but it will eventually log a pkg upgrade IIRC, and clear. Also IIRC it’s faster in more recent versions.

rainer_d

@stephenw10

OK, after letting it sit for the night, that warning has now disappeared.

I will continue later today.

Does the GUI clean up old boot-environments automatically?
The shell-command didn't.

SteveITS

@rainer_d said in 23.09.1 → 24.11: GUI Selects 24.11 but Active Repo Remains 23.09.1:

Does the GUI clean up old boot-environments automatically?

Unfortunately, no.

stephenw10

Indeed, not yet. It's something that's planned though because it's clearly a common problem.

rainer_d

@stephenw10
OK, I just need to know that I need to do it myself.

rainer_d

Thanks everybody!

stephenw10

You should see 26.07 eventually.

SteveITS

said in 23.09.1 → 24.11: GUI Selects 24.11 but Active Repo Remains 23.09.1:

may take longer on a 2100 in my experience but it will eventually log a pkg upgrade

FWIW I'm upgrading an older router now. On the step after 24.11 changing the branch to 25.11 it took about 7 minutes to log "pkg upgraded: 1.20.8_2 -> 1.21.3_4" after boot.

From 25.11 to 26.07 it took about 10? seconds for pkg to upgrade and maybe another 40-60 seconds for the "in progress" warning to clear. So hopefully fixed now.