Error couldn't clean the drive...

• **Etcher version:**1.2.1
• Operating system and architecture: Windows 10 Home v. 1703, built-in SD card reader (Samsung 32 GB micro SD card in adapter)
• Image #flashed: Retropie 4.3
• Do you see any meaningful error information in the DevTools? Yes, although I’m not sure what it means.

I am trying to install the retropie onto my SD card, however Etcher keeps hanging on “starting” for a few seconds then erroring out (see below). So far I have tried to reinstall Etcher a couple times, tried to run Etcher as both administrator (I get the error) and not as the administrator (just hangs on “starting”). I tried cleaning the SD card with diskpart, however I keep getting this error. I can manually copy files onto the SD card from within windows, so the SD card isn’t locked out.

Any advice that can be offered would be greatly appreciated.

Thank you.

Windows Error Message:

Etcher DevTools

[MakiseKurisu]

Here is a workaround (for me at least) for “cannot zero sectors on disk” with error code 5@0101000F. All is done through diskpart so Etcher can incorporate this with your own diskpart script:

list disk #find out which disk you want to wipe
clean #throw out error, just a confirmation step but I always do this before applying workaround
convert gpt #disk in question is in MBR. I only burnt MBR image so I don't have a case where disk is in GPT
clean #this time you should be able to wipe the disk

No reboot or unplug reqiured. By doing this Etcher will be able to clean the disk again and complete the burning process.

[HennieLouw]

Hi All, Small thing, but I also get the "couldn’t clean the drive’ error.

Then I created a new local account with a username that has no spaces in it. Works like a charm.

I suspect that the ‘diskpart’ operation isn’t escaping spaces in the path. I’m not able to test it now, but perhaps a small tweak to the line https://github.com/resin-io/etcher/blob/93b772f1976d5f7989d900d6fdcf9f9c84759694/lib/cli/diskpart.js#L72

childProcess.exec(diskpart /s "${filename}", (execError, stdout, stderr) =>’

Would solve the problem.