Thanks guys. I forgot how freakin' long it takes to scan these drives.
I managed to run a scan on all three drives and it seems to have turned up with no errors, so I think they're fine for now.
I have been running a couple benchmarks on them, but I noticed a peculiarity. Currently, I'm using my rig in my sig, and my 2 external eSATA enclosures are hooked up to my JMicron JMB363 (I think; Device manager only says 36X) SATA controller. The controller controls both SATA ports, as well as an unused IDE channel.
I noticed that when I benchmarked one drive alone on one particular SATA channel, it would start off at around 140mb/s read before gradually dropping down. When I tried to benchmark both drives at once though (through the same controller) both drives immediately tanked down to 60ish mb/s read until I stopped one of them. I suppose this isn't a good idea.
Curiously, when I switched the same hard drive that benched 140mb/s read to my other enclosure running on the other SATA port, it seems limited to 125mb/s read no matter what. If it somehow starts off above that, it nearly immediately spikes down very low before "recovering" to just under 125mb/s and staying there, almost a straight line, until the drive normally can't sustain 125mb/s read.
I switched the HD back and forth and ruled out the HD being faulty; I also switched cables on the enclosures to rule out the enclosure. I thought one of my SATA ports was acting up at this point, but I just decided to switch the ports to rule out the cable, and the effects reversed themselves... SO, my ports are actually fine, but it was the stupid cable causing problems. So much for these SATA2 cables from Monoprice.
I swapped the cable back to the standard eSata cable supplied by Icy Dock and I'm back in business.
I'll post the screenshots in a couple hours, as I'm still running HDTune and CrystalDiskMark to verify that everything is peachy now. Are there any particular settings I should be using? I'm using default settings in HDTune (partial test, close to accurate, 64kb block size) and for CrystalDiskMark, I'm using 50/100/1000/4000MB test sizes. So far it doesn't seem as close to the benches I've seen of the WD1002FAEX; or at least not as close as I imagined it would be.