My question too, just as Kangalow asks…JetPack isn’t meant to run from Jetson, the encoding error is quite unusual and has me wondering if that is the case. As far as encoding error, you could get slight increases in information running ls through base64 (not readable in the usual sense, but easily copied and pasted over the web) or cat -r (indicates control characters, but others may not show exactly):
ls -l * | base64
ls -l * | cat -r
In any case an encoding error (if run from a host it is meant to run from) would imply some rather severe corruption. On x86 machines I use memtest86 to burn in all new hardware, it might be interesting if there were some way to adapt to ARMv7. The question of memory testing won’t apply though until knowing JetPack was run in the correct environment.
EDIT: Additional note…this still wouldn’t account for the SATA error.