Oooh, the input/output errors are bad. That means that the reason the filesystem was corrupted is because your drive is failing. The only way to really recover from that is a reinstall, and you will need to reinstall to a new flash drive and probably discard the old one.
1 Like
fuck
Do you know how much flash drives cost?
They’re not cheap for sure; for me in the US, a good-quality 32 GB drive costs about $18-$30. I wish there was an alternative here, but I don’t think there really is. Drives have one job; store data without losing it. If you can’t store data (input error), or if the drive forgets the data you store (output error), it’s failing at its one job. Every time you write to a flash memory chip (and sometimes even when you read from it), it “burns” the chip a tiny bit in order to store the data. After the chip gets burnt enough, parts of it start burning out and either refusing new data or forgetting old data, which is when you start getting input/output errors. There isn’t any solution to this other than to replace the flash memory, which typically means replacing the whole drive.
It is theoretically possible that the issue is the computer and not the drive. Perhaps something on the way to the drive is not letting data through or is forgetting it. That’s relatively unlikely though, and you’d need a second computer to test the theory. If you have a second computer, you can try booting the drive into recovery mode and running fsck from that. If you get more input/output errors, the problem is almost certainly the drive.
1 Like
So it’s the drive, ok. Appreciate your help.
1 Like
Sandisk is terrible. 0/10