etcher: Etcher Flashing Validation Failed
- Etcher version: 1.1.2
- Operating system and architecture: Windows 10 x64 Build 10.0.15063
- Image flashed: RASPBIAN STRETCH WITH DESKTOP
- Do you see any meaningful error information in the DevTools? It can not open
I’m having problems when flashing raspbian stretch image into my Raspberry pi zero w. I tried to flash on linux and windows with various sd cards (8 GB | 16 GB) but the problem persist. This is the error message shown by etcher.
How can I fix this?
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 35 (9 by maintainers)
Sorry about resurrecting this old thread, but I agree with @fvilers! It seems my Windows 10 Notebook only corrupts SDCards only when I run the Balena Etcher flashing/validating processes depending on battery…! The issue does not happens when my Notebook is being powered from power switch. Wouldn’t it be time for calling testers to check this scenario? After receiving enough feedback, the Balena Etcher development team could add an alert / warning message, right before the process begins.
Thanks @fvilers - that was the lead I needed. In my case I was trying to write the SD card on my laptop, but it only validated successfully once I was plugged directly into the mains adapter and not through a docking station, so the issue went beyond just Windows 10 battery/power/energy saving. I hope this helps someone!
I think this is definitely Etcher issue. I use the internal PCIe SD card reader on my HP Elitebook 8460p and using ANY SD card (several Adata, Kingston, and Sandisk 16GB and 32GB) I get the message trying to image 2018-10-09-raspbian-stretch-lite.img to SD. Indeed the files in the SD are corrupted as Raspbian fails to boot properly and many things show as fail on OS load screen. However using the same MicroSD and cards and reader I can image using Win32DiskImager v1.0.0 and everything works just fine. This is not a matter of verification failing, Etcher is actually writing corrupt data to SD card.
Guess what? I successfully flashed all my cards with the laptop running powered on the sector. It seems like Windows 10 battery saving can cause issue with the flashing process, maybe a read or write rate not high enough.
I got this error on W10 1903 as well using the same 42-in-1 reader with an ONN Micro SD card.
Digging into it a bit deeper this looks like a low level problem with either the reader, writer or both and not etcher.
I ran some benchmarks on linux with dd instead and what appears to be happening is it will be able to read up to some point and then all the blocks after that throw a buffer_IO error on async page write.
Sometimes it can read/write with no issues (briefly), quite a lot of the time it fails.
Also, just for giggles I bought another of the same brand (from Walmart) and get the exact same issue when swapping either the memory card or the reader, so it looks like there is a flaw.
Maybe if I can find some time in the next millenia I’ll dig into it with an oscilloscope.
Same problem here, with a internal SD reader of a 2016 Dell notebook and with a SD reader in my desktop. If I made an image of an old card with Emlid Raspbian and flash it, no error occurs. Someone know what is happening? I’m using Windows 10 with latest updates.
I am using a ‘Digipower 42-in-1 Card Reader’ USB to SD card(walmarts best).
I just tried it again with a different brand new SD card on my HP Printer(which has a built in USB->SD) and it worked. Either the prior card or the prior usb->sd reader is suspect. Will update this once I figure out which.
Edit: Must have been a bad SD card reader. Have flashed 3 SD cards since w/ this tool and the verification worked fine once I switched readers.