Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[Agent24]

---

Lacosta wrote:

1. lol im using NTFS partition.

and this hd work fine in first day.

and like all 16 pages here, the HD fail after some Hours/days of use

and that screen was taken when i tried to run SEAGATE DOS TOOLS.

and official seagete software dont recognise the hd

---

Would love to know what hardware you do have - motherboard? and if you are using an expansion SATA card or not.

[Cantbecanit]

Now yer seeing it Agent, if you look at the screenshot he's not booting the drive, he's booting the DVD according to the bios, all you can see is Kernal 32 Fat, no mention of NTFS at all, either the mission is beyond him or he's lying about what he's done, can you see any mention in that screen of a 2TB drive, I can't, WD postboys who have a few spare moments to come here and post up a problem that doesn't exist, or a so old PC it's like asking a Ford T to do the quarter in 15 seconds.

Mate, buy a PC that can run this drive, your antique simply isn't up to it, had you had a 2007 onwards PC you could blame the drive, you don't and your expectation is too high imo, so perhaps Seagate should print a warning on the box to say....THIS IS A MODERN PRODUCT DO NOT EXPECT IT TO RUN WITH AN OLD PC, THAT'S WHY BILLY BOY FITTED WINDOWS WITH COMPATABILITY MODE, not even this works with some old programs, I wonder why?

[Agent24]

---

Cantbecanit wrote:

Now yer seeing it Agent, if you look at the screenshot he's not booting the drive, he's booting the DVD according to the bios, all you can see is Kernal 32 Fat, no mention of NTFS at all, either the mission is beyond him or he's lying about what he's done, can you see any mention in that screen of a 2TB drive, I can't, WD postboys who have a few spare moments to come here and post up a problem that doesn't exist, or a so old PC it's like asking a Ford T to do the quarter in 15 seconds.

Mate, buy a PC that can run this drive, your antique simply isn't up to it, had you had a 2007 onwards PC you could blame the drive, you don't and your expectation is too high imo, so perhaps Seagate should print a warning on the box to say....THIS IS A MODERN PRODUCT DO NOT EXPECT IT TO RUN WITH AN OLD PC, THAT'S WHY BILLY BOY FITTED WINDOWS WITH COMPATABILITY MODE, not even this works with some old programs, I wonder why?

---

I'm not seeing anything (for now) - I simply want to know what hardware he's got so I know if that drive should work in his system or not.

Without knowing any of that I can't decide anything about what is going on with his machine.

But what you are saying sounds a bit far-fetched.

1) He never said he was booting from the HDD! He said he was trying to boot Seatools.

2) We know NOTHING about what the FAT32 in his boot error message is referring to! It could be referring to the filesystem of the media from which this program is booting, or any other number of things, and may be nothing to do with the HDD itself.

3) A PCI Device IDs listing on the POST screen proves nothing about if his HDD is detected by the BIOS or not.

4) A Ford T probably could do a quarter-mile in 15 seconds if it was retrofitted with the appropriate engine, just as a Pentium 1 should support a 2TB drive with the appropriate SATA card.

Besides, for capacity issues, HDDs are detected by the BIOS anyway, but it just can't "see" the full size.

That is why DDO software works, the BIOS doesn't have to support the full capacity of the drive!

Finally, what has software compatibility mode in Windows got to do with anything? A SATA controller and a SATA HDD are not software. It has about as much relevance is me telling you that my keyboard has orange status LEDs on it.

[Cantbecanit]

Missing the point, 2TB 2010, Pentium 2003 no Sata ports, I wonder why it isn't working?

If he's booting Seatools DOS and the drive isn't found then his Sata card must be something to do with that?

If you do the Ford T you suggest, then that is a full PC upgrade, where his drive will work because the bios HAS heard of a 2TB drive and his MB HAS Sata ports.

Software compatability, was an example that a game written for Win 95 is unlikely to play on Win 7, hence 2010 drive tring to work with 2003 PC with I suspect a $5 sata card which is probably technically 5 years old also.

Have you not seen the issues with brand new Sandybridge units and sata ports, if Intel can drop the ball on todays specs what hope is there for getting hardware that is 8 years apart to work, and in the PC world 8 years is like dog years, so you are taliking about a 90 year old trying to communicate with a 17 year old, as they have nothing in common the chat is going to be short if at all.

[Agent24]

---

Cantbecanit wrote:

Missing the point, 2TB 2010, Pentium 2003 no Sata ports, I wonder why it isn't working?

If he's booting Seatools DOS and the drive isn't found then his Sata card must be something to do with that?

If you do the Ford T you suggest, then that is a full PC upgrade, where his drive will work because the bios HAS heard of a 2TB drive and his MB HAS Sata ports.

