WD Introduces Red: NAS Optimized HDD Line
by Jason Inofuentes on July 10, 2012 8:13 AM EST
WD did everyone a favor when they reorganized their products under color-coded branding a few years ago. With the Blue (mainstream), Green (quiet and cool) and Black (performance) lines well laid out, consumers have a much easier time picking out the right drive for their application, rather than poring over spec sheets and complex model numbers. And now there's another line to add to that list: Red. Designed specfically to be used in 1-5 bay NAS devices, the Red line has hardware and software features that make it suited for that particular climate, while delivering impressive performance and reliability. WD has worked with major NAS manufacturer's to ensure compatibility with as many common NAS products as possible, and has a list of the tested devices here.
The secret sauce in these drives is the firmware, or as WD is calling it NASware. NAS devices in the home are often used for bulk storage of media, they may have some shared documents and be used as back-ups, too; but they're most often used to store movies, music and images. ATA streaming command is featured in NASware, to alter the behavior of the drive while streaming media, in an effort to ensure smooth playback, even while serving mutliple streams. They've also included error correction optimizations to prevent a drive from dropping out of a RAID array while it chases down a piece of corrupt data. The downside is that you might see an artifact on the screen briefly while streaming a movie, the upside is that you won't have playback pause for a few seconds, or for good depending on your configuration, while the drive drops off the RAID to fix the error.
Then there's the matter of performance. With quoted performance of around 150 MB/s these drives are nudging into Black territory. WD's new balance mechanism contributes to this. By actively balancing the drive during use there's no need to slow the drive down to prevent damage, so performance remains high. There's also a reported power savings, which WD says will make up the price delta for these drives over the rest of the line through your power bill. Speaking of price, the MSRP for the 3.5" 1TB, 2TB and 3TB drives are $109, $139 and $189, respectively. And these drives are available at your favorite e-tailer starting today. Ganesh is patiently awaiting our review samples so he can put them through the ringer and see how they do.
Facebook
Twitter
RSS
39 Comments
View All Comments
n0b0dykn0ws - Tuesday, July 10, 2012 - link
I can't wait to see benchmarks, especially if there are some for a 5 drive RAID 5 configuration.Souka - Tuesday, July 10, 2012 - link
and also power consumption/heat.I have a 2-bay NAS running WD Blue in Raid 1, but they're 250GB so 250GB total space.
with more digital data to backup these days (pictures and family movies)...two 1 to 3TB drives would be nice. :)
brshoemak - Tuesday, July 10, 2012 - link
This will really undercut prices of their RE lines, which is fine by me - I never really liked the 'TLER tax' on those drives. Point of references, on Newegg the 2TB RE drives are $230 while the Red version is $140 - and hopefully prices will go down some from there. I know there are differences in the drive lines beyond that, but being designed for RAID arrays is really the only thing that matters to me.Sivar - Tuesday, July 10, 2012 - link
TLER Tax describes it well. The price bump just for the privilege of the hard drive having less aggressive error recovery seems pretty absurd.For most arrays I usually use consumer drives and, if one is reported as dropped, I RMA it. Let the manufacturer eat the expense for the feature they no longer allow users to disable.
ckevin1 - Tuesday, July 10, 2012 - link
I'm interested in hearing how the TLER works on these. For instance, is it situational based on ATA command, or is it always on?I'm very tempted to buy this instead of a green for a desktop data drive -- the warranty is appealing, as are the improvements to balancing & reliability. My only concern is data loss from the time-limited error recovery. Back before I knew better, I used to use a WD RE as a standalone drive, and I had TLER-related corruption problems (which is understandable, since it was designed to have a RAID controller performing error recovery for it). The marketing materials say that Red drives are supported in a 1-bay NAS, however, which suggests to me that they shouldn't have the same issues.
Hopefully this feature can be covered in detail with the eventual review!
creed3020 - Tuesday, July 10, 2012 - link
I just bought a Synology DS212j and this product launch has me really interested. I have one WD 500GB RE4 in my NAS currently but my second slot is currently empty. With this new product I am eager to hear the reviews focusing specifically on their behaviour with RAID arrays, performance, temperature, and power draw. WD might have a real winner here. I also love how single they keep their product branding making it easy to understand what each product is for.DigitalFreak - Tuesday, July 10, 2012 - link
Here's a review of the Red from StorageReview.comhttp://www.storagereview.com/western_digital_red_n...
KonradK - Tuesday, July 10, 2012 - link
If I understand the second paragraph the HDD can issue bad data silently for sake an uniterrupted work.From what HDD knows a purpose of the data it reads? From what it knows that they belong to a watched movie, and not to the file (or filesystem metadata) where error is not allowable?
JasonInofuentes - Tuesday, July 10, 2012 - link
So, that component has to be triggered by the application accessing the file, but it is a triggered event. So, a good scenario would be if you had two streams being sent to two different devices while another client is doing a restore from a back-up. The two streams use the ATA streaming command which triggers these different behaviors, including the error tolerance. The restore, though, is being done without that command, so normal error correction is in effect. If you have a single drive in the NAS then you might experience hangs on all three data transactions if the restore experiences an error that requires a few compute cycles. But if one of the video streams experiences an error that can't be resolved in three revolutions of the disk, then the bad data is allowed to slip through and no one gets slowed down.The frustrating thing about a lot of these standards and commands is that even if the hardware implements the solution, the software has to include it as well. And the other way around, in fact. But, have no doubt, error tolerance is a controlled variable.
Jason
Guspaz - Tuesday, July 10, 2012 - link
I'm a ZFS user, and my drives are in a raidz array. ZFS has per-block checksums, and because I've got redundancy, any failed read can quickly be recovered from (by rebuilding the data from parity and writing the block elsewhere). I would rather have the drive fail very quickly (either by passing on the bad data or presenting a read error) so that my filesystem can recover the bad data and move on.Chances are, if a hard disk can't read the data after the first few tries, it won't do any good to keep trying over and over again, but that's exactly what consumer drives do: they spend large amounts of time re-reading the same block over and over hoping that the read will be good. Unfortunately, the long period of time spent re-trying (I think it's something like 15+ seconds) causes many RAID systems to think the drive is completely dead (because it stops responding for a long period of time). This behaviour is unacceptable for anything used in RAID.