I could resolve one issue. The problem with deleted snapshots was because of my backup process (xsibackup) was running wild. I was able to correct this. But the main issue is still on the table.

For info: I upgraded my v2.2.6(amd64 full) to v2.3.1 dev(didn´t see that 2.3 -rel was out…) After the upgrade I had -27Mb free diskspace of my 8Gb root. No package could do the upgrade due to no diskspace. Made a fresh install of 2.2.6 with old config and upgraded to 2.3 and this time it worked. /illern

That's weird.  Unchecking the box for the host on the master should disable it from being a sync target.  However, there were some fixes to the XMLRPC sync code by another forum member last year.  Those fixes corrected some longstanding things, but they may have inadvertently broken the "disable sync" for individual targets. The XMLRPC sync page is up for the some major rework soon, and I will be sure all this is addressed then. Bill

Hi Jimp, thanks for looking at my issue(s). I verified that box, and I have 3 rows in the /boot/loader.conf.local: ahci_load="YES" kern.cam.boot_delay=10000 kern.ipc.nmbclusters="1000000" I checked it against the "master" (still on 2.2.6), and see no difference, even the file TS is the same.

Thanks a lot!!! That solved it.

Big thanks all!! Appreciate the help. Will check into all suggestions.

https://forum.pfsense.org/index.php?topic=109690.msg610721#msg610721

Any indication you're running out of disk space? Probably would log in the system log. If you have additional packages installed it's possible to be down low enough on free space that it wouldn't have enough room to write the file out to /root/ and then it'd fail verification. Not likely an upgrade to 2.2.6 would succeed either, unless it is disk space and you happen to have enough to fit 2.2.6 (2.3 is ~80 MB bigger).

yeah i have it hidden in a closet and headless i needed to hook up a monitor find the cables hook up a usb rom drive lots of noise in the middle of the night and so on and so on lets say i'm way not happy ;) I downloaded the live iso with my phone and burned the iso its now botting for the first time. I'm also copying the backup to my usb stick so i wil do a full restore in a few minutes too but thise sucks ig time its 6 am in the the netherlands :(

@cmb: That's what happens when you have the wrong URL hard coded under System>Firmware, Updater Settings tab. Now in 2.3 and newer, it's impossible to switch architectures, since it's no longer doing the monolithic updates of old. That explains it. I hadn't noticed that the URL was incorrect. @cmb: Before upgrading any 2.2.x or earlier system, it's a good idea to double check System>Firmware, Updater Settings, and make sure you have "Use an unofficial server for firmware upgrades" unchecked. Then you'll stay with whichever architecture you have installed. With the old style of updates you could (with some caveats) switch back with another upgrade to the other architecture, but that's not possible once you're up to 2.3. Backup your config, reinstall 64 bit, restore. I did notice that the option to manually supply the "firmware" is gone now. I surmised that this had to do with the move to the package methodology. I made a config backup before performing the upgrade, and was able to use that to successfully restore the config and RRD data post reinstall to 64-bit. Thanks for your answer. I appreciate it.

Thank you - and indeed it all worked smoothly - perfection. Thanks again!

Thanks for your help and hard work on 2.3!

@cmb: @chpalmer: I figured it was because I had gitsynced earlier today. Guessing in your case you gitsynced to RELENG_2_3, which is 2.3.1. I did.  :)