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
4741 replies to this topic

#4426
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Hi Everyone. After a short hiatus, I'm back to report on my progress.

After having gone through the procedure to un-brick my Seagate drive, here are the results.

I used a hot-swappable sort of enclosure to connect the drive to the computer. The computer could "see" the drive and the 5 partitions. It took a long time for the computer to "see" these partitions. Of the 5 partitions only one is readable and I was able to copy out my data to another external drive. Needless to say, the transfer rate was painfully slow, like 170 to 500 Kb/sec. I took about 3 days to finally transfer 90 Gb out.

Good :), that's already a form of success.


The other 4 partitions could not be accessed, giving an error message as follows:
"Location is not available.
X O:\ is not accessible.
The request could not be performed because of an I/O device error."

Those is usually the behaviour of a "slow" disk (i.e. a disk that is going to fail soon), sometimes after the unbricking only a part of the disk is accessible, but that means that we are once again fundamentally "outside the scope" of this thread, i.e. your disk bricked itself for reasons different from the original firmware issue and only by pure coincidence the procedure, which is basically a "general reset" revived it.
Now tha tis not anymore bricked the issue becomes data recovery.

I think the above error message or the inability of the computer to access the other partitions is due to firmware problems.

No.
Firmware has nothing to do with partitions, they are simply on a completely different "level", firmware is the lowest possible "physical" layer, on top of it there is the PC/OS "Physical layer" and on top of it there is the "logical layer" (to which volumes/partitions/filesystems belong).
What may happen is that there is a "limit" to the accessible sectors (but this is improbable that it is connected to firmware and more likely to be connected to hardware :ph34r: ).


Does anyone have any idea how to solve this problem?

NO.
http://homepage.ntlw...no-answers.html
(at least not in the DIY "club", professionals may)

The only thing that you can try doing is to image the disk (using any of the variously mentioned "suitable" tools, such as DMDE, DATARESCUEDD, etc.) and perform data recovery on the image (NOT on the original disk).

It is possible that this way you can recover more data than what you have till now, if you need help start a NEW thread, as that would go largely outside the scope of this one.

jaclaz


How to remove advertisement from MSFN

#4427
deceneu67

deceneu67
  • Member
  • 4 posts
  • Joined 10-May 13
  • OS:Windows 7 x86
  • Country: Country Flag
Hello everyone!
From the beginning, please excuse my bad english - I'm not native English speaker. I have an Seagate ST9320320AS (320Gb, 5400.5 Momentus series, FW 0303) hdd with LBA 0 error. The hard drive is recognized by BIOS, but can not be accessed. I tried all the methods shown here, but it didn't work for me.
I used a cable 42. After typing the command F3 T>m0,2,2,0,0,0,0,22, I got the following error message : "F3 T>m0,2,2,0,0,0,0,22

Error 1008 DETSEC 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, File Error 0000000
1

F3 T> "

Is it the harddrive completely defective, or this procedure shown here does not apply to this series?

Please provide me some help!

#4428
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

5400.5 Momentus series, FW 0303) hdd with LBA 0 error.
....
I tried all the methods shown here, but it didn't work for me.
....
Is it the harddrive completely defective, or this procedure shown here does not apply to this series?

