Wasn't this the reason you couldn't run these drives in RAID? I could swear users were aware of the direct cause of this issue before, interesting to see that WD is just now acknowledging it.