Sabine
September 26, 2026, 10:57am
1
I still have a lot of NTFS hard drives left over from my Windows days. I’d now like to consolidate them better with other hard drives (filling up the half-full ones) so that I end up with a few empty hard drives.
I’ve read that you can access them using Fedora.
That’s why I’ve now used “Fedora-44-gnome.”
During my test, I found that this isn’t possible.
Unfortunately, I can’t install Nautilus on them either.
This is what I see when I try to install something.
Question: What’s the best way for me to proceed now?
ChrisA
September 26, 2026, 11:03am
2
Hi Sabine
Can you share the text (from the image) as text?
Sabine
September 26, 2026, 11:37am
3
Curl error (28): Timeout was reached for
https://mirrors , fedoraproject.org/metalink?repo=fedora Wharch=x86_64
[Connection timed out after 30002 milliseconds] -
https://mirrors.fedoraproject.org/metalink?repo=fedore-44aarch=x86_64
Cannot prepare internal mirrorlist: Curl error (28): Timeout was reached for
https: //mirrors.fedoraproject.org/metalink?rept jedora-aasarc {86_64
[Connection tined out after 30002 milliseconds]
Failed to download metadata
(netalink: “https://mixrors.fedoraproject.org/netalink?zepo-updates-released-fa4narc ! 1668")
for repository “updates”: Cannot prepare internal mizrorlist:
Curl error (28): Timeout was reached for
https://mirrors.fedoraproject.org/metal ink?repo=updates-released-faasarch=x86_64
[Connection timed out after 30002 milliseconds}
Sabine
September 26, 2026, 11:41pm
4
Details for @ NTFS:
Updating NTFS
Refreshing package info
Removed 0 files, © directories (total of 0 8). 0 errors occurred.
(process:773): librepo-WARNING **: 21:07:17.285: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-
f4d&arch=x86_64 [Connection timed out after 30001 milliseconds]
(process:773): librepo-WARNING **: 21:13:17,315: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-
openh264-44&arch=x86_64 [Connection timed out after 30002 milliseconds]
(process:773): librepo-WARNING **: 21:14:47,598: LRO_METALINKURL processing failed: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink ?
repo=fedora-44karch=x86_64 [Recv failure: Connection reset by peer]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (28):
Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-f44&arch=x86_64 [Connection timed out after 30001 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (56):
Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo-updates-released-f44karch=x86_64 [Recv failure: Connection reset by peer]
=================
Details for ig gnome:
Updating gnome
Refreshing package info
Removed 0 files, © directories (total of 0 8). 0 errors occurred.
(process:1172): ibrepo-WARNING **: 21:07:21.396: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-
f4d&arch=x86_64 [Connection timed out after 30001 milliseconds]
(process:1172): librepo-WARNING **: 21:13:21.412: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-
openh264-44&arch=x86_64 [Connection timed out after 30001 milliseconds]
(process:1172): librepo-WARNING **: 21:19:21.429: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-44&arch= 86_64
[Connection timed out after 30001 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (28):
Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-f44&arch=x86_64 [Connection timed out after 30001 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (28):
Timeout was reached for https://mirrors ..fedoraproject.org/metalink?repo-updates-released-f44&arch=x86_64 [Connection timed out after 30000 milliseconds]
===============
Details for \ gnome-NTFS:
Updating gnome-NTFS
Refreshing package info
Removed 0 files, @ directories (total of 0 8). 0 errors occurred.
(process:909): librepo-WARNING **: 21:07:21.794: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-
f4d&arch=x86_64 [Connection timed out after 30001 milliseconds]
(process:909): librepo-WARNING **: 21:13:21.811: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors . fedoraproject.org/metalink?repo=fedora-cisco-
openh264-44&arch=x86_64 [Connection timed out after 30001 milliseconds]
(process:909): librepo-WARNING **: 21:19:21.827: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-44karch= 86_64
[Connection timed out after 30000 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (28):
Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-f44&arch=x86_64 [Connection timed out after 30001 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (56):
Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo-updates-released-f44karch=x86_64 [Recv failure: Connection reset by peer]
==============
Details for ig fedora-44-xfce:
Updating fedora-44-xfce
Refreshing package info
Removed 0 files, © directories (total of 0 8). 0 errors occurred.
(process: 737): librepo-WARNING **: 21:07:13.287: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-
f4d&arch=x86_64 [Connection timed out after 30002 milliseconds]
(process: 737): librepo-WARNING **: 21:13:13.316: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-
openh264-44&arch=x86_64 [Connection timed out after 30002 milliseconds]
(process:737): librepo-WARNING **: 21:19:13.345: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-44&arch= 86_64
[Connection timed out after 30001 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (28):
Timeout was reached for https://mirrors ..fedoraproject.org/metalink?repo-updates-released-f44&arch=x86_64 [Connection timed out after 30002 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (28):
Timeout was reached for https://mirrors ..fedoraproject.org/metalink?repo-updates-released-f44&arch=x86_64 [Connection timed out after 30002 milliseconds]
Details for @ NTFS:
Updating NTFS
Refreshing package info
Removed 0 files, © directories (total of 0 8). 0 errors occurred.
(process:773): librepo-WARNING **: 21:07:17.285: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-
f4d&arch=x86_64 [Connection timed out after 30001 milliseconds]
(process:773): librepo-WARNING **: 21:13:17,315: LRO_METALINKURL processing failed: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=fedora-cisco-
openh264-44&arch=x86_64 [Connection timed out after 30002 milliseconds]
(process:773): librepo-WARNING **: 21:14:47,598: LRO_METALINKURL processing failed: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink ?
repo=fedora-44karch=x86_64 [Recv failure: Connection reset by peer]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (28):
Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo-updates-released-f44&arch=x86_64 [Connection timed out after 30001 milliseconds]
Failed to download metadata (metalink: “https://mirrors.fedoraproject.org/metalink?repo-updates-released-fad&arch=x86_64 ”) for repository “updates”: Cannot prepare internal mirrorlist: Curl error (56):
Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo-updates-released-f44karch=x86_64 [Recv failure: Connection reset by peer]
ChrisA
September 27, 2026, 9:02am
5
Hi Sabine
This looks like some connection issue.
can you share how the qube you were trying to install software into, should get access to the internet?
when you have the problem, does the qubes have internet connection? (eg. does ping 8.8.8.8 and ping dns.google.com work?)
Sabine
September 27, 2026, 2:00pm
6
I finally received the new router from Vodafone after a long wait.
Unfortunately, I can only connect to the internet right now if I first dial in with my cell phone and then with the router; the final speed is actually faster this way.
I’ve set everything up in Fritz.Box so that it should actually work.
That’s why I’m not sure how I can really solve this problem.
ChrisA
September 27, 2026, 6:40pm
7
Hi Sabine
It sounds like you’ll have to focus on one problem at the time - eg:
Does your DSL router connect correctly to Vodafone?
Can a standard computer/tablet/smartphone, running a standard OS (Windows / Mac / normal Linux distro, Andorid or iOS) use the router to connect to the internet via WiFi?
Can a standard computer, running a standard OS (Windows / Mac / normal Linux distro) use the router to connect to the internet via Ethernet?
Can a vanilla Qubes OS installation see the WiFi / Ethernet - and can sys-net connect to WiFi / Ethernet?
Can a more customized Qubes OS still use WiFi & Ethernet?
I admit, that the first steps are not related to Qubes at all - but I believe you need to check them, before adding Qubes to the mix of problems.
For the topic of this post:
I keep a small computer with Windows (LattePanda, SBC) around, for when my family asks me questions and want to read/move files on NTFS.
Sabine
September 28, 2026, 7:26am
8
ChrisA:
Ist Ihr DSL-Router korrekt mit Vodafone verbunden?
Yes, and I’ve set everything up, too.
ChrisA:
Kann ein handelsüblicher Computer/Tablet/Smartphone mit einem gängigen Betriebssystem (Windows/Mac/normale Linux-Distribution, Android oder iOS) den Router nutzen, um sich über WLAN mit dem Internet zu verbinden?
Yes, that should be possible, too.
ChrisA:
Kann ein Standardcomputer, auf dem ein Standardbetriebssystem (Windows / Mac / normale Linux-Distribution) läuft, den Router nutzen, um sich über Ethernet mit dem Internet zu verbinden?
Ethernet hasn’t been working for quite some time now.
ChrisA:
Kann eine Standardinstallation von Qubes OS das WLAN/Ethernet erkennen? sys-netVerbindung zu WLAN/Ethernet herstellen?
Only the cell phone is visible and can therefore be identified.
ChrisA:
Kann ein stärker angepasstes Qubes OS weiterhin WLAN und Ethernet nutzen
Fritzbox AX (that’s the one I have), but “Fritzbox UQ” appears at the top of the Wi-Fi Networks list.
ChrisA:
Ich gebe zu, dass die ersten Schritte überhaupt nichts mit Qubes zu tun haben – aber ich glaube, Sie sollten sie überprüfen, bevor Sie Qubes in die Problemstellung einbeziehen.
Yeah, that’s absolutely right. I hope someone else will read what’s written there and not say, “That doesn’t belong there.”
Yes, unfortunately my computer is broken, and my Lexmark CS 720 isn’t working either—that’s the other problem.
ChrisA
September 28, 2026, 8:45am
9
Hi Sabine
My intention for the list, was that you worked with each points, until you could say “now it works and I have tested it.” – so when I read “that should be possible”, I get the impression that you didn’t work enough with that point on the list.
Similar with the sentence “Ethernet hasn’t been working for quite some time now” – your router was replaced (IIRC), so why doesn’t the Ethernet port work on the new one?
If you only have one computer, invite someone with a laptop (family/friend/..?) over for a cup of coffee and test both the WiFi and Ethernet with a “Standard computer” (and a fresh ethernet cable).
The sentence “Yes, and I’ve set everything up, too.” makes me wonder if a “I would like ..” setting in the router config, is causing problems down the list?
Attempting to debug your Qubes problems in your current environment (where the network seems to be unstable/have issues/need some work) is very hard. :-/
Sabine
September 28, 2026, 8:59am
10
Thanks for your reply. I just spoke with a Vodafone representative about this and asked her if she could help me set up my computer.
Now I hope my computer will be working properly in a few hours.
Legend
I beg you, tell us how it worked out.
Sabine
September 30, 2026, 12:57pm
12
Unfortunately, the router still isn’t working.
It looks like I’ll have to do some more testing and try to figure out a solution.
According to Vodafone, I was given the wrong information.
Vodafone hasn’t processed my documents yet either. So, unfortunately, I’m on my own and not really making any progress.
Right now, I’m connected to the internet via my cell phone and laptop. I don’t know how much longer that will last, unfortunately.