Upgrading from OMV6 to OMV7. Incorrect FTP repository.

NordWest · May 11th 2025

When upgrading from OMV6 to OMV7, omv-release-upgrade stops with the following error:

W: Failed to fetch http://ftp.uni-hannover.de/deb…/dists/bookworm/InRelease Could not connect to ftp.uni-hannover.de:80 (130.75.2.22), connection timed out

W: Failed to fetch http://ftp.uni-hannover.de/deb…ookworm-updates/InRelease Unable to connect to ftp.uni-hannover.de:http:

W: Failed to fetch http://packages.openmediavault…c/dists/shaitan/InRelease Could not connect to packages.openmediavault.org:80 (178.254.11.33), connection timed out

The upgrade on the backup device on the same LAN, but in a different building, went through without a hitch. Here, omv-release-upgrade retrieved the packages from RWTH Aachen University.

Does anyone have any ideas?

chente · May 11th 2025

It could be a temporary issue with the remote repository. I'd try updating again later. If it continues to fail, you can change the repository to a more general one.

NordWest · May 11th 2025

How can I do that?

chente · May 11th 2025

You need to manually edit the apt files. The main file is /etc/apt/sources.list, and this is the content of mine.

Code

deb http://deb.debian.org/debian/ bookworm main contrib non-free
deb-src http://deb.debian.org/debian/ bookworm main contrib non-free


# bookworm-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free
deb-src http://deb.debian.org/debian/ bookworm-updates main contrib non-free

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

Display More

Inside that folder are other folders containing files that you may also need to modify. For example, in /etc/apt/sources.list.d

NordWest · May 11th 2025

Thank you very much for your support.

After editing the sources.list, omv-release-upgrade actually started running.

However, it stopped when clamav was edited.

Current status:

Debian is on version 12.

Openmediavault is still the old version 6.9.16-1.

Login via browser: nginx 403 Forbidden.

omv-firstaid isn't working.

Instead of potentially spending a long time searching for errors, I'm considering a fresh install.

Is there a way to back up the configuration and import it into the new system?

chente · May 11th 2025

Quote from NordWest

Is there a way to back up the configuration and import it into the new system?

In the current state of the system, there isn't one. You can save the database as a reference for the new configuration. It's the /etc/openmediavault/config.xml file. This file contains all the information you entered from the OMV GUI, except for user passwords and a few other minor items.

chente · May 11th 2025

Quote from NordWest

Openmediavault is still the old version 6.9.16-1.

What is the content of the /etc/apt/sources.list.d/omvextras.list file on your system?

On mine, it's this:

Code

deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] http://packages.openmediavault.org/public/ sandworm main
deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] https://openmediavault.github.io/packages/ sandworm main
# deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] http://downloads.sourceforge.net/project/openmediavault/packages/ sandworm main

The way to avoid these problems in the future is to choose a generic mirror during the Debian/OMV installation. I usually choose the US one instead of one near my country.

NordWest · May 12th 2025

There is no /etc/apt/sources.list.d/omvextras.list on the system.

But I created one based on your example and then rebooted the system.

Unfortunately, without success.

Amazingly, the system still provides all SMB shares on the LAN, even though it was so messed up by the failed upgrade.

Since the initial installation was quite a while ago and several upgrades have worked well in the meantime, it's now time to do a complete reinstall.

Unfortunately, the upgrade was a disaster. But the support in this forum was a pleasure again. - Thank you very much.

When reinstalling, I will definitely follow your tip regarding the default mirror.

crashtest · May 12th 2025

Quote from NordWest

it's now time to do a complete reinstall.

Sometimes, a clean reinstall is unavoidable and the fastest route to a clean server.

Upgrading from OMV6 to OMV7. Incorrect FTP repository.

chente May 11th 2025

NordWest May 22nd 2025

Participate now!

Tags