WD Red 3TB NAS Hard Disk Drive - 5400 RPM Class SATA 6 Gb/s 64MB Cache 3.5 Inch - WD30EFRX (Personal Computers)

On Windows it comes out to 5.45TB. I transferred a little over 2TB to it and average write speed was 110MB/s. Right now it's just sitting on top of my computer case but after that long transfer I used a temp gun and the surface of the case was 87F and the drive was 101F.UPDATE ****I just purchased a second drive and did some testing on it while blank and uploaded the results under customer images to the right. if (typeof amznJQ != "undefined") { amznJQ.onReady('jQuery', function() { amznJQ.available('popover', function() { var widgetDom = jQuery("#R1DNK1Q35UIWJ_imageSection_FA238A62-41AD-11E6-ABD9-2C376D14C1BB"); var images = widgetDom.find(".review-image-thumbnail"); for (var c=0;c

   Here is a quote from a review at pcper.comI'm going to let the cat out of the bag right here and now. Everyone's home RAID is likely an accident waiting to happen. If you're using regular consumer drives in a large array, there are some very simple (and likely) scenarios that can cause it to completely fail. I'm guilty of operating under this same false hope - I have an 8-drive array of 3TB WD Caviar Greens in a RAID-5. For those uninitiated, RAID-5 is where one drive worth of capacity is volunteered for use as parity data, which is distributed amongst all drives in the array. This trick allows for no data loss in the case where a single drive fails. The RAID controller can simply figure out the missing data by running the extra parity through the same formula that created it. This is called redundancy, but I propose that it's not.Since I'm also guilty here with my huge array of Caviar Greens, let me also say that every few weeks I have a batch job that reads...Read more