• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Zenskas

Seagate Barracuda 7200.11 Troubles

1,248 posts in this topic

Well I finally received a (misinformed) reply from Seagate. For some reason they think I already have the most recent SN05 firmware. I emailed them back to let them know this is not correct. According to the label AND SeaTools for DOS (I can't run the Win version thanks to Seagate's shortsightedness on compiling a 64bit version). Now I'll have to wait again to see if they'll send me the SN05 firmware.

Something that came to mind, how many people with the BSY problem are running a RAID array and how many are using the drive as stand-alone storage / single main drive? I ask because most of the posts I've seen indicate the problems are cropping up with RAID'ed drives and that was the first thing Seagate said to do, disable RAID. Interesting...

0

Share this post


Link to post
Share on other sites
Well I finally received a (misinformed) reply from Seagate. For some reason they think I already have the most recent SN05 firmware. I emailed them back to let them know this is not correct. According to the label AND SeaTools for DOS (I can't run the Win version thanks to Seagate's shortsightedness on compiling a 64bit version). Now I'll have to wait again to see if they'll send me the SN05 firmware.

Something that came to mind, how many people with the BSY problem are running a RAID array and how many are using the drive as stand-alone storage / single main drive? I ask because most of the posts I've seen indicate the problems are cropping up with RAID'ed drives and that was the first thing Seagate said to do, disable RAID. Interesting...

In my case, it's a standalone drive.

0

Share this post


Link to post
Share on other sites

I use my own 3.3V RS232 adapter with MAX3232 (and 2 in series resistances of 1K for protection).

Other people uses 5V power supply with general purpose MAX232, ADM202, etc.

SOME RS232 ADAPTERS ON EBAY (there are a lot of RS232 converters):

1.- 3.3V or 5.0V compatible, with MAX3232

http://cgi.ebay.es/RS232-Serial-Port-To-TT...A1%7C240%3A1318

http://cgi.ebay.es/RS232-232-Serial-Port-t...A1%7C240%3A1318

http://cgi.ebay.es/RS232-Serial-Port-To-TT...A1%7C240%3A1318

http://cgi.ebay.es/MAX3232-RS232-to-TTL-mo...A1%7C240%3A1318

2.- MAX232 and 5V:

http://cgi.ebay.es/MAX232-RS232-To-TTL-Con...A1%7C240%3A1318

http://cgi.ebay.es/MAX232-RS232-Serial-to-...A1%7C240%3A1318

Good searching methods on ebay:

MAX3232

MAX232

And order by lower price first

0

Share this post


Link to post
Share on other sites

I'm using it as standalone drive. I don't think it's got to do with RAID. RAID is external to the drive, the drive just communicates with the host which may be the SATA controller or a SATA RAID controller.

Well I finally received a (misinformed) reply from Seagate. For some reason they think I already have the most recent SN05 firmware. I emailed them back to let them know this is not correct. According to the label AND SeaTools for DOS (I can't run the Win version thanks to Seagate's shortsightedness on compiling a 64bit version). Now I'll have to wait again to see if they'll send me the SN05 firmware.

Something that came to mind, how many people with the BSY problem are running a RAID array and how many are using the drive as stand-alone storage / single main drive? I ask because most of the posts I've seen indicate the problems are cropping up with RAID'ed drives and that was the first thing Seagate said to do, disable RAID. Interesting...

0

Share this post


Link to post
Share on other sites

I read interesting post today. But I don't know if this help our problem...

