[Annihilator]

I tried this with my defective drive not connected and it still says BUSY on port 170h. What the hell is this? The drive i am running this from is a working seagate. What am I doing wrong? Why does it show BUSY even tho the bricked drive isnt connected?

Picture:

This post has been edited by Annihilator: 17 April 2009 - 11:30 AM

[dreamerate]

Good software! Thanks for your sharing!

[chemag]

Does each drive have two lines in Victoria panel? I have one SATA drive that works Ok, and another a ST1000340AS that was in an external USB IOMEGA Desktop drive. This drive has not been recognized some days ago. I have taken the drive and connected it to a SATA connexion but was not detected by BIOS. I have run Victoria but I have the same result connected it or not. I think that it is not detected by Victoria, isn't?

In this conditions, is there any chance to recover the data following the instructions in the previous threads?

PD: I have tried to attach a capture but I have not able to.

[jpk]

Hi all

I think I have a case of "bsy" state with my st31000333as. Although Seagate told me it was not the case according to the S/N, I doubt it, specialy after having read the very detailled threads about this issue. And I have the same symptoms as a member here who could save his drive by using the described fix in this forum.

I therefore downloaded the latest victoria (4.46 for win) and tried to verify according to these instructions. I'm using windows 7 and victoria seems to work OK with administrator rights. But it does not see the affected drive .... It sees the non-affected system drive though (2 lines in victoria for this drive) .... Can some one give me a hint please (FYI I've used version 4.3 also for victoria with same effects)

Thanks in advance

JP

[pedrojpz]

When I connect my defective unit (ST31000333AS) my computer waits forever in the POST message "Detecting IDE drives..." so... How can I do the test? I know I could "hot plug" the drive after computer start (when Windows has already loaded) but I did break other motherboard sometime ago doing this...

My drive spins up, then does some head movement noise (clicks), then spins down and then back to the beginning, spins up again... and this happens over and over again and the unit is not recognized by bios, it does not pass from POST... Is this the famous firmware issue?

Regards.

[Kai-Pirinha]

Does not work with windows 7: its complaining about a missing driver and can't be switcht to PIO mode
i also tried starting Victoria in Windows XP Mode (Virtual PC under Win7): first it worked but showed virtual devices only. next session it didn't start up any more for unknown reason.
(i tried everything with Win7 Ultimate 64Bit)

Fatlips post is almost one year old so i have two questions:
is there a newer tool available that will work with Vista/Win7
Victoria is one example for tools that can find a hard drive not detected by bios. Is it still impossible to update the firmware without a self-build interface?

[jaclaz]

Kai-Pirinha, on Jan 21 2010, 05:03 PM, said:

Does not work with windows 7: its complaining about a missing driver and can't be switcht to PIO mode
i also tried starting Victoria in Windows XP Mode (Virtual PC under Win7): first it worked but showed virtual devices only. next session it didn't start up any more for unknown reason.
(i tried everything with Win7 Ultimate 64Bit)

Really?

fatlip, on Jan 29 2009, 01:11 AM, said:

....
What you need:
1)- a functioning computer running Windows XP/2K/2003 (not sure if it works on Vista)
....

Kai-Pirinha, on Jan 21 2010, 05:03 PM, said:

Fatlips post is almost one year old so i have two questions:
is there a newer tool available that will work with Vista/Win7
Victoria is one example for tools that can find a hard drive not detected by bios. Is it still impossible to update the firmware without a self-build interface?

I don't think the actual problem is Victoria, but rather Windows 7 that has some limits when it comes to "low-level" access.
You would save lots of time if you could borrow a "normal" XP running PC from a friend or the like.
You must understand that this whole "business" of bricked drives has some aspects of "magic" or "hidden secrets", the less variations you introduce, the more the probability that the "spell" works.

You do not need a "self built" interface, you can buy a "real" interface or use a TTL USB cable like the Nokia CA-42.
The main thread:
http://www.msfn.org/...17-t128807.html
is full of examples on where to find both a "real" converter and how to check/connect several models of "Nokia" cables.

If, from your other post:
http://www.msfn.org/board/seagate-barracud...-page-1180.html
yuor BIOS does not detect the drive it may be a BSY state one.

In any case, you need NO firmware update, or at least not for recovering data, the firmware upgrade is useful to avoid that after another 320 log entries the drive re-locks itself, and is actually STRONGLY advised NOT to attempt a firmware upgrade before having a safe backup opf the data.

You can try UNbricking the drive allright, in the worst case it won't work (because the problem is a faulty PCB), but in any case (unless of course you "fry" it with overvoltage or shortcircuits), NOTHING will happen to your data (meaning that a data recovery company will nonetheless be able to retrieve it), as well switching PCB's with another drive is NOT advised. (and since you need one exactly of the SAME series it is not even easy to put in practice, as finding a compatible donour might become a nightmare).

Check also the CarterinCanada guide:
http://www.mapleleaf...agatebrick.html
and this one:
http://sites.google....seagatefix/Home

they are both extremely clear, besides the "main" thread.

jaclaz

[BetKing]

Have a look at my result. Only finding 2 entries. Does that mean my disk can't be found?

 vic43.jpg (101K)
Number of downloads: 33

[BetKing]

Anyone?

[nexus01]

is there any tool or method to really confirm a LBA 0 error too ??

[nicky9499]

I can't see the screenshots in the first post??