brainsucker

Ok, I was stupid enough to fetch the latest nightly build and expect it to work flawlessly (well, played that game many times building openwrt from trunk, never had an issue . Re-etching the latest legacy xenial (3.4.*) fixed the issues immediately, apt upgrade-ed 60+ packages within a minute (was failing within 2-3 with nightly), iozone also completed without any issues. Iozone results with 4k blocks are a lot lower than in epic (SD cards benchmarks) thread, not sure if this is caused by legacy kernel or any other issues or misconfigurations on my side (default governor, etc, etc). Anyway I'm quite happy my EVO+ card is fine (finding it broken would be a shame considering it costs more than OPiZero . If anyone wants me to perform any tests with legacy, nightly or any other builds I'm ready to do so, otherwise I'll probably stick with legacy for a while (mb until mainline release). I had an idea of putting uboot to SPI flash (my 512MB version got it from factory) and trying nightly with USB card-reader and same card (not like that'll prove anything), hopefully I'll find some spare time for that later.

Same thing happens just after iozone start. A bit funny iostat goes haiwire at the same time: mmcblk0 858986433.60 429484694.20 429470094.40 2147423471 2147350472 Copied/verified a few huge files to the card in windows - everything is fine, performance close to declared. Also I tested card with f3probe (ubuntu through virtualbox): capacity is completely real, no errors found, test done in 12 minutes. Still hungry for ideas / possible tests, board seems a bit unusable in such state.

Hello. Got the same issue with a fresh Orange Pi Zero (512MB w SPI flash) and fresh Samsung EVO+ 32 gb card (reputable enough, I think ). "Thing" happens both in 5.24.161226 beta and the latest 5.24.170114 nightly. Just in case anyone wants to look at it: http://sprunge.us/hXAd I might give sd card a test tomorrow (F3 probably), but since its a recommended evo+ bought from well-known computer store (authorized dealer) I highly doubt issue is in card itself Any solution yet? (ideas, or anything I can test are welcome as well) Thanks, Nik.