Question

6

Upgrading Raspberry Pi from Ubuntu 21.10

rated 0 times [ 6] [ 0] / answers: 1 / hits: 924 / 2 Years ago, thu, june 2, 2022, 2:45:23

I have a Raspberry Pi running Ubuntu 21.10, which I recently learned is EOL. No worries, I'll just upgrade to the next version (which, happily enough, is an LTS release)... or so I thought...

I'd like to upgrade to Ubuntu 22.04 LTS, but none of the upgrade tools seem to be working at all, which is very confusing to me.

For context, I'm accustomed to working with Debian, where you simply edit your apt.sources.list and upgrade packages. From what I've found, with Ubuntu, the preferred method of upgrading seems to be the do-release-upgrade tool. However, that tool is not doing anything on my system (and I haven't found any command-line switches like --actually-do-upgrade that I'm missing):

anthony@planetsrv:~$ 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/releaseendoflife



Please install all available updates for your release before upgrading.

It just tells me that I'm EOL -- I know that, that's why I'm trying to upgrade! :) The link just gives the release schedule; I don't see any instructions or tips about upgrading from an EOL'd version.

When running apt update, I get nothing but 404 errors:

anthony@planetsrv:~$ sudo apt update

Ign:1 http://ports.ubuntu.com/ubuntu-ports impish InRelease

Ign:2 http://ports.ubuntu.com/ubuntu-ports impish-updates InRelease

Ign:3 http://ports.ubuntu.com/ubuntu-ports impish-backports InRelease

Ign:4 http://ports.ubuntu.com/ubuntu-ports impish-security InRelease

Err:5 http://ports.ubuntu.com/ubuntu-ports impish Release

  404  Not Found [IP: 2620:2d:4000:1::19 80]

Err:6 http://ports.ubuntu.com/ubuntu-ports impish-updates Release

  404  Not Found [IP: 2620:2d:4000:1::19 80]

Err:7 http://ports.ubuntu.com/ubuntu-ports impish-backports Release

  404  Not Found [IP: 2620:2d:4000:1::19 80]

Err:8 http://ports.ubuntu.com/ubuntu-ports impish-security Release

  404  Not Found [IP: 2620:2d:4000:1::19 80]

Reading package lists... Done

E: The repository 'http://ports.ubuntu.com/ubuntu-ports impish 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://ports.ubuntu.com/ubuntu-ports impish-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://ports.ubuntu.com/ubuntu-ports impish-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://ports.ubuntu.com/ubuntu-ports impish-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.

Same with apt upgrade:

anthony@planetsrv:~$ sudo apt upgrade

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

Calculating upgrade... Done

The following package was automatically installed and is no longer required:

  libfwupdplugin1

Use 'sudo apt autoremove' to remove it.

The following packages will be upgraded:

  apt apt-utils cloud-init gtk-update-icon-cache keyutils libapt-pkg6.0 libgtk-3-0 libgtk-3-bin libgtk-3-common libkeyutils1 libnss-systemd libpam-systemd librados2 librbd1 libsystemd0 libudev1

  python3-distupgrade snapd systemd systemd-sysv systemd-timesyncd ubuntu-advantage-tools ubuntu-release-upgrader-core udev

24 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Need to get 41.2 MB of archives.

After this operation, 122 kB of additional disk space will be used.

Do you want to continue? [Y/n] Y

Err:1 http://ports.ubuntu.com/ubuntu-ports impish-updates/main arm64 libnss-systemd arm64 248.3-1ubuntu8.6

  404  Not Found [IP: 2620:2d:4000:1::19 80]

Err:2 http://ports.ubuntu.com/ubuntu-ports impish-updates/main arm64 libsystemd0 arm64 248.3-1ubuntu8.6

  404  Not Found [IP: 2620:2d:4000:1::19 80]

Err:3 http://ports.ubuntu.com/ubuntu-ports impish-updates/main arm64 systemd-timesyncd arm64 248.3-1ubuntu8.6



