@stephenw10 @Gertjan thank you so much

@stephenw10 Done.

On 24.03 latest (202404160005) it gores more fast or agile, it produces another error but runs then, like there is no error. (feeled) [24.03-RC][root@xxx.xxx]/root: pkg upgrade Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [24.03-RC][root@xxx.xxx]/root: pkg update Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. [24.03-RC][root@xxx.xxx]/root: pfSense-upgrade pfSense-repoc-static: si_get_packages: failed to run the pkg info command: /usr1 pfSense-repoc-static: failed to read the installed pfSense packages >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ...... done Processing entries: .......... done pfSense repository update completed. 736 packages processed. All repositories are up to date. >>> Setting vital flag on pfSense...done. Your packages are up to date

@khashayar said in No /boot/kernel/kernel after upgrade from 2.7.0 to 2.7.2 and reboot: the first pfsense is on a VW I assume you mean VM? If you somehow end up with no kernels available then, yes you would likely need to reinstall. Though in a VM you may have snapshots to roll back to. Steve

@thrx1 said in pfSense CE - is my version really up to date?: email me or alert me in the Web configurator to tell me when there is a new update There’s a newsletter subscription on the bottom of their site, or they post on their blog, or here, and/or Reddit. https://www.netgate.com/blog/rss.xml Showing no update is not a great bug but at least it was in the release notes.

If you have some special edge case it could be useful. The OP here has unexpected output from efibootmgr for example. It usually either fails entirely like you originally saw or returns the list of boot entries without error. Anything other than that would be useful to test on.

@stephenw10 Ok, thank's

No it should not take 30mins. I would check the console to see what's happening. Steve

Yes, it's unexpected to find it boots but then fails later but that can happen. I'd have to guess it's moving the data far faster across when copying out the image and something can't handle it. Good result.

@Antibiotic Reinstall and uninstall again, problem resolved)))

@stephenw10 Yes it did. Took awhile.

Hmm pfsenseboot is in your listed envs above. Is it no longer there? net is shown there too.

@stephenw10 -- thank you! that was it.

@stephenw10 ah, ‘twas late, didn’t look…step 9: https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html

@stephenw10 I appreciate that. You might consider making it easier to find this for others. I spent a few hours with this... frustrating! Thanks for a great product !

@bigbob said in Problem installing net gate 4200: @bigbob the connection I'm looking at says usb10/100/1000 LAN and then all those numbers I posted above. @SteveITS also says domain is home.arpa When you buy a SG-4200, or any other appliance from Netgate, you get a TAC Lite plan, which includes zero to ping support. https://www.netgate.com/support I suggest you check that, they are very good and the support is amazing.

@viragomann thank you

@stephenw10 @Gertjan Reinstall succeeded, thanks for troubleshooting with me! [image: Wk0l-UTk-Mu-G.png]

Just refresh the page. When you first change branch it refreshes the pkg system in the background.

Nope I think that is a real bug. I just replicated it. It's fixed in 24.03.