Domain changed to archive.palanq.win . Feb 14-25 still awaits import.
[11 / 1 / 1]

Accidentally corrupting USB drives

No.1485977 View ViewReplyOriginalReport
Hey there, /wsr/!

I think I might've accidentally corrupted 2 of my USB drives and I'm trying to figure out the exact issue so that I won't accidentally kill anything else.

I have an old PC which is running both 98SE and XP and I spent the past couple of days downloading all sorts of drivers and software for both of those systems, just simply storing them in a folder on my main PC (running Windows 10) because the old one isn't hooked up to the internet. The idea was to collect everything here, then transfer the folder to a USB drive and then transfer it from the USB drive to my old computer.

First of all, transfering the files to my first USB drive took unusually long, around 4 hours for just 30GB. Everything did transfer though and I just went to go sleep after.
Now today I wanted to add something else to that drive, plugged it into my main computer again and while it did get recognized, it wasn't showing the capacity anymore. Trying to open the drive results in Windows Explorer freezing, same when I try to format it. I then tried to wipe it with GParted, which just resulted in an "Input/output error during write" error. Tried it out again afterwards and it's still the same. I believe that drive was GPT and formatted in FAT32, non-bootable.

Suspecting the drive is just fucky, I tried to copy those same files over to my OTHER USB drive (same make, 126GB or so Intenso, but this time bootable with Windows 10 on it) and cancelled the process when the writing speed for some reason slowed down to a permanent 1 KB/s. This one works almost like before, the problem here just being the tiny bit of the folder that I was able to transfer - I can't delete or modify any of the folders or files inside. I also can't format this drive anymore either, neither in Windows 10, nor with Gparted. Trying to wipe it in Gparted spits out the same error I got with the first drive.

Both drives worked perfectly fine prior to this.

Anyone have any idea what the issue might be?