Linux Questions

2902 readers

19 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

possiblylinux127@lemmy.zip

[Thinkpad T14] Files become corrupted but only when downloaded (lemmy.world)

submitted 2 weeks ago* (last edited 2 weeks ago) by Imhotep@lemmy.world to c/linuxquestions@lemmy.zip

9 comments fedilink hide all child comments

I've acquired a second hand Thinkpad T14 recently (gen 1, Intel version). Running Fedora Gnome.

The SSD seems fine.
I tested it with Gnome Disks; I filled the drive with files and checked their integrity; also copied files around, on drive and from USB. No issues.

But many downloaded files become corrupted. The download finishes normally, but if If I try to open said files they fail (in the middle of a video for example) and if I copy them I get an "input/output" error.
LAN or WAN, over ethernet or Wifi, it doesn't matter.

Could it still be the SSD? Or maybe a driver issue?

Thank you for reading!

you are viewing a single comment's thread
view the rest of the comments

[–] themoken@startrek.website 3 points 2 weeks ago (1 children)

No sweat, I hope that's enlightening. Another thing that may be interesting is checking dmesg after you trigger the input/output error (or just generally since you are seeing silent corruption). Bad errors there are usually signs of hardware issues, and may also give you something more specific to search with.

[–] Imhotep@lemmy.world 2 points 2 weeks ago

Yeah I thought of checking dmesg too late, I was already running the - destructive - badblocks command...
It is finishing I think, and found zero errors.
My plan now is to install a different distribution to see if it makes a difference. I the error reappears I'll remember to check the logs.