Really? :unsure:
Guess why the README FIRST:
http://www.msfn.org/...-read-me-first/
(yes the one that you should read BEFORE posting here, that is linked to in big red bold letters on first post and is reminded on the top of each and every page has this to say on the matter:

If you have been pointed to this, it means that you failed to read here before posting there yet another time one of those SAME questions/problems.

The intended Target:
The scope of a thread about problems of Seagate 7200.11 drives is to try and solve two specific problems:

  • BSY - or "busy" state
  • LBA0 - or drive detected by BIOS with size 0

that are caused on a specific model (the 7200.11) by a specific firmware bug:
  • bricking when drive is booted AND Event Log counter is at entry 320, or a multiple of it (i.e. satisfies the expression: ELaddress=320 + x*256 )
Please note how the 7200.11 is also marketed as Maxtor (Seagate and Maxtor are the "same" company nowadays), and also "branded" as HP, IBM and probably a number of other OEM brands.
....

The non-targets:
  • ANY other problem regarding this specific hard disk model (Seagate 7200.11)
  • ANY problem regarding ANY hard disk BUT this specific one (Seagate 7200.11)
  • ANYTHING NOT listed as "target"


Is it the harddrive completely defective, or this procedure shown here does not apply to this series?

Who knows?
But surely the second you said.

jaclaz

#4429
deceneu67

deceneu67
  • Member
  • 4 posts
  • Joined 10-May 13
  • OS:Windows 7 x86
  • Country: Country Flag
I read README FIRST. Even if the tutorial was made to 7200.11, I said it would not hurt to see if it works for 5400.5 (I had nothing to lose if something went wrong). I tried and I saw that the engine responds to commands, except " F3 T> m0,2,2,0,0,0,0,22". That sounds to me like the heads are not moving, so I am going open the harddisk to see if the HDD heads are moving or not

#4430
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

I read README FIRST. Even if the tutorial was made to 7200.11, I said it would not hurt to see if it works for 5400.5 (I had nothing to lose if something went wrong). I tried and I saw that the engine responds to commands, except " F3 T> m0,2,2,0,0,0,0,22". That sounds to me like the heads are not moving, so I am going open the harddisk to see if the HDD heads are moving or not

Good :), then you failed to understand how this thread in which you posted is ONLY related to the 7200.11 model (strangely enough it's title is ."The Solution for Seagate 7200.11 HDDs" and not "Generic thread about any issue with any disk").

You dont' really want to open a disk (at all) and certainly not "to see if the heads are moving". :w00t:

In any case, once you will have opened it , unless you have a suitable CLEAN environment (and if you have one or know how to build one, probably you would not be here asking for help) and you have some previous experience in repairing disks (and again that would make improbable that you would be here), the disk has around 99.99% of probabilities to never work again once re-assembled. :ph34r:

Seriously, DON'T EVEN THINK of opening a disk (of course if not for fun, after having decided that the disk - and any data in it is of no value for you).

jaclaz

#4431
smandurlo

smandurlo

    Newbie

  • Member
  • 40 posts
  • Joined 12-December 11
  • OS:none specified
  • Country: Country Flag

I said it would not hurt to see if it works for 5400.5

it DOES hurt indeed

so I am going open the harddisk to see if the HDD heads are moving or not

you are totally crazy.

Say farewell to your hard drive and data inside.

#4432
deceneu67

deceneu67
  • Member
  • 4 posts
  • Joined 10-May 13
  • OS:Windows 7 x86
  • Country: Country Flag
There is no data that I want to recover from this HDD; a friend of mine gave me this hdd as bricked (for "playing" whith it). That's the reason I tried to see if I can revive the harddisk using the methods shown here for 7200 and to do some experiments on it. I might be totally crazy as Smandurlo said; however, except the fact that I had the errors I specified in my post, the harddisk responded to all commands with no errors.
Indeed I do not have experience in repairing disks, but I had some free time and I said this is a good moment to start :w00t: .

#4433
leonl07

leonl07
  • Member
  • 2 posts
  • Joined 11-May 13
  • OS:none specified
  • Country: Country Flag
Can someone shed some light on this?

Just before the partition regeneration I tried power off & on the drive (detach the SATA cable, and re-attach it after 30s) - however the Hyperterminal program won't response after that. Pressing CTRL+Z does not bring back the session at all.

How can I go about to solve this?

Thanks

#4434
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

There is no data that I want to recover from this HDD; a friend of mine gave me this hdd as bricked (for "playing" whith it). That's the reason I tried to see if I can revive the harddisk using the methods shown here for 7200 and to do some experiments on it. I might be totally crazy as Smandurlo said; however, except the fact that I had the errors I specified in my post, the harddisk responded to all commands with no errors.
Indeed I do not have experience in repairing disks, but I had some free time and I said this is a good moment to start :w00t: .

Sure, one must start somewhere :yes: .

Anyway, read here WHY exactly you started your new experience with the wrong foot :ph34r: :
http://forum.hddguru...php?f=1&t=12166
http://forum.hddguru...&start=0#p79321
(not that the good guys at hddguru are particularly friendly/easy with non-pro's, but from time to time you can get some useful info from there).


Can someone shed some light on this?

Just before the partition regeneration I tried power off & on the drive (detach the SATA cable, and re-attach it after 30s) - however the Hyperterminal program won't response after that. Pressing CTRL+Z does not bring back the session at all.

How can I go about to solve this?

Thanks

Sometimes things simply "hang". :huh:

Start again from scratch, including re-booting the PC (it could also depend on the OS you are running).
Then, after having powered off the drive (possibly for sixty seconds and not thirty), see the recommended guide:
http://www.mapleleaf...agatebrick.html

At this point, many say you need to disconnect the SATA power cable from the drive and wait one minute. Yes, count to sixty. Then plug the SATA power cable back into the drive. There is a bit of debate about this step in the forums but that is what I did and it worked fine in my case. *IF and only if* you choose not to disconnect drive power temporarily, you need to at least change back to the test level prompt (type F3 1>/T (enter)) at this point before continuing.

Now back in HyperTerminal, you'll need to hit CTRL-Z to get a fresh prompt

but you can also try NOT powering it of BUT remember to change level or try closing the hyperterminal window a start a new session.

jaclaz

Edited by jaclaz, 11 May 2013 - 10:19 AM.


#4435
leonl07

leonl07
  • Member
  • 2 posts
  • Joined 11-May 13
  • OS:none specified
  • Country: Country Flag


There is no data that I want to recover from this HDD; a friend of mine gave me this hdd as bricked (for "playing" whith it). That's the reason I tried to see if I can revive the harddisk using the methods shown here for 7200 and to do some experiments on it. I might be totally crazy as Smandurlo said; however, except the fact that I had the errors I specified in my post, the harddisk responded to all commands with no errors.
Indeed I do not have experience in repairing disks, but I had some free time and I said this is a good moment to start :w00t: .

Sure, one must start somewhere :yes: .

Anyway, read here WHY exactly you started your new experience with the wrong foot :ph34r: :
http://forum.hddguru...php?f=1&t=12166
http://forum.hddguru...&start=0#p79321
(not that the good guys at hddguru are particularly friendly/easy with non-pro's, but from time to time you can get some useful info from there).


Can someone shed some light on this?

Just before the partition regeneration I tried power off & on the drive (detach the SATA cable, and re-attach it after 30s) - however the Hyperterminal program won't response after that. Pressing CTRL+Z does not bring back the session at all.

How can I go about to solve this?

Thanks

Sometimes things simply "hang". :huh:

Start again from scratch, including re-booting the PC (it could also depend on the OS you are running).
Then, after having powered off the drive (possibly for sixty seconds and not thirty), see the recommended guide:
http://www.mapleleaf...agatebrick.html

At this point, many say you need to disconnect the SATA power cable from the drive and wait one minute. Yes, count to sixty. Then plug the SATA power cable back into the drive. There is a bit of debate about this step in the forums but that is what I did and it worked fine in my case. *IF and only if* you choose not to disconnect drive power temporarily, you need to at least change back to the test level prompt (type F3 1>/T (enter)) at this point before continuing.

Now back in HyperTerminal, you'll need to hit CTRL-Z to get a fresh prompt

but you can also try NOT powering it of BUT remember to change level or try closing the hyperterminal window a start a new session.

jaclaz


jaclaz - many thanks for your prompt reply. Just managed to bring the HDD back to life!

I have in fact spent around 5hrs today on this and the HyperTerminal just didn't response after power off/on. The solution to this was:

1. Power off / on the HDD (removing SATA cable, and re-attach SATA cable)
2. If the Hyperterminal is not responding, close down the program
3. Remove the cable from PC
4. Reconnect the cable to PC
5. Launch Hylerterminal and connect to the device
6. Press CTRL+Z
7. Proceed with the last step, e.g. F3 T>m0,2,2,,,,,22 (enter)

I have kept the HDD with power since step 1.

Also thanks Phaenius @ post 4341 - I have basically repeat the procedure outlined in that post.

#4436
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

jaclaz - many thanks for your prompt reply. Just managed to bring the HDD back to life!
...
Also thanks Phaenius @ post 4341 - I have basically repeat the procedure outlined in that post.

Good, another happy bunny :).

jaclaz

#4437
grignaud

grignaud
  • Member
  • 1 posts
  • Joined 11-May 13
  • OS:XP Home
  • Country: Country Flag
Please note another delighted user, it worked for me.
Note that the firmware download link is broken. The link should now point to http://knowledge.sea...US/FAQ/207951en

#4438
deceneu67

deceneu67
  • Member
  • 4 posts
  • Joined 10-May 13
  • OS:Windows 7 x86
  • Country: Country Flag
Jaclaz,
Thank you for showing me those topics about 5400.5 series.

#4439
DefectoAntesto

DefectoAntesto
  • Member
  • 2 posts
  • Joined 12-May 13
  • OS:Windows 7 x64
  • Country: Country Flag
I want to thank everyone who has contributed their technical skills to this topic, and report my success with the techniques shared here. :thumbup

I have a 500GB 7200.11, firmware SD36, with a 2008 manufacture date. It was in a LaCie external enclosure that my father used to back up his iMac and store some large files. No issues whatsoever until one day, quite spontaneously, the disk was no longer recognized by his mac. Nor was it recognized by my PC in computer management or any other place.

Fortunately, there was no "mission critical" data on the disk, but there were still some files on there he did not want to lose. I started researching the issue and stumbled across this thread. The symptoms the disk exhibited were just like those discussed here, so I elected to give it a shot.

For simplicity's sake, I purchased a 7200.11 unbricking "kit" off eBay for $20.00, which included a Torx 6 tool and a pre-wired Silicon Labs CP201X USB Virtual COM Port adapter. I also downloaded a copy of PuTTy terminal software since I am on Win7 which does not have Hyperterminal. Then I read, and RE-READ, the guides posted here as to how to do this procedure with the drive. I also spent some time tinkering with PuTTy as it is slightly different than Hyperterminal.

Anyhow, after getting the drive hooked up to the power supply and COM port adapter (and, taking Carter in Canada's advice and taping everything in place so as to avoid accidental movement of the components), I fired up PuTTy and then the drive. I held my breath, hit control-z, and SLOWLY worked through the spin down/spin up commands, the "card pull," the screwing down of the powered board (yikes), and then the final repartitiion commands. All went completely smoothly on the first try. The repartition, surprisingly, took only about a half-second even though others have reported it takes up to a couple minutes.

I then powered everything down, hooked up the drive via a USB to SATA converter and... IT WAS IMMEDIATELY RECOGNIZED by my machine. Of course, being formatted in HFS+ for the Mac, I still did not know whether the data was intact. I rushed over to my dad's place, plugged in the drive via the same converter and ALL DATA WAS INTACT. I did a quick transfer off the disk.

Data was saved, and mission successful. The 7200.11 now has a date with a sledgehammer and the garbage can.

For me, this experience was intellectually stimulating and without a great deal of pressure because the files on the disk were not that big of a deal. So if the project would have failed, it would not have been disastrous. But it has reaffirmed to me that one backup, even two backups, is not enough. I have gone out and picked up a few new backup drives for my own data (and my dad's) and will make sure that a single drive failure never again causes this level of inconvenience.

Again, thank you all who contributed, and particularly those who shared this technique in the first place. Seagate's technical service department (whom I called first) assured me that my disk's SD36 firmware was not affected by the BSY bug. They could do nothing for me, except recommend a data recovery service. Well, it appears pretty clearly to me that the BSY bug was the exact problem, and now, thanks to the folks on this board, it was sufficiently resolved to allow me access to the data.

#4440
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Again, thank you all who contributed, and particularly those who shared this technique in the first place. Seagate's technical service department (whom I called first) assured me that my disk's SD36 firmware was not affected by the BSY bug. They could do nothing for me, except recommend a data recovery service. Well, it appears pretty clearly to me that the BSY bug was the exact problem, and now, thanks to the folks on this board, it was sufficiently resolved to allow me access to the data.

I tend to think that the technical service at Seagate is very similar to the Marketing Department of the Sirius Cybernetics Corporation :whistle: :
http://hitchhikers.w...ics_Corporation

jaclaz

#4441
DefectoAntesto

DefectoAntesto
  • Member
  • 2 posts
  • Joined 12-May 13
  • OS:Windows 7 x64
  • Country: Country Flag


Again, thank you all who contributed, and particularly those who shared this technique in the first place. Seagate's technical service department (whom I called first) assured me that my disk's SD36 firmware was not affected by the BSY bug. They could do nothing for me, except recommend a data recovery service. Well, it appears pretty clearly to me that the BSY bug was the exact problem, and now, thanks to the folks on this board, it was sufficiently resolved to allow me access to the data.

I tend to think that the technical service at Seagate is very similar to the Marketing Department of the Sirius Cybernetics Corporation :whistle: :
http://hitchhikers.w...ics_Corporation

jaclaz

Yes I see a resemblance. ;) Although I suppose when you have put several million buggy hard drives on the market, you have to turn a blind eye in order for the company to keep the lights on. To their credit, the representative was very polite.... just completely unable to solve the problem.

#4442
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Yes I see a resemblance. ;) Although I suppose when you have put several million buggy hard drives on the market, you have to turn a blind eye in order for the company to keep the lights on. To their credit, the representative was very polite.... just completely unable to solve the problem.

Sure :), my newspaper man is also very polite, but he hardly can help with bricked 7200.11's, it is not by choice that he sells newspapers at the corner of the road, instead of working at Seagate (or other "big" firm) technical service.

He needs to wake up much earlier than what the people at Seagate do, gets a lot more cold in winter and hot in summer than they do :(, yet he is very polite and as useless as the Seagate guys when it comes to bricked drives, BUT at least he is good at selling newspapers :yes: .

JFYI, at the time an easy, almost costless "way out" was proposed, too bad that the Seagate Top Management did not think about it :whistle: :
http://www.msfn.org/...151#entry897151

jaclaz

#4443
Phaenius

Phaenius

    Member

  • Member
  • PipPip
  • 177 posts
  • Joined 17-October 12
  • OS:Windows 7 x64
  • Country: Country Flag

Also thanks Phaenius @ post 4341 - I have basically repeat the procedure outlined in that post.


Wow ! Someone thanking me, now that's a first. :) You're welcome, although I did nothing.

Now I must take a snapshot and put it in a frame. :)

#4444
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Now I must take a snapshot and put it in a frame. :)

