Western Digital Announces 200 Gig Drives
twilightzero writes "Video capture fanatics and pr0n moguls, rejoice! Today marks the official release of the Western Digital 200 GB hard drive! Never again run out of space for your X-10 video stream of the neighbor's house! See the graphic, specs, and press release. This also marks the release of WD drives using fluid dynamic bearings rather than the old BB type." The glorious march of technology continues forward, and digital video fans rejoice. Update: 07/26 03:34 GMT by M : Headline corrected. Taco's at a conference, cut him a little slack.
This 20 megger is beginning to feel cramped. I might even be able to upgrade to MS DOS 5.0!
I'm just a little confused!
Mormon news and discussion at Mahonri.org
Would someone care to educate the Slashdot masses about the differences between the old bearings and these new liquid ones? I'm in the market for a new drive, and I'd be curious to know what the difference is. Would the new bearings come at a price premium?
*(ok, maybe not goodness, depending on your point of view ;-)
Intel today announced the availability of the Athlon 3000XP!
Would it be possible to launch a reverse DOS attack on the RIAA by storing hundreds of thousands of fake mp3 files with song names on a 200 gig hard drive, or better yet a network of computers with 200 gig hard drives?
~ now you know
60 gigs a platter, so to get to 200 gigs there must be 4 of them. 4 times 60 is 240. What gives?? Is this one of those deals where they lock out sections of the drive so they can release a larger model later???
I did not come up with the following, but found it somewhere in here.
...)
Our yellow sun yields to the dark
as I begin my web based lark
Flowing, turning, through the pipe
I grep for text and dump the hype...
But as I ride the fiber trail
I test my faith as I read my mail,
Even as my bandwidth fattens,
I question life and 1-click patents...
Although I ask, and though I query,
I know the truth, I grock the theory
Life is a multimedia of sins
so he who collects the most pr0n wins.
(must not laugh
I noticed the Fluid bearings thing on newegg.com on a Maxtor, 40gb drive, earlier today.
"Would it kill you to put down the toilet seat?" -- Maya Angelou
First of all i'm not complaining about "editor" mistakes... i could care less. But this is a western digital drive not a maxtor one, things like that seem rather silly to let slip through the cracks. And just to be sure I checked maxtor to see if they had anything, but all i could really find (in about 15 seconds worth of time) was a page about > 137 gig drives.
can't sleep slashdot will eat me
I've installed a couple different drives with the fluid bearings, and they do run quieter than the older style bearings. Very nice!
Hey, now
Cmdr Taco was quoted as "being disappointed" with the decision, but was "looking forward" to spending more time at home with his computer.
In related news, OSDN has banned drugs, alcohol, controlled substances and Cowboy Neal from the Slashdot campus.
You'll need an ATA133 controller, or a RAID controller that can address drives beyond the current limitation of most ATA100 controllers.
Promise makes one, I'm sure. Maxtor 160gig drives are sometimes bundled with a controller.
I'm in the market for a new machine, and I've been spec'ing out different parts for my budget...These drives are nice and big, but what happens when you lose a 120 gig drive...I've pretty much decided that I'm going to have to get an IDE RAID card and highly recommend them...the RAID cards at work have saved me hours and hours of restoring from backup...Check out the 3ware Escalade, the Promise SuperTrak, or the Adaptec 2400A. RAID 5 is the way to go (with or without removable drives). I've been watching the prices for 120 Gig drives drop and now it's just about the price where I can afford to spend 150 clams to buy an extra drive that would be used to protect myself from a drive failure.
- grunby
Now I hear people say this all the time. But in my nearly (oh wait, this is 2002...we can skip the 'nearly' part now :-P) 20 years of computing experience, I have only had 2 drives that ever died on me (like totally dead, not just developed a few bad sectors or whatever) and they were both Maxtor drives. And I have owned drives that were manufactured by Maxtor, Western Digital, IBM, Seagate, Kalok, Fuji, Quantum, Toshiba and another company that I can't remember the name of right now... :)
My journal has hot
Instead of piping bytes from /dev/null have it repeat instances of something like the Copyright Law or the DMCA.
For kicks, get sued by the MPAA/RIAA and get them to open your files in something like notepad - in court. Smack them with a countersuit for being insanely stupid (which you're bound to win for obvious reasons), retire and live happily ever after, knowing that you've done us all a big favor.
We do not live in the 21st century. We live in the 20 second century.
Backing up this sucker ought to be fun. Hmm, I only need 138,888 floppies! Lessee, at the rate of one floppy inserted a minute, that'll take me over 96 days straight!
If I get started right away, I'll be well prepared for the inevitable HD crash that will follow my installation of WinXP SP-1.
There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
gotta be a bitch. That's something like
138,889 floppies. If they're 1/8 inch
that's a stack about a quarter mile
high!
It's WD, I submitted the article with a different title and it got edited...to the wrong company LOL! I laughed so hard I almost wet myself when I read it...
"Christ what a design! I could eat a handful of iron filings and PUKE a better emergency pump than that!"
The press release is June 25, but the drives just SHIPPED today, THAT'S the news.
"Christ what a design! I could eat a handful of iron filings and PUKE a better emergency pump than that!"
Conner?
I've had several Micropolis 4.3GB SCSI drives (the 3240AV, if I recall) and those are the most damned unreliable drives ever. They go into 'airplane mode' and sound like a prop plane about to take off.
There should be a moratorium on the use of the apostrophe.
Max V.
NeXTMail/MIME Mail welcome
I bought a Maxtor 160GB drive that came bundled with an ATA/133 card. I ended up putting the drive into an ADS Firewire enclosure, which seems to be just as capable as addressing the whole drive as the bundled ATA/133 card.
Perl - $Just @when->$you ${thought} s/yn/tax/ &couldn\'t %get $worse;
What about economics?
I was thinking that raid-5 might be a really cool way to go, but when I looked into it, it seems that raid-1 on the motherboard might be cheaper.
Wouldn't 4 x 120gig drives + raid-1 cost less than 3 x 120gig drives plus a raid-5 controller?
I wonder where the break-even point is...
3 platters = 6 sides.
5 sides for dats (40 gigs each) and the bottom of the bottom platter for positioning.
(That was assuming you're using linux and raid-5 controllers cost around $250-$300...)
Yeah, Taco's grammar, spelling, punctuation, and fact-checking abilities are severely impaired by all the Linux Bong-Hits he's been doing.
When he returns on Monday, he'll be back in top form!
- A.P.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
I own a computer repair/retail store. I have given up on WD several times. We have mainly used Maxtor for the last several years. I have had 2 Maxtor drives die in 5 years. I have replaced more WD drives for several 3rd party warranty companies than I could count. If one of the warranty companies call and sends a computer through our doors, (especially if it is black with a blue logo silkscreened on the front) and it has a WD drive inside, it's a 90% bet that the drive has developed bad sectors. I have enough dead 4.3gb Caviar drives to build a wall across the front of our shop. We have recently been using the new Maxtor/Quantum drives (Qaxtor I guess) and have not had any returns. These new drives look like a Quantum, but have a Maxtor label. I was a little hesitant at first to use them. However, I wanted to test the new drives and I needed a new server, so I built myself a new box consisting of dual 1800 Athlon MP (Tyan Tiger MP), 1GB Mushkin PC2100 DDR, Promise Supertrak SX6000 and FastTrak100,and 8 Maxtor 80GB drives. 6 drives are in RAID 5 (data) and 2 are in RAID 1 (OS installation). So far I have had no problems, other than gasping over the speed of this beast, but only time will tell. Just my 2cents. =)
I have but one thing to say...
LMAO!!
"Christ what a design! I could eat a handful of iron filings and PUKE a better emergency pump than that!"
For the love of God, when will the PC industry stop with these damned limits? I thought they had fixed things, but here's another one. For the last 20 years it's been an endless parade of hard drive capacity limits, one after the next. I can't remember the last time I installed more than 1 OS on a box without being nagged about dire warnings about hard drive geometry crap.
Why the hell do they need to be so stingy with the address bits? Don't they learn anything from experience? Is it a conspiracy to make a few people pay 3X for SCSI?
Here's a hint: Send 64-bits of address to the drive! Store 64-bits of address in the BIOS! Use 64 bits in the device drivers! Use linear addressing! NO EXCEPTIONS ANYWHERE! For once, they wouldn't run out of space in 6 months and cause new headaches for everyone.
I guess it depends on how much drive space you want...You'd still be paying for the RAID 1 functionality on the mobo (albeit not as much as a separate card). 4x120gig with raid 1 on the mobo would probably be around the same price as 3x120gig with a separate raid 5 controller. $/gig with raid 1 is the most expensive so I guess if storage space isn't that great, raid 1 would be the way to go. But as you get more drives with raid 5, the $/gig (or the obligatory $/.jpg of pr0n) goes down...In my situation, I was thinking of getting 4 120 gig drives. I've got about 6 months of the howard stern show (set up a cron job to record it every morning and I've been to lazy to burn it all), vmware images of 3 different os's, and my family's vast mp3 collection all stored between three machines...but hey that's my situation...
oh yeah - and the pr0n...
- grunby
I've probably got enough hard drive space to last me another 5 years
Or until you *finally* decide to upgrade Windows...
I pledge allegiance to the flag...
of the Corporate States of America...
...compared to the new Ford Exorbitant.
Microsoft today announced that due to the revealed Western Digital technology, they can disclose that Windows Longhorn will actually be a Full-Motion Video (FMV) Operating System, which will require a 200Gig drive to install on.
Ñ'
Am I the only one who has had every single Western Digital drive I've ever bought fail completely within months? The failure is usually preceded by a horrible clunking noise that lasts a month or two, followed by catastrophic data loss. And it's happened with every WD drive I've purchased (and that's six so far). Needless to say, I've stopped buying WD drives.
dd of=m00z4k.mp3 bs=1 seek=1874373 count=0
so that no disk space (except the dentry and the inode) is wasted... Oh, you have just bought a shiny 200gb disk, haven't you?
Use unison and two drives to synchronize the filesystems. I actually use unison with two desktop computers and a server to keep all 3 in sync! With copies of everything on 3 hard drives, I don't worry too much.
If tits were wings it'd be flying around.
Would someone care to educate the Slashdot masses about the differences between the old bearings and these new liquid ones? I'm in the market for a new drive, and I'd be curious to know what the difference is.
Well, I can't speak for hard disk drives, but I can maybe draw an analogy.
Wheel bearings - on cars, trucks, bicycles, whatever - use ball bearings. They're a set of caged balls, and one surface literally rolls over the other on a cushion of tiny little balls or cylindrical rollers. Here's an animated GIF and some other neat stuff. The problem is that, whatever the lubrication, eventually the balls and their races will wear, which increases the clearance between the two surfaces and causes looseness ("play") within the bearings. In wheel bearings, this translates into a shimmy in the wheel and weird tire wear. In a hard disk drive, this would result in a shimmy to the platters, causing less precision in data reading and writing as the platters vibrate nanometers back and forth under the heads. As the drives get to higher and higher capacities with the same physical disk size, the tracks being used must be getting smaller, and therefore this error becomes more crucial. Also, notice that hard drives which have been running for a long time tend to get noisy... Never mind that bits of metal being worn out of bearings have to be contained somehow so that the platters and heads don't get damaged.
Liquid bearings are used in all modern car engines. Oil is pumped from the oil pan into a very tiny space between a relatively soft bearing shell and a very smooth and hard crankshaft or camshaft journal. As the shaft spins, the oil is distributed thoughout the bearing surface and eventually leaks out the sides where it drains back to the pan to be pumped through the system again. Here's a picture of the main bearings of a Ford V8. You can see the little holes where oil is pumped into them. While the engine is running, theoretically, the shaft's journal and the bearing surface never actually touch each other; they ride on a cushion of continually replaced microscopic ball bearings (oil molecules). During circulation, the oil takes the heat away from the bearings, and washes away impurities.
How you'd implement something like this in a hard disk drive, I have no idea, and I'd love to see any real techical info on it. (Marketing hype will not answer the questions I have.) But it's a great idea; in a server, with the hard disks spinning all the time, the hydrodynamics of the situation suggest that the platter bearings would never wear, and would therefore never have their tolerances open up and incur vibration.
But a seal would be required to keep the lubricant off the platters, and that seal would itself eventually wear out. Not to mention that it's unlikely they'll include a provision to do an oil change on these things. Stopping and starting cycles will wear the bearing and journal material, causing tiny abrasive bits to be floating in the oil.
I like the idea, I think it's a great step, and I'll look forward to seeing how hard disk manufacturers have solved the problems.
Would the new bearings come at a price premium?For sure! Even if it costs less to machine these than the super-tight clearance ball-bearings that modern hard disks must use, they'll still be a "new feature" which can enhance prices and profit margins. But I think they will actually cost more to make; it's just that ball bearings (like older stepper motor head actuators) have too many limitations to work with modern capacity and track density demands.
Fire and Meat. Yummy.
Still not enough space to rip my whole CD collection. Guess I'll just keep listening to them on my phat stereo, the way music should be! :)
It doesn't mean much now, it's built for the future.
That's what he's saying... He's saying that with hardware, yes you get what you pay for, but with software, that's generally NOT the case.
General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
Does anyone know if fluid dynamic bearings would change the minimum temperature that a drive requires to spin up?
Well, assuming that these fluid bearings are smooth races with a "ball bearing" of oil molecules in between (ie. like bearings in any car engine since the 1930s), absolutely.
From the descriptions, from what I can tell, we're only talking about bringing automotive engine main bearing technology, on some scale, to hard disk drives.
Whatever the liquid lubricant, when it's cold, it's likely to be thicker. Which will mean that it will take more motor torque to get it spinning when it's cold. (Think of how much slower your starter motor turns your engine on a really cold day; not all of that is the reduced efficiency of the battery in cold weather!)
I think, in cold environments, these drives might take a while longer to spin up, but once they're spinning, the turbulence in the oil in the bearings will warm it up quickly enough. Also, when it's really cold, the bearing clearances will be smaller because they probably will have contracted more than the journals.
Compared to ball bearings which will have no fluid filling the bearing clearances as the temperature changes, I'd imagine these will be less prone to vibration and read/write errors as the bearing temperature changes. (Not that it matters much, all modern hard disk drives use a closed-loop servo system to detect the position of the heads relative to the platters.)
Fire and Meat. Yummy.
So you think you are old?
TI-99/4A! :) I had a 5.25" single-sided single-density floppy disk drive, with a whopping 90k per diskette. The average application was about 20k, word processor, Editor/Assembler development package, etc. Sticking in another diskette was like adding a new hard disk drive to your machine today! :)
Then some nut in the TI User's Group realized that we could stick two of the new half-height double-sided drives then becoming popular in PC/XTs into the disk drive bay. 180k per drive, two drives at once! (TI Disk Controller cards wouldn't run double-density, so we didn't get the full 360k/disk.) Literally, you could go weeks or months using nothing but the two diskettes in the two drives.
I kinda miss that. But, then again, that was before the good porn came in large, high-resolution 1+ megabyte JPGs. (16 colors was enough back then, too...)
Fire and Meat. Yummy.
Probably the same reason that the AIX box at work (1 gig of ram, 18 gigs of disk space, quad processor) chokes when you try to grep a file with lines longer than 2048 characters.
Keep ranting about stupid limits, maybe it'll do some good. At least I won't feel lonesome.
If tits were wings it'd be flying around.
Just check to make sure the card is supported by your favorite distro first. I still can't get my integrated raid to work with linux on my soyo dragon plus mobo. Its especially wierd that linux has poor ide raid support considering the people who are most likely to run ide-raid are also big linux fans.
Long and irrelevant? Nah. Kind of interesting. A little slice of life.
If someone had put a scene like that in a movie, it would have been called "over the top" and "cliche".
If you edit this down to the best 10 minutes every week, post it somewhere and then post the URL.
You don't need RAID cards to do RAID-5 under linux. Just get a couple of IDE cards, plug in the drives, and make them IDE. IIRC, Linux Software RAID is faster than hardware RAID, and cheaper too. ATA-100 cards are around 30 bucks and you can do A nice RAID5 with 2 cards. I did just that with the 99 dollar 120 GB 5400 RPM WD drives purchased at Frys here in Phoenix.
Linux - Because Mommy taught me to Share.
...for Western Digital to rethink their webserver strategies.
/products/products.asp
/.ed, but I guess they can!
Here's what filled my web window in my attempt to view the specs of this 200GB hard drive:
Active Server Pages error 'ASP 0113'
Script timed out
The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
I mean, I really didn't think that a company as big as Western Digital could actually be
(For those of you complaining about how 200GB hard drive is not any worthy news, there certainly was enough people interested to still bring the server to a standstill.)
In high school, a few of my friends and I salvaged PDP's and gigantic 5MB drives from dumpsters outside of a telecommunications building. Those beasts weighed a hell of a lot, made of solid steel, with belt driven spindles and massive motors with heatsinks on 'em.
:)
.. and it was really cool to run long lengths of those skinny little wires to the editing stations. After dealing with FC, I'm seriously looking forward to working with Serial ATA and Serial SCSI -- those complex multi-pin connections just gotta go.
:)
Interesting to think that something that's about 1/10th of a percent of the size of those monsters contains almost 41,000 times more data.
Technology. Great stuff.
Another story to bore your socks off:
When I was working at an animation/film editing studio five years ago, we dropped a serious amount of money on a 200GB fibre channel array to feed three Avid workstations. It was a beast of a box, easily weighing over a hundred pounds
Anyhow. Enough of my drivel.
I've worked at a computer store (read: *computer* store, not some Best Buy know-nothing dept) and I've seen a LOT of hard drives either fail or come to us dead in the service department. IBM and Seagate by far have the best track record (aside from those few IBM drives that were having problems). Maxtor, while having a few more failures, has an excellent RMA dept -- it seems like you have your replacement before you even hang up the phone. Fujitsu is crap. Quantum Bigfoot....if you have any important data on one of these drives, back it up! And last but not least, Western Digital. The more recent ones look a lot like IBM drives (buyout? whats the deal?) and seem more reliable than older ones, but those older ones........ They are terrible.
I'm currently running 3 Seagate Barracuda's(40gb and two 80gb's RAIDed) and my only complaint with them is the heat that they generate (did someone mention micropolis? Those things can heat a small room!)
-kwishot
The limit is due to having only 28 bits in the IDE registers to selecting the address. There are four 8-bit registers, and the "head" register uses 1 bit for master/slave selection, one bit to select CHS/LBA addressing, and two bits are "reserved" (originally used to select sector sizes, but in modern times sectors are always 512 bytes).
ATA-6 kludges this 28 bit LBA limit to 48 bits by specifying that the host is to write 20 bits twice!
But for the forseeable future, 32 bit computers will only really use 32 of those 48 bits, which turns out to be only 2 terabytes. If the operating system uses a signed integer (common practice, including the linux kernel until only recently), you only end up with 31 bits of sector addressing, or just one terabyte.
Of course, there are probably even more limits lurking. Doesn't linux ext2/ext3 use 32 bit numbers? FAT32 uses 28 bits for cluster numbers, but clusters can be as much as 32k in the standard (apparantly larger in some systems, though Microsoft doesn't document that in the FAT32 specification).
PJRC: Electronic Projects, 8051 Microcontroller Tools
Others have mentioned backup problems with these large drives and joked about the number of floppies the drive equates to. Assuming my math went okay, here's a list of popular backup media and their estimated time to backup such a beast.
What these large drives mean to users is that you can't just buy one drive, as there is no feasable way to back up the entire drive. You'll need to purchase two identical drives and mirror them for backup purposes. While 200BG seems like a lot, you'll need at least 400GB in reality. You can't let all that good prOn get lost in a head crash.
Drive type
(Native capacity) (native xfer rate)
(time to fill one media)
Time to complete a full 200GB backup* (approx media cost)**
DLT-8000
40GB 6MB/s
2hrs per tape
5 tapes 10 hrs $200
DVD-R
4.7G 2.6MB/s (2x write speed)
30 mins per disk
43 disks 21 hrs $43
CD-R
700MB 3.5MB/s (~20x write speed)
20mins per disk
286 disks 4 days $45
Floppy
1.44MB 25K/s
1.5Mins per disk
138889 disks 20 weeks $13,888
*These times assume 100% efficiency. IE: That the next media will be available immediately after the preceeding one is full. I did not allow any time for insert/eject, preperation/formatting or phyisical movement of the media. You would never be able to achieve these times. Perhaps * 1.5 would be more realistic.
*For media cost, I used pricewatch and took the lowest price I could find for bulk media. In the case of floppies that was 10/$1. These costs do not reflect the price of the device to write to the media.
Article X: The powers not delegated... by the Constitution...are reserved...to the people
In my last 5 years I regularly worked on the servo controller block of a drive controller ASIC so I'd like to point out some much under appreciated issues and correct some recurring miss understandings: a) the servo system, b) the real benefit of fluid bearings, c) error correction, d) why an unused surface, e) spin speed
Some short answers are:
b) Worn ball bearings seriously disturbs the servo system from keeping the read head or the write head on true center of data track. This puts a ceiling on increasing track densities.
c) Very strong error correcting codes are applied to every data block (about 512 bytes) and not on any unused surface.
d) As for unused surfaces, there are multiple issues in this decision, but a new feature from some manufacturers is to reserve one outside surface for a template servo pattern & BIOS code so that the drive can self write its own servo patterning and more cheaply load its BIOS code. This reduces / obviates the many hours it takes of very expensive capital equipment to write servo patterns to drives.
e) Spin speeds above 10K introduce horrendous resonances at the outside of platters that make servoing tracks much harder. One remedy has been to reduce platter diameter & capacity (by about 10% as I recall).
And the long version of a) & b) or 101 of disk drive servoing:
For atleast a decade, hard drives have used embedded servo patterns on every surface that are intermingled with the data areas. Using a dedicated surface for servo worked long ago only because track & data bit densities were much lower. Todays drives typically have 120 or more curved radial servo wedges that costs 5-7% of the surface area. User data tracks nestle between these servo wedges.
1) In these short servo wedge areas, servo tracks contain a few tiny fields of digital servo data followed by several analog modulations so that the servo processor can sense its fractional position within any servo track. Servo tracks actually abutt each other and the only bit change between adjacent servo tracks is in the Gray coded track no. Since IBM patented this many years ago (1980's ?), manufacturers have since added proprietry extra small digital fields to correct for read errors in the digital fields & analog modulations to continuously improve servo tracking and hense improve data track densities.
2) The user data tracks are not neccessarily pitched to be inlign with servo tracks and may be reduced to 2/3 the density of servo tracks. This provides guard space and reduces inter track symbol interference. As the disk spins from servo wedge area on into user data area, it becomes an increasing act of faith that the read head or the write head is indeed still following a track center until we reach the next servo wedge. Such miss tracking is called runout.
A major source for Non-Repeatable Runout comes from worn bearings which introduces random wobbling, and this degrades the servoing and limits tracks densities.
Fluid bearings improve upon ball bearings because they don't introduce this NRR so spinning is quiter but more importantly track densities can keep climbing.
There are quite a few other NRR & RR terms impacting on servo tracking.
I've used several 3ware escalade cards and they are faster than my old software raid5 in everyway. Plus, they setup in their own BIOS, can use hot spares, and were seen instantly by Linux Mandrake on installation (as a scsi disk). The 4 port 6410 escalade can be found for 89MB/sec sustained in Raid5, with bursts WAY higher using WDC120's. It takes some serious U320scsi to do those numbers in the real world.
-- Whitewlf White Wolf Networks
Their drives were always whisper quiet, and very cool to the touch. The only drives I used for the longest time were Fujitsus. Then Fujitsu went out of the consumer HD business to focus on the high-end business (where the big margins are).
:-/
My 20gb Fujitsu of only a year started to not work in my PC a few weeks back, and it's been replaced by a 20gb WD. It's also quiet, and seems to be about the same speed. However, it took WD 1.5 years to catch up to Fujitsu in this respect. And it doesn't (like my Quantums) have any S.M.A.R.T. temperature sensors, even though every Fujitsu I've ever tried supported this
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
A big clarification I would like to make here is that most cheap "hardware raid" controllers are NOT hardware raid controllers. They are clever hacks to implement RAID using a combination of a bios handler for software RAID and an OS driver implementing software RAID at the driver level. That is why linux md running raid5 is often faster - the implementation is better than the device driver provides.
Now, when comparing performance to a real live IDE RAID controller (Adaptec AAA or 3Ware, etc.), it is not as fast. These controllers have an on chip implementation of RAID 5 (ie hardware XOR etc. usually implemented on an intel i960 or somesuch) and perhaps some cache memory, and they interface with the OS using the standard SCSI drive api.
Now software raid 0 or raid 1 is often just as fast as hardware raid 0 or 1 because the implementation is so simple and the drive r/w speeds are the limiting factor.
BTW: does anyone know exactly what to call things like the promise and Highpoint "Raid" controllers that rely on BIOS hooks and software drivers to do the RAID dirty work? -- "Hardware" doesnt work and "Software" doesnt work -- is there a word for it?!?
~GoRK
Hmmm.. I had a similar issue at an apt. I was at, drunk people kept banging on the back door so I finally stuck a camera up. Then I captured video of drunk people banging on the door at 2am looking for friends.. hmm... I wish I had thought of how un-useful that footage was before going through the effort of hanging a camera in my back window.
oh well
BigBlockMopar, a Chrysler man I see. Well I might be able to fill this in a bit. Back when I was working in heavy manufactureing, we used alot of liquid bearings and such. Before the pre-start and early startup of the motors, a micro-oil pump would pump some oil into the sleves. I mean, small the pumps we used were itty itty bitty. Probbly 2" long, and 1/4" in diamiter. It would surpise me that they use something similar for a pre-start application.
The other thing is, once you get the drive spinning, you no longer need to use this pump. Since you can build a micro-pump into the base of the spindle to draw the oil up and into the bearing.
Now, the other thing I can see is a "dry start" since the drives are spinning at 5400-10000RPM the ammount of time that the drive takes to bring the pressure up in the pump, and the ammount of cold ware you get from start up, since most people use their computer every day, I can see this being a possible idea.
The last and best idea is called a centrifugal oil reserve. Where the oil is stored in a center chamber and when the drive powers up the oil is almost immediatly sloshed from the center to the outside, resulting in a very low chance of dry starts. It's cheap, inexpensive and very common on side mount high speed, high load bearings in machines.
Om, nomnomnom...
For more information on how bearings work, and wear in general, do a search on the field of "tribology". It's all there.
Folks, I hate to be the one to throw water on everyone, but here goes...
:-)
Debating which drive manufacturer is "most reliable" is like debating which God is "correct", or the existance of Santa.
You say in 20 years experience you've only lost two drives, both Maxtors.
Well, in my (let me count) um...23 years experience, Maxtor is one of the only two brands of drives that I've not had a failure (the other one is Fujitsu). And I've also "owned 'em all" too. I've got a pile of dead Western Digital drives a foot tall sitting out in my workshop (figured I'd make clocks out of 'em or something). I once had three Seagate drives fail in a 6 month period, and the second and third ones were warrenty replacements starting when the first one died.
So which one of us is right?!
I want a new quote. One that won't spill. One that don't cost too much. Or come in a pill.
Correction.
:P
(any true get gets pissed when someone breaks their concentration)
Should read
(any true geek gets pissed when someone breaks their concentration)
I write my flow without spelling or punctuation, maybe CowboyNeal can check it for me
--toq
Does anyone actually have a Java program designed to control air traffic, or for the operation of a nuclear facility?
The one thing most people fail to consider is the possibility of incramental backups.
/-/4xx04z where tapes will. Additionally, a proper backup procedure should also include a monthly backup to be taken off site in case of a fire, flood, act of god, or act of pissed off ex employee who is owed a lot of money by ex employer (you hear me, you bastards? [yes, I'm joking. Don't sue me.] ; )
Consider that on a 200gigabyte drive, it's improbable that there will be more than a couple gigs of new content in any given week (even if you're a major porn hound.)
2 gigabytes worth of data is plenty small to do incramental archives nightly on a tape drive.
With that said, you're right... A second hard disk is far more efficent for the needs of the average consumer.
Most IT industries use tape drives as well as RAID arrays simply because it creates a sort history of the data on the drive. Where RAID won't protect you from stupid user errors and 1e3+
People seem to forget that tapes are generally an enterprise solution... Not somthing intended for the desktop.
The use of liquid disk bearings and the subsequent discussion about drive noise bring to mind a question I've been meaning to ask for some time. I've noticed that my drive (20GB unbranded, 4GB ext3 partition, 16GB FAT32 partition) under Linux makes much more noise than it does under Windows2000. A couple of years back when I first got Linux installed (SuSE5,2) on a different drive in a different machine, I noticed that the drive made less noise under linux than it did under Win95. Has anyone else noticed anything similar? Is there a reason for this? Should I be using a different format (Reiser, XFS or whatever)?
Didn't anybody read the actual article? The drive comes with a free Promise Technology Ultra ATA Controller Card.
The also explain the 137 gig barrier
28-bit addressing, there are only 28 bits available to access a given address on the hard drive, which when all bits are set equates to 137 GB.
By doubling the number of bits that can be used to access a given address, 48-bit LBA addressing pushes the maximum storage limit to 144 petabytes.
Hmmm, how does going from 28 to 48 bits double the number of bits?
Well how long before we will need to change again? It was not long ago that they came up with the 28 bit system. 137 gigs - no one will ever need that much memory. Now its 144 petabytes - no one will ever need that much memory. Hell a quantum transporter will need at least 4 yottabytes. I say go to 128 bit addressing just to be safe.
Today's vices may be tomorrow's virtues.
When I tried software raid5 the performance was pretty terrible. Software raid1 adds pretty much no overhead though, so that's certainally an option to consider..
Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
For the love of God, when will the PC industry stop with these damned limits?
FYI, for anyone interested in reading a nice list of all such limits with a technical description for each one, I suggest this link.
Yeah. By far my favorite hard drive manufacturer is IBM...most of the Deskstar hard drives I've had have been good, fast (in their time), reliable and relatively cheap. My primary box has an ultra ATA 100 120GB IBM Deskstar and I'm pretty happy with it so far. Its fast, quiet and only cost me $125. :) I don't usually do RAID for desktops, but I might RAID 5 this with another drive sometime because they are so cheap. :)
My journal has hot
> 40% on-disk errors before low-level (factory) format?
Coming from a firmware engineer from a disk drive company, that sentence makes no sense whatsoever.
The "stretched capacity formats" that drive companies are using to reach their 200GB or larger drives are almost purely a function of the heads used in the drive, and have almost nothing to do with the specific media. From the plots I have seen, if media had 1% surface defects I would be surprised...
More data, damnit!
What about when lightning fries your whole machine - both drives? Or what about if you accidently erase an important file and you don't notice in time to recover it (assuming that's possible.) Offsite tape backups would address both of these problems.
I agree with you that drives this size are scary, mostly because there is no affordable way to make tape backups of them. I decided a while back that one should only purchase as much space as they can actually backup, but that isn't going to even be possible for much longer - soon 60G will be the bottom end!
Not any more. You just made it 10. Silly Macintosh. Unix is for real computers.
a cross between a lizard, a borg, and spongebob squarepants?
Technoli
Well the site's administrator COULD put on a custom error page. What I never really understood about IIS overloading is that if the webserver does not have time to process your request, how does it have time to create a fancy error page.
Yes, and this is from old-school thinking where they feel compelled to encode control information into data streams. Rather than using a 32-bit "structure" they should have spent the extra few dollars and used a 32-bit data bus and a synchronized 8-bit control bus. Then we'd have been able to easily have 32-bit addressing and would probably be able to hang 63 devices off the bus.
RANT MODE, ENGAGE!
This could be done pretty easily if the PC world would just LET GO. Stop clinging to compatiblity with things that you'll never use again anyways! When's the last time YOU plugged in a hard drive 1 Gig? Do you really PLAN to use that on a new system? Then why should it matter if the new system can read antique hardware? Bah! The entire industry is hopeless.
RANT MODE, dissolve.
You must not do any video editing. My home machine has 165 GB installed (120 of it in RAID-0), and a significant chunk of that is usually filled. One "60-minute" TV show at 480x480 23.976 fps, with CD-quality audio and with the ads cut out (bringing the length down to about 45 minutes), takes about 20 GB when compressed with Huffyuv. I only keep that file around long enough to crunch it down to a 790-MB MPEG-2 that I can burn to SVCD, but just a few shows will take up a significant amount of space while they're waiting to be compressed.
20 January 2017: the End of an Error.
Um...I have a ScanJet 5470C that delivers 2400 dpi optical resolution. A letter-size scan in 24-bit color at 2400 dpi only takes about 1.5 GB. Given that most photos are smaller and don't need to be scanned at that resolution (about the only time you really need 2400 dpi is when you're scanning negatives and slides), how is it that you'd need more than 13 GB to store a scan?
(If you're going beyond your scanner's optical resolution, you're wasting time and disk space. Nearly everybody advertises a "9600-dpi" scanner nowadays, but no flatbed scanner that I've ever heard of can deliver anything even close to that. (Maybe some ultra-high-end model that might be used in the printing industry or something like that, but certainly not anything that you'd pull off a store shelf. FWIW, a letter-size scan @ 9600 dpi would take about 24 GB...but with currently-available scanners, 94% or more of the information in the image would be redundant.)
20 January 2017: the End of an Error.
My wife and I bought a DV cam to record our wedding and honeymoon. We shot about 5.5 hours total footage and now I'm in the process of editing it down to 1/2 hour to an hour to make a DVD. We added a 120 GB drive to our Mac and the thing now has about 40 GB free. It will continue to lose space as I copy clips around during the editing process.
Only real problem with such huge capacities is that backup media consistently lags behind. When I finish this project, there's no way I'll be able to backup all the source media as that would take 15-20 data DVDs. It's not so bad since I'll be throwing out a majority of the raw footage and can backup just what goes into the final video, but I'd hate to have 200 GB of data I really cared about! Backing up that much to reliable offline media is cost prohibitive to the home user.
Say hello to zMac.
"Is it a conspiracy to make a few people pay 3X for SCSI?"
People often complain that SCSI costs 3X more than ATA, when the HDA (Hard Disk Assembly) is often the same in both. "Why does SCSI cost so much more?" they ask.
That is the wrong question. They should instead ask, "Why does ATA cost so much less?"
The minimum quality level you see with ATA is significantly lower than for SCSI. You can find some really crappy ATA parts out there, and you can find vendors to sell them, and people to buy them. The least-effort engineering that ATA gets is why you can buy a 100 GB hard disk for a buck or whatever. They simply do not put a lot of engineering into a product that cheap.
Now, compare that to the market SCSI gets used in. You are not going to build a $10,000 workstation or server and then put a crap hard disk in it. About the only place SCSI gets used is in that kind of high-end equipment, so the demand is for well-engineered SCSI products. Anyone pushing the kind of crap that ATA is would be laughed at.
So, in the end, you get what you pay for.
dragonhawk@iname.microsoft.com
I do not like Microsoft. Remove them from my email address.
"does anyone know exactly what to call things like the promise and Highpoint "Raid" controllers that rely on BIOS hooks and software drivers to do the RAID dirty work?"
Junk?
dragonhawk@iname.microsoft.com
I do not like Microsoft. Remove them from my email address.
I've come to the conclusion that pretty much all IDE drives currently being sold suck.
I have had zero problems with our IBM SCSI drives.
this is from old-school thinking where they feel compelled to encode control information into data streams.
ATA uses separate registers for control. Data transfer takes place as a separate operation of successive reads of the data register (PIO mode), or as its own DMA transfer.
Rather than using a 32-bit "structure" they should have spent the extra few dollars and used a 32-bit data bus and a synchronized 8-bit control bus.
Sure, that would have made a lot of sense when ATA was standardized in the days before PCI and other 32 bit busses were common. Even today, that'd be a really dumb move, to dedicate a bus to sending the commands and reading status which is such a tiny fraction of all the data transfer. Even with a (senseless) dedicated 8 bit control bus, you'd still need four 8 bit writes to send the sector number to the drive, which is more or less what happens today. In the ATA standard 4 of those bits are for something other than the sector address (LBA mode). Even if your proposed scheme used 32 bits, that's still a "barrier" of 2 terabytes. ATA-6 defines a 48 bit LBA extension, which amounts to just writing a few more bytes over the bus. 2^48 sectors of 512 bytes each is a LOT.
Wide SCSI is only 16 bits wide, by the way. Future disk standards will be serial access, using LVDS signals (1 bit wide) Welcome to the modern world, where transistors are free and wires are what costs money!
Then we'd have been able to easily have 32-bit addressing and would probably be able to hang 63 devices off the bus.
The two device limit is due to electrical signaling requirements. There's two more bits in the "head" register that could have easily been assigned to allow 8 devices to be addressed instead of 2 (and if one of the six unused bytes on the second chip selected had been used, 256 devices could have been addressed). The IDE bus is not terminated. The electrical design allows for only two devices to reliably communicate with one host. The protocol only provides one bit in one register to select between them... but the real limitation is physical, not logical.
This could be done pretty easily if the PC world would just LET GO. Stop clinging to compatiblity with things that you'll never use again anyways!
Sure, go write up your business plan that involves hundreds of millions of PC owners (and operating system vendors) all converting to a new motherboard, new drives, and new software.
Of course, it IS happening with serial ATA, but everyone involved has very realistic goals that make good business and technological sense. The main thing that's driving it is the difficulty of providing 5 volt tollerance and TTL logic levels in modern chips, where the transistor gate-to-substrate and drain-to-substrate breakdown voltages are getting lower and lower as the gate width shrinks (making many more, much faster transistors available). The large number of signals required (over 50 for two controllers) also makes poor usage of a LVDS capable process (UDMA133 is only 66.5 MHz signals on each pin, when LVDS can support gigabit speeds). Silicon gets cheaper and cheaper (per transitor), but the physical packaging technology doesn't move that way, so pins are at a premium. In the not-too-distant future, drives will use a tiny connector (4 pins as I recall), and the same basic protocol as used today.... more or less in exactly the opposite direction as your rant suggesting a 32+8 bit bus and a completely new protocol that throws backwards compatibility to the wind.
PJRC: Electronic Projects, 8051 Microcontroller Tools
Right on.
MiniDV format clocks in at nearly 13 GB per hour.
backup media consistently lags
I've got about 0.3 TB of disk space at home between my 2 TiVo's. They have more disk space than my two computers do. They never get backed up, either, because there's nothing to back them up to. They're their own archive.
Video is driving desire for
- low noise
- high capacity
- random access (linear tape sux!)
- high reliability (no backup, remember!)
and what I see coming (while last mile service is still unacceptably slow) are home NAS systems connected via 802.11b to TiVo-looking consumer electronic devices and to wireless tablets just for watching shows.If I were a disk manufacturer, I'd goad the consumer video recording technology to shift into higher gear (come out with TiVo's with built-in 802.11b and a NAS repackaged as a "VideoArchive") and be ready with all the pieces to satisfy this market.
[I've got a Mini-DV recorder, too, but haven't worked up the courage yet to figure out which IEEE-1394 card to buy for my Linux box and how to get it to work.]
"Provided by the management for your protection."
see the web site of the kookoo CoCo High Priest. The best link on that page is about an innovative 4 MHz acceleration project they are putting together. I'm not kidding.
We had one in the TI world. The TI-99/4A had a TMS 9900 16-bit processor (in *1979*, boys and girls), but back then, memory was super-expensive. The ROM, video processor and TMS9901 coontroller were on the 16 bit bus, everything else was on a kludged together 8-bit bus... including the RAM.
A popular TI hack was to solder 8 bit static RAMs piggybacked over the 2x8bit ROMs which resided on the 16 bit bus. A little address decode logic (piggyback some 74xx chips onto some other ICs, and a little point to point wiring) and you had a TI-99/4A with full 16-bit memory. Instant speed increase of over 40%. And because of the bus bottleneck and the *really slow* doubly-interpreted BASIC, those machines desperately needed speed upgrades. Running object code instead of BASIC, on a TI with that upgrade, was lightning fast.
And I thought that was an impressive TI hack until I saw this. My God, that looks like a bank of 72 pin SIMMs in a TRS-80.
Fire and Meat. Yummy.
Young SWM seeking solution to ponogrophy archival issues? : )
Still, there's enough room on a 1GB DAT for a weekly incremental.
Thanks for the spelling correction, by the way. Me inglish not soo good, which is sad because I'm actually a native english speaker. -_-; I blame fatigue, and cheating on all the spelling assignments in grade school.
So which one of us is right?!
You are.
I've had more than a couple WDs go on me, as well as Seagate, Quantum, others.
I've only had one IBM, but both it and ALL of my Maxtors (including a 200mb drive) still work.
.sig last updated Jan. 14, 2000
Junk?
the problem is getting the point across to the misinformed/ brainwashed masses when you try to explain to them why those devices really are NOT true raid.. "but it says so on the box"... Especially when in a specification quote you list "hardware RAID recommended" and they think that one of those cards would do the job and balk at the price of a real raid card.
What is unfortunate is that other manufacturers have caught on and use the same tactics to sell their hardware as well... like USR advertising 802.11b at 22mb when the only way to do that is using their cards with their modified software... or my current pet peeve... the PCI standard. boards that say they use PCI2.2 are NOT backwards compatible with PCI2.1; when getting a new card, check for SPECIFIC compatibiliy [ie: if it says it works in PCI2.2, then that may not necessaryily mean it would work in a PCI2.1 mb, and vice versa... but anyways... this is going a little offtopic... so to bring it back on topic.... Hard drive sizes that are reaching/exceeding the 200gb range are still doorstops that used to hold gb of data if it crashes and there are no backups..
For me, I would only use such a drive as a "live virual CD jukebox" for my frequently used ISOs...
--
Time is on my side
You are the among the last of a dying breed. Long gone are the days of Kiss The Blade, sociology/ethics/physics/psychology major and euroderf. Almost all the trolls left here are mindless crapflooders. I salute you.
Fire and Meat. Yummy.
Not that it really matters, but I would like to know the actually size in bytes of a drive that they are selling me, and in mb (where 1mb == 1024kb, 1kb == 1024 bytes, not 1 == 1000)
Would it really be much trouble for them to say 198 gb hard drive? I remember when they used to sell 40mb hard drives, and say they were 40mb, and if it was off by 2gb in size, people would have been pissed (or really happy).
People used to get accuraccy, for sizes, and speeds, but now it's all so fluffy
Tibbon
tibbon.com