Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Gradius2

The Solution for Seagate 7200.11 HDDs

Recommended Posts

According to the description I could repair a "BSY" faulty HDD, what I would like to thank you to members of the forum.

 

Now a Seagate HDD(ST31000333AS) puzzles me which have a "0 LBA" error.
According to the description I tried to repair but it was no succes.

(PC recognized the type of the HDD, but in the BIOS I only see 0 Mb, in windows: Not initalized)

 

Thank you in advace for your help!

 

 

HYPERTERMINAL:

 

Rst 0x20M        
(P) SATA Reset             
 PASSPackage Verified                    
No Phy: Staggered spin bypass                            
ASCII Diag mode              

F3 T>m0,2,2,0,0,0,0,22                     
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000                 

User Partition Format   4% complete, Zone 00, Pass 00, LBA 00004AA5, ErrCode 00000080, Elapsed Time 0 mins 30 secs                                 
WriteCapInfo           
Selection = 0000 CurrentCap 74706DB0 HDACap 74706DB0                                                   
No update: HDA EQ Current                        
CurrentHDA 74706DB0 HDACap 74706DB0 NativeCap 74706DB0 48BitCap 00000001 28BitCap 00000001         
NO Save      
User Partition Format Successful - Elapsed Time 0 mins 30 secs                                                             
Zone re-format was skipped.                          
F3 T>

Share this post


Link to post
Share on other sites

After my external Maxtor went dead  opened it it and it lead me here . My segate 7200.11 was bsy. 

I didnt have anything lying around.  but some old computer parts , square speak plugins that had to be filled down and an arduino mega.

I never even downloaded the drivers for the arduino .This is was its first use.

Noticing that the mega had a rx tx I plugged it in hooked it up went into device manager put it on the appropriate com port with the correct baud rate. 

Ran putty in serial mode. Ran rx0 , tx0 in a loop on the arduino to see If I would get back what I sent. 

All was good . Followed the steps as stated .

Not sure if this was mentioned in this 4 year thread but arduino works fine as a max 232 substitute. I would bet a home made DB25 Jtag would also. 

Mark

Share this post


Link to post
Share on other sites

                

WriteCapInfo           

Selection = 0000 CurrentCap 74706DB0 HDACap 74706DB0                                                   

No update: HDA EQ Current                        

CurrentHDA 74706DB0 HDACap 74706DB0 NativeCap 74706DB0 48BitCap 00000001 28BitCap 00000001         

NO Save      

User Partition Format Successful - Elapsed Time 0 mins 30 secs                                                             

Zone re-format was skipped.                          

F3 T>

This is the part that "sounds" very different from previous experience.

At first sight, it seems like *something* *somehow* changed the drive map, putting a "Cap" on it. :unsure:

 

You can *try* (of course with NO guarantees whatsoever) to reset the drive to deafult values with a F,,22 :ph34r:, but really cannot say if it can be of any use.

Read around here:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=985252

AND given link:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-19#entry832570

 

@Mrich0908

Nice to know :yes:, but of course *anything* that can send/receive TTL (at the right "low" TLL level) would do, usually people "playing" with Arduino's also have one or more suitable USB to TTL or Serial to TTL converters, and - more than that - they usually know how to interface things successfully, so I am not surprised that it wasn't mentioned before as posters on this thread - usually - post here looking for help/support as they are not familiar with the matter, while most people knowing where their towel is will simply run the commands an unbrick the drive, without ever posting about their experience.

Thanks for sharing it :).

 

jaclaz

Share this post


Link to post
Share on other sites

