Never mind. Just saw what I was missing in that image. The partition is 200M, not 200K. Carry on!

@dobby_ said in System > Update > Branch > Show nothing (after Upgrade to 23.0.1):

I was looking under that link here pfSense roadmap

I had assumed that was the case.
Those 5 bugs apply only to the plus branch (will not be incorporated in the community version)

However if you look at most of the entries for 2.7 you will see

The search I linked was for target version 23.05 or Plus version: 23.05 which gives a better idea of what is outstanding.

Agree...

What I am trying to do is not waste my time waiting for a download over a small bandwidth connection.

I would like to preload / download the upgrade package... which could take some time...

Once downloaded, then I can come back and upgrade...

Similar to TrueNAS in how they allow you to download the upgrade... then later come back at a convenient time to actually do the upgrade...

Can a preload be done ?

Thanks.

@steveits That's funny - the 3100 is never mentioned in the posts... I don't know how people interpret that to include them.

BTW the post is updated with a "how to check if it effects your device" check.

@wifi-will said in Unable to roll back from 23.01:

@steveits how can we install zfs?
I am not familiar with zfs and cant find a setting or package.
Boot environment just says it does not support

That's not something you can install, you have to freshly install pfSense with ZFS from scratch so the disk layout and ZFS pool on the disk can be created. If you're still running UFS sadly you can't simply install something and switch, that's not something the filesystem can do :)

If you install with a USB key, you can select Auto (ZFS) or Auto (UFS) - always use ZFS until specifically wanting UFS for a special reason.

Cheers

@nick-loenders The only solution I found was to physically visit the unit and perform the upgrade with a file provided by netgate support.

@scourtney2000

I was able to figure this out! I had a DNSSEC-capable DNS server, 1.1.1.2 configured and it was causing issues with syncing up with pfSense updates and packages. I rolled back to 1.1.1.1 and I the 'update' and 'package' functionality started working again.

@rcoleman-netgate Even though Steve is going to do it, I'll do it also. Perhaps more than one request might give it a bit more credence.

Thanks,

Mike

@trunet said in Suricata on pfSense plus 23.01 fails to install:

@bmeeks Would you know how to fix it?

Did your Internet connection have any issues during the attempted install? The error message is basically saying it either failed to download one of the required dependency files, or else the file it got was corrupted and the checksum/size did not match up with what was anticipated.

First, I would repeat the install attempt to see if it works the second time. If it fails again, then I'm not sure what could be wrong. One thing I do know is that package builds were just turned back on this morning for 23.01. They had been temporarily disabled following the 23.01 rollout last week. Perhaps you were unlucky enough to attempt a package install before everything got fully up and running on the Netgate side ???

@rcoleman-netgate

Thanks. I received a link to an image to directly install 23.01 on the two SG-1100s. I did one last Friday, worked fine. I plan to do the second one shortly. These were not in production so there was no useful configuration to back up before the online update attempts bricked them.

Once they are both working, I plan to use them to become familiar with new features of 23.01 while I wait for clear stability before upgrading the SG-3100 that is a production device.

Best wishes,

Ken

@emmaylots said in Upgrade from 22.05 to 23.01 fails device not booting:

Trying to mount root from ufs:/dev/ufsid/63e6b2a98b3567af [rw,noatime]...

Whatever hardware you're on if you are not on a 3100 I would install from the 23.01 install image (request in the link in my signature) and go ZFS.

There is no reason to use UFS on an 1100.

@Gertjan
@johnpoz
Thank you both for the good information and encouragement.
I was able to successfully update my way back to 22.05!
Johnpoz, your graphical description helped me go to: System/Update/System Update/Branch/pfSense Plus Upgrade where I was indeed able to upgrade from pfSense 2.6.0 CE to pfSense Plus version 22.01
After that upgrade completed, I was able to update to 22.05 like you suggested:

fc917bd1-4f79-43c6-8e15-3b4c6694b662-image.png

I selected the PREVIOUS version, it was as simple as that.
After running on 22.05 for a few minutes, I performed a restore by picking the XML file that I had made just prior to attempting to update to 23.01 three days ago.

pfSense and my freeRADIUS setup are now completely restored.

For now, I will sit back and read the Installation topics as they relate to 23.01 and decide when to make the leap.

BTW, pfSense is running on Dell Optiplex 3060 SFF both at home and at work.

Thanks again, you two!

@nguser6947 said in Procedure to offline update hot spare to latest revision?:

@keyser The only package I'm using is pgblockerng.

That is the best package for pSense - period.
But it is also the worst for what you are looking ti do. Because depending on your setup that will either autocreate and sort your firewall rules or create aliasset that cannot resolve when it’s not installed

@joeker Your issue is not related to this.

Open a ticket with TAC. https://go.netgate.com/

@steveits If I set it to Previous Stable Version for its branch, at first it says it is unable to check for updates, but after letting it sit a minute it does tell me it is up to date. While it is set to Current Stable Version it simply says "unable to check for updates"

@pdavis Same! I re-upgraded and didn't have the package issue again. I was also having the "Your device has not been registered for pfSense+" error message which I resolved as well. I don't think they were related but sharing just in case.

Not yet. We need to run testing now it's been released but it should be possible.

@jrey Nice, thanks for the feedback. I noted the time just to say to wait...in the past people have rebooted early and interrupted the update. The default page starts counting at something like 2-3 minutes implying that's all it should take.