Update failed as File not found on medium

Hi, for some reason after a month long holiday, my Tumbleweed update failed:

Here is my zypper lr -d output:

paul@localhost:~> zypper lr -d
#  | Alias                                | Name                     | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                        | Service
---+--------------------------------------+--------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------------------------+---------
 1 | VLC_Tumbleweed                       | VLC Tumbleweed           | No      | ----      | ----    |   99     | rpm-md | https://download.videolan.org/pub/vlc/SuSE/Tumbleweed/                                     | 
 2 | download.nvidia.com-tumbleweed       | nVidia Graphics Drivers  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.nvidia.com/opensuse/tumbleweed                                            | 
 3 | ftp.gwdg.de-openSUSE_Tumbleweed      | Packman Repository       | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/                        | 
 4 | https-download.opensuse.org-0c32967b | home:fusionfuture:joplin | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.opensuse.org/repositories/home:/fusionfuture:/joplin/openSUSE_Tumbleweed/ | 
 6 | https-download.opensuse.org-5c193e60 | openSUSE:Tumbleweed      | No      | ----      | ----    |   99     | rpm-md | https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/                  | 
 7 | https-download.opensuse.org-7d713b7c | openSUSE:Tumbleweed      | No      | ----      | ----    |   99     | rpm-md | https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/                  | 
 5 | https-download.opensuse.org-2566a862 | home:xorcue              | No      | ----      | ----    |   99     | rpm-md | https://download.opensuse.org/repositories/home:/xorcue/openSUSE_Tumbleweed/               | 
 8 | https-download.opensuse.org-a8e88e13 | openSUSE:Tumbleweed      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.opensuse.org/tumbleweed/repo/oss/                                         | 
 9 | https-download.opensuse.org-ca725f80 | openSUSE:Tumbleweed      | No      | ----      | ----    |   99     | rpm-md | https://download.opensuse.org/tumbleweed/repo/oss/                                         | 
10 | openSUSE:repo-non-oss                | repo-non-oss             | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/non-oss                                            | openSUSE
11 | openSUSE:repo-openh264               | repo-openh264            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed                                    | openSUSE
12 | openSUSE:repo-oss                    | repo-oss                 | No      | ----      | ----    |   99     | rpm-md | http://cdn.opensuse.org/tumbleweed/repo/oss                                                | openSUSE
13 | openSUSE:repo-oss-debug              | repo-oss-debug           | No      | ----      | ----    |   99     | rpm-md | http://cdn.opensuse.org/debug/tumbleweed/repo/oss                                          | openSUSE
14 | openSUSE:repo-oss-source             | repo-oss-source          | No      | ----      | ----    |   99     | rpm-md | http://cdn.opensuse.org/source/tumbleweed/repo/oss                                         | openSUSE
15 | openSUSE:update-tumbleweed           | update-tumbleweed        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://cdn.opensuse.org/update/tumbleweed                                                  | openSUSE

Not sure what’s the reason is, probably one of the third-party repos caused the issue?

Looks like it’s because my repos are not consistent, i.e openSuse:Tumbleweed: download.opensuse.org/tumbleweed/repo/oss mixed with cdn ones.

Once I changed the openSuse:tumbleweed to cdn one, the update can continue further.

Time and again in these forums it has been explained that NVidia GPU users have been treated specially. By default, openSUSE-repos-Tumbleweed and openSUSE-repos-Tumbleweed-NVIDIA get installed at some point, and create a repos service that duplicates existing repos. If you wish to keep using your previously existing repos, you should uninstall those two repo packages, thus removing the service and duplicate newer repos. And, those packages should be locked or tabooed so that they don’t get reinstalled. Otherwise, the duplicates created by the service installing the CDNs should be kept, and the old ones, typically d.o.o. versions of the same repos, should be removed. Which to choose depends whether you like the old manual repo management method better, or the new service method. It’s not supposed to matter which. It is after all, your computer.

It happened to me too, error during the update of 4600 rpm a few days ago, always from the OSS Repo as you can see there, third party repositories have nothing to do with it, it’s the OSS repo itself that sometimes gets in the way, first it was GeoIP that blocked now I don’t know what, but sometimes it gets stuck. I follow the updates and when it happens it asks you if you want to cancel, ignore or try again, I type try again and it starts again. It automatically tries again I think 4 times after 30 seconds, then cancels and the update ends there without downloading anything else.

@mrmazda my apology, I know nothing about the topic you mentioned.

I am a relatively confident Linux user, but this is my first openSuse installation and this PC where I installed openSUSE only gets used during weekends, otherwise, I am using a work-provided laptop full time. So I am very very uninformed on any topics on this forum!

Now I did a bit more reading about the duplicate repos issues you mentioned, which makes sense now, but in general duplicate repos should be ok I think. I did some manual converting to CDN a while back And had a similar issue caused by it a while back, it might be that I messed up with duplicate entries which caused some subtle issue like this.

I am guessing that it’s a conflicting issue where CDN and exiting old Url point to repo instances have packages not in consistent states i.e. one thinks it’s here and the other couldn’t find it, and my fix should work. but now I believe a proper fix would be to clean up non-CDN repos as you suggested (not simply disable them).

Thanks again

It’s not clear from your reply whether you’re looking for more help at this point, but I will mention because of your newness to openSUSE, in case you’re not already aware, that zypper package locking and YaST tabooing are the same thing, just by different names, and optional. Any that exist are kept in plain text file /etc/zypp/locks. I use them a lot. Most users probably don’t even know the concept of package locking exists. A package lock keeps an installed package from being updated or removed, and an uninstalled package from being installed. Locks can cause various types of trouble for various reasons. Experienced users using locks generally know their ramifications and how to deal with them when necessary.

I have only nominal hands-on knowledge of the repo management service, having allowed its enabling only once, before I knew it existed, and to lock it out, in order to continue my manual management system for several hundred installations. That system includes a master set of plain text repo files maintained on the LAN server, and each installation keeping an appropriately selected group from among them in its /etc/zypp/repos.d/, none of which are named beginning with the string “repo-”. All have shorter names than the defaults for filename, repo name, and repo nick, and except for /repositories/ repos, use mixed case for all three names.

Thanks, I am ok now.

Probably going to do a bit cleanup in the future, remove the duplicated old one, and keep the CDNs only for the duplicated one. But need move on for now :smiley:

To be clear, my solution is make sure I am using CDN style repos all the way, as it was the repo NO 8 - openSUSE:Tumbleweed causing the issue, I disabled it and enabled the CDN one NO 12 instead which seems to fixed the issue.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.