Software compatability, was an example that a game written for Win 95 is unlikely to play on Win 7, hence 2010 drive tring to work with 2003 PC with I suspect a $5 sata card which is probably technically 5 years old also.

Have you not seen the issues with brand new Sandybridge units and sata ports, if Intel can drop the ball on todays specs what hope is there for getting hardware that is 8 years apart to work, and in the PC world 8 years is like dog years, so you are taliking about a 90 year old trying to communicate with a 17 year old, as they have nothing in common the chat is going to be short if at all.

---

If he is booting Seatools DOS and the drive isn't found then his SATA card might be the reason but there could be other reasons such as:

1) The drive is faulty

2) The cable(s) are faulty

3) The controller needs a driver loaded which Seatools does not have

Of course without knowing more about his situation this is all guesswork. That's why I'd love to see him post again and list the actual specificatons of his machine.

Also, a screenshot of the POST where the BIOS or the SATA card detects the HDDs (Or doesn't as the case may be) would also be interesting.

Sandybridge issue is a different issue though, that problem was caused by a manufacturing\design defect that meant the SATA circuitry in the southbridge chips deteriorated and failed after a few months, but before they failed, they worked OK.

[Lacosta]

oimg, how the heck u will see hd 2terabytes in screen if the bios dont recognise it?

there´s no problem about my pc. i have other 2 hds sata 2 from seagate, and they are perfects.

but this model dont recognise in bios like ALL of every body here.

my motherboard is gigabyte GA945gm-s2 with 4 satas slots.

and in FIRST day the hd was perfect!

but in second day it said GOOD BYE WORLD -.-

[Agent24]

---

Lacosta wrote:

oimg, how the heck u will see hd 2terabytes in screen if the bios dont recognise it?

there´s no problem about my pc. i have other 2 hds sata 2 from seagate, and they are perfects.

but this model dont recognise in bios like ALL of every body here.

my motherboard is gigabyte GA945gm-s2 with 4 satas slots.

and in FIRST day the hd was perfect!

but in second day it said GOOD BYE WORLD -.-

---

I was wondering if it was detected in BIOS but with perhaps 0 size as some of the faulty 7200.11s do.

In any case, your board while not supporting SATA 6Gb/s should still work, just at lower speeds. Other people on the forum have successfully used SATA 6Gb/s drives (Including the ST2000DL003) even on SATA 1.5Gb/s controllers without problem.

(Remember, SATA is designed to be backwards-forwards compatible!)

Seems strange to me that yours doesn't work.

[Cantbecanit]

@ Lacosta, now you see the importance of FULL SPECS when asking for help, I thought you were running an old PC, it now seems that you are running something circa 2008 which should be no problem with this size drive, the screenshot threw me as I didn't see it properly and it shows the Dos program rather than the actual boot page of the PC, this is why I thought the PC was a Pentium when I saw the old dates the software reports.

Now if we are to be able to help fully can you list

PSU make and Watts

If it's a slave or a master drive with O/S and which one and if you've SP'd it at all

Have you updated all drivers and bios files

Are your cables secure, and are they free of bends and kinks

Even if the drive is bad you should go here http://www.gigabyte.com/products/product-page.aspx?pid=2331#fq and have a readand get all the latest updates for it first.

It's also possible that the Dos burn is bad as well, if the CD you burned to is poor or you burned it too fast will also give you this kinda result, rule of thumb, if the disc says 16X burn it at 4X for a safe burn.

@ Agent, I was trying to highlight if boo boos can be made on current systems, then it can happen on older ones also.

Sorry for the agg, but I was under the illusion I was dealing with very old with new at the time.

AND FOR ANYONE ELSE READING, THIS IS THE LAST TIME I AM REPLYING TO ANYONE WHO DOESN'T LIST FULL SPECS WHEN ASKING FOR HELP.

[Dr.Potilas]

I was instructed to sit tight and wait for a possible solution for this matter. Anything yet? Seems like all hope is lost with this one

Is there any estimated cost for "data recovery" in this particular issue?  Have to decide if those photos are too expensive to buy back. I'm pretty pleased with Seagates way to handle this incident (you didn't pick up my sarcasm?) 

Please Seagate pimp my HDD, wait - what?

Please Seagate fix, reply or even 'meh' to this "not a problem". 

[Cantbecanit]

@ DR, I'm not sure there is actually anything wrong with them, it's been a longer time frame with this than the 7200.11 ones were, by now I would've thought a cure would be available if one was needed.

What to do next? this is a hard one, on one hand there is the warranty but that isn't going to get your data back, if it turns out the drives don't have issues and you've simply been unlucky enough to get a duff one then you will wait forever more.

Can you re-fresh me on your specs and how the drive was being used, and I'll see if it jogs any possible workaround.