Having issues on upgrading 18.04 to latest version

[kustomjs]

Hello People
its been long time since I posted on here but I am having issues upgrading my server from 18.04 lts to latest one and when I do update I get this error:

tim@mail:~$ sudo apt-get update
Ign:1 http://old-releases.ubuntu.com/ubuntu bionic InRelease
Ign:2 http://old-releases.ubuntu.com/ubuntu bionic-updates InRelease
Ign:3 http://old-releases.ubuntu.com/ubuntu bionic-backports InRelease
Ign:4 http://old-releases.ubuntu.com/ubuntu bionic-security InRelease
Err:5 http://old-releases.ubuntu.com/ubuntu bionic Release
  404  Not Found [IP: 91.189.91.123 80]
Err:6 http://old-releases.ubuntu.com/ubuntu bionic-updates Release
  404  Not Found [IP: 91.189.91.123 80]
Err:7 http://old-releases.ubuntu.com/ubuntu bionic-backports Release
  404  Not Found [IP: 91.189.91.123 80]
Err:8 http://old-releases.ubuntu.com/ubuntu bionic-security Release
  404  Not Found [IP: 91.189.91.123 80]
Reading package lists... Done
E: The repository 'http://old-releases.ubuntu.com/ubuntu bionic Release' does not have 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://old-releases.ubuntu.com/ubuntu bionic-updates Release' does not have 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://old-releases.ubuntu.com/ubuntu bionic-backports Release' does not have 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://old-releases.ubuntu.com/ubuntu bionic-security Release' does not have 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.

then when I try to do do-release I get this

tim@mail:~$ sudo do-release-upgrade
Checking for a new Ubuntu release
Err Upgrade tool signature
  404  Not Found [IP: 91.189.88.152 80]
Err Upgrade tool
  404  Not Found [IP: 91.189.88.152 80]
Fetched 0 B in 0s (0 B/s)
WARNING:root:file 'focal.tar.gz.gpg' missing
Failed to fetch
Fetching the upgrade failed. There may be a network problem.

Any Ideas how to fix this?

[deadflowr]

18.04 is still supported so the archive still exist where they are and have never been moved to the old-release archives.
revert your sources.

[kustomjs]

deadflowr
how do I revert the sources back?

[deadflowr]

You can either use a repo generator like this https://repogen.simplylinux.ch/
And then replace the current sources.list file with the one you generated.

Or you can copy over a generic sources.list file that comes with the apt docs in the /usr/share/doc/apt/examples folder.
But this one would require re-adding any extras sources like those from the universe and multiverse repositories.
For that run

sudo cp /usr/share/doc/apt/examples/sources.list /etc/sources.list
sudo add-apt-repository universe multiverse
sudo apt update ####  NOTE: this command should actually run as part of the add-apt-repository command, so it might not be necessary
sudo apt full-upgrade

[irv]

Just for the heck of it, do a

cat /etc/network/interfaces

and then copy and paste the output. It should look something like this if you have a static IP on your server.

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto enp4s0
iface enp4s0 inet static
address 192.168.1.105
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameserver 8.8.8.8 8.8.4.4

I just wanted to check your dns-nameserver settings to make sure it is okay.

[kustomjs]

irv
that is outdated information its been replaced by netplan

tim@mail:~$ cat /etc/netplan/*.yaml
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    renderer: networkd
    ethernets:
        enp2s0:
            dhcp4: true

deadflowr
I tried that rep generator still getting error message after doing apt-update:

 

tim@mail:~$ sudo apt-get update
Ign:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Ign:2 http://us.archive.ubuntu.com/ubuntu bionic-security InRelease
Ign:3 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Ign:4 http://us.archive.ubuntu.com/ubuntu bionic-proposed InRelease
Ign:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Err:6 http://us.archive.ubuntu.com/ubuntu bionic Release
  404  Not Found [IP: 91.189.91.38 80]
Err:7 http://us.archive.ubuntu.com/ubuntu bionic-security Release
  404  Not Found [IP: 91.189.91.38 80]
Err:8 http://us.archive.ubuntu.com/ubuntu bionic-updates Release
  404  Not Found [IP: 91.189.91.38 80]
Err:9 http://us.archive.ubuntu.com/ubuntu bionic-proposed Release
  404  Not Found [IP: 91.189.91.39 80]
Err:10 http://us.archive.ubuntu.com/ubuntu bionic-backports Release
  404  Not Found [IP: 91.189.91.38 80]
Reading package lists... Done
E: The repository 'http://us.archive.ubuntu.com/ubuntu bionic Release' does not have 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://us.archive.ubuntu.com/ubuntu bionic-security Release' does not have 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://us.archive.ubuntu.com/ubuntu bionic-updates Release' does not have 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://us.archive.ubuntu.com/ubuntu bionic-proposed Release' does not have 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://us.archive.ubuntu.com/ubuntu bionic-backports Release' does not have 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.

I can ping to 1.1.1.1 and to 91.189.91.39

[irv]

I am using 18.04 but I just upgraded from 16.04.
Can you ping the domain name, try

ping www.google.com

[MAFoElffen]

This is where I posted the default sources.list's for 16.04 and 18.04: https://ubuntuforums.org/showthread....7#post14044977
The second is for 18.04. All you would have to do is to copy and paste it into a text document and save as a file called sources.list... then copy (using sudo) over the existing /etc/apt/sources.list...

Or use this to change your exisiting incorrect sources list:

# Make a copy of the original
sudo cp /etc/apt/sources.list ~/sources.list.old_backup

# Change all instances of "old-releases" into "us.archive" in the sources list file 
sudo sed -i 's/old\-releases/us\.archive/g' /etc/apt/sources.list

# Check your work and see if it is pointing to the correct repo..
sudo apt-get update

EDIT: A sources.list doesn't get to the "old-releases" repo's by accidient. I suspect you used something someone (maybe me) wrote for a specific user, that had a specific problem, with what they had going on, and needed something outside the box, to get back on track to what is recommened. That recent recommendation by me, was for someone that had something specific going on, that was not in the main repo's by about 4-1/2 years past. But my instructions to "that specific user" included instructions on how to get back to the main repo's. Please ensure you undederstand that something applies to you, your system, and your circumstances, before trying things. Just a disclaimer... LOL

...Or referring to my signature line in another forum: "Don't worry! I saw this work in a cartoon once..."

[kustomjs]

I can ping to google

[MAFoElffen]

So please post your /etc/apt/sources.list within code tags...