I'm trying to use this method to recover a Seagate external HD (FreeAgent GoFlex portable) which has the BSY problem, but I'm getting no output in the terminal (I'm using Minicom on Mac OS X). The USB/TTL adapter is working fine. The disk makes some noise, but it is different from the normal spin noise it makes when I plug it via USB.

 

Is it possible that the serial port in this drive is different from the 7200.11? It has 4 pins and I'm assuming it is [-unused- | GRND | RX | TX].

 

What else could I try?

 

Thanks for any help.

Share this post


Link to post
Share on other sites

Is it possible that the serial port in this drive is different from the 7200.11? It has 4 pins and I'm assuming it is [-unused- | GRND | RX | TX].

Well, if it is different from a 7200.11:

  1. the 7200.11 "fix" will NOT likely work
  2. this thread which is for 7200.11 ONLY is not the right place to ask questions about a non-7200.11

To this you add two a few changes from the "known" paths/methods, the use of MacOSX, the use of Minicom (whatever it is), an unspeciified USB/TTL adapter and clearly you are not using the Windows Terminal.

 

Verify it is a 7200.11 with model ending in AS.

 

If it is not one, start a new thread about your issue, after having checked for other existing threads (there is one about the 7200.12 and one about the ES.2 or NS version of the 7200.11) but YMMGV, there is a concrete risk that you might trying to apply either the "wrong" cure to the "right" disease or the "right" cure to the "wrong" disease.

 

Double check with point #1 of the read-me-first:

http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/

 

jaclaz

Share this post


Link to post
Share on other sites

 

Is it possible that the serial port in this drive is different from the 7200.11? It has 4 pins and I'm assuming it is [-unused- | GRND | RX | TX].

Well, if it is different from a 7200.11:

  1. the 7200.11 "fix" will NOT likely work
  2. this thread which is for 7200.11 ONLY is not the right place to ask questions about a non-7200.11

To this you add two a few changes from the "known" paths/methods, the use of MacOSX, the use of Minicom (whatever it is), an unspeciified USB/TTL adapter and clearly you are not using the Windows Terminal.

 

Verify it is a 7200.11 with model ending in AS.

 

If it is not one, start a new thread about your issue, after having checked for other existing threads (there is one about the 7200.12 and one about the ES.2 or NS version of the 7200.11) but YMMGV, there is a concrete risk that you might trying to apply either the "wrong" cure to the "right" disease or the "right" cure to the "wrong" disease.

 

Double check with point #1 of the read-me-first:

http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/

 

jaclaz

 

 

I understand the differences, the thing is that I have spent hours searching for a fix for my HD model, but apparently no one ever had this problem, so my last chance is to try the 7200.11 fix. If it doesn't work I'm throwing the disk out. Being it a Seagate, I think I can at least try the spin down command.

 

My USB/TTL is working fine, Minicom is just a version of the Hyperterminal for Mac.

 

At the moment I just need to find out which pin is which on the serial port of the HD. Just figured this was a better thread, even if for a different model, since the problem is related.

 

Thanks for replying.

Edited by busyhd

Share this post


Link to post
Share on other sites

 

At the moment I just need to find out which pin is which on the serial port of the HD. Just figured this was a better thread, even if for a different model, since the problem is related.

 

Thanks for replying.

 

  1. The pins are the same for most Seagate models, that is NOT the issue. :)
  2. The parameters of the serial transmission may be different depending on model. :unsure:
  3. There is NO evidence whatsoever that your USB/TTL adapter is of the "suitable kind". :w00t: The fact that it works in a loopback doesn't mean that it doesn't use the "wrong" TTL levels.  :ph34r:
  4. PLEASE, STOP posting on this UNRELATED to your issue thread and start a NEW THREAD if you want assistance with your issue (which is NOT related to a 7200.11 and DOES NOT belong to this thread). :realmad:

 

jaclaz

Edited by jaclaz

Share this post


Link to post
Share on other sites

@jaclaz & @CarterInCanada:

 

I took the liberty, even if belatedly, to attach another copy of the full downloadable .pdf version of CarterInCanada's unbricking guide to the end of BlouBul's FGA sticky, therefore creating a second, independent, place it can be downloaded from... just because I don't quite trust the cloud (Google's or not) at all. :D

Share this post


Link to post
Share on other sites

@jaclaz & @CarterInCanada:

 

I took the liberty, even if belatedly, to attach another copy of the full downloadable .pdf version of CarterInCanada's unbricking guide to the end of BlouBul's FGA sticky, therefore creating a second, independent, place it can be downloaded from... just because I don't quite trust the cloud (Google's or not) at all. :D

