@Dobby_ all is fine here too. Just the displeasure of having to go through all this instead of a smooth upgrade.

Yeap same issue here.

Too scared to try again.

Don't want to brick it.

@Dobby_
Ok. I was able to install it on the network. Breath of fresh air.

Yet do I have to set it up from scratch or I can restore from a backup? Even if it’s completely different machine with different interfaces etc?

Believe the Hyper- V boot issue was fixed in 23.05. Problem is we can't get from 2.6 to 23.05 direct yet. https://redmine.pfsense.org/issues/13895

@nedyah700 I'm SO glad I didn't fubar my install. I'm far from an expert and it would have probably taken my tiny company offline for a day.

@SteveITS

24.05.2023 - 20:29 h (8:29 PM)
The last upgrade went faster, it was not rebooting in 10 seconds, it went more smooth and liquid and on
top of all it was also upgrading 3 pkg`s, well done.

2.7 devel vuln 4.jpg 2.7 devel vuln 3.jpg

@goulou said in Smooth update to 23.05 w/ a few comments on DNS Resolver forwarding over SSL/TLS:

Assuming you're right then I guess my question would be how else could I have otherwise restored DNS Resolver at that point? Just re-saving the DNS Resolver settings as-is/ no further changes? If so i could try that on at least 1 other not yet upgraded NG appliance later today.

Yes, just re-saving the settings without pfBlockerNG installed would normally be enough. You might want to double check that the custom options area is empty (or at least has no pfBlocker settings) and that the Python mode script is not set to something for pfBlocker.

@jlw52761 said in Upgrade from 2.6 to 22.05, not 23.01:

I did think about taking a backup of the 22.05 existing firewall then restore to the new 23.01 firewall, but I don't see that working well either due to the differences, but maybe it's worth a shot.

I would think that too, because it is better solve the
problems out (if there will be anything) then staying on a version that will be perhaps not supplied any
more with upgrade or updates for pkg´s on top.

So then you are on 23.01 and will be able to switch between the both 23.01 and 23.05 versions.

@gwaitsi said in 23.01 -> 23.05 Upgrade GUI not updated - upgrade corrupted:

I copied the files from my other 23.01 system

That won't work...just re-register...it's free.

@rcoleman-netgate this sounds like my issue. I upgraded to plus when it came out, so i probably need a new token as you say. it is not letting me go from CE to 23.01 after failed 23.05 upgrade.

what do i have to do?

I initially had some errors when trying to upgrade through the GUI. Ended up SSHing into console and was able to upgrade no problem from there with "pfSense-upgrade".

@wastapi said in Upgrading from 2.4.5 to 2.5.0 fails: mountroot waiting for device /dev/gptid:

@dobby_

1-I am not the OP. But I am on Linux and have the very same issue. It is waiting for device.

I was answering to you, because the original thread was
from the - Feb 24, 2021, 11:53 PM

2-I think the MOST reliable is not on archive.org (from your link) but the OFFICIAL website

He was asking;
I had to find a previous 2.4.5 version to reinstall.

And you wrote;
same problem here. Did you solve it?

So I thought you will be also on the need to get hands
on a version 2.4.5_p1

@yuryk

If you don't specify 'something', this :

ce374e1e-7370-4192-8b06-32173c657b86-image.png

will ask for an A record.

This :
d6e1a4fd-66eb-4922-a669-9ae4fb866379-image.png

doesn't use 'A' (or AAAA) records 😊

Check the "pfSense Packages" forum : the top most post : DNS Broken for pkg.pfsense.org

@mohkhalifa said in Packages are not available:

I don't have the option of "Automatically create a boot enviroment prior to performing system update"

That option would be present if you have installed pfSense 'from scratch - from firmware file - from USB' and you have chosen 'ZFS' as a file system.
That is, if that option exists for your hardware.

ZFS is nice to have, as you can create a 'snap' from your current pfSense, and try out a new upgrade/update, and go back if needed.

@jimp Thanks, that seemed to get rid the error. However since I am moved on from OpenVPN to WG, this was bit of a forcing function for me.

It varies based on hardware, config complexity, and numerous other factors. There is no way to know beforehand how long it will take, so it just retries periodically. There is already a feature request in to get rid of the confusing countdown timer:
https://redmine.pfsense.org/issues/14008

Thanks both!

Close to midnight here, but thanks for the super-rapid responses ...tomorrow morning I'll give it a go!

Chris

@scurrier it went pretty well. Only things that threw me off were:

The serial console was somehow cutting off some of the text at the login screen before rebooting, even though I had already configured my terminal correctly in the last, leading me to think my settings were wrong. They weren't, it was some pfsense console problem fixed by rebooting.

The password prompt for the encrypted config has a timeout but doesn't say so, so when I went to my password manager to get the password, it timed out and I had to reboot and try again.

I'm getting the same error.

I'm running on VMware ESXI 8.0U1.

I have tried 3 times to upgrade to pfSense Plus from CE 2.6.0 brand new install and it fails each time.

Why is it that we don't have a direct upgrade to pfSense Plus? Clearly the upgrade path doesn't work from CE 2.6.0.

On another note, I tried upgrading from CE 2.7.0 and the same result as well.

And lastly, I have noticed I get a SCSI error if there is a VMware snapshot on the machine during a boot of CE 2.6.0. If I remove the VMware snapshot and then reboot, no error. (This is separate from the certs.inc fatal error though and doesn't seem to affect it.)

Can anyone figure out what's causing this problem? Even NetGate's own hardware is failing with this error.

IMG_9122.jpg

Yes, it will be once 23.05 is released.