Error 0x80070570
-
So here's me copying some files to a USB stick. I get the first batch of files onto it, and moved to the other machine - there's not sufficient network capacity to handle what I need to push, so USB sticks are a thing. Long story.
Anyway, I move the first batch of files, empty the stick and go to copy the second batch of files, only to receive the above error, which appears to be some kind of drive error. There's weird filenames on the thumb drive.
So I run the repair disk, it notifies me about a bunch of problems, claims to have fixed them. I go back to the drive, corrupted files are still there - but now I can't delete them because the filename is not valid.
Well done Windows, you have successfully repaired something that is now unusable.
-
Windows is built on the assumption that the physical hardware in the computer isn't defective.
-
Isn't the entire purpose of blue screens of death to not damage the computer if the hardware is defective?
-
Yes, and I'm well aware that the hardware is a little bit defective. However, don't tell me something is 'fixed' when you've ended up leaving it in a state that actually isn't usable anyway.
EDIT: In addition: why would you refuse to let me delete a file with an invalid filename if it already clearly exists?
-
The OS obviously thought it was fixed.
-
And you wouldn't, say, check before reporting success?
-
How do you know it didn't? It's flash memory, right? There's all sorts of hoo-doo going on there the OS has no ability to understand.
-
So it does some voodoo to 'fix' things. Presumably it would do another read to validate that what it is left with is, I dunno, valid?
As in, you don't tell users things are fixed when the filesystem clearly isn't. Repeated 'fixes' do not fix anything.
-
Maybe those file names are supported in 2065?
It's not Windows' fault you're using it 50 years too soon.
-
I say
dd
it from orbit. The only way to be sure.If you have access to a machine that can use
dd
that is.
-
You might have gotten a counterfeit USB drive. See http://sushifury.com/2010/03/i-got-sold-a-fake-usb-flash-drive-on-ebay-heres-how-i-fixed-my-situation-and-how-you-can-avoid-this-situation-yourself/
-
This is not my drive but a drive branded by the company of the person that I'm doing this for, and I don't think it's a fake drive. I think it's just legitimately faulty and I'm bitching that Windows handles it badly.
-
The names may have looked valid until the flash drive flushed its cache. For example. The point is, unreliable hardware is unreliable. You can't blame the OS. Be it Windows or anything.
-
They weren't valid before, they weren't valid afterwards...
-
They weren't valid before, they weren't valid afterwards...
Did you try renaming the file?
-
They weren't valid before, they weren't valid afterwards...
But were they different?
Look, I don't know how else to say it: unreliable hardware is unreliable. That's pretty much the start, middle, and end to your story. I don't understand the WTF here.
-
Did you try renaming the file?
It wouldn't let me because the filename was now invalid.
-
Oh yes, they were corrupted before any repair, differently corrupted after the first repair. Subsequent repairs altered nothing.
And I still have a 1.4GB file, allegedly, on this USB stick - despite Windows repairs - that I cannot open, rename or delete because its filename is invalid.
-
Well I'm sorry Windows wasn't able to magically wave a fairy wand and make your flash memory work correctly via elf magic.
-
I'm not expecting it to magically make it work, but I would expect it to actually say if it can't fix something. Especially when, repeatedly it tells me there is a problem, asks if I want to fix it, and fails to do so, but tells it was successful.
-
Can you delete the file from the command line? It may be an Explorer thing rather than an OS thing.
-
It doesn't matter, the drive is broken. The only correct action to take is to throw it in the nearest trash bin.
-
I would expect it to actually say if it can't fix something
Unless the device is lying to Windows and reporting success when it isn't actually doing what is asked.
Did you try to format the drive?
-
The filename has characters I don't even know how to type.
And yes, the trash bin is the next destination.
As for the device reporting to Windows... Windows was able to glean the fact that the drive is damaged, it tries to repair it... but does it not check once 'repaired' that it was actually able to achieve it? This is what I'm getting at.
-
Can you delete the file from the command line? It may be an Explorer thing rather than an OS thing.
This!
I had a batch of files that apparently were weirdly named and therefor made my explorer crash everytime they would show up. It was my first python script that handled this situation!
The filename has characters I don't even know how to type.
Use some sort of regex or stuff to filter for files that have characters other than normal ASCII + whatever you expect?
-
-
-
but does it not check once 'repaired' that it was actually able to achieve it? This is what I'm getting at.
And what I'm getting at is you have no idea whether or not the OS checked. The OS could very well have checked that the drive was ok, the drive said, "yeah I am good buddy!", then the drive re-mapped some blocks and suddenly, BAM, corrupted files.
-
Oh, I know it didn't check.
Because if I pull the drive out and reconnect, it tells me there is a problem. As in, a problem it was able to identify just by plugging the thing in. Which is when it tells me I should run a repair on it.
-
Your stick is toast, dump it and grab another one.
Windows probably sees gibberish in the FAT table or something like that and tries to fix what it can and reinterpret the rest. Ending up with garbage, since GIGO is still a thing, but apparently garbage that's valid enough to fool it into thinking "I fixed this".
Either format the drive (which should've been your first move really), or grab another one. They're not made of gold, y'know.
-
the drive said, "yeah I am good buddy!"
When he's right, he's right. The storage device says it is ok so Windows accepts this. You should use a tool designed to test/recover data from SD-cards/thumb drives.
The only fault Windows makes is that it believes the device.
-
Windows can't know if specific files are good or not, it can only check the FAT (or whatever NTFS calls its file mapping) and make sure the drive's formatting and overhead are correct.
-
whatever NTFS calls its file mapping
It's a pen drive; it'll be using some flavour of FAT.
-
Not necessarily, I used to use NTFS until Windows XP and Linux finally started supporting exFAT since FAT32 doesn't support large files.
-
It's a pen drive; it'll be using some flavour of FAT.
Because NTFS is some how unsupported?
-
Because NTFS is some how unsupported?
Because FAT is the default for that sort of drive, and most people don't bother changing it
-
The only fault Windows makes is that it believes the device.
Well, that may very well be but do you really want to incur the overhead by distrusting hardware?
At some point you simply have to say: "Good enough" for the sake of expediency.
-
Well, that may very well be but do you really want to incur the overhead by distrusting hardware?
The very first post I made in this thread is:
Windows is built on the assumption that the physical hardware in the computer isn't defective.
-
That's why I was disagreeing with calling it a "fault".
-
Yes well I was trying to make a "done in one" type post but. FINE WHATEVER!
-
It still doesn't necessarily follow that it's a pen drive and so it will be a flavour of FAT.
-
Yes well I was trying to make a "done in one" type post but. FINE WHATEVER!
Has that ever worked anywhere? ;)
-
It still doesn't necessarily follow that it's a pen drive and so it will be a flavour of FAT.
It's still a fairly safe assumption
-
The first thing I always do to any USB drive in my possession is format it to NTFS. It's slightly more fault-tolerant (plugging shit out too early and such) and allows for files larger than 4GiB.
I'd use ext4 TBQH, but I need to be able to use such things on Windows machines so NTFS it is.
-
Windows probably sees gibberish in the FAT table or something like that and tries to fix what it can and reinterpret the rest
In fact, since it keeps telling him there's a problem, perhaps it reported that it was able to fix the files even though it couldn't, and then the next time it plugs it in, it notices there's (still) a problem.
You can't really blame Windows for that.
-
Not necessarily, I used to use NTFS until Windows XP and Linux finally started supporting exFAT since FAT32 doesn't support large files.
Sure, but you basically have to manually reformat a flash drive to get it to use NTFS or something else. They still come FAT32[1]-formatted.
[1] ?
-
exFat maybe. It's been ages since anything was FAT32.
-
exFat maybe. It's been ages since anything was FAT32.
Yeah, that's what the footnote was for (too lazy to check).
FWIW I just checked a Silicon Power 32GB high-speed USB3 drive that I bought last year, that is plugged in to my computer, and it says FAT32. I should probably reformat that but then I'd have to copy 10GB of shit off it and put it back.
-
If you have a USB3 port, that'll take like 15 seconds.
-
If you have a USB3 port, that'll take like 15 seconds.
I don't (here at the office.) It would have to wait until I get home.
Oh, it's only ~6GB. It'd still take a while.