fatlip Posted January 29, 2009 Posted January 29, 2009 (edited) Some people have been wondering if their drive is actually suffering from the "BUSY" state problem that causes the drive not to be detected in the BIOS. There should be ZERO risk to your drive doing this as long as you follow the instructions!!!!!!Victoria is a powerful program, so do not mess around with any options other than specified, unless you really know what you are doing!!!!!Here is a quick and dirty guide to check if this is in fact, what has happened to your drive;What you need:1)- a functioning computer running Windows XP/2K/2003 (not sure if it works on Vista)2)- your "suspect" hard drive installed and hooked up to a SATA port in your PC3)- WinRar, or another program that can extract RAR files4)- Download this software - Victoria for Windows5)- Extract the rar file to a location you can remember "C:\Temp or C:\Victoria"6)- Go to the folder and execute the the "Victoria43.exe" file7)- Now you will see the opening screen:8)- Next you need to switch the program to PIO mode in the top right9)- Now click the PCI Scan button10)- You will see a list of drives listed; hopefully your bricked drive will be obvious, but go down the list and when you select the suspect drive, you will see this at the bottom:I hope this helps some of you actually diagnose the problem instead of "guessing".FatlipAddendum: I have seen drives that show as BUSY that have other issues beyond just being stuck in this state! It is a start, but not a "Be all end all" determination if you have a bricked drive. Edited February 5, 2009 by fatlip
lost00 Posted January 29, 2009 Posted January 29, 2009 (edited) Yes, I was seeing the green BUSY button when i connected the defective SATA hdd. Edited January 29, 2009 by msfn00
poolcarpet Posted January 30, 2009 Posted January 30, 2009 (edited) this will work even if the hard disk is not detected in BIOS???--> Ok, I just tried. Mine's not showing up in BIOS and it's showing BUSY as well in this victoria utility, and DRDY and DRSC is lighted up too (BLUE).I tried without the faulty disk connected and I don't see any of the BUSY status lighted up. Edited January 30, 2009 by poolcarpet
fatlip Posted January 30, 2009 Author Posted January 30, 2009 This does a scan of connected devices regardless of BIOS status. I should point out that other lights at the bottom can be active, but the BUSY light will always stay BUSY!this will work even if the hard disk is not detected in BIOS???--> Ok, I just tried. Mine's not showing up in BIOS and it's showing BUSY as well in this victoria utility, and DRDY and DRSC is lighted up too (BLUE).I tried without the faulty disk connected and I don't see any of the BUSY status lighted up.
tontano68 Posted January 30, 2009 Posted January 30, 2009 Seeing as I have only one hard drive (Seagate), how would thew Victoria for does work? Is it self-bootable?
poolcarpet Posted January 30, 2009 Posted January 30, 2009 borrow a friend's pc and connect your hard disk to that pc and test with victoria.alternatively, get the rs232 connections and connect to the hard disk and check via the serial connection.Seeing as I have only one hard drive (Seagate), how would thew Victoria for does work? Is it self-bootable?
PoTTeRKaTz Posted February 5, 2009 Posted February 5, 2009 I tried this program victoria but avg reports it as a trojan.beware
puntoMX Posted February 5, 2009 Posted February 5, 2009 That could be correct, this program isn't your average home-brew-garden-tool, so it might trigger an AV program with a falls alarm. Don´t worry about that but you are right to keep your eyes open .
PoTTeRKaTz Posted February 11, 2009 Posted February 11, 2009 That could be correct, this program isn't your average home-brew-garden-tool, so it might trigger an AV program with a falls alarm. Don´t worry about that but you are right to keep your eyes open .ok. i deactivated the AV and checked the drive. loaded up winxp and then connected the sata drive. it isnt seen by windows or by victoria.can i still fix it by the datacable method??the drive spins up and i can hear it. when i plug it in nothing happens. not seen in bios also.Maxtor Diamond Max 22 500gb firmware cant update from MX15
idbirch2 Posted March 10, 2009 Posted March 10, 2009 OK, so once we've established we have this problem, is there a way to fix it or do I have to send it off to Seagate?
Annihilator Posted April 17, 2009 Posted April 17, 2009 (edited) 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: Edited April 17, 2009 by Annihilator
chemag Posted July 13, 2009 Posted July 13, 2009 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 Posted September 17, 2009 Posted September 17, 2009 Hi allI 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 advanceJP
pedrojpz Posted January 2, 2010 Posted January 2, 2010 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.
Recommended Posts