Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Terabyte Hard Drive Put To the Test

Posted by Zonk on Mon Aug 13, 2007 03:15 AM
from the where-did-the-missing-69-gigs-go dept.
EconolineCrush writes "As a technical milestone, Hitachi's Deskstar 7K1000 hard drive is undeniably impressive. The drive is the first to pack a trillion bytes into a standard 3.5" form factor, and while some may argue the merits of tebi versus tera, that's still an astounding accomplishment. Hitachi also outfitted the drive with 32MB of cache—double what you get with standard desktop drives—making this latest Deskstar a leader in both cache size and total capacity. That looks like a great formula for success on paper, but how does it pan out in the real world? The Tech Report has tested the 7K1000's performance, noise levels, and power consumption against 18 other drives to find out, with surprising results."
+ -
story

Related Stories

[+] The First Terabyte Hard Drive Reviewed 495 comments
mikemuch writes "ExtremeTech has a review and benchmarks of the Hitachi Deskstar 7K1000 1TB Hard Drive, which ushers in the terabyte age. It performs well on HDTach and PCMark benchmarks, though not as speedily as professional-grade drives. It could be just the ticket for digital media junkies. 'One of the first issues to note is that you may not see an actual one terabyte capacity on your system. First, the formatted capacity is always less than the raw space available on the drive. Directory information and formatting data always take up some space. Second, the hard drive industry's definition of a megabyte differs from the rest of the PC business. One megabyte of hard drive space is 1,000,000 bytes: 10^6 bytes. Operating systems calculate one megabyte as 2^20 bytes, or 1,048,576 bytes. Once installed and set up, Hitachi's 1TB hard drive offers up an actual formatted capacity of about 935GB, as measured by the OS. That's still a lot of space, by anyone's definition.'" Update: 05/17 21:52 GMT by Z : Adding '^s' missing from article.
[+] New Water-Cooled Hard Drives Coming 145 comments
CoolHandLuke writes "NEC and Hitachi are teaming up on a liquid cooling system for hard drives. The goal is to cut down on noise levels while providing more efficient cooling. 'Hitachi and NEC are developing the water-cooled hard drive systems for desktop computers mainly to reduce noise levels to 25 decibels, 5 decibels quieter than a whisper. To do this, NEC and Hitachi actually wrap the hard drive in "noise absorbing material and vibration insulation." According to Hitachi and NEC, the cooling cold plate they're planning to use is the most efficient plate ever used for heat conduction, which means they'll be able to cool the hard drives quicker and more efficiently.'"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Test? (Score:5, Funny)

    by Anonymous Coward on Monday August 13 2007, @03:18AM (#20209465)
    Now, my porn collection, THAT is what would put this drive to the test.
    • Re:Test? (Score:5, Funny)

      by Hydryad (935968) on Monday August 13 2007, @03:37AM (#20209581)
      Why am I not surprised at all that porn is the third word in the comments about a terabyte hard drive. Pushing forward innovation since the dawn of time, hot steamy sex.
      • Re:Test? (Score:5, Funny)

        by Anonymous Coward on Monday August 13 2007, @05:30AM (#20210091)
        Pushing forward.... and back... and forward.... and back....
  • by BadAnalogyGuy (945258) <BadAnalogyGuy@gmail.com> on Monday August 13 2007, @03:19AM (#20209469)
    ge ge ge kanashhk shhk shhk fzzke kek shhk shhk

    I love the sound of head crashes in the morning. Smells like... a coffee break.
  • by FF8Jake (929704) on Monday August 13 2007, @03:23AM (#20209493)
    I'm not losing my 1.5TB of porn to a single Hitachi Deathstar.
    • RAID 6 Please (Score:4, Interesting)

      by the_doctor_23 (945852) on Monday August 13 2007, @03:57AM (#20209705)
      Make that RAID-6. With consumer grade drives I would not want to see a second drive die during a RAID-5 rebuild.
      For example a 3ware 9650SE-8LPML can be had for as little $520.
        • Re:RAID 6 Please (Score:4, Informative)

          by Anonymous Coward on Monday August 13 2007, @06:25AM (#20210363)
          Because it isn't safer, at least not unless you have a battery-backed interface card *anyway*. And usually the only cards with battery-backing are... hardware raid cards. I have been known to use linux-md on an old hardware raid card, when the card had a very slow processor. But these days, raid cards have processors in the 300-600 MHz range, AND ASIC or FPGAs to do parity. They're more than adequate.

          Also, linux-md doesn't guarantee ordering, which hardware-raid cards, as they're intended for use with oracle and friends, do.
          • Re:RAID 6 Please (Score:5, Interesting)

            by Spazmania (174582) on Monday August 13 2007, @08:24AM (#20211173) Homepage
            Depends on the raid card. I run about 80 servers with a mix of HP/Compaq SmartArray, Adaptec aacraid, LSI Megaraid and Linux MD raid systems.

            The Adaptec and LSI Megaraid cards are truly heinous. Just last week I had a system that wouldn't boot because the megaraid card decided that the NVRAM and on-disk settings didn't match... Even though the "force boot" option was set. Force-boot is supposed to write the on-disk config to nvram on a mismatch. As often as not, a machine with a megaraid card crashes on a single-disk failure instead of continuing to operate minus one disk. It'll reboot fine but not before you lose the unwritten data and deal with filesystem corruption. And God help you if a second disk develops a bad spot... It won't do the best it can to rebuild; it'll simply flunk leaving the good portions of the data unrecoverable.

            I'll match Linux MD against those cards for reliability purposes any day. I wish there was some hardware I could buy that enhanced it with a battery-backed cache and parity acceleration. Then I could throw away the megaraid and adaptec cards.

            The SmartArray cards are actually very good. Expensive as hell, but good. Sadly the primary configuration utility is on a CD instead of in the bios and some goober at HP decided to rig the disc so it won't boot on any hardware that's not HP/Compaq. Fortunately you can boot Knoppix, copy the linux config utilities and configure it that way.

    • by tibike77 (611880) <tibikegamez@ya h o o .com> on Monday August 13 2007, @04:03AM (#20209725) Journal
      Only 1.5 TB of porn ? That's like what, 350 DVDs worth ?

      That's 85-125 USD for your entire collection in one single copy.
      Or make that a nice round 200$ for two sets of copies.
      So, where can I get two 1.5 TB HDDs for 100$ each ?

      Sure, the "seek time" would suck, but then again who cares, it's porn, not like you'll die if you wait 15 more seconds before you start looking at it... or are you ?
  • by Absolut187 (816431) on Monday August 13 2007, @03:27AM (#20209513) Homepage
    Recording technology: Perpendicular.

    Ah, its finally here.
    I remember reading about this like 4 years ago.
    Cool.
  • whoops (Score:4, Insightful)

    by scapermoya (769847) on Monday August 13 2007, @03:32AM (#20209545) Homepage
    FTFA: "Gigabyte drives were only "missing" 24 bytes, and that was easy to swallow."

    i think they meant 24 megabytes, which is easy to scoff at now, but wasn't when the first gigabyte drives dropped.
  • by Don Sample (57699) on Monday August 13 2007, @03:33AM (#20209549)
    He spends a lot of time talking about the difference between binary and SI terabytes and gigabytes, and then comes out with:

    Back in the day, the gap between decimal and binary capacity wasn't big enough to ruffle feathers. Gigabyte drives were only "missing" 24 bytes, and that was easy to swallow.
    Um, 24 bytes is the difference between kilo meaning 1000 and kilo meaning 1024. A binary gigabyte is 1,073,741,824, or 73 megabytes bigger than an SI gigabyte.
  • by _Shorty-dammit (555739) on Monday August 13 2007, @03:37AM (#20209593)
    This marketing BS always pisses me off. For years and years and years we've used 1024 in the computer world, since it's a power of 2, and computers deal with powers of 2. A 931GB drive is NOT a 1TB drive. And we don't need new stupid labels like tebi, we just need storage manufacturers to stop being retards.
    • by Jugalator (259273) on Monday August 13 2007, @04:00AM (#20209717) Journal
      Tera is the SI unit for 10^12 so unless you want to introduce special cases for the computer industry alone, we need a new prefix.
      • by _Shorty-dammit (555739) on Monday August 13 2007, @04:04AM (#20209735)
        Way to pay attention. Nobody gives a rat's ass about "the SI unit." These are computers. And we've always used kilobyte/megabyte/etc as they applied to computers. You think you're right, but you're not. A kilobyte will always be 1024 bytes. A megabyte will always be 1024 kilobytes. A gigabyte will always be 1024 megabytes. And a terabyte will always be 1024 gigabytes...
        • The revisionists are everywhere unfortunately..

          Every time I see a wikipedia page with MiB or mebibyte or whatever the heck, I want to change--fix--it!

          e.g..

          http://en.wikipedia.org/wiki/Voodoo2 [wikipedia.org]
        • by Valacosa (863657) on Monday August 13 2007, @04:52AM (#20209913)

          Nobody gives a rat's ass about "the SI unit." These are computers.
          Yeah. Making nomenclature consistent across industries is damned inconvenient! Why bother?

          Look, I hate marketing dishonesty as much as the next guy, but borrowing the SI prefixes honestly does nothing but add confusion. Hard drives are easy, because one can safely assume that the marketing 'tards went with whatever number was bigger. But what about my phone's data plan? Aside from the whole kB vs kb thing, how do I know which definition of "kilo" my provider has gone with? Do they consider themselves with the "computer industry" or with the rest of the world? And (this is the best question), will the not-very-well-paid support grunt even know the difference?

          Would you like it if you agreed to sell a dozen POS systems to a bakery, only to be told after the contract, "Sorry sir. This is the baking industry. You agreed to give us thirteen systems." Or if you got a $30 bill from your ISP with the explanation, "This is the computer industry. Though our adverts say this plan is $30 a month, that's hex. In base-ten dollars, you owe us $48."

          You hate marketing people skewing reality. Good. It is only through fighting ambiguity that they can be stopped from getting away with this.

          Do you know the difference between a pipe and a tube? If you get into any business involving either, I hope you don't repurpose the words everyone else has settled upon.

          You think you're right, but you're not.
          It's that extra bit of humility that really makes your post shine.
        • by PMBjornerud (947233) on Monday August 13 2007, @06:32AM (#20210419)

          Nobody gives a rat's ass about "the SI unit." These are computers. And we've always used kilobyte/megabyte/etc as they applied to computers.
          Well, maybe electrical engineers would prefer to have 992 watts on the kilowatt, grocers would like to define a kg as 977 grams. Maybe 1023 tons of TNT is what fits on a standard truck, so it would be handier than that stupid 1000 for a kiloton. And the food industry, maybe they would like to redefine kilocalories as 1005 to the kilo, just because of some weird internal workings of molecular workings?

          But instead of going with whatever number that fits their specific field, they all went with 1000. Really, that IT people refuse to do the same makes us look utterly retarded.

          Not that it matters anyway. With 8 bits on the byte, we're doomed before we even start. There is no hope in sight until we just ditch this shit, get a clue from the network people, and start counting bits in multiples of 1000.
          • by poot_rootbeer (188613) on Monday August 13 2007, @09:56AM (#20212179)
            Maybe 1023 tons of TNT is what fits on a standard truck, so it would be handier than that stupid 1000 for a kiloton.

            Are those "long" tons (2240lb), "short" tons (2000lb), or "metric" tons (1000kg)?

            Ambiguous terms of measurement do exist outside of the computer industry, too -- which, I should point out, is actually "the software development industry" plus "the hardware manufacturing industry" plus "the IT service industry" and so forth.

            Drive manufacturers have always used base-10 prefixes to describe the capacity of winchester drives. It's not a marketing ploy, it's historic convention.

          • by Anonymous Coward on Monday August 13 2007, @05:14AM (#20210019)

            The definition of Tera of anything is 10^12 of that object.

            Let us take your absolutism to its logical conclusion.

            Prima: I've got a huge car!

            Secunda: Dude, I've got a huge cat!

            * SUV-sized cat walks in.

            Prima: Dude!

            Secunda: (looking to camera) No, you see, "big" is an adjective, and must be read in the context of the noun it describes. A big cat is not the same size as a big car, or a big house, or a big boat. Prima: I see what you're saying. Similarly, a "kilo-gram" is prefixing the gram, a base-10 system, thus 10^3 grams; while a "kilo-byte", prefixing the byte, part of a base-2 system, refers to 2^10 bytes?

            Secunda: Exactly! Humans, complex machines that they are, make use of context to bring out meaning.

            Prima: But on Wikipedia it says this use is incorrect?

            Secunda: Well, Wikipedia has the quality of a scientific journal... assuming submissions to scientific journals were all accepted for publication, and could be edited by anyone at any time.
            Prima: So, the individual or group with the most amount of time ends up producing the predominant content?

            Secunda: Exactly! The best way to confirm whether an article is likely to be useless is to read its talk page; in fact, you are more likely to learn from this page, as it illustrates the points of contention that one side or the other has tried to suppress.

            Prima: So for the past two decades we have called 1024 bytes a "kilobyte", until one standards body associated with manufacturers of hard drives decided to redefine it...?

            Secunda: Precisely. Worse, the previously unambiguous (outside of hard drive manufacturing) "kilobyte" is now defined as "1000 bytes". It'd be like renaming the mile to the "iMile", then stipulating that all future uses of "mile" should be based on the origin of the word - i.e. one thousand double paces.

            Prima: But paces vary from person to person - it's like you're making an arbitrary change based in a tenuous argument that goes against the principle that language evolves other than by edict!
            Secunda: Now you're getting the hang of it. Have you considered becoming a Wikipedia editor?

            Tercera: Listen you two, either shut up or get a room.

            Prima: Let's get some beer.

            Secunda: Word.

            * SUV-sized cat disappears in a puff of semantics, replaced with a slightly overweight puddytat.

    • by this great guy (922511) on Monday August 13 2007, @05:39AM (#20210143)
      Contrary to common belief, power-of-10 prefixes (as used by disk manufacturers) are much more commonly used than power-of-2 prefixes in the IT world. People claiming the contrary are wrong. Here are a few examples:
      • A 128 kbit/s audio stream is 128 * 10^3 bit/s (power of 10)
      • A 100 Mbit/s ethernet card is 100 * 10^6 bit/s (power of 10)
      • A 480 Mbit/s USB2 link is 480 * 10^6 bit/s (power of 10)
      • A 500 GByte disk is 500 * 10^9 bytes (power of 10)
      • A 56 kbaud modem is 56 * 10^3 baud/s (power of 10)
      • A 1.5 GHz processor is 1.5 * 10^9 Hz (power of 10)
      • A 6 Mbit/s DSL line is 6 * 10^6 bit/s (power of 10)
      • A 650 MByte CD is 650 * 10^6 bytes (power of 10)
      It is a total mystery to me why people think that power-of-2 prefixes should be the norm, when the only few places where they are used are to refer to the size of files and RAM sticks.

      Spread the truth. Mod me informative ;-)
      • by SoapBox17 (1020345) on Monday August 13 2007, @05:53AM (#20210201) Homepage
        If you notice, everything listed in the parent is in powers of 10 bits (or Hz) except for disc capacities. Like everyone else said, this is because disc manufacturers want to confuse you. When talking about m/g/k bits the convention is to use powers of 10, and when talking about bytes it is to use powers of 2. Hence, as the parent said, powers of 2 are used for file sizes and RAM sizes... because those are usually in bytes.
      • It's worse than that actually, because as the sizes grow, the disparity grows too.
        • When you say 1KB, the difference is 2.4% or 24 bytes.
        • When you say 1MB, the difference is 4.8% or 48KB.
        • When you say 1GB, the difference is 7.4% or 74MB.
        • When you say 1TB, the difference is 10% or 100GB.
        So, the higher the capacity, the more difference is there between binary and decimal units. 2.4% difference is significant enough, but it's not as bad as 10%. Lacking 100GB, or a full tenth of the capacity is however quite noticeable.
  • by Zebedeu (739988) on Monday August 13 2007, @03:44AM (#20209641)

    The Tech Report has tested the 7K1000's performance, noise levels, and power consumption against 18other drives to find out, with surprising results.
    Suspense!

    Come on! Just tell us what the results were directly, don't make us have to break Slashdot law and RTFA!
    • Re:Visit our site! (Score:5, Informative)

      by LarsG (31008) on Monday August 13 2007, @05:46AM (#20210179) Journal
      I've RTFA, and still don't get what the 'surprising results' is supposed to be.

      It has huge capacity - check.
      It is noisy and sucks power - check.
      It is not a speed champion - check.

      Not exactly surprising for the first 1TB drive on the market.
  • Conclusion [techreport.com] in the article: Too expensive.
  • by emj (15659) on Monday August 13 2007, @04:12AM (#20209777) Homepage Journal
    The problem is this will be full in 24h with a 100Mbps connection anyways, or ~6 hours if you live in sweden.
  • Meaningful tests? (Score:5, Insightful)

    by mrkh (38362) on Monday August 13 2007, @04:27AM (#20209825)
    I'm not that convinced by the testing methods here. The boot and load times page shows 20 seconds difference between the slowest and fastest drives which they barely comment on, and yet the drive with the slowest boot time is among the quickest when loading Far Cry and Doom 3? Something is not right there.

    And if they're really timing level loads with a stopwatch, why on earth are they quoting 2 decimal places (and besides, the variability in reaction time is accounting for most of the supposed differences in any case). Half of their tests don't appear to tell anybody anything significant, and the most worthwhile page in there is the conclusion. Pretty graphics though.

  • Real-world use (Score:5, Interesting)

    by zuki (845560) on Monday August 13 2007, @06:31AM (#20210399) Journal
    Been using this drive as my primary music streaming audio drive while on the road, with rugged real-world everyday mission-critical use
    in front of thousands of people, where one mis-hap is already too much.

    So far things have been flawless, and it has made a huge difference for me due to portability compared to anything else of the same capacity.
    as previously this meant a two-drive combo with heftier power supply.

    The weight and size make it easier to have it as a carry-on item, rather than in my checked luggage!
    As far as performance, it has been able to handle 4 simultaneous 24-bit / 96 kHz audio tracks playing back with no hiccups whatsoever.
    The drive-to-drive copying in Firewire 800 or SATA has been quite speedy and error-proof.... (copying 900 gig at a time is always a good test)
    Dream come true if you ask me.... I still carry a backup anyway, LOL!
    (ymmv(TM), batteries not included, kids don't try this at home, etc....)

    Z.
  • by AbRASiON (589899) * <slashdot&scottylans,com> on Monday August 13 2007, @06:36AM (#20210433) Journal
    So this baby has 200gb platters, it sounds all impressive and all, except we've had 188gb platters for ages now.
    Seagate has announced (and released, I think?) their 1TB HDD with only 4 platters (cooler, quieter, less power, less weight, less cost to manufacture) that's 250gb a platter

    Samsung have announced the F1 using 333GB per platter! 1.6TB if they copy Hitachi and slap 5 of them in a 3.5" unit - or rather 333gb single platter, light, cheap drives, be damned if anyone can find the F1 yet though :/

  • On another note... (Score:4, Insightful)

    by gerardrj (207690) on Monday August 13 2007, @11:14AM (#20213123) Journal
    TOO states " As the first hard drive to reach the terabyte mark, Hitachi's Deskstar 7K1000 will be remembered, too. Squeezing a trillion bytes into a 3.5" hard drive form factor is a monumental engineering achievement"

    I doubt that anyone will remember this in a year. Quick; what was the model and manufacturer of the first drive to pass 500GB, or 1GB. Both were monumental engineering achievements in their time. These milestones will not be remembered because they are all evolutionary; a 10-30% jump in capacity. When we see 10x capacity increases in one generation, THAT name might be remembered.

    That said.. good job Hitachi, but we all know that WD and Seagate will be out with their versions in a month or so.

    • by ipooptoomuch (808091) on Monday August 13 2007, @03:43AM (#20209631) Journal
      500GB of data loss?!? I CRIED for a half hour over a filled 160GB drive after it got killed by an electrical storm. Even though it wasn't technically covered under warranty, the fine folks at best buy still took it back after I said a defective flux capacitor on the drive started it on fire.
          • Re:Data loss (Score:5, Informative)

            by encoderer (1060616) on Monday August 13 2007, @08:13AM (#20211071)
            Yesterday at a Best Buy in Ohio a guy and his wife were looking at 42" Sony LCDs. There was a 1080P for $1899 and a 1080i for $1599. Guy asked the sales associate what the difference was.

            Sales associate, I shit you not, said "The "P" is actually a newer product. It is 7 minor revisions later. We still carry the "i" because it's still very popular. The same thing happens with our wireless equipment, too. the "N" version is out, but most users are still buying the "G" Version"

            I approached the guy after the sales associate left and said "listen, that guy has no clue what he's talking about. I is interlaced, P is progressive. On an "i" it's drawing 540 lines every frame, on a "p" it's drawing all 1080. Go with the "P" if you can afford the difference. It's worth it"
    • Re:Data loss (Score:5, Insightful)

      by jimicus (737525) on Monday August 13 2007, @03:51AM (#20209681) Homepage
      RAID 1+0 is the way to go for redundancy. Unless you're unlucky enough to lose both drives in one of the pairs making up the array, you can survive more than one drive failing.

      It's also the way to go for speed - your controller doesn't have to calculate the parity bits for every write operation (yes I know the parity sum is simple - that doesn't stop it from adding a bottleneck).

      RAID5 is most useful where:

      1. You desperately need the space.
      AND
      2. You can't afford the drives (or, for that matter, power/larger RAID controller) required to acheive the same space in RAID 1+0.
      • Re:Data loss (Score:4, Informative)

        by Ex-MislTech (557759) on Monday August 13 2007, @05:21AM (#20210049)
        Some problems with RAID 1+0:

        Not all hardware controllers will allow you to do a reconstruct to add more
        space and extend the partitions later on RAID 10 or 1+0.

        Recovering from a failed 1+0 is ok if it is a "simple" failure.

        I have had better luck recovering RAID5's than 10's or 1+0's.

        • Re:Data loss (Score:4, Informative)

          by zeromemory (742402) on Monday August 13 2007, @07:25AM (#20210689) Homepage

          Not all hardware controllers will allow you to do a reconstruct to add more
          space and extend the partitions later on RAID 10 or 1+0.
          Likewise, many hardware controllers won't let you extend a RAID-5 array, (unless they implement some dynamic stripe size hack, a la ZFS's RAID-Z [sun.com]).

          Recovering from a failed 1+0 is ok if it is a "simple" failure.
          Please explain what a !simple failure would be. Here, let me give you a 'simple' failure case where RAID-5 would be pretty difficult to recover from: a drive fails in your RAID-5 array, and you lose power or experience another hardware failure shortly afterwards, before you can replace the drive. Whoops, you just became another victim of the RAID-5 write-hole [wikipedia.org] (see the section under RAID-5 performance).

          OK, here's why we use RAID-10 at my installation: it provides great performance and can survive multiple drive failures without the overhead of something like RAID-6. RAID-10 also has no 'write-hole'. Don't just take my word for it, though, check out this article [adaptec.com] from Adaptec comparing the merits of all the basic RAID levels and their nested brethren.
        • Re:Data loss (Score:5, Informative)

          by walt-sjc (145127) on Monday August 13 2007, @08:40AM (#20211317)
          I lost 3 drives out of 6 within a few hours of each other. Raid 1+0 saved my bacon. Zero down time. Got the email alert about the first drive, and scheduled a trip to the datacenter. Then I got the other two back to back a couple hours later. These were all 15K rpm SCSI drives which had survived a 2 week stress test burn-in, and had been in production for about a year, so it was totally unexpected. In another case, I lost 2 drives in a Raid 5 and had to resort to restoring the machine from backups - a day lost. Raid 6 performance is even worse than Raid 5, so I personally see no point - YMMV. Raid 5 and 6 rebuild time is also VERY slow compared to 1+0, taking 3 times longer in my testing.

          Anyway, what's that old saying? Expect the unexpected? When you buy a pile of drives, you are likely to get the batch from the same manufacturing line, day, etc. This probably also increases the chances of simultaneous failures if there is a physical quality problem. If you have two fail, expect a third. I generally don't mix up batches because I want to know where all the drives from a particular batch are, but maybe I should.
      • Re:Data loss (Score:5, Informative)

        by blackicye (760472) on Monday August 13 2007, @05:07AM (#20209983)

        BTW: Turn off S.M.A.R.T. This is like the indication of an ink cartridge: When the maker thinks you need a new
        drive.


        In my experience, when S.M.A.R.T. tells you a drive is dead or dying, its not kidding.
        • Re:Data loss (Score:4, Insightful)

          by xtracto (837672) on Monday August 13 2007, @05:28AM (#20210077) Journal
          Yeah, I've got to agree with you. I think that is one of the worst advices I have read on slashdot... A hard disk died on me a month after the S.M.A.R.T. thing started to annoy... it was on a laptop. Fortunately, I bought a bigger driver and passed all the information before the defective drive went dead.

          While I agree that the S.M.A.R.T. heuristics might be a bit sensitive but if you consider what is at stake (yeah... your valuable pr0n collection), then I guess its better safe than sorry.

          And, comparing it to the ink cartdriges? I am sure *your life* (or work...) does not depend on printing or not that pr0n picture...
          • Re:Data loss (Score:4, Insightful)

            by proxima (165692) on Monday August 13 2007, @07:48AM (#20210869)

            I have my desktop set up to mail me a warning and shut down on any SMART error. That should give me enough time to buy a new disk and salvage my data.

            I've always thought you have a slightly better chance of getting valid data off of a drive if you never actually power it down when it's failing. This is anecdotal from a power outage causing many old hard drives in a building to give up, with their computers normally having uptime measured in months or even years.

            Of course, to recover data like this you would need another computer accessible via the network, rather than installing a replacement in the desktop itself. Read any possible data off it while you still can, without putting it through the stress of powerdown/powerup.
      • Re:Data loss (Score:5, Informative)

        by Eivind (15695) <eivindorama@gmail.com> on Monday August 13 2007, @05:32AM (#20210097) Homepage
        That's nonsense. It isn't even true in theory. (at some point the remaining charge is below the noise-floor) If it wasn't you could store an infinite amount of data on a drive by simply filling it once with dataset1, overwrite by dataset2, overwrite by dataset3 and so on. You claim dataset1 will always be recoverable, so in this method, you could recover each of the sets and have stored triple amounts of data on the drive. You claim *any* amount of overwriting will be insufficient, so I guess I can store 1000 datasets on the drive then. Cool. Hint: The real world doesn't work like that

        Secondly, even if in theory you where rigth (which you aren't), in *practice* most data is not valuable enough that theres much real risk that anyone will recover it, even after something as simple as a one-time-all-nulls overwrite. (which is just about the suckiest overwrite you can do) Yes, in that case an expert lab *can* recover it, but odds are it won't happen.

        In practice, if you do the standard wipe, which is usually some variant of all-nulls, all ones, 3 times random, there is -zip- chance that anyone will be able to get at the data that was once on the platter.

        Now, what many (clueless people) do are "format" the drive or "delete" the files. These functions don't overwrite even once 99% of the platter, so files removed in this manner are certainly recoverable -- they're there in plaintext, just not referenced from the filesystem anymore. Something as simple as "cat /dev/hda | strings" will recover huge amounts of text from a hard-drive which has been erased in this manner.
          • Re:Data loss (Score:5, Insightful)

            by Eivind (15695) <eivindorama@gmail.com> on Monday August 13 2007, @07:39AM (#20210785) Homepage
            No. I don't think you are. Or you are, but for a different reason.

            Even the NSA very very probably can not recover any useful information from a disk overwritten the way I wrote. They have lots of money and expertise, but the laws of physics apply to them too.

            But they could get at the information on your computer by other means that you'd be unlikely to detect, if they really wanted to. For example, if the information is from the net and you don't encrypt everything, they could easily wiretap your broadband. Getting a hardware-keylogger into your keyboard would be possible too, aswell as dozens of other tricks.
      • by MrNaz (730548) on Monday August 13 2007, @06:20AM (#20210347) Homepage
        You really, really need to buy a lottery ticket.
      • Re:Data loss (Score:4, Informative)

        by Feanturi (99866) on Monday August 13 2007, @10:47AM (#20212823)
        What are people doing with drives to make them fail?

        I've got the same question, as I've gone through a lot of hard drives over the years but only due to upgrading, not failure. The only exception was the IBM Deskstar GXP75 that had the whole click of death thing going on. I don't count that one since it was a known issue that resulted in a class action suit, which I didn't bother to take part in. The first one failed within a month, so I replaced it at the store, and the replacement failed after a day. Replaced again. The third one failed after a week but I was tired of going back to the store by then so tried an experiment - the click of death was kicking in somewhere near 500MB after the beginning of the drive so I repartitioned it to leave the first 500MB unpartitioned. My experience with the drive up to that point told me that wherever the click of death manifested, it would consistantly happen in whatever part of the drive it first happened at. That drive has been in constant use ever since then (it's been like 5 years or so by now hasn't it?) and still works great, since it never accesses the 'bad part' anymore.
    • Re:5.25"? (Score:4, Insightful)

      by Fweeky (41046) on Monday August 13 2007, @08:59AM (#20211511) Homepage
      Except they'd have more parts, more complexity, and the larger components would need to be made to even finer tolerences since they need to remain well aligned over a much larger area (and they'd need to be stronger if you wanted to keep the same sort of RPM). They'd be much more expensive, and you'd probably still have to drop the density per platter a lot to keep it within the realm of sanity, not least because of things like thermal expansion having a much larger effect.

      File next to the disk with multiple drive head assemblies; possible, but just not worth it when you could just fit more, smaller, cheaper, independent disks in the same space.