Only don't get a Seagate frame :w00t: (they tend to have the glass become opaque suddenly after some time :angel ).
:lol:


jaclaz

#4445
chris1946

chris1946

    Newbie

  • Member
  • 10 posts
  • Joined 17-May 13
  • OS:XP Home
  • Country: Country Flag
Hi, I have sick 7200.11 and am trying to revive it long enough to rescue the data. Unfortunately I am stuck at the beginning. The loopback doesn't work. I have the " FT232BM/BL Seagate Barracuda 7200.11 Firmware Fix tool, complete, USB powered" from ebay and have connected as instructed.
My computer knowledge is not too good but I can follow the instructions ok. My first problem was setting up hyperterminal, so maybe there is something amiss there. I set the connection as indicated, and then checked the device manager and did the same there. The com3 was set different to the connection in the hyperterminal so I changed that.
I shorted out the RX and TX pins but get nothing on the screen when I type on it, so that means the loopback doesn't work. Could it be that my converter is defect? I am using a laptop with usb2 and winXP and when I plug the converter in I get the red and green leds light up initially.
I have read all the important posts/threads but I am stuck. Any ideas? Should the com3 have the same settings as the hyperterminal?

I'd be grateful for any help

Chris

#4446
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
Let's separate the issues.

A loopback is a way of testing only the interface.

