Once you’re back up and running, throw this in. #Xnconvert ubuntu 20.04 updateIf you’re brazen like me you’ll tackle that with one command:Īpt update apt -y dist-upgrade apt -y autoremove reboot Run all of the regular updates, just to be sure you’re fully current. I would recommend testing whatever services you have running on the server, just to be sure everything is working properly, before you continue to the 20.04 LTS upgrade. Once all of that is over, your server will reboot, and you should be able to log back into a fully functioning Ubuntu 18.04 LTS install. In general I would always recommend keeping your existing versions of any files it asks you about. Run these commands:ĭon’t walk away at this point… you’re going to have to answer some prompts along the way. I’ve run into a problem on some servers with messages that cloud-init was held back. #Xnconvert ubuntu 20.04 upgradeI almost always run apt-get dist-upgrade instead of just apt-get upgrade because I always assumed the former does everything the latter does, and more. Hold on! Failure may be looming in the near future. Then if you’re running ufw, which you should be, do this to give yourself a back door in case something goes wrong (assuming you’re running this update over ssh, which of course Ubuntu will warn you is a Bad Idea). First, edit /etc/apt/sources.list in your text editor of choice (I like nano) and add these lines at the end:ĭeb xenial-security main universe multiverse There’s some stuff to do before you run that do-release-upgrade command. Then we won’t have to think about this for another 3 1/2 years! Whew! Then we can do the 18.04 LTS to 20.04 LTS upgrade to get ourselves current. First we’ll upgrade from Ubuntu 16.04 LTS to 18.04 LTS. Yes, this is going to be a two-step upgrade. #Xnconvert ubuntu 20.04 fullIt’s probably also a good idea first to do a full backup of your server that you can restore from if things go totally off the rails. If you don’t like to do that, you may need to prefix some of these commands with sudo in order for them to work. Also note that I am brazen and always run sudo -s before I get started. If you do the same and it breaks something, don’t blame me. Before the 16.04 to 18.04 updateįirst off, caveat emptor. I’m running it again today on another server, so I thought I’d consolidate it into a blog post here while I’m at it. A few months ago I scraped together tips from a few different resources (which I regrettably did not make note of for citation here), and came up with a rough script for myself that seems to work. So you reluctantly acknowledge that it would be a very good idea to do the OS upgrade. But if you’re like me you may also have discovered that you can no longer access new PHP versions from the “ondrej” repository once LTS ends. Maybe you’ve even set up ESM (Extended Security Maintenance) to avoid the upgrade. Yes, support for it ended almost 6 months ago. So, like me you’ve decided to procrastinate on the OS upgrade on your server running Ubuntu 16.04 LTS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |