Make a USB boot drive of 14.1-RELEASE and test first if you can boot the server BIOS/UEFI into LiveCD. Then check the current running software if it's compatible with the latest versions like php,mysql,python etc.
What services do you currently provide with this server?
When I upgrade my server I first make a full backup which i restore into a virtual machine where i perform a test upgrade and take notes of the upgrade steps. Sometime there's minor changes between the upgrades but if you skip several upgrades those changes accumulate and it will be hard to track all of them.
Before starting any minor/major version upgrade, I'd try getting 11.3-RELEASE-p3 patched to p14 as I understand that to be the latest for 11.3-RELEASE. AFAIK you should be able to just fetch and install these patches even though 11.3-RELEASE has gone EOL.
Got to 13.0, pkg-static -f ran without errors but the headaches started with portmaster -af. Constant abort. Tried removed the port where the STOP occurred via pkg remove but as you all know it doesn't just remove the pkg it removes a bunch of packages.
Also looked at /etc/make.conf and saw old line for perl5.30 which doesn't exist. Commented out the line and currently running portmaster -af again and it breaks. So this is not going to work. running now freebsd-update install (the final one)
Now the issue will be that so many pkg's have been removed this web server with pgsql will not run. Apache has been removed earlier when pkg remove was run.
I think it might be simpler to recreate the VM with july 28/24 backup and that will end up with a running FreeBSD 11.3-p4 as it was.
feebsd-update page states to run portmaster -af, followed by freebsd-update install, will running portmaster -af AFTER the final freebsd-update install (for 13.0) work?
Hi, I am looking for help trying to understand what is taking to so long. I started a jail upgrade from 12.2 to 14.1 on Sunday. Previous ones have been long already, like one day. Okay. This one has been running for four days already. Here's the status: The following files will be updated as...
Assuming a restore of the FreeBSD 11.3 VM from 3 days ago, it might be best to follow the portmaster man page and reinstall all before running just portmaster -af
1. portmaster --list-origins > ~/installed-port-list
2. Update the ports tree
3. portmaster -ty --clean-distfiles
4. portmaster -Faf
5. pkg delete -afy
6. rm -rf /usr/local/lib/compat/pkg
7. Back up any files in /usr/local you wish to save,
such as configuration files in /usr/local/etc
8. Manually check /usr/local and /var/db/pkg
to make sure that they are really empty
9. Install ports-mgmt/pkg and then ports-mgmt/portmaster.
Remove both from ~/installed-port-list.
10. portmaster --no-confirm `cat ~/installed-port-list`
It is easier to install a fresh new copy of FreeBSD, and install the software using packages, preferably not ports. Then you can restore the data from backups.
I never had a pleasant experience using portmaster due to it always aborting on 'any' port failure and I often find 'something' doesn't build. I used portupgrade which can be instructed to continue despite failing to rebuild a port in the list, though there can be fallout from such a failure but damage to uptime was greatly minimized.
To have much better uptime you want to build your ports in a separate clean environment from the running system using systems like poudriere or synth; its like having a dedicated build machine but still only using the same machine. Once builds completed you can use pkg to upgrade them in one step which is much better than having things break during the "days" it takes my system to go through the repetitive steps of rebuilding a port and all that depends on it.
For freebsd-update, I'd just go grab the newest copy of it and tell it to take me to the last version I intend to reach though there 'may' be value in having it install patches to your current version. I'd skip going to things like 13.0 completely unless that is the final target. Everything I have looked into with the 'must upgrade to this version first' for freebsd-update only seemed to be to get a newer copy of freebsd-update that had a bugfix before putting other changes on the system; irrelevant if you go get a newer copy yourself first as you now have those bugfixes and with even less system changes being made. This came from trying to review various updating notes but I'd like to know if someone can say where updating needs a step taken for reasons other than freebsd-update needs a bugfix.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
