I just tried (several times) burning the ASDB-X latest image file on a Win 10 PC using Etcher. I extracted the image file, and then used Etcher. 1. The target micro SDHC card is a Samsung 32 GB Pro Endurance (smallest card I could find that can take writes for extended periods) Target Pi is a 4b. 2. Etcher reports flash failed at every attempt, yet I see the /Boot directory and most of the files in Windows. 3. Windows constantly shows card properties as 256 GB, not 32. WTF? 4. Windows bitches about formatting the card after Etcher runs. After failed burns, I tried reformatting the card in FAT, FAT32 and EX FAT with the same burn fail messages from Etcher 5. Does the image file / Pi4b require a specific file format? or does the image file make it's own? 6. I haven't tried to boot the Pi from this card yet because I don't want to ignore the Etcher burn fail message. Aloha and Gracias! My other feeder is doing just fine. This second one is 2 of three that will get deployed elsewhere around me.
The size discrepancy of the sd-card and the errors would suggest to me: You got a counterfeit non-functional card. The boot partition is at the start and pretty small. Often counterfeit cards have a very small capacity which would lead to exactly what you see, first bit goes fine, then it fails.
Same thing just happened with another brand new 32 GB card. It does the burn, completes the validation phase, then fails during the finishing message in Etcher. I checked the card before hand and it showed 32GB in FAT32 format. After burning, I see the card is labeled Boot, (46 files in the root) with one subfolder named overlays ( w/ 243 files) and 48 MB used out of 242 MB unused space. So not a bad card. Etcher at fault? win 10 issue? Any alternate methods to try?
Forgot to mention that after the burn fail the card is ruined and can't be formatted bact to 32 GB capacity.
Card recovered by deleting all volumes found and reformatting with Disc Management. Bact to a clean 32 GB FAT 32 card.
Try and place 4 GB worth of files on the drive and see how that goes .... almost can guarantee you that it will fail.
Lessons learned: Both Cards were good. Etcher invokes various windows processes during burning the ADSB-X image that result in burn failure messages, which then invoke windows error messages about having to format the card. I tried 2 brand new cards in 3 Win 10 computers with the same failed results. What did "apparently" work is that I skipped verification in Etcher and ignored the Windows warnings and ejected the card, re-mounted and edited the config file and loaded the card into the Pi 4b. Guess what It booted and seems to be feeding! My best guess about this mess is that the boot partition must be FAT, and the rest of the card must be EXT4, and Win 10 does not understand EXT4, hence the "format the card errors" from windows.
Is it a windows warning now or an Etcher error .... big difference. I mean i'd say it's obvious you can't format after burning an image file ... if you do you destroy the image you just put on the card. Maybe the superfuous Windows warnings need some mention in the guide .... if they don't have already.
No, I did not accept the WIN message to format the card(s) after burn. I get the Etcher burn fail message AFTER the validation complete message then Etcher says "Finalizing" then Burn Failed, followed up by a bunch of win 10 warnings about the card not being accessible, need to format the card, etc. The new feeder is working, but not correctly in toto. There has got to be a be a better way to deploy these "appliances" as you so aptly noted in another thread here. I'm trying to deploy multiple feeders here in the Hawaiian islands and just want minimal drama. And NO the guides say nothing about ignoring superfuous Windows warnings. BTW the R Pi 4 site says you have to manually expand the EXT4 partition. Help me make this simple and I'll deploy more. Mahalo Mr. W
to be clear, as I posted above "What did "apparently" work is that I skipped verification in Etcher and ignored the Windows warnings and ejected the card, re-mounted and edited the config file and loaded the card into the Pi 4b." I'm not an idiot that would format a card after burn.
Have you tried the Raspberry Pi imager? https://www.raspberrypi.com/software/ We're working on making it simpler ... it takes time, i'll very likely change the guide over to Raspberry Pi imager, Balena has been a bit of trouble lately. How is it not working correctly?
Balena Etcher always reports "Burn Failed". It completes the write, completes the verify, but the errors out as soon as the "Finishing" message pops up. I just tried the Pi Imager and it works fine. Windows still complains about needing to format the card after the burn, but as I said earlier I've been ignoring those messages anyhow. Thanks to pointing me to the Pi Imager!