...snipping repetitive similar lines, you get the idea :)...



E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/s/systemd/libnss-systemd_248.3-1ubuntu8.6_arm64.deb  404  Not Found [IP: 2620:2d:4000:1::19 80]

E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/s/systemd/libsystemd0_248.3-1ubuntu8.6_arm64.deb  404  Not Found [IP: 2620:2d:4000:1::19 80]

E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/s/systemd/systemd-timesyncd_248.3-1ubuntu8.6_arm64.deb  404  Not Found [IP: 2620:2d:4000:1::19 80]



...snipping some more...



E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

I came across this question which suggests that the packages have moved to old-releases.ubuntu.com or us.archive.ubuntu.com, but neither of those seem to work for me. I also came across this question where the resolution seemed to be a complete wipe and reinstall, which I'd rather avoid.

Here's my current sources.list (stripped of comments):

deb http://ports.ubuntu.com/ubuntu-ports impish main restricted

deb http://ports.ubuntu.com/ubuntu-ports impish-updates main restricted

deb http://ports.ubuntu.com/ubuntu-ports impish universe

deb http://ports.ubuntu.com/ubuntu-ports impish-updates universe

deb http://ports.ubuntu.com/ubuntu-ports impish multiverse

deb http://ports.ubuntu.com/ubuntu-ports impish-updates multiverse

deb http://ports.ubuntu.com/ubuntu-ports impish-backports main restricted universe multiverse

deb http://ports.ubuntu.com/ubuntu-ports impish-security main restricted

deb http://ports.ubuntu.com/ubuntu-ports impish-security universe

deb http://ports.ubuntu.com/ubuntu-ports impish-security multiverse

How should I proceed to update my system? Can I just update the release name in my sources.list like I would in Debian, and do the big upgrade that way? Or is there any way to get the original tools (do-release-upgrade) to work properly?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

skaing

Add To Favorites

Follow

Total Points: 462

Total Questions: 124

Total Answers: 113

Location: Nauru

Member since Thu, Feb 2, 2023

1 Year ago

skaing questions

1 I'm getting errors that I don't understand installing NodeJS on a freshly installed Ubuntu that is otherwise blank

Wed, Feb 8, 23, 10:29, 1 Year ago

1 Vim is opening with Vi when I use Sudo - why?

Mon, Apr 10, 23, 17:06, 1 Year ago

1 How to remove specific character from file

Sat, Mar 25, 23, 18:49, 1 Year ago

1 Can you connect an iPhone to your Ubuntu media sharing?

Fri, Jul 30, 21, 13:04, 3 Years ago

1 How to make a virtual machine with .vdi file

Sat, Apr 16, 22, 14:36, 2 Years ago

View All

answered 2 Years ago biryanrownies · Accepted Answer

I figured out the issue I was having with the old-releases server.

Because I'm using a Raspberry Pi, and on an ARM architecture, my sources.list looks like deb http://ports.ubuntu.com/ubuntu-ports/ impish main restricted. Specifically, notice that the URL ends in ubuntu-ports.

On the old-releases server, they apparently don't use a separate directory for the ports vs the main architectures. By updating my sources.list entries to http://old-releases.ubuntu.com/ubuntu/, I was able to get the latest updates to 21.10.

After I got the sources.list figured out, I was able to apt update and apt upgrade, and at that point do-release-upgrade was able to function and upgrade me to 22.04.

Note: as part of the apt upgrade on my system, a new kernel was installed. I should have rebooted at this point, but did not. I just ran do-release-upgrade immediately after. The release upgrade tried to uninstall the older kernel version (the one which was currently running, which the apt update replaced) but threw up a big warning "You're about to uninstall the kernel you're currently running, are you sure???". In my case I said "no", and just did an apt autoremove after rebooting after the release upgrade was finished. I suspect that if I had rebooted after apt upgrade, I would not have seen this issue.

Note 2: The upgrade tool seems to be smart about your architecture, and re-added the -ports for me when it updated my sources.list automatically.