Anyone ever have a write-blocker that somehow altered data in transit coming from the source drive? I was copying some data using a write-blocker and noticed when I hashed the copied files, they didn’t have the same hash values as I was told the files were meant to have. I thought perhaps the write-blocker was faulty in not protecting the source, but when I swapped it out with another write-blocker, and did the copying process again, the copied files now had the correct hash value. I tested copying the files a number of times with the ‘faulty’ write-blocker, and every time I got different hash values on copied files. Seems very weird to me. Any thoughts what could cause this?