Seagate Hard Drive Fiasco Grows
AnInkle writes "Two months after acknowledging that their flagship 1.5TB Barracuda 7200.11s could hang while streaming video or during low-speed file transfers, Seagate again faces a swell of complaints about more drives failing just months after purchase. Again, The Tech Report pursued the matter until they received a response acknowledging the bricking issue. Seagate says they've isolated a 'potential firmware issue.' They say there's 'no data loss associated with this issue, and the data still resides on the drive;' however, 'the data on the hard drives may become inaccessible to the user when the host system is powered on.' If users don't like the idea of an expensive data-laden paperweight, Seagate is offering a firmware upgrade to address the matter, as well as data recovery services if needed. By offering free data recovery, Seagate seems to be trying to head off what could become a PR nightmare that may affect several models under both the Seagate and Maxtor brands."
You better believe PR nightmare. After this how many will ever trust either the company or their products again?
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
Seagate has always been my favourite hd manufacturer. But I have to confess, when they bought Maxtor, I got nervous. They were never a commodity hd company. Always a bit pricier but worth it.
" They say there's 'no data loss associated with this issue, and the data still resides on the drive;' however, 'the data on the hard drives may become inaccessible to the user when the host system is powered on.'" ...so, my data is there, I just can't see it? That's reassuring.
For your first drive: /dev/sda /dev/sdb
sdparm -I
For your second:
sdparm -I
or whatever your drive is.
It appears to affect 1GB drives as well, such as the ST31000333AS.
I will ask if they have a firmware updater for Linux.
And, of course, the Seagate referenced page says: "This can be done in Windows - it's easy! Download and run, or simply run as is, the Seagate Drive Detect software program." No mention of Linux, MacOS, Solaris, or BSD. So I guess there is an implied "If you are not using Windows - it's hard!".
Then later in the page, "you can download SeaTools for Windows" with a convenient link. Again, no mention of Linux, MacOS, Solaris, or BSD.
What they don't tell you is that you can create a self-booting (MS)-DOS floppy/CD so you can test your drive, regardless of your OS (as long as the system is X86). Get it here: http://www.seagate.com/www/en-us/support/downloads/seatools/seatooldreg but if you DO need to flash it, you have to contact Seagate via Email and wait for a response and code so you can use yet another program to flash the drive.
I guess we now know what generation disk integrated the Maxtor people/facilities. This presumably means Seagate joins Maxtor on the never-again list.
"Oh if it crashes and takes your primary business machine offline just email use the serial number and we'll email you a keygen^H^H^H^H^H^Hdetection tool then email us the output of the tool and well email you some other shit that only runs on X86 windows... oh you're running PPC Linux on an embedded appliance... too bad, so sad."
I drink to make other people interesting!
Friends don't let friends buy Seagate.
Work done by an officer's doppelganger in a parallel universe cannot be claimed as overtime.
It would have been nice for them to do this for my 1Tb drive that died last month....
Those damn things had known issues to, the drive itself was likely intact as I heard no damage noises. It simply wouldn't power up one day.
They shipped me a refurbished model as I didn't have 2 grand to pay for data recovery...Kinda pisses me right the fuck off.
You can't take the sky from me.
Two of my drives are on the list of potentially affected drives. This is actually reassuring because one of the drives for a few weeks now has had mysterious issues similar the description in the article. I just wonder where I can download the firmware update... it appears that I have to contact seagate support, which I cannot do without registering on their website!
Given Seagates increasingly poor product quality, this has guaranteed I will never buy another Seagate drive. They used to be my favourite manufacturer, but this kind of sloppiness is unacceptable. Obviously all they care about is turning out high density cheap drives, with no thought to real quality assurance.
With the economy as it is this could spell the death of Seagate.
========
CINC, 4th Penguin Legion
Now I can finally say I told you so to all the Seagate fanboys who wouldn't stop circle-jerking when I kept saying that after a decade of frontline support I know that Seagates have a higher rate of failure than even their higher marketshare can compensate for. I kept getting fed the same old lines about how long their warranties were and how that made everything ok. Nevermind that this offer of data recovery is a last-ditch desperate measure that's an exception to all precedent. In most cases when I've been ring-side to a Seagate failure all I could do was point and laugh and say 'How good is your warranty at getting data back, bitch?'
I always buy WD, and in the dozens I've bought only one failed, infant mortality, and it was replaced less than two weeks with virtually no hassle.
I support the Slashcott and will not be reading or commenting from 2/10/14 to 2/17/14. Beta is steaming pile of dog shit
So we're going to lynch them for being open and honest that their drives have a problem and they're doing everything possible to minimize the harm to their customers? My, my, how progressive of us all. We're going to rail on them because they only made a firmware patcher for Windows. Well -- color me silly here but this is an emergency patch. It's an issue that's been discovered fairly recently and so they haven't yet made a firmware loader for other operating systems that makeup Help your community instead of bemoaning your minority status. I've never understood why a community of technical people can be so smart except when it comes to their choice of operating system, where they promptly start screaming "help, help, I'm being repressed!" This behavior is tolerated inside the linux/free software community and I'm at a loss for why... At least in the GLBT community, we tend to give these people a loving, but firm kick in the ass, not indulge them. You all could learn from the example.
#fuckbeta #iamslashdot #dicemustdie
I can't find any reference to the free data recovery services mentioned in the article summary. Can someone help? My 500GB Seagate 7200.11 drive was hit with this problem about a month ago and I would like to get it fixed (for free).
I will. And I've actually been down on Seagate ever since they took AAM off their drives with the 7200.x series.
But hey, just because I'm a W-D fan right now and not a Seagate fan doesn't mean I'll never trust Seagate again. This kind of stuff just goes around in circles. At one time, W-D couldn't make a drive that worked and Seagate was the top of the industry.
Every company that is on top at one time has problems at another. Not every company that sucks makes it to the top though (I'm looking at you Maxtor).
It'll go around again I think, even though Seagate bought Maxtor, they'll likely remember how to make good drives again at some point.
http://lkml.org/lkml/2005/8/20/95
Isn't that the message coming from Seagate?
Save yourself the time and effort, the required firmware updates are on bittorrent http://thepiratebay.org/torrent/4627627/Seagate_1.5TB_ST31500341AS_Firmware_Update
Only the State obtains its revenue by coercion. - Murray Rothbard
Oh, it gets better. We purchased two expensive 15,000 RPM SCA drives recently to work as backups for our RAID arrays on our Linux servers. Called Seagate *FIRST* to verify compatibility, as well as with Adaptec. Then a few months later when we needed to use one to replace a failed drive, it would NOT negotiate properly, making it useless.
Hours on the phone with Seagate we FINALLY get confirmation that there is a "firmware problem" with the drives we have and we should "upgrade the firmware". We go through the crap of getting a "key" and being sent the firmware only to find that their self-booting program would not run on our servers. Their suggestion? Find some other SCSI SCA machine just lying around and try it there. WE DON'T HAVE any such machines. We asked if we could mail the expensive, useless drives to them so THEY could upgrade the firmware. The response was "you can send in the drives for exchange, but we can't guarantee the drives sent back will have the firmware you need". This is support?????
If you can't make the fucking effort to go read the article and follow the links, why should we do it for you?
However, this replacement for me was the opposite process, only worse. They also had a list of other things I had to comply with in order to get a replacement for a drive that failed when only 2 months old:
Needless to say, I wasn't happy with that. I spent some time on the phone with them, after spending two days running around town trying to find shipping materials that would comply with their asinine requirements (they stated they would void the warranty on my drive if I failed to comply with the packing requirements). Eventually I convinced the person on the phone - we'll call him Raj - to talk to his manager about the situation. Raj then was able to to get his manager to eventually approve of sending the drive first, so I would have the proper packing materials to send my drive back in.
And then when the replacement arrived, there was a copy of a note that Raj had written while on the phone with me where he described me as "extremely irate". If I ever have to deal with them again, they'll see what irate really is when it comes from me...
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Nice to see that my xmas present might suddenly die...
And it looks like Seagate is not being very helpful towards Linux users...
Climate Progress - Hell and High Water
I work at a PC repair shop where I RMA hard drives weekly. I RMA just as many Seagates as I do Western Digitals. Truth be told, Seagate has always been very friendly to us. Sure they say that you have to have the crazy packaging. I always wrapped the drive in bubble wrap, threw in some packing peanuts for good measure and taped the box up and never had a single problem. I've only sold 4 or 5 1TB+ Seagate drives so far however I've had no complaints on them. The only series of drives that I've ever had complaints on actually were a series of WD800s all made in early 2008. We had 5 come back to us dead from brand new machines within a week of the customer buying them. WD was very generous however and sent us WD1600s in return so this was no big deal. I honestly don't see why Seagate offering free data recovery and a firmware upgrade to fix the drives is so crazy. Most companies would try to ignore it, Seagate however is taking the right path here and doing what they can to fix the issue.
Western Digital went to crap a while back (personal opinion, based on professional experience)
Now Seagate appears to be going down the same path
Both are/were leading-edge drive manufacturers
So has magnetic hard-drive technology simply reached an end-stage of current magnetic and mechanical capability, and does this hasten the introduction of technologies like SSD?
The opinions expressed here are those of this individual, and may not reflect the policy or practice of the collective
Tried migrating an existing iscsi san drive from a solaris8 box to a RHEL5. Original ufs san partition was formated back in solaris8 box days. But now, after successfully installing the iscsi-initiator-utils, the damned linux box cannot correctly mount the ufs san drive. The kernel is supposed to support it. WTF? Ideas?
I just finished replacing a Seagate drive in my laptop that died on me about a month after I bought it. Glad to know my decision to never buy another Seagate hard drive came at such a good time. Probably saved myself a lot of headache by paying the extra money for a more reliable product
If only wisdom could come without experience. Then I'd still have all my data. Thanks, Seagate.
It really seems like these businesses don't know how to make reliable hardware anymore: with this recent Seagate fiasco, Microsoft's laughable Zune Day of Death as well as their XBox red ring of death problem, Apple's (or I think Samsung's...) battery recall problem, and the capacitor theft of a few years back, and who knows what else I'm forgetting. It really seems like hardware is much more unreliable than years ago.
Of the list of common problems I've mentioned, I know of at least 1 person who has suffered them. And the fact that such things are so common makes me wonder if quality is really going down the toilet.
...but I'm definitely frustrated to have not one but TWO Barracuda 7200.11 drives fail. The first was DOA, and the RMA'd replacement just failed after only a few weeks. I've heard rumors that Seagate is returning different drives to customers. Like, larger ones. I'll wait and see.
I don't understand why manufacturer's keep insisting on writing the apps for Windows or DOS, with the growing trend to use these drives in other systems.
I use Supermicro systems in my datacenter, and the coolest thing is, all of their flash utils, and CDROM discs boot FreeDOS. This alleviates the problem that you just might not be running Windows on your server. I wish all manufacturers would get the hint.
-- If we don't stand up for our rights, now, there will be no right to stand up for them later.
My understanding (so far) is that it only affects the 1.5TB drive, not the 1TB ones. (I have a 1.5TB drive, the flash procedure doesn't suit me and the retailer are offering to replace it with a 1TB - which Seagate were saying aren't affected - this was a week or two though).
I use Friend/Foe + mod-point modifiers as a karma/reputation system.
I tried getting through their contact page. It was incredibly frustrating, and they won't even let you contact them unless you agree to some ridiculous terms absolving them from anything and everything, allowing them to email you whenever they want, stuff like that, in order to signup for an account.
Google's a little more helpful. This page at least might be kinda sorta related: http://www.seagate.com/www/en-us/support/downloads/other_downloads/cuda-fw
Then I tried to search for some of the terms in the title of the page (eg. "SD14") and it couldn't find any pages. That's some search function you've got there, Seagate -- it isn't by any chance hooked up to an empty database is it? Did you by chance have it on a 7200.11 drive?
smartctl -i /dev/sdb
will give you all the info you need.
Ever since I first read about this I was just glad I had the older 1 TB version but apparently my three drives are affected as well. I hadn't noticed any problems though. However, I do have mine in Linux Software RAID 5 and only access them over NFS so I wonder if that would mask any issues?
Here they are as identified by the SeaTools software:
http://cupcakecarnival.net/gallery/main.php/v/Computers/Seagate_ST31000340AS/SeaTools_freedos.jpg.html
I have opened a ticket to get the new firwmare and am awaiting response.
They mentioned Barracuda 7200.11 which I have. I don't have 1 TB. Are smaller sizes affected? None of the links said so.
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
I can certainly relate to that issue on the older Dell drive array sub-systems. It seems certain versions of the hard drives will only work in the disk array. So I had to call up Dell and specifically told them it has to be a Fujitsu drive with certain firmware for the array to properly initialize the drive.
Of course Dell sent us the wrong drive and it didn't work. Took a couple of re-tries for Dell to send us the right drive.
This is after we updated the firmware on the SCSI drive enclosure and PERC4 cards suggested by Dell.
Update the firmware my ass. Sheesh
Whatever happened to "If it aint broken..don't screw with it?"
Lucky their EMC2 products don't have this problem as I've replaced a couple of dozen Fibre Channel 300Gig drives of various brands and they all work just fine. Least they did something right.
I had a set of Western digitial bought at the same time but put in unrelated computers that all failed within days of each other. Never bough another western digital in the last ten years. But now from what I read they have a good rep.
My last drive was a refurbed Seagate 750GB. died after about 30 days. Vendor replaced it. then it died again. Seagate replaced it. Died again.
So now Seagate is on my shit list. My next drive however is going to be a western digital as they seem to be very quiet compared to the seagates these days.
Some drink at the fountain of knowledge. Others just gargle.
Bought four 320GB Seagate Drives last year....
Two are already dead.
Going with WD 1TB drives for now.
And, of course, the Seagate referenced page says: "This can be done in Windows - it's easy! Download and run, or simply run as is, the Seagate Drive Detect software program." No mention of Linux, MacOS, Solaris, or BSD. So I guess there is an implied "If you are not using Windows - it's hard!".
Yeah, they should totally support an OS that has less than 1% market share. You forgot to add Amiga to that list. Of course, even if they did, someone here would be bitching that the tool wasn't open source.
hdparm -I /dev/sda | grep -A 2 Model
That gives you Model, Serial Number and Firmware version.
Gate.
Actually, yes you can. And if you don't, these sorts of disasters happen. Needless to say, this is not a good time for Seagate to be having reliability problems with their product line.
yes, yes it does
I purchased 2 Seagate Barracuda 1TB ST31000304AS Aug 27/08. One failed 3 days ago taking 800 GB with it. Given type of failure, their i365 Site is saying it will cost me $399 to $1700 just to recover. No talk about them trying to recover at their cost. Also, fine print says replacement drive could be a re-manufactured. Needless to say, no more Seagates for me
I gave up on WD and Seagate/Maxtor quite a while ago.
Now running on 3.5TB of Samsung drives, a mix of HD103UJ 1TB and HD501LJ 500GB drives.
Quiet, fast and (to date at least) very reliable.
Barbara Felden claims prior art on the flip phone, sues Motorola, Nokia.
I agree. And yes I own two Seagates and I've also owned IBMs as well so I'm familiar with HD failure. My issue isn't so much the failure although the "death without warning" isn't reassuring. The way Seagate handled the matter is why I question wither people can ever trust them again. Hardware can be replaced. Trust not so easily.
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
I think I have the worst luck right now. I am a huge Seagate fan, but this shit has gone too far. I have been dying to set this ZFS system for months now, and I'm now dealing with this crap.
I bought FOUR of these drives from DirectCanada.com. The first two drives was two weeks prior to the first Slashdot story about these drives. The second batch I ordered was just last week, and now this story shows up.
What a fucking coincidence.
I plug all of these drives in (2 different firmwares right now fyi) and two of them failed the Seatools tests, while the other two drives greeted me with the click of death upon first boot-up.
It costs me 11$ to ship these drives back to Seagate. In total, I am spending an additional 44$ on top of the purchase price of these drives to send these paperweights back to the manufacturer.
Seagate better get their shit together or else they're losing my business for good. I don't have TIME to call or email them, asking for friggin' firmware updates! Just post them on the site already.
If they could just cover the RMA shipping costs...
That's a lot more than they're required to do and more than most companies would do.
Considering the mounting evidence, stalling, and potential class-action lawsuit. I'd say your "required to do" would have quickly turned into, "we have to".
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
Believe it or not, some people actually adopt them early because they need the space for non-pr0n (especially in RAID5 setups).
Never mind - in another thread someone pointed out to me there are 2 different bugs. One of which, at least, is affecting 1TB drives (the bricking bug).
I use Friend/Foe + mod-point modifiers as a karma/reputation system.
Wait a minute. You purchased two drives for use in a critical application and they had to work with a particular controller you already owned - and you didn't test the configuration when you received the units but instead waited months and until the need was critical??? Geez, I wouldn't be broadcasting that around too loudly if I were you.
The tyrant will always find a pretext for his tyranny - Aesop
My philosophy with this is always buy the extra drive/s when building the RAID/whatever. You know they are coming from the same source at the time and it will be a bitch finding them 2 years later even if the price has come down for that drive. You can just throw them in a drawer and put a sticky note on the drive (bag) saying "do not use; spare drive for nutsak/server", and put one on the drive bay on the machine that says, "spare in phil's left desk drawer". Then forget about it.
Really? Not I2C or JTAG or some other standard? Just RS-232?
I mean, if I read you correctly, I can plug a sufficiently-modern hard drive into a +5/+12V power supply, and speak plain-old RS-232 to it? Using nothing but a few wires (and maybe a MAX232C to get it to work with TTL voltage levels) I can talk to a hard drive using a 20-year-old dumb terminal?
It's been a long time since I thought of hard drives as anything other than "places where host computers store stuff", but it's only tonight that I've realized that of course there's a full-fledged "computer" (for lack of a better word) on every hard drive... Anyways, long story short...
That sounds like fun.
Got a picture of what that "little external interface board" looks like, and where the relevant pins on the controller board are? Or is it blindingly obvious just from looking at the controller board of the drive?
Seriously, it's the middle of the night but that sounds like a fun weekend project.
A few years ago, I put together yet another machine with a RAID array, it had 8 brand-new Seagate drives.
Within a month, one drive had died. Within the next month, two more of the drives had died. Guess what Seagate replaced them with? Refurbs.
Of the three refurbs, two died within two weeks. And another of the original.
I called Seagate, and asked them to replace the entire lot, as they were obviously from a bum lot. They agreed, and I was happy... until they sent me 8 more REFURBS.
Just for fun, I put them in a machine and gave it light duty. Within a month, FOUR of them had died.
At that point, I decided to never buy Seagate again. Every manufacturer can (and does) have bad lots, but giving me refurbs was particularly low-class.
Now, for SATA, I buy only WD RE or RE2 drives, and in buying them by the dozens for three years to run in RAID arrays, my failure rate has been lower than with any other IDE/SATA drives, I've only lost one or two. They're good enough that I install them on all of the desktops for my clients as well, and have yet to have one fail in that usage.
I can't comment on WD's service, as I haven't had a chance to test it - and I like that.
Oh, you're not stuck, you're just unable to let go of the onion rings.
I have a drive that needs a firmware upgrade, but I don't have any available Windows PCs to attach it to. Do you guys know whether the upgrade can be applied using Linux? If so, where can I find the Linux firmware upgrade?
There are many comments attached to this story with anecdotes of how every brand has had good and bad runs with their products.
Spinning platters are not going to to last for ever.
I've been holding off purchasing some new computers for a remote industrial application until solid state drives are widely available and a bit cheaper as I am under the impression that they could potentially last a long time.
Our storage requirements are small but reliability is key! I can't imaging we'll run into the write-limit either.
I'm hoping to install these computers and close the (physical) door on them for 10-15 years.
Will solid state drives have a longer lifespan than convention spinning platters?
I'm also going to go for remote KVM and reundant power supplies. What other hardware features would you look for? Is fanless an option? I'd love to have no moving parts in there at all.
Yup, just RS-232 with TTL matching circuitry. A little board like this one does just fine, although you do have to give the board +5VDC and jumper TX/RX to the appropriate pins on the drive. For the 7200.11s, there is a block of four pins adjacent to the SATA data connector on the back of the drive - the pin closest to the SATA connector is RX, and the one right next to it is TX. Note that this will just give you a terminal interface to the controller, as opposed to letting you actually use the drive for its intended purpose.
:-) I've not actually tinkered with my drives in such a manner, but it seems a few folks have, with good results.
Note - if you blow your drive up, it's all on you.
Please stand clear of the doors, por favor mantenganse alejado de las puertas
For $129 shipped I thought I'd take my chances on the 1.5 terabyte drive. I couldn't get the firmware update from Seagate in any timely fashion so I went with the torrent. The drive is flashed and has been purring away for a couple of weeks now, no excessive noise, no freezing up, no problems. I was prepared for the worst when I ordered it and have been pleasantly surprised so far. The fact that Seagate is aware of the issue and willing to do whatever it takes to keep the drives rolling all the way up to free data recovery is enough for me.
I have a Seagate Barracuda 750g in this computer now. It's probably got to be the WORST drive I've ever had..
My previous drive was a WD that had a 16mb cache, designed for RAID, blah blah. It freaking rocked speedwise, until it barfed and made it so that I could not access the data any longer. So not trusting WD any more, I bought Seagate. Wow, what a MISTAKE!!! Windows 7 reports a WIM score of 2.0 on it.
From HDTune
10.0mb/sec minimum
66.4mb/sec maximim
58.4mb/sec average
13.5ms Access Time
110.1 Burst
= Grow a brain...
y philosophy with this is always buy the extra drive/s when building the RAID/whatever.
The problem with that is some manager droid will see "6-drive array" on an inventory and see 8 drives on the purchase order for the 6 drive array. Said manager droid will snafu spare drives for some other application when you're not looking.
Failing that some bean counter will see 8 drives on the purchase order for a 6 drive array and request that you reduce the cost by removing all the "spare parts" because they can be ordered only if they are needed...
Don't believe me, try ordering more than you need and see if you get them or if they aren't snafu'd by a manager bot.
I drink to make other people interesting!
Yes, smaller sizes are affected. Sorry, I don't have a link for you, but I remember reading it. All 7200.11 models are bad. Note that I've done the reading on this because the 500GB Seagate 7200.11 in my girlfriend's machine just failed a week ago.
I bought two of the Seagate 1.5 TB drives. I put them through the standard 7-day torture test pre-deployment before they went into production, which revealed a problem. A quick google search revealed that I wasn't the only one.
Seagate support emailed me a firmware update that completely solved the problem. (knock on wood) They then easily passed the next round of torture test, and have been in production ever since as part of a D2D backup storage array.
What parent poster says is true - ALL manufacturers have the occasional bad seed. In my experience, hard drive failures are usually due to mfg defects, much less so due to "wearing out". I have the most problems within the first month of purchase, or 5 years later, but I have plenty of drives from about 1 GB on up that have seen so many years of heavy, continuous use that their size is no longer relevant, but still work beautifully.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
Seagate may be making the "right moves" now, but IMHO, they should have been more proactive, before this many defective drives were out "in the wild".
The 1.5TB Seagates have been drives to avoid for Apple Mac Pro owners since day 1, since they have all manner of issues in them. (Web sites like xlr8yourmac.com have advised people not to use them due to firmware issues.)
It sounds like in both the case of the 1.5TB and now the troublesome model of the 1TB drive, Seagate was pretty slow to respond to complaints. I've read a number of stories of people who had arrays of 3 or 4 of these new drives fail in a matter of only a couple months, only to send them back for warranty replacements that died quickly too.
A little better QA testing before initial sale seems like it should have caught these problems.
Some people really do have x86 servers that aren't Windows... Being able to build a DOS "disk" for flashing purposes on such "1%" machines (because it's not feasible to put Windows on) is extremely important in such scenarios and doesn't seem unreasonable.
There really is a not-insignificant chunk of other stuff out there.
But (and this is the crucial difference between you and the OP), you bought the drives from Dell (who presumably manufactured the server which they were to be fitted to) on the express instruction that they had to fit a particular server model.
It's therefore Dell's problem to get it right and the drives can keep on going back until they do.
Gathering model and serial numbers from Linux can easily be done using hdparm or smartctl.
I have several FreeAgent Desktop drives running at a customer. Does the Firmware update even work through USB?
I also happen to have purchased an eSATA drives for my (older) subnotebook. It neither has eSATA nor floppy nor cd-rom. I equipped it with a PC-Card (one single slot) eSATA adaptor. And it only runs Linux. All my other machines don't have SATA. How am I supposed to run the testing app, let alone the update app?
absolutely fantastic drives! very reliable indeed. i also like WD flavoured drives too but Spinpoints are definitely rock as far as HDD's go.
You would wonder where you can find RS232. The fact that RS232 is still one of the standard ports available on nearly ALL microcontrollers makes it quite popular. Still a lot of scientific instruments, even upgraded versions of older instruments, contain RS232 (mostly to be 100% compatible.....) Although for something like HDs i would not have expected it.
If you can't make the fucking effort to go read the article and follow the links, why should we do it for you?
Why? Because this is Slashdot, dumbass.
Answer TFQ.
So make the order for an 8-drive array with two drives in 'offline mode'.
I am TheRaven on Soylent News
...while checking hard drives:
"Sea gate... Sea gate nicht... Sea gate... Sea gate nicht..."
(Alright, I'll get me coat...)
np: The Orb - Once More (Bedrock Edit 2) (Cydonia Versions)
"I'm not anti-anything, I'm anti-everything, it fits better." - Sole
This is just freakin' cool.
Fry's isn't open at this hour, but I built one of those a few years ago and dug it out of my parts box, and yes, you can talk to the bare metal of the drive this way. (Failing that, I found a schematic that does the same thing with a 74LS14, seeing as how most serial ports can speak TTL now by default!)
Anyways, looks like there are commands for diagnostics, memory peeking/poking, raw sector reads/writes, the works. 38400 8N1, or 9600 8N1. (Googling around, looks like some Samsung drives with Marvell "CPU"s like 57600 8N1)
Got the T> prompt, level "T" meaning "T"ests, and you can "Q"uery it. There appears to be self-help, pressing "?".
At level C (F3 C> prompt, "F3" refers to the architecture, "C" refers to the level), you can get a list of all commands with "Q", for Query.
^V echoes commands on, useful.
^C resets/spinsdown the drive.
More googling...
Looks like there are two groups of people: One group of Eastern European hackers intent on protecting their commercial ability to do data recovery -- there's an expensive but slick GUI wrapper around some of the common fixes, and everyone in Eastern Europe (I wound up in a Russian and a Polish forum) seems friendly enough to talk about hacking the terminal interface, but (obviously) doesn't want to give a cookbook answer. (I do kinda respect the "Read between the lines of our hints and you'll eventually figure it out!" attitude, though. :)
For instance, the tail end of this video (which is basically the "cookbook" answer for the commercial product, and provides a lot of hints at the DIY solution -- the video doesn't show the commands being sent via the terminal window, as I guess that'd make it too easy :)... but the status window of the commercial tool, plus the status bits at the bottom of the GUI screen, makes it clear what's going on. Specificlaly, the status log shows the results of commands that have arguments that look an awful lot like the ones that the drive's self-help output, like this one:
Level T m: Rev 0001.0000, Flash, FormatPartition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertifyTrkRewrit es],[ValidKey]
The video also shows some drive (or drive board?) powering on/off activity. These appear to be the level 2 commands "U" (SpinUpDrive), "Z" (SpinDownDrive), and/or the level 1 command "e" (SpinDownAndResetDrive. And/or some other commands that I haven't figured out, to power down the drive so that the PCB can be removed for the BSY fix, then power it back up again after the PCB's plugged back into the "drive" half of the drive.
Not sure if those are the same as the power on/off things the video is showing, or if there are other commands to control power. Also not sure about things like SmartControl, (level 1 "N"), but maybe that's how to clear things like the SMART list (/1 to get to level 1, then N1 to clear it?)
There also appears to be a fairly active thread at msfn.org about a "Look, just hook the drive up to a serial port, and be careful not to make any typos, and remember that all the control-characters are case-sensitive" sor
It's always reassuring that when hardware manufacturers merge they manage to keep the worst of both companies.
My next batch of drives will be Samsung, the previous 2 I bought (20gb each) are still working.
haven't had a seagate since 3.2gb was the biggest on the block, but ask some place like storagereview.com, you know, a friendlier place..
Bought the NEW 3 platter seagate 1tb from Newegg. 3 out of 3 died within one week.
Though, this might be because of Newegg's TERRIBLE shipping procedure
Linux has something like a 50%+ share or more of the server market. And guess what, dude, most of those have hard drives.
And for total computers- all non-MS-Windows machines adds up to probably more than 15% of all computers. Even if you were WalMart and turned away 15% of your potential customers, you would go out of business.
>My philosophy with this is always buy the extra drive/s when building the RAID/whatever.
Of course we did that. I had lots of drives. And they got used up. Hard drive models change constantly, it wasn't long before we couldn't buy 36GB 15,000 RPM Cheetah drives anymore.
We still had a few known compatible drive spares when we ordered the untested ones. On the next drive failure our test WAS to use the new model. When it failed, I used an older spare. And since then, yet another failed (seems to happen in groups). I then when on a rampage buying identical *used* spares off Ebay/etc while we are still trying to get the newer models fixed by Seagate.
Wow. That sucks dicks.
What would be really cool is to find a way to change short-stroked drives into using the entire platter. IT would be like over-clocking your hard disk and getting more space instead of making it go faster.
When information is power, privacy is freedom.
or not to upgrade... I have a 500GB 7200.11 drive that has a history of other problems, like the 32 MB cache being disabled. Supposedly my firmware was affected by that as well yet I don't see the problem on my specific drive. So now I wonder if this "failure to start" at power-on could really affect me or not. Hard to say, maybe I haven't seen it because I rarely power off the computer.
So now I'm kind of stuck... I guess I'll install the updated firmware but I know how things typically go and it will probably break my drive or something...
They finally fixed the broken 640 GB drives which had the stall out/disappear/NCQ errors the 1.5TB's had about a month ago. Thank god. I have not seen such widespread failures across so many products since the Deskstar fiasco.
I own two of these drives, bought at the same time from the retailer and shipped to me in the same box, and one had the affected firmware, one did not. I updated the affect drives firmware to avoid any potential problem and all is well! I keep one as a internal drive for all my data and have seperate drives for OS only, then I have the other 1.5TB in a eSATA enclosure and mirror the data and copy it over to it on a weekly basis. All have been working fine for 2-3 months.
This is what happens when you do not have a proper testing regime in place.
Tisk, tisk, tisk.
Why? Simple. During the DeathStar fiasco almost a decade ago, IBM refused to acknowledge the issue. Leaving small businesses to clean up their mess and cover the costs of replacing prematurely failed drives and lost customer data.
Seagate, on the other hand, has readily acknowledged the issue and pledged to replace drives and pay for possible data recovery?
That's absolutely amazing. No vendor is perfect, shit like this happens occasionally. The true test of a good supplier, vendor, manufacturer, etc. is not what they do when everything's going right. It's what they do when it goes all wrong.
Does anyone has a plain e-mail address of Seagate to contact to for the firmware and instructions?
Their page does state about contacting them via e-mail, but no e-mail address is given (http://www.seagate.com/www/en-us/about/contact_us/ http://www.seagate.com/www/en-us/about/contact_us/world_wide_contacts/contact-techsupport-emea).
Having experienced this several times makes me wonder are manufactures purposely making their newer drives incompatible with older drive arrays in hopes the customer would simply say, "Screw it..just buy a new drive enclosure and buncha drives with some spares"? That would leave a sour taste in my mouth if I ever have to go that route.
I was lucky to have older spares in storage that I was able to use before we upgraded them to EMC2 products. I left the company some time ago so don't know if maybe 5 years from now will they have the same issues with the EMC2?
Had the same results with a batch of Samsung drives; received a box of 15 whereof 6 died short after...
Only had 2 Western Digital disks and 3 IBM disks crashed in my life .. and I've really had many of these brands the last 15 years!
I once had the hint to watch the manufacturer dates ; if the dates are in the holiday period June-August the batch could be more buggy/failing than a batch outside the holiday stocks... I don't know if this hint is true but I sure regard all manufacturers dates from now on...
--- I am known for the ones who want to find me on the net. Is that a privacy risk or a privilege? One might wonder..
The problem is BIOS no detect after a few months of usage (typically 3 months)
I've got some other Maxtor, Quantum and Seagate drives having the exact same problem, not being able to be detected while the data is intact on the disk.
These disks are years old; which would mean this bug is still being fixed?
Until today, Segate denied there is problem with SD15 1TB drive. SD15 is still the newest firmware.
Same with those disks, they never knew anything .. nothing is wrong .. it's always the hardware of the customer ;)
These problems are so adjadent with the problems I've already had years ago; what gives?
--- I am known for the ones who want to find me on the net. Is that a privacy risk or a privilege? One might wonder..
Do mind flash can fail too; while a disk could loose a bit of it's information or crash far out; memory can also get corrupted and bad after writing a couple of hunderd-thousand times. For an industrial machine this could be important; unless working with solid state raids which might drop the speed a bit.
I've had CF cards fail after a time; while a disk was reoverable almost all the times; this solid state memory was a hell to recover any of my data...
Raids were a good way to go with disks; there are plentoria of cards available allowing raid between 2/3 solid state devices... maybe the new future?
--- I am known for the ones who want to find me on the net. Is that a privacy risk or a privilege? One might wonder..
Had the same experiences with Seagate; they failed swapping their harddrives with FIXED versions.
To my opinion, such should not be allowed to sell bad, malfunctioning products.
Know your product is faulty? Why the heck release refurbs? Ain't these companies CARING about DATA STORAGE or only caring about the paper wads...
End result .. company gets sale .. customer gets screwed over and over...
--- I am known for the ones who want to find me on the net. Is that a privacy risk or a privilege? One might wonder..
Let's hope it's just as easy to update the firmware. Those of us who don't have x86 machines might have an issue, from what other commenters have said. Not to mention that little OS we like to refer to as OS X. :)
I was able to determine on my PPC Mac running Leopard that I did indeed have one of the drives in question. However, reading more about the firmware update programs that are increasingly windows-only among manufacturers, I certainly hope that Seagate doen't drink the Microsoft kool-aid.
It's the Stay-Puft Marshmallow Man.
I bought a Seagate Barracuda 320 GB drive to use a my main System drive about a year ago. It promptly failed about an hour after installing XP, and before I could put any important data on it. I took it back and exchanged for a Western Digital Caviar 320 GB drive. I still use that drive today. If you need a HDD, go with WD.
This morning I received an e-mail from my fileserver's RAID controller with this:
Sat, 17 Jan 2009 08:12:53 Pacific Standard Time:
[rr232x]: An error occured on the disk at 'ST3320620AS-xxxxxxxx' at Controller1-Channel1.
Sat, 17 Jan 2009 08:12:55 Pacific Standard Time:
[rr232x]: Successfully repaired bad sector on disk 'ST3320620AS-xxxxxxxx' at Controller1-Channel1: LBA 0x21f53300 sectors 0x37 .
It's a RAID5 5 disk 320GB drive array with Seagate drives. Right up to now all drives showed zero disks errors. I had to replace drive #3 a few months ago as it was showing up excessive bad sectors even though the controller didn't fail the drive. The drive would generate maybe 25 bad sectors a month and didn't replace it until it reached close to 90 and it took few months to get that high.
I know bad sectors happen on drives and that's life but when you start seeing that number climb eventually it'll fail.
I am not too worried at the moment as I do make constant backups and it is a RAID5. I just pray I don't lose two drives at once then I'd be like..great..time to rebuild the array from backups.
I haven't lost faith in Seagate as the drive in question is an older drive that I've had for about 3 years without problems.
I'd take issue with "readily". After reading about the drive's increasingly more common failure and Seagate refusing to acknowledge it was a problem, I think that Seagate was pressured (finally) into admitting it, and have been nothing but obfuscating regarding the subject until now.
:) Their data recovery sounds like (wording wise) you have to be a business to be qualified for it. But that's just how I read it. We'll see. I am not willing to let Seagate get a free pass... this isn't over yet. :)
At least they finally got bullied into admitting it. The same tactic didn't work for IBM, though.
It's the Stay-Puft Marshmallow Man.
Use the command:
smartctl -a /dev/sdX
(X is the drive number)
This will give you a detailed report including the drive's make, model, serial number, firmware revision, and S.M.A.R.T. status values. It will also show the drive's error log if present.
Other methods include examining the kernel boot messages (dmesg is your friend), or using hdparm.
Oh, no! You have walked into the slavering fangs of a lurking grue!
...but then, I've never had a problem with any other brand of drive either. I've used WD, Maxtor, and Seagate. A lot of it is just the luck of the draw. Yeah, some are notoriously bad, and some have a batch of notoriously bad drives (ie. deskstar drive, already mentioned many times in the comments here).
I did work at a mom&pop computer repair shop for about a year (07/06 - 08/07) where we used exclusively Seagate drives, and I'd guess we had about a 1% failure rate in that year. Don't know for sure, but I do know it wasn't very many.
My personal main drives are 300GB and 320GB (both IDE) Seagate drives, have worked well for 1-2 years now.
There is no -1 Disagree mod. Slashdot.org/faq defines mod options. USE IT.
i've replaced my seagate barracuda IDE drives atleast 6 times within 1 year . Whenever it gets spoilt ie within 3 months of heavy usage i go to the warranty agent or reseller and get the replacement within 5 days. Here in India the amount of people for replacement there is so huge that is a queue 50 gets formed on average for an hour . The drives are pathetic. I had a drive fail within a week of replacement.
When the summer comes the drive failure rate is much much higher.
SSD's please.
Having followed the 1.5TB NCQ/Cache Flush issue, it seemed to be necessary to boot from some kind of DOS device (floppy, CD-Rom, USB memory stick). That's not terrible, considering that it might well be difficult or impossible to flash the firmware of a drive that's in use, and have it come back without at least a warm reboot or reset.
I guess Mac owners might have a bit more trouble, unless they can boot DOS natively from EFI. Good job they're using x86 CPUs these days, mind...
Some of us are old enough to remember the mid-nineties, when, for example, *every* *single* ISP in Chicago dumped all their brand-new early Seagate Barracudas due to hardware failures. I, personally, was working for a major telecom, and was administering a Sun server with a box of external drives - four Seagate Barracudas, and had *five* hardware failures - three drives giving hardware error messages in /var/adm/messages, and Sun replaced them... and one they replaced *twice*.
I, personally, haven't bought Seagate since. Seems like Seagate's more interested in "get them out the door" than quality, when their flagship product has so many problems.
mark
Proven technology. Sure, it's not so fast, but it is human readable.
Every disk and tape drive I've come to know well has a 3-wire TTL level RS232 port for diagnostics and manufacturing. But the specs for the ports are usually NDA level confidential.
thegodmovie.com - watch it
We'll see how it pans out, but at least they're off to a better start. As far as the data recovery, I'm sure it only applies to data that can be shown to result in money loss. Unfortunately, those photos of Uncle Joe getting drunk and making a fool of himself at our cousins wedding is not worth anything to anyone but our own sentimentality.
I bought a 500 GB Seagate Barracuda about three months ago with plans to install it. My system drive is five years old and on the small side - and I wanted more storage. I got lazy and just did not do the swap out. Then I thought I would get a video card and power supply upgrade as well since prices are pretty good now. So I ordered the stuff from Newegg. Figured I would do the crap all at once. So the Seagate has been sitting on my desk in its antistatic bag for an age.
Then I see that there is a Seagate issue story on Slashdot. Okay. It would be just my luck. So I hit the link and check it out. And lo and behold my brand new drive is one of the blighted models. I have put in a ticket on their customer service system for the needed firmware -- it seems the flaw varies according to the exact serial number. No answer yet. But a look at their forum board shows that the firmware is not even out yet. Next Tuesday say the posters. Sure am glad this drive is serenely gathering dust on my desktop instead of fragging data in my desktop. Seagate has a good rep for doing no hassle returns. And I have had one good experience with them on a dinking drive. The saga continues. But as of now it appears that the promised fix is... promised.
So sometimes it pays to be lazy.
"No fear. No envy. No meanness." Liam Clancy
all I can say is that out of the last 8 hard drives I've installed 3 WD, 4 Seagate, and 1 Maxtor, I've had five drive failures 2 seagate, 2 wd, and the maxtor. Kind of hard to backup data when even my backup drives fail within days of the primaries. Is it just me or has the rate of failures for all manufactures been increasing lately? All of the hd's I've purchased over a year and a half ago are running fine regardless of the manufacturer.
You sir, are a Grade A drooling zealot. A Windows one at that.
Damn! How long did your girlfriend's model last?
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
MOD PARENT UP, I sent him that drive!
http://thepiratebay.org/torrent/4627627/Seagate_1.5TB_ST31500341AS_Firmware_Update
The most reliable drive I had was a Quantum Bigfoot. One of those monster 5.25 HDDs made in the early 90s. The reliability may have been because of the slow speed. It came out of a Compaq returned to an Office Max and sat on a shelf for months. When I started work there they said I could have it. I wanted the magnets out of it. It bounced around in a backpack and was hauled from class to class for several months. A group of friends and I put together a Linux server on the cheap and I offered it up if there was any possibility it was still working. That drive powered our server for 4 years before being replaced with a new drive and used as a secondary drive. The primary drive failed 2 years later and the entire server was scrapped. I'm going to have to see if that Bigfoot is still around somewhere and see if it still runs.
When I started looking recently at high capacity drives, I simply viewed the number of negative reports on Seagate 1 and 1.5 terabyte drives on Newegg. There was no doubt there were problems with these drives. And it's not merely a matter of capacity because Samsung, Hitachi and other drive manufacturers did not receive so many negative reviews for their 1TB drives.
Clearly Seagate, which used to have a rep for very good drives, let themselves drop the ball when they went to TB and higher drivers.
Note that as far as I know, Seagate drives under 1TB don't have any particular problems. It's the 1TB and 1.5TB models that are problematic.
Once again the IT industry let itself push technology beyond where they could make it reliable. This is a chronic, endemic problem with the industry and the fault lies squarely with management (although when it comes to software, the engineers are frequently equally to blame.)
Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
heheh. Good point. Well, I'll give them this much, they aren't claiming to only use their drive 6 hours a day. :) I couldn't believe that shit coming from IBM. Yeah, right, guys. I should hear from them by early next week.
It's the Stay-Puft Marshmallow Man.
the nice thing about serial ports (they aren't really RS232 until you add the level shifter) is they are generally very simple to work with (in terms of what software you need on the microcontroller). So it is very common to use the serial port on a microcontroller for a diagnostic/configuration interface.
note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
For Linux Use /dev/sdd1 /dev/sdb
hdparm -I
OR
smartctl --info -d ata
For FreeBSD Use /dev/ad8
smartctl --info
rjb
Can't believe this -- had a 1T fail yesturday (from SMART=healthy to dead) and a 2nd 750 come up with multiple read errors (though not dead -- just multiple read errors). Oddly -- I was planning to take it back to the retailer, since the drive model number doesn't match the external box (external box is retail, drive label says it is OEM only. Model # doesn't match but serial # does!). Never seen such oddness, but it was a Fry's open box, so they said they'd replace it. Six month old drive.
Head go bad? Move the media to another drive. In seconds.
You mean, roughly 86400 seconds?
Please wait while we find an agent to assist you...
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
All agents are currently busy. Please stand by.
An agent will be with you in a moment. Thank you for your patience.
The next available Agent will be with you in a moment.
Hello. How may I help you?
Dennis: Hi, apparently I need a new firmware version for my 500GB SATA drive
Dennis: Model number: ST3500320AS
Serial number: xxxxxxxxx
Firmware revision: SD15
Christopher H.: I am sorry we do not support firmware under the 1.5Tb drives over chat please call in at 800 732-4283 or try our email at discsupport@seagate.com
Dennis: eh... I am resident in Israel, and I do not appreciate calling an international number. I also made a support ticket yesterday, and have not yet received any response. Is there any sane reason whatsoever as of why your company cannot simply provide a public download link?
Christopher H.: I am sorry the email can take 3 to 5 days
Dennis: And the reason you cannot provide the required firmware update over chat for drives with capacities UNDER 1.5TB? I do not want to lose 500GB of data... this is also my system drive.
Dennis: well.. not 500GB but 436GB still
Thank you for using Seagate products. You may now close this window.
Your session has ended. You may now close this window.
It was about 4 months old when it started showing problems. Within a month, it was totally dead.
Damn. :( Now, I am worried about mine! And Seagate is not replying to people! Ugh.
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
Just found it on the Seagate website. However, no md5 checksums provided for the ISO. Hope that the Flash utility has some internal checksumming...
I do happen to have a MAX3232-based RS232 level converter, I am conversant in terminal emulators, and I do happen to have some 7200.11 Barracuda's in the field and in stock.
Any pointers to the 7200.11 RS232 console location/pinout/baud ?
What's the statistical risk of a Barracuda 7200.11 not coming back up after a power cycle? Any external factors that increase the risk?
Hmm, found some pinout using the "master/slave jumper block", but alas, that jumper bank isn't there anymore, on the recent SATA drives.
Also, based on the command line instructions that are floating around the web, there's no straightforward description of how to "reset the BSY status", other than perhaps by invoking firmware reset, which seems equal to drive power-cycle = hardly any help...
So if a drive goes terminally BSY at power up, I have to send it back to Seagate :-/ Which is the right thing to do anyway with such a symptom - a nicely serious and reproducible problem :-)
You talk to it at 38400 8N1. Here's the Seagate 7200.11 fix, including pinouts and every command required to solve both the BSY problem and the LBA 0 problem.
No idea, but now that there's a DIY fix, people can actually start trying to replicate the bug. w00t!
one word: smartmontools
'twas able to pull the drive's model #, serial # and firmware without needing to reboot my (linux) fileserver.
Thanks again. Well I downloaded the ISO and noted along with you that there was no checksum.(Put it in my survey for all the good it will do.)
Did not flash the drive. Sort of wanted to wait until the smoke cleared. Really appreciate your updates. My power supply has not arrived in any case and I was going to bundle the work. I will wait for a good fix -- if they can even manage. It pays to be lazy. I am thinking this may be a total design cluster freak and I will have RMA the drive.
"No fear. No envy. No meanness." Liam Clancy
JFTR
External USB drives, linux 2.4:
cat /proc/scsi/usb-storage*/*
Gives the serial number (Which may or may not be the actual drive number) /proc/scsi/scsi reports the "revision" - um..?) smartctl -a /dev/sda can read the serial however.
Serial number is the one that is reported to USB/SCSI software
Matches the number on the Basics box, and a Seagate owner told me it looks like a Seagate serial number.
There's probably another way for internal drives, but I am not seeing one right now (cat
Oh, and can someone tell me whether the data is still there after this magical RS232 F3> hacking? They talk of "formatting" and they accidentally their English.
Is the data
* there again unchanged
* overwritten
* partially overwritten
* there but you need to do some MBR magic
thanks.
Will using this firmware update on a raid break the array? I have one of these 1.5TB drives and another 320GB drive in one system and a raid0 of two 500GB drives on another. I don't want to lose my entire install due to an update.
I just bought 3 of these to build a terabyte raid. It was a good deal on newegg.com. Seagate!! Thought this company was the gold standard before. I cannot build a server with these disks knowing this in advance. Seagate!!!!!!!!! Maybe Toshiba still makes good disks?.. :(