Can't update my Linode - "no longer has a Release file"
Linode
Linode Staff
Hello
I am not able to update my Linode, when I use this command sudo apt update I receive result like this
Ign:1 http://mirrors.linode.com/ubuntu groovy InRelease
Ign:2 http://mirrors.linode.com/ubuntu groovy-updates InRelease
Ign:3 http://mirrors.linode.com/ubuntu groovy-backports InRelease
Ign:4 http://mirrors.linode.com/ubuntu groovy-security InRelease
Err:5 http://mirrors.linode.com/ubuntu groovy Release
404 Not Found [IP: 2600:3c01:1::607e:6379 80]
Err:6 http://mirrors.linode.com/ubuntu groovy-updates Release
404 Not Found [IP: 2600:3c01:1::607e:6379 80]
Err:7 http://mirrors.linode.com/ubuntu groovy-backports Release
404 Not Found [IP: 2600:3c01:1::607e:6379 80]
Err:8 http://mirrors.linode.com/ubuntu groovy-security Release
404 Not Found [IP: 2600:3c01:1::607e:6379 80]
Hit:9 https://download.docker.com/linux/ubuntu groovy InRelease
Hit:10 http://dl.google.com/linux/chrome/deb stable InRelease
Reading package lists... Done
E: The repository 'http://mirrors.linode.com/ubuntu groovy Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://mirrors.linode.com/ubuntu groovy-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://mirrors.linode.com/ubuntu groovy-backports Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://mirrors.linode.com/ubuntu groovy-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
How do I fix this?
5 Replies
isackey
Linode Staff
The version of Ubuntu(20.10) you're running has been deprecated as it has reached its end of life as of July 22, 2021 and is no longer supported. I was able to recreate the exact issue by deploying a Linode in Fremont with Ubuntu 20.10 and running the sudo apt update generated the same error messages you're seeing.
To save you time and effort, I'd recommend you spin up a new Linode with a supported Ubuntu version and transfer your files over. We don't normally recommend inline upgrades as the can present a myriad of problems that maybe difficult to troubleshoot and resolve.
Tools like FileZilla, Cyberduck, SCP and a few others can be used to transfer files between two Linodes. These guides below have more information on them.
How to Transfer Files with SFTP
Transfer Files with FileZilla
This community post from our Community Question Site also has some good information that should be helpful as well.
You can upgrade from 20.10 to 21.04 by running sudo do-release-upgrade and follow the on-screen prompts however, this is not recommended and you should take a backup of your Linode before trying this.
Most likely do-release-upgrade will not work in this case:
$ sudo do-release-upgrade
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflifePlease install all available updates for your release before upgrading.
In this case, the manual from https://help.ubuntu.com/community/EOLUpgrades will help to update EOL products:
for Hirsute Hippo this file has to be downloaded, extracted and run:
http://archive.ubuntu.com/ubuntu/dists/hirsute-updates/main/dist-upgrader-all/current/hirsute.tar.gz
isackey
Linode Staff
To re-confirm my test, I spun up a second Linode running Ubuntu 20.10 and checked the version before running the sudo do-release-upgrade command.
root@localhost:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.10
Release: 20.10
Codename: groovy
After running the command I was greeted with the same prompt you got but at the same time the upgrade proceeded.
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,272 kB]
Fetched 1,273 kB in 0s (0 B/s)
This prompt then appeared after which I proceed by pressing Y to continue.
Reading cache
Checking package manager
Continue running under SSH?
This session appears to be running under ssh. It is not recommended
to perform a upgrade over ssh currently because in case of failure it
is harder to recover.
If you continue, an additional ssh daemon will be started at port
'1022'.
Do you want to continue?
Continue [yN]
A series of prompts appeared and after following through, my distro was successfully upgraded to 21.04. To confirm this, I run the lsb-release -a command and as you can see from the output below, its currently on 21.04. I'm not sure which distro you tried this from but this is the second test I'm running to confirm this.
root@localhost:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
This is also what the tail of the souces.list file looks like before and after the upgrade.
Before
deb http://security.ubuntu.com/ubuntu/ groovy-security main restricted
# deb-src http://security.ubuntu.com/ubuntu/ groovy-security main restricted
deb http://security.ubuntu.com/ubuntu/ groovy-security universe
# deb-src http://security.ubuntu.com/ubuntu/ groovy-security universe
deb http://security.ubuntu.com/ubuntu/ groovy-security multiverse
# deb-src http://security.ubuntu.com/ubuntu/ groovy-security multiverse
After
eb http://security.ubuntu.com/ubuntu/ hirsute-security main restricted
# deb-src http://security.ubuntu.com/ubuntu/ groovy-security main restricted
deb http://security.ubuntu.com/ubuntu/ hirsute-security universe
# deb-src http://security.ubuntu.com/ubuntu/ groovy-security universe
deb http://security.ubuntu.com/ubuntu/ hirsute-security multiverse
# deb-src http://security.ubuntu.com/ubuntu/ groovy-security multiverse
deb http://archive.ubuntu.com/ubuntu hirsute main restricted # auto generated by ubuntu-release-upgrader
deb http://archive.ubuntu.com/ubuntu hirsute-updates main restricted # auto generated by ubuntu-release-upgrader
deb http://security.ubuntu.com/ubuntu hirsute-security main restricted # auto generated by ubuntu-release-upgrader
Alternatively, you can also #comment out all the lines in your /etc/apt/sources.list and add append the following to the bottom.
deb http://security.ubuntu.com/ubuntu/ hirsute-security universe
deb http://security.ubuntu.com/ubuntu/ hirsute-security multiverse
deb http://archive.ubuntu.com/ubuntu hirsute main restricted # auto generated by ubuntu-release-upgra>
deb http://archive.ubuntu.com/ubuntu hirsute-updates main restricted # auto generated by ubuntu-relea>
Next, you can run sudo apt update or sudo apt upgrade and your upgrade should go through successfully. I tested this many times and can confirm it works.
You can point to the archived repos. See: https://askubuntu.com/questions/91815/how-to-install-software-or-upgrade-from-an-old-unsupported-release
