etcher: operation timed out after X ms, 5 tries with error: Command failed: diskpart /s "C\Users\\AppData\Local\Temp\_diskpart\-xxxxxxxxxxxxx"

@jhermsmeier Did you have a chance to look at the unmounting repo?

@jviotti yeah, fiddled with it a bit, and started reading through the win32 API docs, but haven’t gotten around to anything substantial yet.

I tried the card on my laptop and in several lab systems with the same result.

@Ringworks where there any systems you tested where the card reader was external?

My bad, didn’t look to hard at the dd command, just copied and pasted it this morning half asleep. For some reason I thought it was zeroing the whole 32GB.

Were they purchased from a reputable store, or is it possible that they’re fakes? They were purchased form a reputable source, not to worried about, still have 10 days left to exchange/return them. I bought more than two, and those two happen to be the only two to display symptoms and where the only ones I chose to “burn” using Etcher in Windows. All the other disks worked perfect in the Ubuntu VM with Etcher.

I have a laptop with Debian on it, I’ll see if there is GParted provide better result indirectly with Hardware. I’ll need to charge it and blow the dust off it, I’ll report back in tomorrow.

Hi @Lefel95 ,

Thanks for reporting! Can you show us where Etcher says your drive is corrupted? Regarding the error that you show there, it seems that for some reason diskpart was unable to clean your drive.

Is this something you can actively reproduce only with a certain image? If so, can you link us directly to the image so we can try it ourselves?

If you can actively reproduce, can you try the following right after you get the error shown above?

• Open cmd.exe
• Execute diskpart.exe
• Execute list disk to show the available drives. Take note of the id of the removable drive
• Execute select disk N, where N is the id of the removable drive obtained above (make sure you select the right one, otherwise you might wipe out another drive unintentionally)
• Execute clean

The last command hopefully reveals more information about the issue.