Very good. :)

If you could also update the sticky here:

http://www.msfn.org/board/topic/133387-debricking-the-seagate-drives/

 

It would be perfect. :thumbup

 

jaclaz

Share this post


Link to post
Share on other sites

 

                

WriteCapInfo           

Selection = 0000 CurrentCap 74706DB0 HDACap 74706DB0                                                   

No update: HDA EQ Current                        

CurrentHDA 74706DB0 HDACap 74706DB0 NativeCap 74706DB0 48BitCap 00000001 28BitCap 00000001         

NO Save      

User Partition Format Successful - Elapsed Time 0 mins 30 secs                                                             

Zone re-format was skipped.                          

F3 T>

This is the part that "sounds" very different from previous experience.

At first sight, it seems like *something* *somehow* changed the drive map, putting a "Cap" on it. :unsure:

 

You can *try* (of course with NO guarantees whatsoever) to reset the drive to deafult values with a F,,22 :ph34r:, but really cannot say if it can be of any use.

Read around here:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=985252

AND given link:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-19#entry832570

 

@Mrich0908

Nice to know :yes:, but of course *anything* that can send/receive TTL (at the right "low" TLL level) would do, usually people "playing" with Arduino's also have one or more suitable USB to TTL or Serial to TTL converters, and - more than that - they usually know how to interface things successfully, so I am not surprised that it wasn't mentioned before as posters on this thread - usually - post here looking for help/support as they are not familiar with the matter, while most people knowing where their towel is will simply run the commands an unbrick the drive, without ever posting about their experience.

Thanks for sharing it :).

 

jaclaz

 

 

Thank you for help!

I tried command, according to description.

I received the following response from the Hyperterminal:

 

Rst 0x20M        

ASCII Diag mode              

F3 T>/2      

F3 2>Z     

LED:000000CE FAddr:0025DF1F                          

Rst 0x20M        

ASCII Diag mode              

F3 T>/2      

F3 2>Z     

Spin Down Complete                 

Elapsed Time 0.131 msecs                       

F3 2>U     

Spin Up Complete               

Elapsed Time 8.900 secs                      

F3 2>/     

F3 T>F,,22         

Drive Configuration restored to defaults.                                        

RAW OFF      

RWSWD-OptChange: Ctrl 0001 Dvgas 0008 Rvgas 0008 Fvgas 0008 SumOf 0008                                                                     

WriteCapInfo           

Selection = 0000 CurrentCap 00000000 HDACap 74706DB0                                                   

Update Cap and Save                  

CurrentHDA 74706DB0 HDACap 74706DB0 NativeCap 74706DB0 48BitCap 74706DB0 28BitCap 0FFFFFFF        

SaveCapInfo          

(P) SATA Reset             

 PASSPackage Verified

                   

F3 T>m0,2,2,0,0,0,0,22                     

ţ

Rst 0x20M        

(P) SATA Reset             

 PASSPackage Verified                    

ReadCap successful - set 48Bit <- Current = 74706DB0 RWSWD-OptChange: Ctrl 0001 D                                                                               

vgas 0008 Rvgas 0008 Fvgas 0008 SumOf 0008                                         

(P) SATA Reset             

Package Verified               

No Phy: Staggered spin bypass                            

ASCII Diag mode              

F3 T>    

 

After that, the real size was visual n the BIOS. However in the windows it was still in "not initialized" state, the contents (data) are not visual.

Than I connected the HDD to the adapter again, than when I opened the hyperterminal I got the following message:

 

Rst 0x20M        

(P) SATA Reset             

 PASSPackage Verified                    

ReadCap successful - set 48Bit <- Current = 74706DB0 RWSWD-OptChange: Ctrl 0001 Dvgas 0008 Rvgas 0008 Fvgas 0008 SumOf 0008                                         

(P) SATA Reset             

Package Verified               

No Phy: Staggered spin bypass                            

ASCII Diag mode              

F3 T>

Earlier I have not seen this message:  "No Phy: Staggered Spin bypass"

 

How can I save the datas?

Share this post


Link to post
Share on other sites

 

