Etcher Flashing Validation Failed #1725
Comments
|
Have you got a different SD card-writer you can test with? |
|
Same issue w/ a brand new SD card & brand new reader. More feedback form the app regarding what went wrong / how much validation succeed would be nice / help troubleshoot.
I tried flashing it w/ Win32 Disk Imager and it said 'Write Successful' though i'm not sure if that program does any verification. |
|
Might be with the zip handler (or the zip file) – will give this a run and check. |
|
Same problem here. On Windows 10 I tried several times to flash Jessie light onto two different SD cards (one of which brand new) with Etcher-Portable-1.1.2-x64. Each time I get the above potential corruption message. |
|
Are you all on Windows 10 Insider Preview builds? |
|
No, I do not use an Insider Preview version but a regular customer release of W10 |
@jhermsmeier I think this is not the problem. I did checksums (SHA256) and the generated code is the same shown on the raspbian download webpage, and I'm using the latest version of 7-Zip. I tried to flash with Win32DiskManager. The flashing proccess looks well done but my raspberry pi zero w dont boot. |
|
@Alpha-Phoenix wait, you flashed the same image with Win32DiskManager, and it still didn't boot? |
|
So, I just tested this on Windows 10 build 14393 and the current fast-ring Win 10 Insider Preview build, and the RPi Zero W I have here boots – can't reproduce this so far. @NateZimmer @Alpha-Phoenix what kind of SD-card reader are you using (make & model, or is it built-in, and if so, what machine is it)? |
|
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. |
|
I can't find my SD card reader (model or maker), but I've tried to flash using an usb adapter and the problem still happening. I'm using a ATIV Book 2.4 270E4E-KD5 14"" |
|
My trials were done on the internal cardreader/writer of a Toshiba SatelliteC50 laptop using Windows10 build 15063. |
|
I too am getting this message. Windows 10. Tried 3 different new SD cards. |
|
@AllistonJohn for me it was a bad SD card reader. I'd recommend trying a different SD card reader. |
|
Ok I will try that! Thank you.
John
…On Sat, Sep 23, 2017 at 9:25 PM, Nathan Zimmerman ***@***.***> wrote:
@AllistonJohn <https://github.com/allistonjohn> for me it was a bad SD
card reader. I'd recommend trying a different SD card reader.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1725 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ad19j6NRzF_bHAavzKnNub8J41E3JEzqks5sla-bgaJpZM4PR0dd>
.
|
|
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 tried different cards, and a different computer, a different formatter,
and a different flash utility and still got an error. I continued on and
used the card as is.
…On Wed, Sep 27, 2017 at 6:02 PM Ricardo Maroquio ***@***.***> wrote:
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?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1725 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ad19jwtgzjIVijPs0WF5hYg5NK2ChGaGks5smsYJgaJpZM4PR0dd>
.
|
|
@AllistonJohn @maroquio which image were you two flashing? |
jhermsmeier
changed the title
|
I also ran into trouble while flashing the Raspbian image to the Kingston 8 GB card. Etcher takes lot of time validating. Also, using windows 10. Etcher got stuck at 23% validating and showing 35 mins ETA |
|
I also ran into this issue, 4 of 6 SanDisk cards (16gb) where written with a validation failure. The file is 2017-09-07-raspbian-stretch-lite.img. I'm going to boot on them later one, hoping they will be ok. As something mentioned before, flashing with Win32DiskImager-0.9.5 doesn't gave any error (event with MD5 checked). Card read in Lenovo T460s built-in. |
|
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 burned it successfully in Linux command line and it’s working normally.
Regards,
Ricardo Maroquio
Em 26 de out de 2017, à(s) 15:35, Fabian Vilers <notifications@github.com> escreveu:
… 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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I have the same problem with a brand new SanDisk USB stick. Maybe this is because Windows is creating the "System Volume Information" hidden folder just after write is completed and volume is mounted - and before verification is done... |
|
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. |
|
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 had this problem too. I've tried flashing 2 brand new SD cards, and one new USB flash drive, al of which failed. I tried toggling all the windows power features on and off as well. After a couple of hours of frustration I decided to try another flashing software, Rufus worked in the first go. Although I really like etcher, I need it to work! |
|
I know this was closed a long time ago, but etcher still seems to have issues with a certain combination of OS and USB-flash-reader/writer hardware. Just adding more info in case it helps anyone get around this. Just downloaded etcher 1.5.45 portable (on Windows 10). It is failing on a DigiPower Multi Card Reader - Model No: DP-MCR4 (reader/writer works fine otherwise) with a Sandisk 32GB Ultra microSDHC UHS-I card. Not getting the popup message, but there is a subtle, almost unnoticeable, red dot on the final screen that says "1 Failed Device". When I hover the mouse pointer over that I get an explanation that the "Source and destination checksums do not match" Same failure occurred for both the zip of 2019-07-10-raspbian-buster-full (~2.4 GB), and the unpacked .img file (~6.3 GB). The files are stored on an NTFS drive, so file size shouldn't be an issue. The .img file was unzipped using 7zip so the zip64 format shouldn't have mattered. One thing that might be interfering with etcher is Windows' disk/drive management. After the flash/validation process is complete, Windows displays a "Format disk" prompt saying that the flash drive must be formatted before it can be used. Clicking cancel presumably dismisses that prompt without Windows taking any action. But, if that could be disrupting the validation/checksum process, maybe there is a way etcher could prevent Windows from attempting to re-mount the drive/filesystem until the validation is complete (if so, someone could open a new github issue for that). After etcher flash/validation, and after disconnecting and reconnecting the USB flash reader + card, Windows shows that there is a valid boot partition on the microsd card. The card still boots up, resizes the filesystem, initiates the Raspbian Buster setup process, etc. I still have concerns using etcher (with this combination of OS and reader/writer hardware) that there will be something corrupted on the flash drive and I won't find out what it is until much later, so unless I can dig up another reader/writer that works, I'm with @jungerm2 ... can't use Etcher right now.
|
|
@rthomas67 See #2210 ? |
|
Sorry about resurrecting this old thread, but I agree with @fvilers! |
|
2 weeks ago working windows update borked. ig alternatives rufus , etc seems to hang . |
|
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 checksum error with different ISOs on different USB ports with differents USB. Definitely it's a software error but don't know what's happening. I tried with an AC power plugged and didn't work, and also without AC Power plugged and I'm on Ubuntu 20.04 and in the past I used balena a lot of times for different ISOs without problems. However, now any ISO validation finish in ckecksum error. Without validation, installing Ubuntu on the SSD gives an error of files corrupted. What's happening?
|
|
@ZurMaD It might be worth opening a new issue, rather than adding comments to an already-closed issue. |
|
@dundir It seems those cheap XX-in-1 card readers tend to be generally unreliable, see e.g. raspberrypi/rpi-imager#212 |
|
All Microsoft product is a useless sh..t, it is fact, but this error not unconditionally Windows 10 bug, because i use Debian Linux, but i got same issue. |
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?
The text was updated successfully, but these errors were encountered: