Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

The Solution for Seagate 7200.11 HDDs

- - - - -

  • Please log in to reply
4721 replies to this topic

#4701
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

Driver problem for the TTL adapter?

NO, if a virtual COM port is created and the loopback test works then the driver is fine.

Have you checked ALL the points I listed in my previous posts?
Have you double-checked them?
Have you also double checked the speed/parity/etc?

JFYI, by convention when I terminate a sentence with that little "hook" which is called a "question mark", it means that the sentence is a question, for which I would like to have an answer.

There are cases where the PCB needs to be completely detached from the disk (as in the first original attempts/tutorial).

jaclaz


How to remove advertisement from MSFN

#4702
gogeta

gogeta

    Newbie

  • Member
  • 10 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

 

Driver problem for the TTL adapter?

NO, if a virtual COM port is created and the loopback test works then the driver is fine.

Have you checked ALL the points I listed in my previous posts?
Have you double-checked them?
Have you also double checked the speed/parity/etc?

JFYI, by convention when I terminate a sentence with that little "hook" which is called a "question mark", it means that the sentence is a question, for which I would like to have an answer.

There are cases where the PCB needs to be completely detached from the disk (as in the first original attempts/tutorial).

jaclaz

 

 

Yes i have checked all the points on the previous post, many times. Now i have completely remove the PCB, swapped the TX-RX and i can finally enter in the terminal!!
Now another problem. When i put this commands the terminal give me these codes:

F3 T>/2

F3 2>Z

LED:000000CE FAddr:00280569
LED:000000CE FAddr:00280569 

Last row is repeated about every minute.

I have isolated only the contact on the lower side of the PCB, that is listed on the guide.

I will wait your info, thanks!


Edited by gogeta, 28 May 2014 - 06:14 AM.


#4703
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

Type SLOWLY :w00t: ;), AFTER having waited 15 or 20 seconds after having powered the PCB:

http://www.msfn.org/...-hdds/?p=841755

 

There isn't a "lower" or "upper" side (it depends on the way you look at it), there are the "motor" contacts (which are near the motor) and the head contacts (which are the other set), the recommended guide:

http://www.mapleleaf...agatebrick.html

suggests to try insulating the "motor" contacts, but it may depend on the actual disk and the situation in which it is "bricked", just like the Tx/Rx (if it doesn't work invert the wires), if one sets of contacts does not work, try again insulating the "other" one.

 

jaclaz



#4704
gogeta

gogeta

    Newbie

  • Member
  • 10 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

I have successfully send all the commands!

F3 T>/2       

F3 2>Z      

Spin Down Complete
Elapsed Time 0.154 msecs
F3 2>U

Spin Up Complete
Elapsed Time 6.399 secs
F3 2>/1

F3 1>N1

F3 1>/T

F3 T>i4,1,22

F3 T>
F3 T>
EchoInterfaceCmds: On
EchoInterfaceCmds: Offm0,2,2,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewr
ite Retries = 00C8

User Partition Format Successful - Elapsed Time 0 mins 00 secs

F3 T>

But still not recognized by windows! What to do now?

Thank you for your patience!



#4705
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

 

But still not recognized by windows! What to do now?

Thank you for your patience!

What do you mean "not recognized by windows"?

I.e. is the DISK device seen in Disk Manager BUT NO DRIVE letter appears in Explorer?

 

The actual original issue may have been:

1) a BSY the disk is NOT seen/detected by the BIOS

2) a LBA0 the disk is seen/detected by the BIOS

 

Is the disk now seen by the BIOS?

If yes, it should also be detected in Disk Manager and this means that it is not "bricked" anymore (i.e. the fix was successful :yes:).

 

Still it is possible that further steps are needed to recover the pre-existing partition(s) or, should this fail, only the recoverable data, see:

http://www.msfn.org/...hdds/?p=1078040

(for the record :whistle:, not hidden a zillion pages back in the megathread, it is last post before your original one)

 

jaclaz



#4706
gogeta

