stressdisk

gcd(0x2200,0x7800) = 512 So some part of the chain with 512 byte buffer size corrupted the data. It doesn't look like a memory corruption but if this were my computer I'd run the equivalent of memtest86 on it. It looks like a filing system corruption to me. Running `diskutil info` on the main harddisk and the sd card might be interesting to see if the block sizes match. Running a disk tester on the sd card and the main disk might be a good idea too. Here is one I wrote: https://github.com/ncw/stressdisk

Here is a little program I wrote to stress test disks. It was originally written for HDD but it works well on SSD and Flash too. I test all my media with it for 24 hours. In fact I'm testing two 5TB external Seagate drives as I type! https://github.com/ncw/stressdisk

A long time ago I wrote a program for stress testing hard disks. You can download the modern version of it here: https://github.com/ncw/stressdisk It got used a lot to soak tests disk for servers that were going into production or being shipped out to far away places. However it quite soon became apparent that a lot of the errors weren't caused by bad disks at all, but rather by bad RAM. It even discovered a set of bad RAM for 200 computers which passed all the manufacturers tests but failed when in use. Moral of the story: if you care about data integrity check your RAM as well as your disks! I run memtest86 then stressdisk on any new systems I'm building. Also, testing RAM is hard! Memtest86 does an excellent job, much better than the manufacturers tests.

If you like testing your media then you'll probably enjoy: https://github.com/ncw/stressdisk my project to test media. I test all my flash / hard disks with it and have sent plenty back over the years which failed!