(first of all, I'm sorry that my poor english. ^^)

(from RAID, SCIS, SSD distribution company)

http://www.andico.co.kr/bbs/view.php?id=ad...c=asc&no=21

2009/01/07 "Important : There is 2 7200.11 series."

there is 2 version of 7200.11 series.

1. old 7200.11

2. new 7200.11 (generation 2)

Old Seagate 7200.11 (firmware SD15) has problem with RAID Card(Especially Intel IOP348 chipset).

Seagate ES.2 also had same issue. So Seagate released new firmware "AN05".

Now, ES.2 don't have firmware problem anymore.

But Seagate don't develope new firmware to fix problem for 7200.11.

They say "If you wanna RAID, you should use ES.2".

Here's problem when use old Seagate 7200.11(SD15) :

- CRC Error (Command Abort)

- HDD Missing

Model:

500GB ST3500320AS

500GB ST3500620AS

640GB ST3640630AS

640GB ST3640330AS

750GB ST3750330AS

750GB ST3750630AS

1TB ST31000640AS

1TB ST31000340AS

But Newest 7200.11 "GEN2" don't have RAID problem.

This harddisk has New "ASIC" & "Firmware"

Model:

1.5TB ST31500341AS

1TB ST31000333AS

640GB ST3640323AS

640GB ST3640623AS

320GB ST3320613AS

320GB ST3320813AS

160GB ST3160813AS

1.5TB model still has freezing problem.

Solution is that update firmware to "SD1A" or "CC1H" firmware.

SD1A/CC1H firmware don't have freezing problem.

Edited by killerB
0

Share this post


Link to post
Share on other sites
RAID is external to the drive, the drive just communicates with the host which may be the SATA controller or a SATA RAID controller.

That's partially correct. While RAID is external to the drive, it still has to do with how it communicates with the drive. I seem to remember that were some drives out there that because of their own firmware, they could not be RAID'ed. I'll look up the specific cases later, I'm at work right now and can't use too much internet time for it...

0

Share this post


Link to post
Share on other sites

I'm no HDD expert, but I think this tool is for those who have set HPA (Host Protected Area) to some large value, and then want to recover those lost space.

Unfortunately in our case, the factory size is reported as 0GB, so I don't think this tool will work... :(

But I'd really be happy if someone proves me wrong... :)

Hmm, sound promising, anyone willing to use their hdd as a guinea pig?
Anyone try this tool once the drive has been cleared of BSY and in a 0 LBA state?

http://hddguru.com/content/en/software/200...y-Restore-Tool/

Even if this does work (long shot), I'm not sure what this might do to any data on the drive.

User beware.

0

Share this post


Link to post
Share on other sites
Anyone try this tool once the drive has been cleared of BSY and in a 0 LBA state?

http://hddguru.com/content/en/software/200...y-Restore-Tool/

Even if this does work (long shot), I'm not sure what this might do to any data on the drive.

User beware.

I think that wont works.

HDD Capacity restore tools change current HPA to factory NPHA, as setmax, hdat2, taft or victoria too.

The problem is the translator that convert 28 bits CHS to 48 bits LBA.

This translator is in the Host Protected Area (HPA). In this case (ST3500320AS on x86 computers) this area is at end of the hdd (last 2113 sectors).

There are 1081856 hiddens bytes.

HPA detected: current 976771055, native 976773168

Modify HPA is a littel dangerous (HPA can pass from 48 bits to 28 bits and after that HPA of 28 bits cannot pass to 48 bits).

DiscWizard is the only tool of the manufacturer that works correctly with the translator (inside of HPA).

0

Share this post


Link to post
Share on other sites

Is there any developer or programmer here?

I want develope tools for obtain drive info and parameters through serial port.

0

Share this post


Link to post
Share on other sites

i wouldn't try this if you still want the data on the hard disk. plus another point to consider, if you run this and brick it, you might not be able to RMA the drive.... so it's double whammy.

be very very careful!!!

I'm no HDD expert, but I think this tool is for those who have set HPA (Host Protected Area) to some large value, and then want to recover those lost space.

Unfortunately in our case, the factory size is reported as 0GB, so I don't think this tool will work... :(

But I'd really be happy if someone proves me wrong... :)

Hmm, sound promising, anyone willing to use their hdd as a guinea pig?
Anyone try this tool once the drive has been cleared of BSY and in a 0 LBA state?

http://hddguru.com/content/en/software/200...y-Restore-Tool/

Even if this does work (long shot), I'm not sure what this might do to any data on the drive.

User beware.

0

Share this post


Link to post
Share on other sites

Oh hai.

I'm one more with this BSY bug (I think!)

2009 is a bad year for me, lost ALL my data in this ST31000340AS drive. Exactly in January 1st.

Anyway, I have done some job in my disk. I've removed the BSY stat and flashed the firmware to AD15. But the this isn't recognized yet. So I must clear SMART, G-List, etc etc.

The interesting part is that I have updated the firmware through an identical ST31000340AS drive. Changed logical boards and fireup the Firmware update O.O

Worked and won't destroy any data in the good hard disk.

PS: Sorry bad english, I'm exausted and english is not my native language, I'm brazilian so I speak portuguese.

0

Share this post


Link to post
Share on other sites
The interesting part is that I have updated the firmware through an identical ST31000340AS drive. Changed logical boards and fireup the Firmware update O.O

Worked and won't destroy any data in the good hard disk.

PS: Sorry bad english, I'm exausted and english is not my native language, I'm brazilian so I speak portuguese.

So were you able to recover the data off the failed drive?

I've tried a PCB swap to no avail, but the boards were noticeably different anyway.

0

Share this post


Link to post
Share on other sites
The interesting part is that I have updated the firmware through an identical ST31000340AS drive. Changed logical boards and fireup the Firmware update O.O

Worked and won't destroy any data in the good hard disk.

PS: Sorry bad english, I'm exausted and english is not my native language, I'm brazilian so I speak portuguese.

So were you able to recover the data off the failed drive?

I've tried a PCB swap to no avail, but the boards were noticeably different anyway.

Unfortunatelly not. Because the 7200.11 don't start with logical board change :(

The drive tries to initialize but the motor stops after some head tickling noise.

Conclusion: My 2 logical boards are fine, and the 2 disks are fine too. So it's the freakin BSY bug :(

0

Share this post


Link to post
Share on other sites

I wonder if this affects China version of these models?

I have two China ones, a 1TB and a 500GB. I hope they won't experience the same problem as the Thailand one.

Any of you guys out there, having this problem and is NOT made in Thailand?

0

Share this post


Link to post
Share on other sites
I wonder if this affects China version of these models?

I have two China ones, a 1TB and a 500GB. I hope they won't experience the same problem as the Thailand one.

Any of you guys out there, having this problem and is NOT made in Thailand?

Thailand here. But this is a firmware problem, so it's replicable to all disks. If was a hardware failure, OK. But it's not. (IMO)

0

Share this post


Link to post
Share on other sites

I've got a ST31000340AS from China that's not being recognized.

Bought it on August 22nd, failed on Dec 23rd. Christmas eve, the day before I got an external drive from Santa.

0

Share this post


Link to post
Share on other sites

Does your computer hdd led stay constantly on all the time when this hdd is plugged in?

I've got a ST31000340AS from China that's not being recognized.

Bought it on August 22nd, failed on Dec 23rd. Christmas eve, the day before I got an external drive from Santa.

0

Share this post


Link to post
Share on other sites

Strange... I'm hearing a lot of people having drives fail around Christmas time... so did mine... Dec 23rd... strange... and mine was bought in January...

0

Share this post


Link to post
Share on other sites

Mine happen between Nov and Dec.

I realize this as well, so i though its a timebomb issue. I tried changing the BIOS clock to a few months back and connect the hdd again but still cannot detect.

I guess what is bombed is bombed. Wish I could time travel back and backup my data.

Strange... I'm hearing a lot of people having drives fail around Christmas time... so did mine... Dec 23rd... strange... and mine was bought in January...
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.