Pass 1 (forwards)ĭdrescue: Write error: Input/output error
Opos: 434765 kB, run time: 42s, remaining time: 5mĬopying non-tried blocks. Rescued: 434765 kB, errsize: 0 B, current rate: 2228 kB/s
Is Etcher the problem? Of course NOT! Trying it also with ddrescue and same situation: ddrescue also already reports an error while burning:īash-3.2# ddrescue -force /Users/tk/OMV_4_Renegade.img /dev/rdisk2 This is repeatable with 4 of those crappy 4 GB TF cards (I stopped then testing). Try to burn an Armbian image and Etcher reports an error already while burning. I put the TF card into the SD card adapter, then the adapter into the USB reader and attach the reader to an USB3 port of my laptop. Also involved: a crappy USB SD card reader/writer:
We recently replaced a bunch of crappy Intenso TF cards with SanDisk Ultra A1 at a customer so now I have something crappy to play with. Since I fear a lot of people still do not get that every burning tool that does not verify burning results is CRAP I just did an experiment. So why shouldn't be there firmware updates? And of course there's a controller running a software that can be buggy. Why? These things are complex, they have an SDIO interface to access the flash media and an USB controller to present the storage as mass storage device. Thanks for the firmware-link, I never thought about a update to a card-reader/writer