gogeta

    Newbie

  • Member
  • 10 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

 

 

But still not recognized by windows! What to do now?

Thank you for your patience!

What do you mean "not recognized by windows"?

I.e. is the DISK device seen in Disk Manager BUT NO DRIVE letter appears in Explorer?

 

The actual original issue may have been:

1) a BSY the disk is NOT seen/detected by the BIOS

2) a LBA0 the disk is seen/detected by the BIOS

 

Is the disk now seen by the BIOS?

If yes, it should also be detected in Disk Manager and this means that it is not "bricked" anymore (i.e. the fix was successful :yes:).

 

Still it is possible that further steps are needed to recover the pre-existing partition(s) or, should this fail, only the recoverable data, see:

http://www.msfn.org/...hdds/?p=1078040

(for the record :whistle:, not hidden a zillion pages back in the megathread, it is last post before your original one)

 

jaclaz

 

 

I ear the sound that the device is connected in windows, appear unit "F:" but still in this issue.

Now the unit is detected by the bios.

Device manager is in "waiting" condition like before this operation for restoring the unit.

In the attached image in red i sign: Device manager and "This PC" in waiting condition - "F:" unit partially recognized.

 

I ear also the unit that sometimes work (tipical sound of hdd that read/write)

 

Ps: vedo che hai la bandierina italiana, possiamo parlare in italiano? Grazie ;)

Attached Files

  • Attached File  pc.jpg   58.68KB   0 downloads

Edited by gogeta, 28 May 2014 - 07:17 AM.


#4707
gogeta

gogeta

    Newbie

  • Member
  • 10 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

On my netbook with xubuntu i can use "fdisk -l" correctly, only for about one minutes... after the drive will not see anymore until restart the unit.

this is the response of the command

Disk /dev/sdf: 500.1 GB, 500107862016 bytes
48 heads, 46 sectors/track, 442379 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xda688281

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *        2048   976771071   488384512    7  HPFS/NTFS/exFAT

I presume to have the same issue like this thread: http://www.msfn.org/...11-malediction/

 

Edit: with TestDisk in Xubuntu i recognize the NTFS partition and the files that there are in the HDD! I have write the partition table but still not recognized by Windows... 

We are one step closer to the solution!

 

Edit 2: for safe i still trying to copy important files to another hdd. But sometimes the drive hang up and no partition were found! After a while the partition reappear and i can continue :(


Edited by gogeta, 28 May 2014 - 08:28 AM.


#4708
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

Well, what you should attempt doing is to image the DISK (NOT the drive or partition or volume, NOR "files" inside them) "as is", using an appropriate tool.

You will need another hard disk, same size or bigger.

 

Under Linux the suitable tool would be ddrescue (actually it is advised to use Linux and ddrescue), as in the thread you mentioned:

http://www.msfn.org/...11-malediction/

and see also this:

http://www.msfn.org/...seagate-720011/

 

The idea is that ddrescue attempts to read "good" data and keeps a log of what it managed to read, so that access to not read parts can be re-attempted later.

Once you have an "as good as possible" image on a surely working disk, then we can attempt recovering data.

 

 

Ps: vedo che hai la bandierina italiana, possiamo parlare in italiano? Grazie  ;)

 

No, not here (this is an international board and the "common" language is English)

 

In any case. now that the disk is not "bricked" anymore, if you need assistance start a NEW thread (as opposed to continuing here on the "megathread").

 

jaclaz


Edited by jaclaz, 28 May 2014 - 09:23 AM.


#4709
gogeta

gogeta

    Newbie

  • Member
  • 10 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag

Ok i will open another thread for my specific issue, thanks!



#4710
Entarger

Entarger
  • Member
  • 1 posts
  • OS:none specified
  • Country: Country Flag

@gogeta: Did you shut off the power für 10sek, as it stand in the description on page 5?

 

My Maxtor DiamondMax22 works again.

 

 

BIG THANKS!


Edited by Entarger, 18 June 2014 - 01:31 PM.


#4711
CarterInCanada

