External HDD fails to mount

I have been in the kitchen for 4 hours and came to read for a moment before getting a shower.

Why is there a ; in the repo names? Where did these repos come from? Did you add these repos from the Software Repository Selector or did they come from Discover?

Going to get a shower and I will be back.

OK, I had time to read further down, it looks as if these repos were added from Discover . I am not sure what to do to fix this at this time. @rugyada may know.

This topic took a different path and may be hard to follow.
Let’s try to fix the repository issue.

Did anyone ever whispered: DO NOT manage repository with Discover or dnfdragora?
(same goes for system upgrade. Forget that they exist)
I have the feeling that you did, so once the current issue is fixed please don’t do again :wink:

To restore the correct .repo files set you may want to download
distro-release-repos-25.01-2-omv2501.znver1.rpm from [HERE]
assuming the system is ROME znver1.

Extract the rpm as an archive an copy the yum.repos.d content to your /etc/yum.repos.d/

Disable any additional repo (brave, librewolf, and/or the likes),
sudo dnf clean all;dnf clean all;dnf repolist
you must have only OM repos.

Postedit:
do also

sudo rm -rf /var/cache/PackageKit/* /var/cache/app-info/*
sudo pkcon refresh force

Run the distro-sync command and check if it still complain about metadata.

1 Like

Okay, I’ve done all that now. The original file openmandriva-rolling-znver1.repo is identical in it’s text to the backup BACKUP-REPO, as I checked there were no differences using a text-compare website. NEW-REPO has changes made to the text as I believe is supposed to be the case. And I’ve installed the new file and checked that the text matches the text in NEW-REPO just to be certain, and it does match.

Should I now run the command sudo dnf dsync --refresh again?

1 Like

What is the output of

dnf repolist

sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync-log.txt

You can also abort the transaction with (N)
Upload this dsync-log.txt file here.

The output of dnf repolist is:

[mandriva@openmandriva-x8664 ~]$ dnf repolist
repo id                                    repo name
brave-browser                              Brave Browser
mullvad-stable                             Mullvad VPN
repository                                 LibreWolf Software Repository
rolling-znver1                             OpenMandriva Rolling - znver1
rolling-znver1-extra                       OpenMandriva Rolling - Extra - znver1
rolling-znver1-non-free                    OpenMandriva Rolling - Non-free - znver1
rolling-znver1-restricted                  OpenMandriva Rolling - Restricted - znver1
[mandriva@openmandriva-x8664 ~]$

Disable them.

The Software Repository Selector GUI doesn’t list Mullvad or LibreWolf, it only lists Brave, which for some reason the GUI lists as being disabled. Do I need to disable them manually using command-line? If so, how do I do that?

Would those repos hinder installing ntfs-parts? Worth thinking, before we stray further.

Not sure where the others put their repo files configuration.
Probably the same place where Brave Browser does: /etc/yum.repos.d
You should find a line mentioning: enabled=1 to change to enabled=0

then run again
sudo dnf clean all;dnf clean all;dnf repolist

Edit: What I originally posted was wrong. Looking. A simple way to disable any repo is to open the .repo file and change enabled=1 to enabled=0. Sorry for the confusion, I was either trying to work to fast or work on to many things at one time…

1 Like

Not really, we need to sort the repository issue first.

sudo dnf config-manager --disable brave-browser

according to manpage (and tested - also --enable seems to work)

IMO it’s easier for the user to edit the repo files from 1 to 0 mainly because that way he knows how to restore them later.

2 Likes

1 Like

1 Like

Sorry to extend this further, but, I managed to change enabled=1 to enabled=0 for Brave Browser and for Mullvad, but LibreWolf doesn’t have a line like that. This is the whole content of the librewolf.repo file, which by the way is located where you predicted it would be:

[repository]
name=LibreWolf Software Repository
baseurl=https://repo.librewolf.net
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://repo.librewolf.net/pubkey.gpg

Remove it and add it back later.

Edit: Then do as @rugyada suggested and upgrade your system first with the commands she posted.

I don’t think that Librewolf repo is correct. It doesn’t look to be structured correctly and it is not named correctly. I am guessing that it came from Discover.