this post was submitted on 15 Nov 2025
18 points (90.9% liked)
Linux Questions
2866 readers
1 users here now
Linux questions Rules (in addition of the Lemmy.zip rules)
- stay on topic
- be nice (no name calling)
- do not post long blocks of text such as logs
- do not delete your posts
- only post questions (no information posts)
Tips for giving and receiving help
- be as clear and specific
- say thank you if a solution works
- verify your solutions before posting them as facts.
Any rule violations will result in disciplinary actions
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Huh, storage or RAM problems would be evident in your file tests (and elsewhere). Can you visit websites normally? Stream YouTube etc.? It would be very strange for a broken network device to corrupt files.
Also, since you didn't mention where the downloads are coming from... No chance of corruption at the source?
The input/output error makes me think disk issue (since it should copy corrupt files just fine, it's just data) but that should also be triggered by copying from a separate device. A more thorough disk check may be in order, like a badblock run or something.
Is there any chance this could be caused by malware on their router? I'm puking this right outta, well, you know where; just curious if the evidence would even fit my theory...
I mean, anything is possible, but that seems farfetched to me. The router is typically a hard target for malware unless you have physical or at least LAN access. They are generally pretty locked down and don't execute anything from remote access, they examine packet headers and send them on their way. If it was compromised I'd expect something more nefarious than ruining file transfers too.
The biggest strike against this being a network hardware/driver issue is that normal browsing works. If packets were being screwed up in transit, connections would drop, text and images would be corrupt as well (which the browser would probably choke on). It seems to have an issue only when the disk is involved, when data is being saved.