CarterInCanada

    Newbie

  • Member
  • 20 posts

Hello digital warriors!! Hard to believe but it's been FIVE YEARS since this whole bricked drive mess started. Jaclaz, you Jedi Drive Master you. I see you're still jousting with the newcomers who refuse to read properly. You're unstoppable man. Well done you!

 

I popped in because I'm shifting some web things around and mapleleaf mountain (with my guide included) will soon evaporate into the ether. But Don't Panic!

 

I couldn't leave you folks hanging. I still get one or two emails a month with successful unbrickings so I wanted to keep the content up on the interwebs for people to access and use. Since there's not really any need to 'update' the guide per se (the method hasn't changed in years), I've merely refreshed it to clear a few broken links and made it into a 2mb downloadable .pdf file complete with the same instructions and photos you see now (I might have added one or two more jokes since I had a few ciders open while I worked last night). The whole thing is parked out on a Google drive page anyone can access found here:

 

https://docs.google....2R4bDJJT19rMDQ/

 

(jaclaz, I was going to update the thread that has the old mapleleafmountain pointer but it's locked, I'm guessing you have the keys to the kingdom and can update it for these kind folks?)

 

I'll happily leave the guide there until all these drives finally die. Google seems to be the omnipresent cloud beast for the forseeable future so it should be safe there. Clicking on the link will give you a 'preview' of the file and you can then download a proper copy for your very own with the controls at the top of the page. I notice that the links within the guide don't function in the 'preview' but work fine once you have the .pdf on your local machine.

 

I just last week retired my final 7200.11 from the backup cabinet so despite the firmware screwup, I can't complain about getting my use out of them over the years. My world is now all about growing a 25-acre orchard of apples and pears and berries I bought a while back and generally doing garden things that have nothing whatsoever to do with hard drives. Putting in wine grapes next year even. The cats are still happy and send their regards. It's a good gig up here in Canada.

 

I wish you all well with your continued electronic repair work. Just remember the golden rule and DON'T PANIC!

 

Cheers!

 

Carter In Canada



#4712
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

Good news :), though if you hadn't banned rebots.txt from your site (WHY? :w00t:), by now it would have been indexed/backed up by the Wayback Machine.
If the site is going to evaporate not-so-soon, there may still be time for it to be mirrored/saved.

Regards to you (and to the cats of course).

JFYI ;):



jaclaz


Edited by jaclaz, 22 June 2014 - 04:23 AM.


#4713
bobseag

bobseag
  • Member
  • 4 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Well, I seem a few years late to the party here, but just the other day my Seagate 1TB drive experienced what I believe to be the BSY error. One minute I was in Windows 7, viewing files through Explorer, and as I tried to open a file the entire volume disappeared. After a bit of investigation I realized the drive no longer appeared in BIOS, which led me to research the issue online, and brought me here.

My model is ST31000340AS with firmware SD15.

 

I've spent many hours reading documents, hundreds of posts on this blog, the README file, and watching youtube videos, etc. I believe I understand the process to attempt to fix the drive but am hung up on something mundane. The drive has data that unfortunately I've not backed up recently; recovery of the data is very important to me.

 

I recently purchased a UBS/Serial/TTL hardware device from ebay. My issue is that I can't seem to get the device to work, even in a loopback test. But I suspect I'm missing something obvious since the device is new and the seller has a good online rep, and seems to have sold dozens of such devices.

 

The symptom of my issue is that when I send a character (hex or text) on the tx line, I get a response on the rx line, but the response is always null (0x00). I've tried this on WinXP, Win 7, multiple USB ports, multiple versions of the driver (the device is based on an FTDI chip), and using multiple terminal apps (including SerialTrace which shows a wonderful verbose debug output of every event). I've modified baud rates, COM port numbers, etc. Either the device showed up DOA or I'm missing something.

 

btw, I have tried the device with the Seagate drive and I get no response; I've tried it with the drive controller board attached to the physical drive and with the board completely removed from the physical drive.

 

Can anyone help with the loopback test I'm experiencing?

