Used the version 1.4.4 of Etcher to burn linux mint ISO and the software reported that it had run and completed successfully but of course not only did it not burn the image, it also bricked my USB stick and it will only format as 2.2MB even though as of last week it was a perfectly working 128GB stick. I got the same error as the guy below who was trying to install Mint and got an efi folder and nothing else. Don’t use this software to burn a mint ISO. Thanks for nothing guys.
I was able to re-partition the drive to recover the USB stick.
Still don’t recommend this software.
exactly same thing happen to me
it turned my usb into 2.2mb , with only efi folder in it
able to re-partition the whole usb to recover
anyone know whats wrong?
Same happened to me. USB-stick was killed when flashing Mint 19. Etcher 1.4.5, macOS Mojave 10.14.
I’m still trying to bring my USB back alive to be usable again. Failed in my initial trials (on Windows).
How did you do to recover the stick? OS, Tool, command, settings? Thanks for any advice.
Apparently they have no answer for this. What good is having a forum if you are not going to participate in the conversation? I have been using this type of software for 30+ years and have NEVER had one that borked the partition as bad as Etcher did. Totally WORTHLESS software and I will NEVER use this poorly designed software again! Only value it has is it was free and I did not waste any money to find out how useless it is!
Hi, we are checking this out, and keep you posted. We don’t expect anything like this to happen,
I was using Kingston DT50 (DataTraveler50), 16 GB.
Happy news: I have reflashed the stick, and also tried and selected another way to boot the live-stick, and now I actually got it working! So, maybe it was just my mistake/competence in how I managed the boot options in my first trials. So for my case, you can close it as solved/no issue.
(By the way, I understand now (hope correct), that when checking the USB stick in Windows or MacOS, they will not recognized the “Linux part” or the stick; they will only see the boot part (efi-folder).)
@hehemrin yes, that last observation is very much correct - Windows sees much less than Linux and OSX devices. That was likely the issue, that on Windows you can’t always check if the end result is correct because of this.
Most of the time reformatting the disk with another tool should do the trick to put back your stick into it’s original - Windows-usable - state. (Windows prefers FAT or NTFS partitions, I think)
Thanks for the update, and glad things worked out!
Hello I also have the same problem, and it seemed that I had solved it until etcher told me this error when I wanted to burn the iso.
Hi @Sunk1911 ,
Is the source image (tahr64.iso) located on an external drive by chance?
Same thing happened to me. It bricked 4 drives. Use Rufus instead it works every time. I only tried this software because Proxmox said to use it. Never again.
Can someone please tell me how to get these drives back?