Ah, cool. 👍

Hmm, well I'm not aware of any specific issue with that CPU platform. Could be something BIOS specific.

I would try a clean 2.7.2 install and see if it fails the same way.

No worries. I'm pretty sure we found and fixed that bug. The next installer build should have that.

@stephenw10 said in pfSense stops updating packages:

@compiz said in pfSense stops updating packages:

it starts with crashed page

How is it failing? Definitely DNS not resolving?

Should probably move this to a new thread if pkgs are updating OK now.

Yeah DNS not resolving, but let's close this topic. It seems to be ok now only facebook show "connected" and "disconnected" all the time, I will reboot it later tonight and I think this will fix everything :)

Thanks for all the help!

@stephenw10 Everything worked. Thank you for your input, it's much appreciated.

Huh. Well that's unexpected. It was clearly loaded the EFI console previously. https://imgur.com/4lH0PK0

Good result though. 😁

Yup 24.02-Beta2 is the current version of the Net Installer. A new version is coming soon. And likely a new naming/numbering scheme with it. 😉

Hmm, well also shouldn't be unique to home/lab. If an NDI is seen as eligible it will show the branches. The subscription type doesn't matter.

The most common issue there is that the NDI changed but that doesn't seem likely here if you were able to just reinstall.

@Patch said in 2.6.0 to 2.7.2 experience:

@lightingman117 yep package all appearing 3 times on my install form many months ago

Packages look normal now, yay!

You upgrade to 2.7.2 yet?

@revengineer said in CE Edition Download???:

When you open the file in an archive manager (I use 7zip), you see and extract the file as pfSense-plus-installer-24.02-BETA2-amd64-20240312-0600.img. Hence the confusion.

FWIW Netgate has posted they’re going to change the numbering scheme. The installer is beta for a few months now. It offers a choice of versions to install.

Oh, I see so if you have this specific UFS install the 2.7.0 kernel will not boot from it. The 2.7.2 kernel will boot from it but you have to go through 2.7.0 because that was the first version that added dynamic repos. Hmm. Yeah I'm not sure what we can do about that at this point. You can always install 2.7.2 clean and restore the config from 2.6.

@stephenw10 said in Version weirdness after 23.05.1 -> 23.09.1 update:

That happens if another instance of pkg-static is running which it is just after an upgrade.

Gotcha, I figured as much. And I would imagine an 1100 without a RAM disk takes a bit longer than a 2100 with, which is most of our clients.

FWIW my second 1100 upgrade last night fared far better, although there was a period roughly around 12:25/12:30 to 12:45 am CDT where pfSense-repoc "failed to fetch the repo data" and the forum was offline, which I'm guessing were related.

@stephenw10

That's excellent, thank you.

Also many thanks for the clarification regarding the CLI upgrade process. I agree that not switching branches automatically makes much more sense.

What about SWAP usage? If you have a 2100-MAX with the SSD

https://forum.netgate.com/topic/188008/sg2100-128gb-ssd-and-swap/

@stephenw10
You are correct. This is exactly what the problem was. EFI partition was never formatted after creation. I followed the steps you outlined and the upgrade completed successfully. Thank you so much for taking the time to figure out the issue and helping me. Have a great day!

@stephenw10 Thank you!

I found that the "DTBFAT0" partition is the partition that works.
pfsense-recovery-firmware-usb-drive.jpg

You should be able to just select all the defaults for the 1100. The installer detects that and sets defaults appropriately.

That should be fixed. If you do see it again reinstall the Wireguard package.