The device should be okay for the time being, so I think you should have time to replace the card. We haven’t had any experience with Transcend Premium, hence our recommendation of the tried & tested type above.
The integrity checks are done through checking against the fingerprint file shipped with the system. It’s found at
/resinos.fingerprint in the host OS. It can be checked by running
md5sum --quiet -c /resinos.fingerprint
Please note, that some checksum fails are expected, as they are overridden at runtime by device-specific versions, thus they will fail the check, this is fine and does mean normal operation. For example on current OS versions this result would be a good outcome:
root@xxxxxxx:~# md5sum --quiet -c /resinos.fingerprint
md5sum: WARNING: 3 computed checksums did NOT match
There’s also checksum on the files in
/mnt/boot (the boot partition), which can be checked by
cat /mnt/boot/resinos.fingerprint | sed 's/ \// \/mnt\/boot\//' | md5sum --quiet --check -
This should report a few files changed that do change in the normal course of operation (such as
cmdline.txt, etc. on the Raspberry Pi for example).
Please note, that these might change, and the fingerprints are used only for general diagnostics, as part of a whole toolset to debug devices misbehaving. We don’t really recommend relying on this in your day-to-day work with devices, and if there’s any checksum failures, don’t recommend jumping to conclusion. We just mention it here to give you some more background info. Overall we are working towards ensuring that you wouldn’t need to do these checks ever, and have a well behaved device without worrying about data integrity.