Hard Drives Made for RAID Use
An anonymous reader writes "Hard drive giant Western Digital recently released a very interesting product, hard drives designed to work in a RAID. The Caviar RE SATA 320 GB is an enterprise level drive without native command queueing and uses an SATA interface. In works better in RAID than other drives because of features like its time-limited error recovery and 32-bit CRC error checking, so it is an option when previously only SCSI drives would be considered."
Sheesh, this is a VERY thinly disguised ad. Here's a direct link to NewEgg $169. Has the same details as this "story."
If they would stop eating around the hard drives, leaving crumbs in them, we wouldn't need to use Raid to take care of the cockroaches in them. Ugh.
Advice for my fellow geeks: before seeking out that threesome you dream of, you might see what a TWOsome is like first.
Interesting that they don't have NCQ, whereas SCSI drives generally do (well, called TCQ on SCSI IIRC)
Is this just marketing speak, has it truly included scsi features, or could it actually be better performing than SCSI in a RAID array?
"In works better in RAID..."
You should change "In" to "It"
Thank you very much.
While I've been a proponent of SCSI for a long time -- Apple really was thinking ahead when it had it in Macs all those years -- it has been getting thread-worn. Ultra-wide-tall-double-hex-SCSI is just getting to be too much!
SATA is the right technology, especially for controllers since each channel is dedicated. The only alternative is Firewire, and there are no native controller drives.
I love my computer -- You make me feel alright (Bad Religion)
How does the lack of Native Command Queuing improve RAID performance? Generally I thought NCQ improved all drive's performance, and TFA says that NCQ is normally part of Enterprise High-Performance.
"It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
http://www.wdc.com/en/products/Products.asp?DriveI D=92
I bought one to replace what I thought was a bad drive in a RAID configuration about a year ago.
Proper TechReport's review here.
Go read. Now!
Here's an interesting quote from Tom's Hardware:
"In sum, we must state that all Command Queuing enabled drives have an advantage over those that do not support this feature. At the same time, CPU load is also slightly higher when Command Queuing technologies are used. However, considering the performance of today's processors, the additional CPU load is a marginal factor."
Basically, you put some load on the processor for increased disk performance... Why not include it?
Support alternatives to Paypal: http://www.e-gold.com
The manufacturer specifically says to only use these in a RAID-1 configuration (mirroring). They have a reason for this: The error recovery mechanisim is abbreviated. So what does Sal do... He connects two drives in a RAID-0 configuration. Now his data reliability has gone to about 1/4 of a regular drive.
NCQ allows hard drive to reorder various commands/accesses to suit its current head position. Depending on your app you might not see a lot benfits from it e.g when you do serial access all the time but lack of it will certainly cause degradations when multiple apps are active. Also by using one big hard-drive instead of multiple smaller ones its putting all eggs in one basket. Mechanical problems are more frequent than magnetic ones for a hard drive..
This sig doesnt exist.
These buggers are hard to find for anywhere near decent cash. I've found one model that is fairly popular, going by several different names and brands, but nobody seems to have them in stock. They look like a GREAT deal and loaded with most or alll of the best features of raid5. (hot swap, live rebuild, live GROW, etc) Has anyone seen one IN STOCK anywhere?
D =45&Cat=Producti harasyfor5.html9 19&refid=1057r e-mini.html
u cts_id/657
Same exact models:
http://www.raidweb.com/fb605fw.html
http://www.micronet.com/General/prodList.asp?CatI
http://www.firewiremax.com/fire-wire-1394-ilink/m
http://www.pcrush.com/prodspec.asp?ln=1&itemno=77
http://www.cooldrives.com/firewire-raid-5-enclosu
http://www.topmicrousa.com/combo-205.html
same internals, different enclosure:
http://fwdepot.com/thestore/product_info.php/prod
http://www.cooldrives.com/fii13toatade.html
Everyone I call says they have them in stock. Then I ask them to check and they suddenly change their mind and say no it's not really in stock, (despite what their web page says) and they expect it in the generic "1-2 weeks". (retail-speak for "we don't know when it'll be in, please call back later")
Two of them actually told me they have yet to receive any of these units, so I don't think they've shipped from the manufacturer yet? (vaporware?)
I work for the Department of Redundancy Department.
Is there a reasonable cost, relatively low power RAID-5 setup for home networks? I'd love to set up a file server with gigabit ethernet and RAID-5 to serve as the home directories for my multiple machines. Things like the Buffalo LinkStation are a step in the right direction, but no RAID, etc. Is my only solution a Celeron or Pentium-M based PC? If so, is it possible to set up such a system to act as home directories for a combo of Windows, Mac, and /or Linux machines?
Ooh, a sarcasm detector. Oh, that's a real useful invention.
EIDE drives are the cheapest type. But AFAIK, each drive has a controller card onboard, which seems redundant when all the drives are being controlled in conjunction. Software RAIDs seem to have parity (pun intended ;) with HW raid controllers, but wouldn't a real "Made for RAID" drive have nearly no controller logic of its own (maybe just data separator and head/spindle speed/position calibration)? Lots of logic for controlling the RAID drive will be on the central controller card, or running on the CPU. So why have more on the drive? The cheaper the drives, the bigger the array at the same budget (shared overhead of common controller).
Am I correct, or are some RAID drive makers already doing this? Or have I just got all the controller:drive economics wrong?
--
make install -not war
Is it just me, or did this review stink for lack of proper testing and comparison...
If I were comparing this product and it's performance, I certainly would not be benchmarking a SATA based RAID setup against a single Parallel ATA drive. Something in this arrangement just doesn't seem... well, logical.
If you were really going to try to impress me with it's performance, then you would have to show me how it compares to "non-RAID" optimized drives of near simular characteristics. Show me how this drive performs against, say, Hitachi SATA 320 gig drives using an identical test rig. Also show me how this drive compares to 320 gig SCSI drives. Show me the results as JBOD, RAID-0, RAID-1 and RAID-5. You know, like the real world.
While the graphs are pretty, I'm afraid that this "review" it fairly content-free.
Ron Gage - Westland, MI
And what if the electronics of the drive fails? Or the motor? Or the drive-head actuator?
Sorry sir, but this is a bad idea.
Meme of the day: I browse "Disable Sigs: Checked". So should you.
Buffalo TeraStation
Supports RAID 5.
I emailed if external USB hard drives could be added and swapped to a raid 5 array, and if it can be done "on the fly"...
but all I got was this lousy message:
"Please call (800) 456-9799 x. 2013 between 8:30 and 5:30 CT and our presales guys will be able to assist you."
I'm one of those weird people that would rather communicate in writing. Oh well - no sale.
Spoon not. Fork, or fork not. There is no spoon.
Where's the review of how well it facilitates serving pages through Apache? Oh, that's replaced by "Look how neat the drive looks!"
I don't moderate anymore. Karma penalty for 90% fair mods? Can I mod that unfair?
IMHO, the biggest things manufacturers could do to make the drives more RAID friendly is to change the name (even with just a v1, v2, etc...) when they change platters.
Nothing is worse than buying a bunch of drives and a couple of spares and building the array and then discovering down the road that in fact one of your spares came from a different production run and has a slightly different (maybe 3 block smaller) geometry and can't be used on your array. Usually there is absolutely no indication on the box or the drive that one of your drives is different unless you decode the cryptic serial number.
For that matter, just printing the exact LBA count on the back of the box would be a huge boon.
This isn't limited to ATA drives either. I've seen it plenty of times in professional SCSI solutions too, especially as the arrays start to get older.
I read the internet for the articles.
I would think if these drives are really designed for RAID (like other drives have been in the past), then they would have support for synchronized spindles.
The idea behind synchronized spindles is that in order to read data from a disk, you have to wait for the platter to come around part of a revolution for your data to become available, just like picking up your suitcase on the luggage carousel at the airport. How long you need to wait is a matter of luck, because the disk can be assumed to be in a random position when you decide you want your data. When you have RAID without synchronized spindles and you want data that's bigger than the stripe width (or when you're writing and need to update the parity), you have to wait for multiple disks, and they will tend to be spread out so that you tend to wait longer than if you were just waiting for one. With synchronized spindles, as soon as the whole group hits the right position, you've got what you're looking for, and you're done.
So, the point is, not having synchronized spindles tends to increase average access time, so having synchronized spindles is a desirable feature for a drive designed specifically for RAID.
Buy their gear if you must but I would not put my data on it.
-- RLJ
I'm no expert, but I look forward to mostly buying 2 platter drives from now on. Early failures seem to double when you add a third platter, and 5 platters is just scary. You can get 250gb SATA 2 platter Seagate drives for about $110 each, which seem to have a great record for reliability so far. But when I need real SCSI reliability I'll just get a real SCSI. The warranty for most SATA drives may be 5 years, but usually it's void if you put it in a server.
What do you mean sat on the wayside ? It's been out and about for donkeys years, I've been involved in storage for 9 years and it pre-dates me by a LOOOONG time.
Did you miss the Redundant bit in Redundant Array of Inexpensive Disks ?
The idea is that one drive going bad doesn't take out the whole array in mirror, not that you have it all on one drive you fool.
"Yeah, boss... drive, uh, died. I'll get a nice new one-- let me... uh... take this one home. I think it's, y'know, dead. Honestly this time."
Since I wanted some facts, Wikipedia ordered two systems for database service, both dual Opterons with 4GB of RAM and six drives. One with 10,000 RPM SCSI drives and one with 10,000 RMP SATA drives. The SATA system, without NCQ, was generally faster and ended up with a higher proportion of the site load assigned to it. The SCSI system was sometimes faster in mixtures which included lots of writes with lots of reads and that made it lag a bit less in replication of bulk update operations, so newer systems have been SCSI. If more drive bays had been available, adding another couple of SATA drives would probably have made the SATA set faster for that case as well and still cheaper.
:)
If lower access times are needed, SCSI drives beat SATA drives just because you can only get 15,000 RPM with a SCSI interface. May also make sense to have 15,000 RPM drives if you're already spending a lot of money on 16GB of RAM.
The question about this drive which interests me is whether drive write caching can be easily turned off and will stay off, so you don't lose database data when the database thinks the data has been flushed to the surface but it hasn't really been flushed. If you can't do that, it's unsuitable for a lot of database work - certainly unsuitable for use with RADI controllers with battery backed up write caches, where you have the battery to make sure you don't lose cached data if the power goes off. Anyone who things colo power and UPS will protect against loss of power hasn't suffered enough yet...
So, I have seven database servers, all with identical copies of the data. Do I really care if I lose all the data on one of them because one drive in a RAID 0 set fails? The completely redundant systems do the job better than any RAID setup can.
You consider RAID 0 when you don't care about losing the data if there's a drive failure and want the benefits of striping and the extra space available for a given number of drive bays, compared to other RAID levels. RAID 5 can get you some of the space but it's slower for database work.