Cheers


Edited by bobseag, 27 June 2014 - 07:51 AM.


#4714
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

It is possible that the device is DOA, but what is the issue with the loopback test?

 

(the loopback test will be - obviously - totally independent from the transmission protocol/baud settings/etc, that are otherwise vital for communicating with the hard disk board).

 

How EXACTLY are you trying to perform it?

That would be point #8 of the read-me-first:

http://www.msfn.org/...-read-me-first/

 

There may have been an issue in installing the driver, but I doubt it, if the driver is installed correctly you should get an added (virtual) COM port.

 

Check if, by any chance, you are not selecting the right COM port, or if in your different attempts to install different drivers (why?) you created a conflict of some kind, but I also doubt it.

 

The device (if not DOA) will work:

  1. on XP
  2. with normal Terminal
  3. on any USB port

anything different from the above is an unneeded complication and/or a variation with no actual advantage of any kind (i.e. the idea is that if you don' t have XP then we replace - say - Terminal with Putty or something else).

 

jaclaz


Edited by jaclaz, 27 June 2014 - 08:04 AM.


#4715
bobseag

bobseag
  • Member
  • 4 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Thanks for the very quick reply.

Unfortunately, it's not the COM port. I used the default port # that was assigned when the drivers installed, and that didn't work. Then I changed the port # in device mgr and in the terminal app (to match that given in devmgr) and that didn't help either.

Its strange that when I have the loopback wired up I can send a character out the tx line, and I can see something (null / 0x00) return. When I don't wire up the loopback and I send a character, I see the character go out the tx line, but nothing comes back on the rx line. I guess that's how it's supposed to work, but if the rx side of the device was experiencing a fault I would expect to receive nothing in return - regardless of whether I'd wired up a loopback between tx/rx.

I'm not prone to blame a brand new part, but I can't think of any other reasons this loopback test would fail.

Regards



#4716
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag
Actually that is exactly the way it should work (what you type is lost forever if there is no loopback), compare with:
http://www.msfn.org/...-48#entry851176

You have no way (without an oscilloscope or a TTL probe) to know if the issue is in the TX part (receiving characters from terminal but transmitting a single 0x00 instead) or if the issue is in the Rx part (receiving the characters fine by forwarding to terminal a single 0x00), it's a loop! ;)

If you have (in the drawer where you have things that might come into use) a Nokia CA-42 you could try with it.

Still, you have not fully excluded a "queer" issue with the actual driver install / OS install, if you could do just the loopback test on another PC (you won't do any damage to it obviously, and even a very old one will do nicely) it could help pinpointing the issue to a DOA adapter.

From the photos in the link you posted the stupid thingy has at least one led, how it behaves (when you send data through the terminal)?
Or has it more than one led?

jaclaz

#4717
bobseag

bobseag
  • Member
  • 4 posts
  • OS:Windows 7 x64
  • Country: Country Flag

How I wish I had a drawer full of cables, old drive, boards, etc. I just moved countries and did a big cleanout, bringing only two computers and a few DVI cables with me. Ugh.

 

The driver/OS issue is something I've tested a bit. I've tested on a WinXP system with one set of drivers (for XP) and on a Windows 7 64bit system with two different versions of the manufacturer's drivers. None of these environments produced a successful loopback.

 

I didn't post photos but maybe you followed the link to the device I bought on ebay. The device has six leads and came with three cables - one for ground, and one each for tx/rx. It has a toggle to choose 3.3v or 5v and I've tried both during loopback tests, but am sticking with 3.3v. Also has a "power on" LED, which is lit constantly when cabled to a USB port, and two small leds for rx and tx, which light up when I transmit/receive (but again when I receive it's just 0x00).

 

I'm going to assume the device is DOA and either exchange or purchase something different.

 

btw, thanks for the (evidently) years of service you've put in to this blog. Once I get a functioning RS232/TTL device I hope to follow the rest of the instructions and get a working drive again. I may be back with other questions in the future....

 

Best Regards


Edited by bobseag, 27 June 2014 - 12:21 PM.


#4718
bosman

bosman
  • Member
  • 2 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Hi - I have a BARRACUDA 7200.11 ST31500341AS 9JU138-302 with CC1H firmware that I think has the BSY issue (not showing up in BIOS).

Drive has been running 24/7 for the past 4.5 years as an FTPserver at work without any issues until yesterday.

Now, when first powered on it makes about 8-10 slow quiet tick tick noises and nothing. I've tried the drive in a USB caddy and my laptop wouldn't recongise it.

 

When I enter my serial number  on seagate.com it says I'm running the latest and indicates that this drive/firmware is not affected. But when I look at this the model number has update to SD1B  http://knowledge.sea...?language=en_US

 

Is my drive affected by the BSY bug? is it worth buying or is the drive just stuffed. http://www.ebay.com/...=item415de51284

 

I actually had a 1TB fail years ago with the BSY issue and found somebody local to me who lent me there cable and I was able to fix and then update firmware and that HDD is still running strong today..

 

Thanks



#4719
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

Generally speaking the 8-10 (actually they are usually reported as 11 or 12 ticks correspond to a "click of death" :ph34r:(i.e. not BSY, not LBA0).

It is still possible (though improbable :() that the fixing routine, which is a form of "reset" of the disk drive firmware might help, but noone can really say.

If you have a backup of the data on the disk, just throw the stupid disk drive in the dustbin. (it is not even worth the attempt).

If you have not a backup of the data (and you need them), then you should consider attempting a recovery by a professional, which of course will cost you quite a bit of money, considering that the routine - if performed without results - might make recovery more difficult.

More or less what happens is that the disk when powered on attempts several times to read some key sectors on the actual disk surface, and clicks when it fails to read these data. This could been a defect/problem in the firmware (looking for the data in the "wrong" area), in the actual head or in the platter surface (please read as *anything* between US$ 300 and US$ 1,500 :w00t:).

Though, as said it is possible that the "generic" reset might work, if it is an issue with firmware, a professional may be able to "inject" the correct addresses (and this would be a relatively "easy" recovery, without needing to open the disk), if it is a head, a head transplant would be needed (opening physically the disk drive in a "clean room"), and if it's the actual platter it is possible that no data (or only partial data) can be recovered.

 

jaclaz 



#4720
bosman

bosman
  • Member
  • 2 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Thanks for the response Jaclaz

I fired up the drive and actually it is 11 clicks so it doesn't look good. I've already purchased the tool and its on its way, I will try but not expecting result to be favorable.


Edited by bosman, 20 July 2014 - 10:56 PM.


#4721
bobseag

bobseag
  • Member
  • 4 posts
  • OS:Windows 7 x64
  • Country: Country Flag

jaclaz,

Thanks to you and other contributors for this thread. After having problems with a UBS/serial/TTL device, I returned it and received a new one. The loopback test that previously wasn't working (due to a faulty device) worked right away. I was able to recieve the short string of info from the drive that confirmed the existence of the BSY issue, then set to follow the steps in your process to recover the drive. In about 10 minutes the drive was recovered and my data is now safely backed up on another drive.

Many, many thanks for the help.

Cheers,

Bob



#4722
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,018 posts
  • OS:none specified
  • Country: Country Flag

jaclaz,

Thanks to you and other contributors for this thread. After having problems with a UBS/serial/TTL device, I returned it and received a new one. The loopback test that previously wasn't working (due to a faulty device) worked right away. I was able to recieve the short string of info from the drive that confirmed the existence of the BSY issue, then set to follow the steps in your process to recover the drive. In about 10 minutes the drive was recovered and my data is now safely backed up on another drive.

Many, many thanks for the help.

Cheers,

Bob

Good :), yet another happy bunny in the basket!

http://www.msfn.org/...artup/?p=828512

 

jaclaz






9 user(s) are reading this topic

0 members, 8 guests, 0 anonymous users


    Baidu (1)


How to remove advertisement from MSFN