It's settings (speed/parity/etc.) are not relevant, the loopback test is a sort of continuity test.

The hyperteminal session settings (which are the ONLY settings that you should "tune" to the ones required by the 7200.11) will overrule the ones of the (virtual) COM port anyway.
The connection is established within a hyperterrminal session and the session parameters are what "counts".

Try:
  • removing the adapter
  • uninstall drivers
  • re-connect the adapter and reinstall the drivers
  • start a new session in hypererminal (do not change any settings for speed, parity, etc).
  • connect the data in/data out wires of the adapter together and do again the loopback test.
  • if you can test the above on another PC additionally it would be better (should the issue being *something* on the specific laptop or it's OS install/drivers/*whatever*
  • if the loopback test is unsuccessful disconnect the adapter and check (with a multimeter or the like) if by any chance the wire(s) have not been properly soldered and/or that they are not interrupted.

Only if the loopback test is successful, then try it again after having started a new session with 38400/8/N/1/N (still leave the settings of the COM port alone).

It is possible that the adapter is DOA (Death On Arrival), unfortunately this can happen :(.

This one? :unsure:
http://www.ebay.it/i...d-/280748167812
check that you have connected correctly the connector of the wires (from the pictures it seems like it could be connected upside down/reversed) and or use a short piece of wire to create the loop between the pins of the board to exclude issues with wires or connector.


jaclaz

Edited by jaclaz, 17 May 2013 - 12:09 PM.


#4447
chris1946

chris1946

    Newbie

  • Member
  • 10 posts
  • Joined 17-May 13
  • OS:XP Home
  • Country: Country Flag
jaclaz,
thanks for the information, I'll try that as soon as I get a chance. Yes it is that adapter and I already contacted the vendor and he replied that if it doesn't work he'll send me a new one, fair enough.

Chris

I just checked it and it looks like DOA. At least all is not yet lost :)

Edited by chris1946, 18 May 2013 - 02:42 AM.


#4448
Calyps0

Calyps0
  • Member
  • 6 posts
  • Joined 19-May 13
  • OS:Windows 7 x64
  • Country: Country Flag
Hey guys. I've got an ST31500341AS with CC1H firmware and I wanted to confirm here if my problem can be fixed through this solution or not. I see most of the drives here have BSY state error or are non-detectable in BIOS, but mine is somewhere in the middle. It is detected by bios and windows but with very long lags. The disk manager says the drive can't be initialized and gives Cyclic redunancy check error. I've tried low level formatting and it was going well but got stuck at 29% , then the drive disappeard and started giving loud clicking sounds , as if heads are stuck. Checking in HDD regenerator results in endless bad sectors from the beginning, then gets stuck around 7% and becomes undetectable ..also while it's working, I hear this sound like when normal drive is working and heads are reading, but in my case it's like it reads for 1 second and then there's a long pause, then it reads again for 1-2 sec, then again a long pause... However when I ran Victoria from DOS - it said drive is stuck in BSY mode.

The data on there isn't important and its already gone, so I'm not worried - all I want to know is if its possible to make it work again? Thanks.

Edited by Calyps0, 19 May 2013 - 07:09 AM.


#4449
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,411 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Hey guys. I've got an ST31500341AS with CC1H firmware and I wanted to confirm here if my problem can be fixed through this solution or not. I see most of the drives here have BSY state error or are non-detectable in BIOS, but mine is somewhere in the middle. It is detected by bios and windows but with very long lags. The disk manager says the drive can't be initialized and gives Cyclic redunancy check error. I've tried low level formatting and it was going well but got stuck at 29% , then the drive disappeard and started giving loud clicking sounds , as if heads are stuck. Checking in HDD regenerator results in endless bad sectors from the beginning, then gets stuck around 7% and becomes undetectable ..also while it's working, I hear this sound like when normal drive is working and heads are reading, but in my case it's like it reads for 1 second and then there's a long pause, then it reads again for 1-2 sec, then again a long pause... However when I ran Victoria from DOS - it said drive is stuck in BSY mode.

The data on there isn't important and its already gone, so I'm not worried - all I want to know is if its possible to make it work again? Thanks.

No, that disk is "gone for good" (and this thread is ONLY for BSY and LBA0 related issues).

A disk (a working disk, even if "bricked") is either BSY (or LBA0) or it is not.

There is NO such thing as "low level format" on any hard disk built in the last -say - 12 years, so I wonder WHAT you have been running. :unsure:

The good news are that attempting the BSY or LBA0 solution detailed here won' t do harm to a disk, it will behave (if it applies/works) as some sort of "reset".

Point is that it is a complete waste of time in your case, as it won't solve the issues you described (I mean it won't make, even if the "reset" works, which I doubt would in this case, that drive in any way "more reliable" or reliable at all), and since you don't have data that you may need to retrieve, there is no use for the procedure.