After that, the real size was visual n the BIOS. However in the windows it was still in "not initialized" state, the contents (data) are not visual.

....

How can I save the datas?

 

If the disk is seen in BIOS with it's real size, and it is seen in disk manager as "uninitialized disk" your next step would be to attempt making a "dd-like" or "forensic sound" image.

 

You will need a larger HD formatted in NTFS to host the image, or a same size or bigger to make a clone.

And the use of ddrescue (under Linux - recommended) or datarescuedd (or similar porgrams) under Windows.

 

Mind you it is entirely possible that the disk is now recognized in BIOS but that you won't be anyway able to access the physical sectors.

 

Once you will have made this image (or clone) start a new thread and we will see how to recover data (if possible), or if you have difficulties in finding or using the tool, as well start a new thread, the disk drive is now "unbricked" and it does not belong here anymore.

 

The message "No Phy: Staggered Spin bypass" should have no relevance.

 

jaclaz

Share this post


Link to post
Share on other sites

Hi all, i been reading the "read me first" post before but I can not find if it is normal that the hdd makes clicking noises and then stop spinning on 0LBA or BSY state or if that noises comes from another problem.

 

My hdd is a Seagate 7200.11 (ST31500341AS) 1,5 TB and was working fine until the blue screen of death appear and can not boot anymore.

Then boot from another hdd and win7 recognizes the drive with the correct model and capacity but shows like if was empty, no acces to my data at all.

Before read on internet why that happens I though where a bad sector problem and I attempt to do a chkdsk from win7 on my other working hdd. After some minutes when the hdd starts to clicking I freak out and restart my pc and I notice on the boot screen the firmware was fvck. BIOS recognize the hdd as (ST_M13FQBL) with a 3,86 GB capacity and the clicking noise still there until stops spinning after few seconds on every re boot.

My question is if this can be solved with this guide and if that is possible how I must proceed so I can try to do it myself before fvck my hdd even more and have to send it to some recovery data center and waste money.

 

Thank you very much!
 

Edited by Hazard

Share this post


Link to post
Share on other sites

Unfortunately your issue is not solvable following this guide.

IF it is LBA0 then it may apply.

IF it is BSY then it may apply.

 

You have the disk NOT in LBA0 (as you see 3.86 GB) nor in BSY state as you see it in BIOS.

 

You are experiencing the so called "click-of-death":

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=1082429

 

Applying the LBA0 or BSY solution won't likely help in your case :(.

 

jaclaz

Share this post


Link to post
Share on other sites

 

 

After that, the real size was visual n the BIOS. However in the windows it was still in "not initialized" state, the contents (data) are not visual.

....

How can I save the datas?

 

If the disk is seen in BIOS with it's real size, and it is seen in disk manager as "uninitialized disk" your next step would be to attempt making a "dd-like" or "forensic sound" image.

 

You will need a larger HD formatted in NTFS to host the image, or a same size or bigger to make a clone.

And the use of ddrescue (under Linux - recommended) or datarescuedd (or similar porgrams) under Windows.

 

Mind you it is entirely possible that the disk is now recognized in BIOS but that you won't be anyway able to access the physical sectors.

 

Once you will have made this image (or clone) start a new thread and we will see how to recover data (if possible), or if you have difficulties in finding or using the tool, as well start a new thread, the disk drive is now "unbricked" and it does not belong here anymore.

 

The message "No Phy: Staggered Spin bypass" should have no relevance.

 

jaclaz

 

 

Succeeded :) !

Thank You very much for your help!

I saved the data using the GetDataBack program, with complete success.

 

I summarize the case (0 LBA error), the following steps resolved:

 

1., Fixing 0 LBA error:

Hyperterminal:

F3 T>m0,2,2,0,0,0,0,22

 

2., Reset the drive to deafult values

Hyperterminal:

F3 T>/2     

F3 2>Z    

 

F3 2>U    

                   

F3 2>/    

 

F3 T>F,,22      

 

3., Data Rescue

GetDataBack (Classic) using.

 

 

Thanks again!

PePeT

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

×
×
  • Create New...