RAM corruption, possible eMMC corruption
Hi everyone,
I've been tinkering with my PinePhone for a while and noticed that eMMC is likely corrupt/being corrupted sometimes.
I tested that by downloading files from remote host and checking if their sha256sums match, which they didn't. Also rsync just fails to copy file quoting the same mismatch error.
After running PostmarketOS update using apk update && apk upgrade it just stopped unlocking (lock screen just reappears after a valid pin code), though apk verify said nothing about that.
I'd like to know if anyone else has/had that problem and if there're any workarounds to get eMMC stable.
Forgot to mention: I also tried mounting tmpfs (which should be RAM-backed, I believe) and downloading my image there, but the result is the same — checksums mismatch
Another addition: each time I run sha256sum on the same file, it yields a different checksum, so that's possibly RAM and not eMMC (updating thread title as well)
I've been tinkering with my PinePhone for a while and noticed that eMMC is likely corrupt/being corrupted sometimes.
I tested that by downloading files from remote host and checking if their sha256sums match, which they didn't. Also rsync just fails to copy file quoting the same mismatch error.
After running PostmarketOS update using apk update && apk upgrade it just stopped unlocking (lock screen just reappears after a valid pin code), though apk verify said nothing about that.
I'd like to know if anyone else has/had that problem and if there're any workarounds to get eMMC stable.
Forgot to mention: I also tried mounting tmpfs (which should be RAM-backed, I believe) and downloading my image there, but the result is the same — checksums mismatch
Another addition: each time I run sha256sum on the same file, it yields a different checksum, so that's possibly RAM and not eMMC (updating thread title as well)