To recap:
  • if the issue is caused by the original "log entry error 320+n*256", this procedure allows to "reset the disk" and later upgrade the firmware so that the disk won't be anymore affected by the original "log entry error 320+n*256" issue
  • if the issue is caused by *something else* this procedure may act as "general reset", that in most cases will revive the disk long enough to recover data from it
  • in any case after a successful procedure the disk NEEDS to be tested with Seagate disgnostic tools BOTH the "long" and "short" test and if any of them does not pass successfully the disk has to be RMAed (if within warranty) or used as doorholder/thrown in the dustbin/dismantled to get the magnets and platters for fun, etc, and in NO case used as storage media.

You can try the procedure alright, but even if it goes through, I doubt that the Seagate diags will later provide a "pass" result. :(

jaclaz

#4450
Calyps0

Calyps0
  • Member
  • 6 posts
  • Joined 19-May 13
  • OS:Windows 7 x64
  • Country: Country Flag


Hey guys. I've got an ST31500341AS with CC1H firmware and I wanted to confirm here if my problem can be fixed through this solution or not. I see most of the drives here have BSY state error or are non-detectable in BIOS, but mine is somewhere in the middle. It is detected by bios and windows but with very long lags. The disk manager says the drive can't be initialized and gives Cyclic redunancy check error. I've tried low level formatting and it was going well but got stuck at 29% , then the drive disappeard and started giving loud clicking sounds , as if heads are stuck. Checking in HDD regenerator results in endless bad sectors from the beginning, then gets stuck around 7% and becomes undetectable ..also while it's working, I hear this sound like when normal drive is working and heads are reading, but in my case it's like it reads for 1 second and then there's a long pause, then it reads again for 1-2 sec, then again a long pause... However when I ran Victoria from DOS - it said drive is stuck in BSY mode.

The data on there isn't important and its already gone, so I'm not worried - all I want to know is if its possible to make it work again? Thanks.

No, that disk is "gone for good" (and this thread is ONLY for BSY and LBA0 related issues).

A disk (a working disk, even if "bricked") is either BSY (or LBA0) or it is not.

There is NO such thing as "low level format" on any hard disk built in the last -say - 12 years, so I wonder WHAT you have been running. :unsure:

The good news are that attempting the BSY or LBA0 solution detailed here won' t do harm to a disk, it will behave (if it applies/works) as some sort of "reset".

Point is that it is a complete waste of time in your case, as it won't solve the issues you described (I mean it won't make, even if the "reset" works, which I doubt would in this case, that drive in any way "more reliable" or reliable at all), and since you don't have data that you may need to retrieve, there is no use for the procedure.

To recap:
  • if the issue is caused by the original "log entry error 320+n*256", this procedure allows to "reset the disk" and later upgrade the firmware so that the disk won't be anymore affected by the original "log entry error 320+n*256" issue
  • if the issue is caused by *something else* this procedure may act as "general reset", that in most cases will revive the disk long enough to recover data from it
  • in any case after a successful procedure the disk NEEDS to be tested with Seagate disgnostic tools BOTH the "long" and "short" test and if any of them does not pass successfully the disk has to be RMAed (if within warranty) or used as doorholder/thrown in the dustbin/dismantled to get the magnets and platters for fun, etc, and in NO case used as storage media.

You can try the procedure alright, but even if it goes through, I doubt that the Seagate diags will later provide a "pass" result. :(

jaclaz


Thanks for explaining...but It's not exactly "gone" yet since I still manage to sort of access it and check for bad clusters, even with delays... I've been using this tool http://hddguru.com/s...vel-Format-Tool




9 user(s) are reading this topic

0 members, 9 guests, 0 anonymous users



How to remove advertisement from MSFN