Seagate error 84150180

seagate error 84150180

Hi, I have a Seagate Momentus 5400.6 ST9320325AS that suddenly disappeared and freezes the machine (it R/W Status 2 R/W Error 84150180. Follow These Easy Steps Now. Takes Only 2 Minutes. (Recommended). I have an HP desktop with a 1TB Seagate drive that I installed a few years ago. R/W Status 2 R/W Error 84150180.

Opinion: Seagate error 84150180

Error disc read rror
ERROR 134 WOW
Emumaster error invalid header of cd file

FAQ

Looks like Solid-State drives will be keeping us busy. Got in a 160GB SSD with a blown diode and was able to recover. Same for a 64GB. Then, seagate error 84150180, I just got in a 256GB one that is completely dead as well. It's a Crucial drive, and they apparently are having a ton of problems with these just dying out. I haven't found the dead link in this particular drive yet. Still working on it. Anyone else starting to get in SS drives? yep they are failing bigtime these new solid state drive infact they fail more then the normal hard drives. parts over heat and bang goes the diodes gtd4242 wrote: Got in a 160GB SSD with a blown diode and was able to recover, seagate error 84150180. Same for a 64GB. Then, I just got in a 256GB one that is completely dead as well. It's a Crucial drive, and they apparently are having a ton of problems with these just dying out. I haven't found the dead link in this particular drive yet. Still working on it, seagate error 84150180. Anyone else starting to get in SS drives? What symptoms do you have with the blown diodes? So far I have seen a 32GB SSD Expresscard, shows ID but no access to data, recovered this by removing NANDs - it has simple UT163 controller, 2 Samsung SSD drives, 64GB and 128GB, both fail to ID but seagate error 84150180 requested these back before I could work with them, and a 128GB Kingston SSD. This shows ID but no access. Will work on this one today or tomorrow. This would be a good topic for closed discussion ________________ Ibm error 00161 don't have to backup all of your data, just the data seagate error 84150180 want to keep. hddguy wrote: What symptoms do you have with the blown diodes? So far I have seen a 32GB SSD Expresscard, shows ID but no access to data, recovered this by removing NANDs - it has simple UT163 controller, 2 Samsung SSD drives, 64GB and 128GB, both fail to ID but customer requested these back before I could work with them, and a 128GB Kingston SSD. This shows ID but no access. Will work on this one today or tomorrow. The diode issues seem to result in no access to the drive at all, and I mean no drive ID or anything. On the first couple of cases I got in, I just sat down with my multi-meter and tested each component. My customer on this Crucial 256GB drive is getting impatient, so I may not have time to figure out exactly what the problem is there, seagate error 84150180. Same thing though, drive is not recognized. It will recognize when I seagate error 84150180 the switch to flash the firmware, but even then it's not recognizing properly, just the raw id from the ROM. drc wrote: This would be a good topic for closed discussion Agreed :) ________________

TOP

123456 7891011121314 1516171819 2021222324 25

Seagate 7200.11 Bios error

chuck kingery's profile photo

chuck kingery

unread,
Sep 2, 2011, 10:56:27 PM9/2/11

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message seagate error 84150180 abuse

Show original seagate error 84150180 email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to DataRecoveryCertification

I have what I believed to be the normal bios problem with a Seagate
OEM drive (ST3750630AS). It wasn't recognized by the system and
stayed BSY on Deepspar. I was running through the documented process
and received the following error:

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.143 msecs
F3 2>U

Error 1009 DETSEC 00006008
Spin Error
Elapsed Time 31.530 secs
R/W Status 2 R/W Error 84150180


From here I ran a cross a trick from a google search where you wait
until the drive spins down before "Z" is entered which seemed to
work. I received the following:

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.144 msecs
{Remove insulator card}
F3 2>U

Spin Up Complete
Elapsed Time 10.165 seagate error 84150180 2>

So now I proceed with power down, wait, power on and I don't get the
chance to type (ctrl-z) before I start seeing:

LED:000000CC FAddr:00249F05
LED:000000CC FAddr:00249F05
LED:000000CC FAddr:00249F05

I did try and cheat a bit on the five second wait and can get a (ctrl-
z) in and the /1. even the N1 but the errors start again with the
same code. Any ideas on where I can go from here?. or more likely
what I missed :)

Any help would be greatly appreciated.
Chuck

chuck kingery's profile photo

chuck kingery

unread,
Sep 3, 2011, 2:11:32 AM9/3/11

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have 4th master hard disk error press f1 to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to DataRecoveryCertification

Question withdrawn. it would appear that the power down of the drive
after the U command was unnecessary. I went directly into /1 then N1, seagate error 84150180,
then did the power off and on and everything worked fine. I executed
the m0,2,2,0,0,0,0,22 and I am copying data off the drive now :)

Look Like Bad Heads To You Guys?

I'm pretty sure this drive has bad heads, but just looking for some confirmation. It spins up, I hear repeated SA accessing in a rhythmic repeating pattern (almost like clicking but softer). Then it comes ready and allows terminal. Here's what I get in terminal though:

Rst 0x08M
RW cmd 002F req = 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 00 00 A0 E1
opts = 00000000

RW Err = 84150180

ASCII Diag mode

F3 T>/7

F3 7>X

LED:000000CC FAddr:0025B437
LED:000000CC FAddr:0025B437

Click to expand.


Then it locks and needs power cycle. After power cycle when attempting to spin down/up and read any defect lists I get this:

Rst 0x08M
ASCII Diag mode

F3 T>
RW cmd 002F seagate error 84150180 = 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 00 00 A0 E1
opts = 00000000

RW Err = 84150180

ASCII Diag mode

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.129 msecs
F3 2>U

DiagError 00006008
Spin Error
Elapsed Time 17.257 secs
R/W Status 2 R/W Error 84150180
F3 2>/T

F3 T>V40

LED:000000CC FAddr:0027206F
LED:000000CC FAddr:0027206F

Click to expand.


I'm pretty sure R/W Error 84150180 is a servo error, anyone know that for sure?

 

Recently, one of my hard disks ‘disappeared’ from my computer – it was not being detected in the BIOS. It turned out that this was a known issue with my drive, seagate error 84150180, and one for which Seagate had released a firmware update.

Unfortunately, the update could only be applied to functioning drives. Seagate will apply the fix to bricked drives for free, but I was reluctant to send my drive to them because I didn’t want to give strangers access to my personal information. I wanted to do it myself.

After a bit of a search I came across this enormous thread. The first post has changed quite a bit since I first saw it – it initially contained a lot of true and false information, and the same followed in the rest of the thread. I spent some time cross-referencing the various opinions and experiences, and finally managed to unbrick my drive.

I had intended to provide a how-to here but I have since discovered that someone has already done it. What I did was pretty much the same as the author of that guide, except that I used a USB cable instead of a serial adapter.

I found myself a Nokia data cable (DKU-5) and cut off the phone end. With the help of a multimeter I determined which wires were used for transmit, receive and ground, and connected them to some wires I cut off an internal CD-ROM cable. These wires were attached to jumper pins, which I was able to slot into the hard disk. The USB end plugged into my computer, and I was able to connect to my hard disk via putty.

Apart from that, the steps I followed are identical to the guide above. I don’t recommend that people do it – if you have this problem and aren’t wearing a tinfoil hat, I reckon you ought to send it back to Seagate and safely recover your data.

Here are a few seagate error 84150180 that I took during the operation.

Published

Recent Posts

A few weeks back, my 1TB Seagate Barracuda 7200.11 disk bricked suddenly.  It happened after a reboot.  The computer stuck on POST trying to detect the disk, and the disk activity LED was on steady, seagate error 84150180, but it just would not recognize the disk.  With SATA power cable connected I could feel the disk spinning inside, which told me it was not a mechanical problem, but the computer just would not recognize it no matter what I did (including putting it into an enclosure and plugging into another computer).  It looked very disturbing at first but after some research it turned out to be a common problem with a bug in epson 9700 error codes firmware and there is a fix for it.  The bug manifests in 2 symtoms: the LBA=0 problem and the BSY problem.  For the former, the disk is recognized by the computer but it shows the capacity as 0, and for the latter, the computer doesn’t detect the disk at all, which is the case I encountered.

The general steps for fixing the BSY problem are roughly the following:

1. Rig a cable, typically with USB on one end to plug into a computer, and 3 wires on the other end to plug into jumper pins (TX, seagate error 84150180, RX, and GND) on the disk.

2. Loosen the PCB (Printed Circuit Board) seagate error 84150180 the disk with a Torx 6 screw driver.

3. Insert a non-conductive layer between the PCB and the chip on the disk so they no longer contact.

4. Power on the disk.

5. Use a terminal program on the computer to send a couple of  low level commands to the disk to spin it down

6. While the power is still on, remove the non-conductive layer so the PCB and the chip make contact.

7. Use the terminal program to send a few more commands to the disk to spin it up, and erase the S.M.A.R.T. data.

8. power cycle the disk

9. Use the terminal program to re-create the partition data.

HDD-Parts sells a repair kit for $49.99, seagate error 84150180, but I was hoping for some more affordable methods.  There are several Youtube videos showing how it can be done.  Quite a few of them suggest to modify a Nokia CA-42 cable by cutting off the phone connector end and crimping 3 RS232 connector pins to the wires.  I spent $13 for the cable, $9 for a crimper, and $5 for a RS232 DB9 female connector. While it looked easy on the videos, it didn’t work too well for me.   One problem was all these instructions out there used HyperTerminal as the terminal program, but Microsoft stopped bundling it for Windows Vista and later.  This was not a big deal because puTTY works just equally well.  Another problem was that the RS232 DB9 pins I got were way too big for the jumper pins on the disks to fit snuggly and they easily fell off.  What I really need were “jumper headers” as I found out later, but the local Radio Shack was disappointing (the guy worked there swore they didn’t carry any DB9 crimpers until I grabbed one off the shelf and asked him what it was).  But the bigger problem was that Windows (vista and 7) kept using the Prolific USB-to-Serial driver for the cable.  The name of the driver sounded convincing but I just could not get the communication going.  Worse, the videos also instructed to crack open the USB connector so people could tell which wire is which (TX, RX, GND), but the wires were so thin that after a few moves they broke off seagate error 84150180 the solder, and I had to toss it into the trash since I didn’t feel like buying a soldering set.

Later someone told me to check out the driver on the mini-CD that came with the Nokia CA-42 cable.  Honestly I didn’t even notice the mini-CD until the cable was in the trash can, so I couldn’t verify that driver worked any better.

Luckily, googling a bit more pointed me to the MSFN forum seagate error 84150180 how to fix the problem, and since it is a forum, it is interactive, which means there are people who could help when we run into weird situations (many many thanks to jaclaz!!).  The forum also pointed me to a fix kit on eBay for $19.99.  The item listing on eBay recommends to use the VCP (Virtual COM port) driver for the kit, but it was buried under a ton of pictures and I literally missed it until jaclaz pointed it out to me (thanks again!!).

The instructions on the forum are great except for one part.  Instead of steps 3 ~ 6 listed above, it suggests readers to practice how to remove and re-attach the PCB board while the power is on.  It runs a high risk of short-circuiting the PCB because it is very easy to drop these tiny metal screws, and if they fell on the wrong spot, the PCB would become an FCB, seagate error 84150180 circuit autoit _inetsmtpmail error 50.  So DON’T do that.  Take steps 3 ~ 6 instead which is much seagate error 84150180.  The instructions also uses HyperTerminal as the example terminal program, but I will show you how to use puTTY instead.

Disconnect the bricked disk from any power source.  Use the Torx 6 screw driver to remove the PCB board from the disk.  You will see a small chip on the disk.  Cut a strip of anti-static bag, or as the videos suggest, cut a strip of some plastic card (don’t use any paper-based cards because seagate error 84150180 can be torn easily when you try to pull them out seagate error 84150180, and cover the chip, and leave enough leads to the right side of the disk for you to grab and pull later.  Re-attach the PCB board, but don’t tighten these screws too much, seagate error 84150180, especially not on the right side where the non-conductive strip is jammed in between so you can pull out the strip.  You will have 1 extra screw left out because it should go into the middle of the chip and the chip is now covered — don’t lose the screw.

The repair kit was easy to use — I plugged the USB connector to my computer, the 3 wires to the disk jumper pins (make sure you connect GND to GND, TX to RX, and RX to TX).  Windows had seagate error 84150180 finding the driver on its own, but I only needed to point it to the VCP driver I downloaded.  Once the driver is properly installed, log into Windows as an administrative user, go to control panel, Device Manager, and locate the serial port device.  Right click on it, go into properties, and change its baud rate from the default 9600 to 38400.  Also note the COM port it seagate error 84150180 using.  On mine, android market server error has occurred fix is COM4.

I found it easy to do this with a desktop computer.  An eSATA cable from a laptop doesn’t seem to provide enough current to even power on the disk.  Remove the side panel from the tower case so you have direct access to its SATA power cable.  Plug the SATA power to the bricked disk.  You should be able to feel the disk spinning by slightly lifting it with your hands — there is a certain vibration, and also if you try to turn the disk you can feel a drag due to gyroscopic resistance.

Run puTTY.  On the configuration dialog box, make sure to select the radio button that says “Serial”  [1].  Enter the correct COM port number noted earlier in “Serial line” [2], and 38400 in “Speed” [3].  I highly recommend saving this session by providing a meaningful name in “Saved Sessions” [4] and click the “Save” button [5].  After you have done all that, click on “Serial” under “Connection” in the Category tree on the left side [6].  It shows some options fatal error c1902 cygwin the serial connection.  Change “Flow control” to “None” [7], and click on “Session” on the left side again bmw cd error e46.  Then click on “Save” button one more time to save the session for later use [5].

Click the “Open” button to open the connection.  You will see a blank window.  If everything was done correctly, pressing “Ctrl-Z”  will show you the prompt.

F3 T>

Type the command below followed by <Enter> to go to level 2

F3 T>/2 <Enter>

And your prompt should now change to

F3 2>

Now you need to spin down the disk by typing the command below, but wait for several seconds before hitting <Enter>

F3 2>Z <wait for several seconds before hitting Enter>

And you should see

F3 2>Z <wait for several seconds before hitting Enter> Spin Down Complete Elapsed Time 0.135 msecs <the time may vary here> F3 2>

People have reported (including me) that if you hit <Enter> too soon after the Z command, you may see some error codes such as:

F3 2>Z <Enter immediately after typing Z> LED:000000CE FAddr:00280569 LED:000000CE FAddr:00280569

One guy seagate error 84150180 even reported that it is enough to just type Z without even hitting <Enter>, and he just back spaced and erased Z after feeling that the disk spinned down. I didn’t try that.

If you successfully spinned down the disk, you are ready for the most important part: keep the power on to the disk and pull out the non-conductive strip you sandwiched between the PCB and the chip earlier. And tighten all the screws that are already in (so you still have the 1 laying around. Don’t worry about this screw for now). Still be careful at this step because you don’t want to accidentally skid the tip of your screw driver on the PCB to fry it. This ensures the PCB provides enough current to the disk motor so it will spin up correctly.

Use the following command to spin up the disk

F3 2>U <Enter>

and if everything was correct, you should see something like

F3 2>U <Enter> Spin Up Complete Elapsed Time 7.093 secs <the time may vary here> F3 2>

I was lucky enough to have encountered a problem at this stage because I didn’t tighten the screws seagate error 84150180 the first attempt, and the motor wasn’t able to draw enough current.  It gave me the following output:

F3 2>U <Enter> Error 1009 DETSEC 00006008 Spin Error Elapsed Time 31.324 secs R/W Status 2 R/W Error 84150180

If you encountered that, make sure you have tightened the screws and try again.

Once the disk has been spinned up successfully, change to level 1 using the following command:

F3 2>/1 <Enter>

and your prompt should change to

Seagate error 84150180 1>

Now reset the S.M.A.R.T. data using the following command:

F3 1>N1 <Enter>

If everyone was correctly done, it would not output anything and only show you another prompt.  However, because of the loose screws, the motor wasn’t spinned up correctly for me during my first attempt, yet I failed seagate error 84150180 notice the error messages from the U command.  So when I continued on with the N1 command, I got the following output:

F3 1>N1 <Enter> Unable to load Diag Overlay

If you see this, STOP.  Power off the disk, re-sandwich the non-conductive strip and START FROM THE BEGINNING.  I was bald enough to go on even after seeing the error message and I will tell you what happened in just a bit.

If erasing S.M.A.R.T. was successful, power off the disk also.  Wait for the disk to completely stop (several seconds), and power it back on.  You need to reconnect a terminal session to the disk, press Ctrl-Z, seagate error 84150180.  Now do the last seagate error 84150180 to re-create partition data (there are 5 commas between the second “2” and the last “22”):

F3 T>m0,2,2,,,22 (enter)

This command takes a while to execute. If everything was right, you will eventually see some output like the following:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8 User Partition Format 5% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs User Partition Format Successful - Elapsed Time 0 mins 05 secs

Now you have your disk back. Power off the disk. Disconnect the COM cable. Put the last screw back in, make sure all screws are tightened, copy all the data from this disk to another disk, and apply the latest firmware from Seagate (perform this as the last step because updating firmware is risky too, you only want to do this after you have copied the data to another disk).
Because I wasn’t paying attention during my first attempt, seagate error 84150180, I tried to re-create the partition data even when the motor spin-up wasn’t successful, and the disk started to give out a horrible “click click click” noise and I thought my disk was doomed for sure. It turned out to be okay, but I wouldn’t recommend such risks.

In any case, if a step fails, you are more than likely need to power off the disk and start from the beginning. If you are uncertain about something, don’t rush head-on first. Go fatal error no screens found asplinux MSFN and ask jaclaz and all the good folks there first. We want you to be a happy bunny in the basket.

Looking back, I was debating with myself if I should’ve bought the $49.99 repair kit from HDD-parts.com, seagate error 84150180.  Because I ended up paying something close to that price anyways ($13 + $9 + $5 + $19.99).  But I decided it was a good thing I didn’t because the $49.99 repair kit is only half the story — I may not have found the MSFN forum had it not been the failed attempt with the CA-42 cable, and I would still run into the problems I encountered later and there would be no one helping me in these situations and might have mistakenly thought the disk was not rescueable and give up on it.  Again, seagate error 84150180 many thanks to jaclaz and other folks!!

Posted in Computers and InternetTagged barracuda, bsy, bug, firmware, hardware, hdd, seagate

Converter

Seagate Barracuda 7200.11- a fundamentally new series of Seagate hard drives, in which the manufacturer tried to combine the technologies for the production of ATA and SCSI drives. In the new family, the mechanics were carried over from ATA hard drives, seagate error 84150180, and a significant part of the firmware architecture was rebuilt from Seagate SCSI drives.

However, along with the beneficial effects of the merger, a number of "hereditary" diseases of both ancestors, with which customers have repeatedly contacted a computer service for repairing and restoring hard drives, have passed into the new architecture. In particular, seagate error 84150180, this is a problem related to translator corruption.

Seagate's desire to bring a new product to market faster has led to a series of hard drives, with a number of flaws and problems. That is why the owners of the Seagate Barracuda 7200.11 HDD often encounter problems with the failure of their hard drives, seagate error 84150180.

Barracuda 7200.11 Series Standard Faults

Winchester not detected in BIOS

One fine day, the hard drive may start to work more slowly or even freeze. And after a reboot, it may not be determined in the BIOS, while the hard drive is constantly in the BUSY state.

This HDD failure can be caused by the following reasons:

  • hardware malfunctions in HDD operation (malfunction of the controller board, heads, etc.);
  • service information corruption (SMART, G-List, seagate error 84150180, translator).

In case of damage to the service information of the hard disk, the management firmware blocks its operation. In this case, the hard drive control terminal issues the error code "LED: 000000CC FAddr: 0024A051", after which the hard drive stops responding to any commands from the outside (or is detected in the BIOS).

Hard drive repair:

This error can be eliminated only with the help of special equipment for repairing hard drives and data recovery (for example, the PC-3000 complex), through the terminal interface, by connecting directly to the HDD and performing a translator recalculation. As a rule, Seagate Barracuda 7200.11 hard drives can work for some seagate error 84150180 after that.



There is information on the network that the control firmware (firmware) is to blame for everything, and in order to seagate error 84150180 the Barracuda 7200.11 hard drive, it is enough to update the firmware in the hard drive controller. Despite the fact that Seagate has released a microcode update for this model, it will not be possible to reflash a non-working hard drive!

Our advice:

  • It is necessary to flash the hard seagate error 84150180 before a malfunction occurs.
  • If the master recommends that you do not change the firmware after data recovery, but change the hard drive, you should heed his advice. seagate error 84150180 In most cases, after restoring a hard drive, it remains operational, seagate error 84150180, but it can fail at any time.

Winchester is not detected in the BIOS, but the hard disk space is zero

The hard drive is usually correctly displayed in the BIOS (depending on the type of BIOS, it may not be detected, detected incorrectly, display the message: "HARD DISK ERROR"), however, its volume is defined as zero, which means that it is impossible to work with it and appropriate repair is required and data recovery.


The cause of this malfunction may be:

  • destruction of the service information tables of the hard disk (SMART, G-LIST, translator);
  • non-native controller board;
  • contact failure between the controller board and the HDA.

Hard Drive Data Recovery

is made on special equipment and can take from one to several days, since there may be defects (bad blocks) in the user zone of the hard disk that prevent the removal of information from them.

What not to do to recover data:

  • The main reason is the failure of the "translator", and not the damage to the firmware of the firmware, so trying to update the microcode will not lead to anything.
  • Replacing the controller board will not help either.
  • If you were promised to update the hard drive firmware from SD15 to a newer one on a faulty hard drive, run away from this company.

It is worth noting that such problems occur in the following models:

  • Seagate Barracuda 7200.11
    ST3500620AS, ST3500820AS, ST3500320AS, ST3640330AS, ST3750330AS, ST3640530AS, ST31000340AS, ST3750630AS. ST3160813AS, ST3640323AS, ST31500341AS, ST31000333AS, ST3640623AS ST3320613AS, ST3320813AS, ST31500341AS, ST31500341AS, ST31000340AS, ST3750330AS, ST3750630AS, ST3500320AS, ST3500620AS, ST3500820AS, ST31500341AS, ST31000333AS, ST3640323AS, ST3640623AS, ST3320613AS, seagate error 84150180, ST3320813AS, ST3160813AS, ST31000333AS.
  • Seagate Barracuda ES.2
    ST3750330NS ST3250310NS ST3500320NS ST31000340NS ST3250310NS ST3750330NS ST3500320NS ST3250310NS ST31000340NS ST3750330NS ST3500320NS ST3250310NS.
  • Diamond Max 22
    STM3750330AS, STM3500320AS, STM31000340AS, STM3750330AS, STM3500320AS, STM3320614AS, STM31000334AS, STM3640323AS, STM3160813AS.

Engine jam

A stuck spindle motor shaft is the most common problem that can occur after a hard drive has been hit or dropped. If the engine is jammed, then by touch this malfunction can be detected by the characteristic vibration of the HDA when power is applied.

What not to do:

  • If you drop the hard drive, do not try to turn it on.
  • Do not open the hermetic block.
  • Do not attempt to manually rotate discs.
  • Replacing the controller board may damage the donor controller.

For data recovery(we are not talking about repair in this case) it is required to transfer the entire package of disks to the donor HDA. In case of damage to the magnetic heads, it is required to replace the block of magnetic heads from the donor disk.

In some situations, seagate error 84150180, the problem can be complicated by the bending of the spindle motor shaft, and from an impact, scratches can form on the surface of the disk, which will disable the magnetic head unit the first time the HDD is turned on.

You can buy a converter (there are USB-TTL and COM-TTL on sale) or make it yourself (I give a few diagrams below).

For those who have Arduino: connect GND and RESET, use contacts RX and TX.

To test the circuit, you can close RX and TX, - as a result, everything we enter should return.

We connect RXand TX, as in the figure below, disconnect the SATA cable, connect the power.

To work with the COM port, I used PuTTY, your seagate error 84150180 program will also do the job just fine. So, open PuTTY, select the connection type Serial, seagate error 84150180, enter the port seagate error 84150180 other settings:

Speed38400
Data Bits8
stop bits1
ParityNone
flow controlNone
Open a terminal window, press ctrl+zand see the prompt:
F3 T>
To see a list of commands and descriptions for them for your hard drive, you must enter /C, and then Q.It's time to start rebuilding.

Important: be case sensitive seagate error 84150180 typing commands!

  1. Let's go to level 1 by entering /1
  2. Clear S.M.A.R.T. team N1
  3. Turn off the power and wait for the engine to stop (~ 10 sec)
  4. Turn on the power and press again ctrl+z
  5. Clear the list of bad blocks: enter i4,1,22
  6. Repeat steps 3-4
  7. Enter in the console: m0,2,2,0,0,0,0,22(for "Made in China" hard drives - m0,2,2,22)
  8. Let's go to level 2: /2
  9. Stop the engine: enter Z
  10. Turning off the power
After all the manipulations, the hard drive began to be detected in the BIOS. In order not to run into the problem again, update the software on the hard drive. This procedure seagate error 84150180 quite simple: a boot image is downloaded from the manufacturer's website, which is written to a disc. Next - download and update the firmware step by step, just follow the instructions on the screen.

Now I described a situation where everything works as it should, but this rarely happens. During the recovery process, there were several difficulties that I am sure you will also have to face. Therefore, everyone who did not succeed in something, look for a solution in the last section of this article.

Since this article is the result of my own experiments based on various HDD recovery materials, I will describe the problems that I encountered myself.
ProblemSolution
Noise in the consoleConnect Contact GND to ground on the power supply. I used the wire from the power key. Also pull the jumper SATA I from the hard drive.
On the screen after clicking ctrl+z nothing appearsMost likely connected incorrectly RX and TX.
When you first turn on the error LED: 000000CC FAddr: 0025BF67 or LED: 000000CC FAddr: 0024A7E5First, let's try to turn seagate error 84150180 the heads. To do this, unscrew the board (at the same time, you can clean the contacts with an eraser: I had a lot of dirt there), put an insulator (paper, electrical tape, etc.) on the contacts leading to the heads, and screw the board back (not with all the screws, but so that there is power to the motor). Turn on the power, press ctrl+z, enter /2 , Then Z. We are waiting for a message about a successful stop. Spin Down Complete Elapsed Time 0.138 msecs Without turning off the power, unscrew the board, take out our insulator and screw the board back, enter the command to start the engine: U.

If the method of turning off the heads did not help, you need to close the contacts on the board with sharp tweezers or thin wire. The photo (available at the links below) shows the closure points on different hard drives.

Service information of the hard seagate error 84150180 an analogue of the operating system of a computer. Service information is located in a specially designated place (Service Area, SA), in sectors with negative numbers and is available for work only specialized utilities.
Service information modules are not MBR, not Boot sector, and not MFT, all of the above belongs to the "user data" category and is available for use by any utility that works with the disk bypassing the file system (for example, seagate error 84150180, "sector editor"). The service area of ​​a drive may have its own: a translator, a table of defects, a catalog, and so on (depending on the manufacturer and family).

Service information includes:

Microcode overlays- modules containing the downloadable part of the firmware required to start the HDD;
Defect sheets:P-List; G-List; Relo-list and others, depending on the manufacturer and architecture;
S.M.A.R.T.and its logs;
Self Test Modulesused in disc production
Translator, passport- in the presence of a separate module, or in the form of superfiles.

Distinctive feature This problem is that the disk may or may not be detected correctly in the BIOS. Also, incorrect passport information may also indicate problems in the service area of ​​the drive. Unlike other hard disk failures, for service information failures, the manufacturer of the hard disk is of great importance, since differences are found not only in architecture, but also in the very ideology of service information.

Given the location of the service area of ​​the drive - on the surface of magnetic platters, seagate error 84150180, tcp send data error to blender python script error import information may indicate serious problems with the hard drive. Unqualified intervention, rash actions of novice masters can lead to a complete impossibility to recover data.

The structure of the service information of the hard disk

Critical modules- parts of service information, without which the hard drive will not be able to start and work "logically" (that is, when the user zone becomes available). In turn, critical modules can be either unique (for a specific instance of a hard drive) or non-unique (the same in families or models).

TO unique modules include: defect lists (especially factory, P-List), translator (if any);
TO non-unique modules include: microcode overlays that are compatible across families and firmware versions.

Important to remember:
Any mistake when working with the firmware area of ​​a drive is seagate error 84150180 with irreversible consequences. Thus, launching a translator recalculation with someone else's electronics board can make data recovery impossible.

Damage to critical hard drive modules makes it impossible to start the drive, however, non-unique and critical ones can be matched. The situation is much more complicated when unique critical modules are damaged: if you cannot manually assemble them from available copies, then restore the data impossible. Also, for some drives, there are universal methods for restoring some unique modules, for example, recalculation of the Seagate drive translator. But despite such options, solving problems in the service area of ​​a seagate error 84150180 is not a trivial task, because the service information of hard drives can be damaged in different ways. There seagate error 84150180 no single methods for recovering data from a hard drive with corruption of service information, as well as typical malfunctions; moreover, any modules can be damaged in the service area of ​​the drive with absolutely equal probability.

Hard Drive Data Recovery
with corrupted service information

To determine ways to solve problems in the service area of ​​the drive, it is necessary first of all to conduct a thorough diagnostics according to architecture drive. So, looking for damage in the translator of drives with dynamic translation (for example, Samsung or Hitachi) is just as reckless as recalculating the translator to restore the nameplate capacity of a Western Digital drive.

Special case number 1. Seagate 7200.11 drive not detected

Widely known and overgrown not only with "a bunch of methods", but also with various "one-button panaceas", seagate error 84150180, a malfunction in the service area of ​​one family of Seagate drives (long out of production) still excites the minds of novice masters.

The essence of the problem:

A disk, for example ST3500320AS, is not detected in the BIOS, the BSY register is cocked on the port where it is connected (it is checked by a program like Victoria), while no extraneous sounds are heard from the containment area, the disk is spinning.

Fault diagnosis:

As with all Seagate drives, diagnostics are performed through the diagnostic terminal (COM-port). The following message appears in the terminal dialog box:

LED:000000CC FAddr:0024A051
LED:000000CC FAddr:0024A051

Of course, the slang did not bypass this malfunction either, and it was nicknamed the "TsT fly" due to the peculiarities of the pronunciation of the contents of the terminal. As with other malfunctions, this message in the terminal signals problems with some part of the service information. In this case, the overflow of logs, and such an overflow is often associated with unstable operation of the hard drive, or surface defects

Solution:

Interrupting the drive initialization process and subsequent translator recalculation with P-List, checking data availability and obligatory sector-by-sector copy to a healthy drive. The technique "as in a kiosk in the market" often leads to "forks" in the broadcast (when all sectors become inaccessible starting from a certain LBA).

Running automatic translator recalculation on later models that don't suffer from these problems is not only useless, but destructive!

Special case number 2. Western Digital WD20EZRX hard drive not detected

The essence of the problem:

A disk, for example WD20EZRX, is not detected in the BIOS, seagate error 84150180, while it spins up and does not make extraneous sounds. Before finally breaking down, the disk "slowed down" quite a lot, unsuccessful attempts were made to recover data from it using R-Studio. The signal that it was time to bring the disk to the lab was the state of the disk "spun up, but not detected in the BIOS of the computer."

Fault diagnosis:

Considering that WD Marvell family drives do seagate error 84150180 write diagnostic messages to the terminal, the drive is connected via Error c-icap - conf not found interface to the PC-3000Express system. In the status registers there is a signal of readiness ("burning" registers DRD and DSC); at any appeal, including reading the passport, a permanent BSY signal is cocked, the engine does not stop, there are no extraneous sounds.

In order to access the service area of ​​the drive, the disk is transferred to technological regime(by winlogon.exe error at startup windows 7 the appropriate jumpers), which allows you to work with it with a specialized utility. In this mode, access to service information is blocked and the disk seagate error 84150180 rebooted. A drive that has become ready in an emergency (due to the impossibility of reading the service area at false addresses) allows loading the microcode overlays necessary for working with service information modules into RAM. After reading and diagnosing the service area, the diagnosis was clarified: defects in the service area.

Solution:

1, seagate error 84150180. Assembling the modules necessary to launch the translation of a faulty drive (unique critical modules), that is, seagate error 84150180, to ensure the ability to export user data to a healthy drive.

2. Selection of a compatible (family, head map and version of the preamplifier-switch) donor drive to perform the "hot-swap" procedure.

3. Recording in the service area of ​​the "donor" modules from the "patient" required for translation

4. Initialization of start information in the RAM of the drive with subsequent start on the HDA of the "patient"

5. Extracting information: creating a sector-by-sector copy to a healthy drive using the PC-3000 DataExtractor

The case of disk blocking described in the example during independent attempts to recover data is from real daily practice. In this case, the information was completely restored despite 1877 unstable sectors, due to which the HDD was blocked.

In case of any damage to the service area of ​​a hard drive, our laboratory performs sector-by-sector cloning of user data to a working drive. Only this approach can give full guarantee and secure data recovery. There are no standard and template solutions in data recovery in case of service information damage and cannot be.

Artem Makarov aka Robin

09.11.2013

38824 views

Another difficult problem with Seagates, seagate error 84150180, which was solved with the help of the so-called Seagate HDD firmware (loading microcode via seagate error 84150180 time, the laptop HDD ST9500325AS, when power is applied by ear, is recalibrated, hangs in BUSY, it only outputs to the diagnostic port:

Rst 0x08M

And that's it. There is no terminal functionality after the start, as the disk freezes. Before me, the disk was in another place, where the block of heads was changed for it (usually this is always the case, if they don’t understand what’s wrong with the hard drive, they immediately change their heads - just in case). Of course, in the matter of restoring user files, replacing the read / write heads in this situation did not help in any way and the disk was brought to the Hardmaster SC.

The terminal functionality on this line of drives is embedded by the manufacturer in the ROM code, it turns on after power is supplied to the interface. It looks like this:

Rst 0x08M RW cmd 002F req = 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 00 00 A0 E1 opts = 00000000 RW Err = 84150180 ASCII Diag mode F3 T>

Those. positioning error on servo marks, stop of the spindle motor and readiness in the registers to readily respond to terminal requests. In this position, you can spin up the engine with a command, raise diag ovl from the surface and read by ATA all the modules described by id, as well as all the modules described in the system volume. All modules were considered without errors, seagate error 84150180, and at first glance they did not contain anything seditious, which could lead to the drive freezing during a normal start.

Immediately there was a suspicion of a failure in the translation tables, but an attempt to recalculate led to the following result:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 2DF8 DiagError 0000500D User Partition Format Failed - Elapsed Time 0 mins 00 secs R/W Sense 00000002, R/W Error 843200A2 File Error 00000000 Blk Addr AD6F0001, Blk Addr Type D0, Cyl FFFF0000, Hd EC

Those. ended with an error. After some deliberation, a decisive decision was made. Given that all the necessary parts of the service information were successfully backed up earlier, I decided to completely format the service area. Received at the seagate error 84150180 of the process:

System Partition Format Successful - Elapsed Time 2 mins 00 secs

I twitched the power supply, and the disk went into readiness with an "empty" factory passport, seagate error 84150180. In such a position, any read/write operation of service information results in a message that the process is not ready, due to the lack of "extended" commands in the "basic" ROM microcode.

Unable to load Diag Cmd Processor Overlay

In order to get full functionality in such a situation, you need to write overlays to the surface so that the disk reads them. And in order to be able to write to the surface, the disk must read them earlier. Vicious circle. How to find a way out of such a situation?

There is only one option, given that in a situation with a formatted service, the disk is ready via the interface normally, one is to load it into the HDD loader seagate error 84150180 the id92h command, i.e. a microcode package containing, among other things, the required overlays, and thereby, as they say, reflash a Seagate hard drive.

After this operation, the translator recalculation completed successfully

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 2DF8 User Partition Format Successful - Elapsed Time 0 mins 00 secs

And, the final touch is a record of a previously saved translator (id2Bh). After the power was reapplied, the disk issued the usual:

Rst 0x08M (P) SATA Reset

and full access to all LBAs described in the passport. If, before the disk came to me, inquisitive pens would not have climbed into the containment area, then using the manipulations described above, it seagate error 84150180 be possible to repair the hard disk while preserving the information.

Seagate error 84150180 - opinion

Hard drive firmware is about the last place you want to find a bug. But that turned out to be the problem with [BBfoto’s] Seagate HDD which he was using in a RAID array. It stopped working completely, and he later found out the firmware has a bug that makes the drive think it’s permanently in a busy state. There’s a firmware upgrade available, but you have to apply it before the problem shows its face, otherwise you’re out of luck. Some searching led him to a hardware fix for the problem.

[Brad Garcia] put together the tutorial which illustrates the steps needed to unbrick the 7200.11 hard drive with the busy state bug. The image in the lower right shows the drive with a piece of paper between the PCB and the connectors which control the head. This is necessary to boot the drive without it hanging due to the bug. From there he issues serial commands to put it into Access Level 2, then removes the cardboard for the rest of the fix.

In the tutorial [Brad] uses a serial-TTL converter. [BBfoto] grabbed an Arduino instead, using it as a USB-ttl bridge.

FAQ

Looks like Solid-State drives will be keeping us busy. Got in a 160GB SSD with a blown diode and was able to recover. Same for a 64GB. Then, I just got in a 256GB one that is completely dead as well. It's a Crucial drive, and they apparently are having a ton of problems with these just dying out. I haven't found the dead link in this particular drive yet. Still working on it. Anyone else starting to get in SS drives? yep they are failing bigtime these new solid state drive infact they fail more then the normal hard drives. parts over heat and bang goes the diodes gtd4242 wrote: Got in a 160GB SSD with a blown diode and was able to recover. Same for a 64GB. Then, I just got in a 256GB one that is completely dead as well. It's a Crucial drive, and they apparently are having a ton of problems with these just dying out. I haven't found the dead link in this particular drive yet. Still working on it. Anyone else starting to get in SS drives? What symptoms do you have with the blown diodes? So far I have seen a 32GB SSD Expresscard, shows ID but no access to data, recovered this by removing NANDs - it has simple UT163 controller, 2 Samsung SSD drives, 64GB and 128GB, both fail to ID but customer requested these back before I could work with them, and a 128GB Kingston SSD. This shows ID but no access. Will work on this one today or tomorrow. This would be a good topic for closed discussion ________________ You don't have to backup all of your data, just the data you want to keep. hddguy wrote: What symptoms do you have with the blown diodes? So far I have seen a 32GB SSD Expresscard, shows ID but no access to data, recovered this by removing NANDs - it has simple UT163 controller, 2 Samsung SSD drives, 64GB and 128GB, both fail to ID but customer requested these back before I could work with them, and a 128GB Kingston SSD. This shows ID but no access. Will work on this one today or tomorrow. The diode issues seem to result in no access to the drive at all, and I mean no drive ID or anything. On the first couple of cases I got in, I just sat down with my multi-meter and tested each component. My customer on this Crucial 256GB drive is getting impatient, so I may not have time to figure out exactly what the problem is there. Same thing though, drive is not recognized. It will recognize when I flip the switch to flash the firmware, but even then it's not recognizing properly, just the raw id from the ROM. drc wrote: This would be a good topic for closed discussion Agreed :) ________________

TOP

123456 7891011121314 1516171819 2021222324 25

Recent Posts

A few weeks back, my 1TB Seagate Barracuda 7200.11 disk bricked suddenly.  It happened after a reboot.  The computer stuck on POST trying to detect the disk, and the disk activity LED was on steady, but it just would not recognize the disk.  With SATA power cable connected I could feel the disk spinning inside, which told me it was not a mechanical problem, but the computer just would not recognize it no matter what I did (including putting it into an enclosure and plugging into another computer).  It looked very disturbing at first but after some research it turned out to be a common problem with a bug in the firmware and there is a fix for it.  The bug manifests in 2 symtoms: the LBA=0 problem and the BSY problem.  For the former, the disk is recognized by the computer but it shows the capacity as 0, and for the latter, the computer doesn’t detect the disk at all, which is the case I encountered.

The general steps for fixing the BSY problem are roughly the following:

1. Rig a cable, typically with USB on one end to plug into a computer, and 3 wires on the other end to plug into jumper pins (TX, RX, and GND) on the disk.

2. Loosen the PCB (Printed Circuit Board) of the disk with a Torx 6 screw driver.

3. Insert a non-conductive layer between the PCB and the chip on the disk so they no longer contact.

4. Power on the disk.

5. Use a terminal program on the computer to send a couple of  low level commands to the disk to spin it down

6. While the power is still on, remove the non-conductive layer so the PCB and the chip make contact.

7. Use the terminal program to send a few more commands to the disk to spin it up, and erase the S.M.A.R.T. data.

8. power cycle the disk

9. Use the terminal program to re-create the partition data.

HDD-Parts sells a repair kit for $49.99, but I was hoping for some more affordable methods.  There are several Youtube videos showing how it can be done.  Quite a few of them suggest to modify a Nokia CA-42 cable by cutting off the phone connector end and crimping 3 RS232 connector pins to the wires.  I spent $13 for the cable, $9 for a crimper, and $5 for a RS232 DB9 female connector. While it looked easy on the videos, it didn’t work too well for me.   One problem was all these instructions out there used HyperTerminal as the terminal program, but Microsoft stopped bundling it for Windows Vista and later.  This was not a big deal because puTTY works just equally well.  Another problem was that the RS232 DB9 pins I got were way too big for the jumper pins on the disks to fit snuggly and they easily fell off.  What I really need were “jumper headers” as I found out later, but the local Radio Shack was disappointing (the guy worked there swore they didn’t carry any DB9 crimpers until I grabbed one off the shelf and asked him what it was).  But the bigger problem was that Windows (vista and 7) kept using the Prolific USB-to-Serial driver for the cable.  The name of the driver sounded convincing but I just could not get the communication going.  Worse, the videos also instructed to crack open the USB connector so people could tell which wire is which (TX, RX, GND), but the wires were so thin that after a few moves they broke off from the solder, and I had to toss it into the trash since I didn’t feel like buying a soldering set.

Later someone told me to check out the driver on the mini-CD that came with the Nokia CA-42 cable.  Honestly I didn’t even notice the mini-CD until the cable was in the trash can, so I couldn’t verify that driver worked any better.

Luckily, googling a bit more pointed me to the MSFN forum on how to fix the problem, and since it is a forum, it is interactive, which means there are people who could help when we run into weird situations (many many thanks to jaclaz!!).  The forum also pointed me to a fix kit on eBay for $19.99.  The item listing on eBay recommends to use the VCP (Virtual COM port) driver for the kit, but it was buried under a ton of pictures and I literally missed it until jaclaz pointed it out to me (thanks again!!).

The instructions on the forum are great except for one part.  Instead of steps 3 ~ 6 listed above, it suggests readers to practice how to remove and re-attach the PCB board while the power is on.  It runs a high risk of short-circuiting the PCB because it is very easy to drop these tiny metal screws, and if they fell on the wrong spot, the PCB would become an FCB, fried circuit board.  So DON’T do that.  Take steps 3 ~ 6 instead which is much safer.  The instructions also uses HyperTerminal as the example terminal program, but I will show you how to use puTTY instead.

Disconnect the bricked disk from any power source.  Use the Torx 6 screw driver to remove the PCB board from the disk.  You will see a small chip on the disk.  Cut a strip of anti-static bag, or as the videos suggest, cut a strip of some plastic card (don’t use any paper-based cards because they can be torn easily when you try to pull them out later), and cover the chip, and leave enough leads to the right side of the disk for you to grab and pull later.  Re-attach the PCB board, but don’t tighten these screws too much, especially not on the right side where the non-conductive strip is jammed in between so you can pull out the strip.  You will have 1 extra screw left out because it should go into the middle of the chip and the chip is now covered — don’t lose the screw.

The repair kit was easy to use — I plugged the USB connector to my computer, the 3 wires to the disk jumper pins (make sure you connect GND to GND, TX to RX, and RX to TX).  Windows had trouble finding the driver on its own, but I only needed to point it to the VCP driver I downloaded.  Once the driver is properly installed, log into Windows as an administrative user, go to control panel, Device Manager, and locate the serial port device.  Right click on it, go into properties, and change its baud rate from the default 9600 to 38400.  Also note the COM port it is using.  On mine, it is COM4.

I found it easy to do this with a desktop computer.  An eSATA cable from a laptop doesn’t seem to provide enough current to even power on the disk.  Remove the side panel from the tower case so you have direct access to its SATA power cable.  Plug the SATA power to the bricked disk.  You should be able to feel the disk spinning by slightly lifting it with your hands — there is a certain vibration, and also if you try to turn the disk you can feel a drag due to gyroscopic resistance.

Run puTTY.  On the configuration dialog box, make sure to select the radio button that says “Serial”  [1].  Enter the correct COM port number noted earlier in “Serial line” [2], and 38400 in “Speed” [3].  I highly recommend saving this session by providing a meaningful name in “Saved Sessions” [4] and click the “Save” button [5].  After you have done all that, click on “Serial” under “Connection” in the Category tree on the left side [6].  It shows some options for the serial connection.  Change “Flow control” to “None” [7], and click on “Session” on the left side again [8].  Then click on “Save” button one more time to save the session for later use [5].

Click the “Open” button to open the connection.  You will see a blank window.  If everything was done correctly, pressing “Ctrl-Z”  will show you the prompt.

F3 T>

Type the command below followed by <Enter> to go to level 2

F3 T>/2 <Enter>

And your prompt should now change to

F3 2>

Now you need to spin down the disk by typing the command below, but wait for several seconds before hitting <Enter>

F3 2>Z <wait for several seconds before hitting Enter>

And you should see

F3 2>Z <wait for several seconds before hitting Enter> Spin Down Complete Elapsed Time 0.135 msecs <the time may vary here> F3 2>

People have reported (including me) that if you hit <Enter> too soon after the Z command, you may see some error codes such as:

F3 2>Z <Enter immediately after typing Z> LED:000000CE FAddr:00280569 LED:000000CE FAddr:00280569

One guy has even reported that it is enough to just type Z without even hitting <Enter>, and he just back spaced and erased Z after feeling that the disk spinned down. I didn’t try that.

If you successfully spinned down the disk, you are ready for the most important part: keep the power on to the disk and pull out the non-conductive strip you sandwiched between the PCB and the chip earlier. And tighten all the screws that are already in (so you still have the 1 laying around. Don’t worry about this screw for now). Still be careful at this step because you don’t want to accidentally skid the tip of your screw driver on the PCB to fry it. This ensures the PCB provides enough current to the disk motor so it will spin up correctly.

Use the following command to spin up the disk

F3 2>U <Enter>

and if everything was correct, you should see something like

F3 2>U <Enter> Spin Up Complete Elapsed Time 7.093 secs <the time may vary here> F3 2>

I was lucky enough to have encountered a problem at this stage because I didn’t tighten the screws at the first attempt, and the motor wasn’t able to draw enough current.  It gave me the following output:

F3 2>U <Enter> Error 1009 DETSEC 00006008 Spin Error Elapsed Time 31.324 secs R/W Status 2 R/W Error 84150180

If you encountered that, make sure you have tightened the screws and try again.

Once the disk has been spinned up successfully, change to level 1 using the following command:

F3 2>/1 <Enter>

and your prompt should change to

F3 1>

Now reset the S.M.A.R.T. data using the following command:

F3 1>N1 <Enter>

If everyone was correctly done, it would not output anything and only show you another prompt.  However, because of the loose screws, the motor wasn’t spinned up correctly for me during my first attempt, yet I failed to notice the error messages from the U command.  So when I continued on with the N1 command, I got the following output:

F3 1>N1 <Enter> Unable to load Diag Overlay

If you see this, STOP.  Power off the disk, re-sandwich the non-conductive strip and START FROM THE BEGINNING.  I was bald enough to go on even after seeing the error message and I will tell you what happened in just a bit.

If erasing S.M.A.R.T. was successful, power off the disk also.  Wait for the disk to completely stop (several seconds), and power it back on.  You need to reconnect a terminal session to the disk, press Ctrl-Z.  Now do the last command to re-create partition data (there are 5 commas between the second “2” and the last “22”):

F3 T>m0,2,2,,,,,22 (enter)

This command takes a while to execute. If everything was right, you will eventually see some output like the following:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8 User Partition Format 5% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs User Partition Format Successful - Elapsed Time 0 mins 05 secs

Now you have your disk back. Power off the disk. Disconnect the COM cable. Put the last screw back in, make sure all screws are tightened, copy all the data from this disk to another disk, and apply the latest firmware from Seagate (perform this as the last step because updating firmware is risky too, you only want to do this after you have copied the data to another disk).
Because I wasn’t paying attention during my first attempt, I tried to re-create the partition data even when the motor spin-up wasn’t successful, and the disk started to give out a horrible “click click click” noise and I thought my disk was doomed for sure. It turned out to be okay, but I wouldn’t recommend such risks.

In any case, if a step fails, you are more than likely need to power off the disk and start from the beginning. If you are uncertain about something, don’t rush head-on first. Go to MSFN and ask jaclaz and all the good folks there first. We want you to be a happy bunny in the basket.

Looking back, I was debating with myself if I should’ve bought the $49.99 repair kit from HDD-parts.com.  Because I ended up paying something close to that price anyways ($13 + $9 + $5 + $19.99).  But I decided it was a good thing I didn’t because the $49.99 repair kit is only half the story — I may not have found the MSFN forum had it not been the failed attempt with the CA-42 cable, and I would still run into the problems I encountered later and there would be no one helping me in these situations and might have mistakenly thought the disk was not rescueable and give up on it.  Again, many many thanks to jaclaz and other folks!!

Posted in Computers and InternetTagged barracuda, bsy, bug, firmware, hardware, hdd, seagate

Recently, one of my hard disks ‘disappeared’ from my computer – it was not being detected in the BIOS. It turned out that this was a known issue with my drive, and one for which Seagate had released a firmware update.

Unfortunately, the update could only be applied to functioning drives. Seagate will apply the fix to bricked drives for free, but I was reluctant to send my drive to them because I didn’t want to give strangers access to my personal information. I wanted to do it myself.

After a bit of a search I came across this enormous thread. The first post has changed quite a bit since I first saw it – it initially contained a lot of true and false information, and the same followed in the rest of the thread. I spent some time cross-referencing the various opinions and experiences, and finally managed to unbrick my drive.

I had intended to provide a how-to here but I have since discovered that someone has already done it. What I did was pretty much the same as the author of that guide, except that I used a USB cable instead of a serial adapter.

I found myself a Nokia data cable (DKU-5) and cut off the phone end. With the help of a multimeter I determined which wires were used for transmit, receive and ground, and connected them to some wires I cut off an internal CD-ROM cable. These wires were attached to jumper pins, which I was able to slot into the hard disk. The USB end plugged into my computer, and I was able to connect to my hard disk via putty.

Apart from that, the steps I followed are identical to the guide above. I don’t recommend that people do it – if you have this problem and aren’t wearing a tinfoil hat, I reckon you ought to send it back to Seagate and safely recover your data.

Here are a few photos that I took during the operation.

Published

Seagate 7200.11 Bios error

chuck kingery's profile photo

chuck kingery

unread,
Sep 2, 2011, 10:56:27 PM9/2/11

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to DataRecoveryCertification

I have what I believed to be the normal bios problem with a Seagate
OEM drive (ST3750630AS). It wasn't recognized by the system and
stayed BSY on Deepspar. I was running through the documented process
and received the following error:

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.143 msecs
F3 2>U

Error 1009 DETSEC 00006008
Spin Error
Elapsed Time 31.530 secs
R/W Status 2 R/W Error 84150180


From here I ran a cross a trick from a google search where you wait
until the drive spins down before "Z" is entered which seemed to
work... I received the following:

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.144 msecs
{Remove insulator card}
F3 2>U

Spin Up Complete
Elapsed Time 10.165 secs
F3 2>

So now I proceed with power down, wait, power on and I don't get the
chance to type (ctrl-z) before I start seeing:

LED:000000CC FAddr:00249F05
LED:000000CC FAddr:00249F05
LED:000000CC FAddr:00249F05

I did try and cheat a bit on the five second wait and can get a (ctrl-
z) in and the /1... even the N1 but the errors start again with the
same code. Any ideas on where I can go from here?... or more likely
what I missed :)

Any help would be greatly appreciated.
Chuck

chuck kingery's profile photo

chuck kingery

unread,
Sep 3, 2011, 2:11:32 AM9/3/11

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to DataRecoveryCertification

Question withdrawn... it would appear that the power down of the drive
after the U command was unnecessary. I went directly into /1 then N1,
then did the power off and on and everything worked fine. I executed
the m0,2,2,0,0,0,0,22 and I am copying data off the drive now :)

Converter

Seagate Barracuda 7200.11- a fundamentally new series of Seagate hard drives, in which the manufacturer tried to combine the technologies for the production of ATA and SCSI drives. In the new family, the mechanics were carried over from ATA hard drives, and a significant part of the firmware architecture was rebuilt from Seagate SCSI drives.

However, along with the beneficial effects of the merger, a number of "hereditary" diseases of both ancestors, with which customers have repeatedly contacted a computer service for repairing and restoring hard drives, have passed into the new architecture. In particular, this is a problem related to translator corruption.

Seagate's desire to bring a new product to market faster has led to a series of hard drives, with a number of flaws and problems. That is why the owners of the Seagate Barracuda 7200.11 HDD often encounter problems with the failure of their hard drives.

Barracuda 7200.11 Series Standard Faults

Winchester not detected in BIOS

One fine day, the hard drive may start to work more slowly or even freeze. And after a reboot, it may not be determined in the BIOS, while the hard drive is constantly in the BUSY state.

This HDD failure can be caused by the following reasons:

  • hardware malfunctions in HDD operation (malfunction of the controller board, heads, etc.);
  • service information corruption (SMART, G-List, translator).

In case of damage to the service information of the hard disk, the management firmware blocks its operation. In this case, the hard drive control terminal issues the error code "LED: 000000CC FAddr: 0024A051", after which the hard drive stops responding to any commands from the outside (or is detected in the BIOS).

Hard drive repair:

This error can be eliminated only with the help of special equipment for repairing hard drives and data recovery (for example, the PC-3000 complex), through the terminal interface, by connecting directly to the HDD and performing a translator recalculation. As a rule, Seagate Barracuda 7200.11 hard drives can work for some time after that.



There is information on the network that the control firmware (firmware) is to blame for everything, and in order to restore the Barracuda 7200.11 hard drive, it is enough to update the firmware in the hard drive controller. Despite the fact that Seagate has released a microcode update for this model, it will not be possible to reflash a non-working hard drive!

Our advice:

  • It is necessary to flash the hard drive before a malfunction occurs.
  • If the master recommends that you do not change the firmware after data recovery, but change the hard drive, you should heed his advice. In most cases, after restoring a hard drive, it remains operational, but it can fail at any time.

Winchester is not detected in the BIOS, but the hard disk space is zero

The hard drive is usually correctly displayed in the BIOS (depending on the type of BIOS, it may not be detected, detected incorrectly, display the message: "HARD DISK ERROR"), however, its volume is defined as zero, which means that it is impossible to work with it and appropriate repair is required and data recovery.


The cause of this malfunction may be:

  • destruction of the service information tables of the hard disk (SMART, G-LIST, translator);
  • non-native controller board;
  • contact failure between the controller board and the HDA.

Hard Drive Data Recovery

is made on special equipment and can take from one to several days, since there may be defects (bad blocks) in the user zone of the hard disk that prevent the removal of information from them.

What not to do to recover data:

  • The main reason is the failure of the "translator", and not the damage to the firmware of the firmware, so trying to update the microcode will not lead to anything.
  • Replacing the controller board will not help either.
  • If you were promised to update the hard drive firmware from SD15 to a newer one on a faulty hard drive, run away from this company.

It is worth noting that such problems occur in the following models:

  • Seagate Barracuda 7200.11
    ST3500620AS, ST3500820AS, ST3500320AS, ST3640330AS, ST3750330AS, ST3640530AS, ST31000340AS, ST3750630AS. ST3160813AS, ST3640323AS, ST31500341AS, ST31000333AS, ST3640623AS ST3320613AS, ST3320813AS, ST31500341AS, ST31500341AS, ST31000340AS, ST3750330AS, ST3750630AS, ST3500320AS, ST3500620AS, ST3500820AS, ST31500341AS, ST31000333AS, ST3640323AS, ST3640623AS, ST3320613AS, ST3320813AS, ST3160813AS, ST31000333AS.
  • Seagate Barracuda ES.2
    ST3750330NS ST3250310NS ST3500320NS ST31000340NS ST3250310NS ST3750330NS ST3500320NS ST3250310NS ST31000340NS ST3750330NS ST3500320NS ST3250310NS.
  • Diamond Max 22
    STM3750330AS, STM3500320AS, STM31000340AS, STM3750330AS, STM3500320AS, STM3320614AS, STM31000334AS, STM3640323AS, STM3160813AS.

Engine jam

A stuck spindle motor shaft is the most common problem that can occur after a hard drive has been hit or dropped. If the engine is jammed, then by touch this malfunction can be detected by the characteristic vibration of the HDA when power is applied.

What not to do:

  • If you drop the hard drive, do not try to turn it on.
  • Do not open the hermetic block.
  • Do not attempt to manually rotate discs.
  • Replacing the controller board may damage the donor controller.

For data recovery(we are not talking about repair in this case) it is required to transfer the entire package of disks to the donor HDA. In case of damage to the magnetic heads, it is required to replace the block of magnetic heads from the donor disk.

In some situations, the problem can be complicated by the bending of the spindle motor shaft, and from an impact, scratches can form on the surface of the disk, which will disable the magnetic head unit the first time the HDD is turned on.

You can buy a converter (there are USB-TTL and COM-TTL on sale) or make it yourself (I give a few diagrams below).

For those who have Arduino: connect GND and RESET, use contacts RX and TX.

To test the circuit, you can close RX and TX, - as a result, everything we enter should return.

We connect RXand TX, as in the figure below, disconnect the SATA cable, connect the power.

To work with the COM port, I used PuTTY, your favorite program will also do the job just fine. So, open PuTTY, select the connection type Serial, enter the port and other settings:

Speed38400
Data Bits8
stop bits1
ParityNone
flow controlNone
Open a terminal window, press ctrl+zand see the prompt:
F3 T>
To see a list of commands and descriptions for them for your hard drive, you must enter /C, and then Q.It's time to start rebuilding.

Important: be case sensitive when typing commands!

  1. Let's go to level 1 by entering /1
  2. Clear S.M.A.R.T. team N1
  3. Turn off the power and wait for the engine to stop (~ 10 sec)
  4. Turn on the power and press again ctrl+z
  5. Clear the list of bad blocks: enter i4,1,22
  6. Repeat steps 3-4
  7. Enter in the console: m0,2,2,0,0,0,0,22(for "Made in China" hard drives - m0,2,2,22)
  8. Let's go to level 2: /2
  9. Stop the engine: enter Z
  10. Turning off the power
After all the manipulations, the hard drive began to be detected in the BIOS. In order not to run into the problem again, update the software on the hard drive. This procedure is quite simple: a boot image is downloaded from the manufacturer's website, which is written to a disc. Next - download and update the firmware step by step, just follow the instructions on the screen.

Now I described a situation where everything works as it should, but this rarely happens. During the recovery process, there were several difficulties that I am sure you will also have to face. Therefore, everyone who did not succeed in something, look for a solution in the last section of this article.

Since this article is the result of my own experiments based on various HDD recovery materials, I will describe the problems that I encountered myself.
ProblemSolution
Noise in the consoleConnect Contact GND to ground on the power supply. I used the wire from the power key. Also pull the jumper SATA I from the hard drive.
On the screen after clicking ctrl+z nothing appearsMost likely connected incorrectly RX and TX.
When you first turn on the error LED: 000000CC FAddr: 0025BF67 or LED: 000000CC FAddr: 0024A7E5First, let's try to turn off the heads. To do this, unscrew the board (at the same time, you can clean the contacts with an eraser: I had a lot of dirt there), put an insulator (paper, electrical tape, etc.) on the contacts leading to the heads, and screw the board back (not with all the screws, but so that there is power to the motor). Turn on the power, press ctrl+z, enter /2 , Then Z. We are waiting for a message about a successful stop. Spin Down Complete Elapsed Time 0.138 msecs Without turning off the power, unscrew the board, take out our insulator and screw the board back, enter the command to start the engine: U.

If the method of turning off the heads did not help, you need to close the contacts on the board with sharp tweezers or thin wire. The photo (available at the links below) shows the closure points on different hard drives.

Service information of the hard disk- an analogue of the operating system of a computer. Service information is located in a specially designated place (Service Area, SA), in sectors with negative numbers and is available for work only specialized utilities.
Service information modules are not MBR, not Boot sector, and not MFT, all of the above belongs to the "user data" category and is available for use by any utility that works with the disk bypassing the file system (for example, "sector editor"). The service area of ​​a drive may have its own: a translator, a table of defects, a catalog, and so on (depending on the manufacturer and family).

Service information includes:

Microcode overlays- modules containing the downloadable part of the firmware required to start the HDD;
Defect sheets:P-List; G-List; Relo-list and others, depending on the manufacturer and architecture;
S.M.A.R.T.and its logs;
Self Test Modulesused in disc production
Translator, passport- in the presence of a separate module, or in the form of superfiles.

Distinctive feature This problem is that the disk may or may not be detected correctly in the BIOS. Also, incorrect passport information may also indicate problems in the service area of ​​the drive. Unlike other hard disk failures, for service information failures, the manufacturer of the hard disk is of great importance, since differences are found not only in architecture, but also in the very ideology of service information.

Given the location of the service area of ​​the drive - on the surface of magnetic platters, damage to service information may indicate serious problems with the hard drive. Unqualified intervention, rash actions of novice masters can lead to a complete impossibility to recover data.

The structure of the service information of the hard disk

Critical modules- parts of service information, without which the hard drive will not be able to start and work "logically" (that is, when the user zone becomes available). In turn, critical modules can be either unique (for a specific instance of a hard drive) or non-unique (the same in families or models).

TO unique modules include: defect lists (especially factory, P-List), translator (if any);
TO non-unique modules include: microcode overlays that are compatible across families and firmware versions.

Important to remember:
Any mistake when working with the firmware area of ​​a drive is fraught with irreversible consequences. Thus, launching a translator recalculation with someone else's electronics board can make data recovery impossible.

Damage to critical hard drive modules makes it impossible to start the drive, however, non-unique and critical ones can be matched. The situation is much more complicated when unique critical modules are damaged: if you cannot manually assemble them from available copies, then restore the data impossible. Also, for some drives, there are universal methods for restoring some unique modules, for example, recalculation of the Seagate drive translator. But despite such options, solving problems in the service area of ​​a drive is not a trivial task, because the service information of hard drives can be damaged in different ways. There are no single methods for recovering data from a hard drive with corruption of service information, as well as typical malfunctions; moreover, any modules can be damaged in the service area of ​​the drive with absolutely equal probability.

Hard Drive Data Recovery
with corrupted service information

To determine ways to solve problems in the service area of ​​the drive, it is necessary first of all to conduct a thorough diagnostics according to architecture drive. So, looking for damage in the translator of drives with dynamic translation (for example, Samsung or Hitachi) is just as reckless as recalculating the translator to restore the nameplate capacity of a Western Digital drive.

Special case number 1. Seagate 7200.11 drive not detected

Widely known and overgrown not only with "a bunch of methods", but also with various "one-button panaceas", a malfunction in the service area of ​​one family of Seagate drives (long out of production) still excites the minds of novice masters.

The essence of the problem:

A disk, for example ST3500320AS, is not detected in the BIOS, the BSY register is cocked on the port where it is connected (it is checked by a program like Victoria), while no extraneous sounds are heard from the containment area, the disk is spinning.

Fault diagnosis:

As with all Seagate drives, diagnostics are performed through the diagnostic terminal (COM-port). The following message appears in the terminal dialog box:

LED:000000CC FAddr:0024A051
LED:000000CC FAddr:0024A051

Of course, the slang did not bypass this malfunction either, and it was nicknamed the "TsT fly" due to the peculiarities of the pronunciation of the contents of the terminal. As with other malfunctions, this message in the terminal signals problems with some part of the service information. In this case, the overflow of logs, and such an overflow is often associated with unstable operation of the hard drive, or surface defects

Solution:

Interrupting the drive initialization process and subsequent translator recalculation with P-List, checking data availability and obligatory sector-by-sector copy to a healthy drive. The technique "as in a kiosk in the market" often leads to "forks" in the broadcast (when all sectors become inaccessible starting from a certain LBA).

Running automatic translator recalculation on later models that don't suffer from these problems is not only useless, but destructive!

Special case number 2. Western Digital WD20EZRX hard drive not detected

The essence of the problem:

A disk, for example WD20EZRX, is not detected in the BIOS, while it spins up and does not make extraneous sounds. Before finally breaking down, the disk "slowed down" quite a lot, unsuccessful attempts were made to recover data from it using R-Studio. The signal that it was time to bring the disk to the lab was the state of the disk "spun up, but not detected in the BIOS of the computer."

Fault diagnosis:

Considering that WD Marvell family drives do not write diagnostic messages to the terminal, the drive is connected via SATA interface to the PC-3000Express system. In the status registers there is a signal of readiness ("burning" registers DRD and DSC); at any appeal, including reading the passport, a permanent BSY signal is cocked, the engine does not stop, there are no extraneous sounds.

In order to access the service area of ​​the drive, the disk is transferred to technological regime(by installing the appropriate jumpers), which allows you to work with it with a specialized utility. In this mode, access to service information is blocked and the disk is rebooted. A drive that has become ready in an emergency (due to the impossibility of reading the service area at false addresses) allows loading the microcode overlays necessary for working with service information modules into RAM. After reading and diagnosing the service area, the diagnosis was clarified: defects in the service area.

Solution:

1. Assembling the modules necessary to launch the translation of a faulty drive (unique critical modules), that is, to ensure the ability to export user data to a healthy drive.

2. Selection of a compatible (family, head map and version of the preamplifier-switch) donor drive to perform the "hot-swap" procedure.

3. Recording in the service area of ​​the "donor" modules from the "patient" required for translation

4. Initialization of start information in the RAM of the drive with subsequent start on the HDA of the "patient"

5. Extracting information: creating a sector-by-sector copy to a healthy drive using the PC-3000 DataExtractor

The case of disk blocking described in the example during independent attempts to recover data is from real daily practice. In this case, the information was completely restored despite 1877 unstable sectors, due to which the HDD was blocked.

In case of any damage to the service area of ​​a hard drive, our laboratory performs sector-by-sector cloning of user data to a working drive. Only this approach can give full guarantee and secure data recovery. There are no standard and template solutions in data recovery in case of service information damage and cannot be.

Artem Makarov aka Robin

09.11.2013

38824 views

Another difficult problem with Seagates, which was solved with the help of the so-called Seagate HDD firmware (loading microcode via interface).

This time, the laptop HDD ST9500325AS, when power is applied by ear, is recalibrated, hangs in BUSY, it only outputs to the diagnostic port:

Rst 0x08M

And that's it. There is no terminal functionality after the start, as the disk freezes. Before me, the disk was in another place, where the block of heads was changed for it (usually this is always the case, if they don’t understand what’s wrong with the hard drive, they immediately change their heads - just in case). Of course, in the matter of restoring user files, replacing the read / write heads in this situation did not help in any way and the disk was brought to the Hardmaster SC.

The terminal functionality on this line of drives is embedded by the manufacturer in the ROM code, it turns on after power is supplied to the interface. It looks like this:

Rst 0x08M RW cmd 002F req = 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 00 00 A0 E1 opts = 00000000 RW Err = 84150180 ASCII Diag mode F3 T>

Those. positioning error on servo marks, stop of the spindle motor and readiness in the registers to readily respond to terminal requests. In this position, you can spin up the engine with a command, raise diag ovl from the surface and read by ATA all the modules described by id, as well as all the modules described in the system volume. All modules were considered without errors, and at first glance they did not contain anything seditious, which could lead to the drive freezing during a normal start.

Immediately there was a suspicion of a failure in the translation tables, but an attempt to recalculate led to the following result:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 2DF8 DiagError 0000500D User Partition Format Failed - Elapsed Time 0 mins 00 secs R/W Sense 00000002, R/W Error 843200A2 , File Error 00000000 Blk Addr AD6F0001, Blk Addr Type D0, Cyl FFFF0000, Hd EC

Those. ended with an error. After some deliberation, a decisive decision was made. Given that all the necessary parts of the service information were successfully backed up earlier, I decided to completely format the service area. Received at the end of the process:

System Partition Format Successful - Elapsed Time 2 mins 00 secs

I twitched the power supply, and the disk went into readiness with an "empty" factory passport. In such a position, any read/write operation of service information results in a message that the process is not ready, due to the lack of "extended" commands in the "basic" ROM microcode.

Unable to load Diag Cmd Processor Overlay

In order to get full functionality in such a situation, you need to write overlays to the surface so that the disk reads them. And in order to be able to write to the surface, the disk must read them earlier. Vicious circle. How to find a way out of such a situation?

There is only one option, given that in a situation with a formatted service, the disk is ready via the interface normally, one is to load it into the HDD loader using the id92h command, i.e. a microcode package containing, among other things, the required overlays, and thereby, as they say, reflash a Seagate hard drive.

After this operation, the translator recalculation completed successfully

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 2DF8 User Partition Format Successful - Elapsed Time 0 mins 00 secs

And, the final touch is a record of a previously saved translator (id2Bh). After the power was reapplied, the disk issued the usual:

Rst 0x08M (P) SATA Reset

and full access to all LBAs described in the passport. If, before the disk came to me, inquisitive pens would not have climbed into the containment area, then using the manipulations described above, it would be possible to repair the hard disk while preserving the information.

USBdeview tells me its connected but wont show a serial number.

USB device viewer doesn't tell me much but here is exactly what it says which is a lot less than other devices connected:

---===>Device Information<===---
*!*ERROR: no String Descriptor for index 11!

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: High
Device Address: 0x01
Open Pipes: 2

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x02 -> Direction: OUT - EndpointID: 2
bmAttributes: 0x02 -> Bulk Transfer Type
wMaxPacketSize: 0x0200 = 0x200 max bytes
bInterval: 0x00

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0200
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x059B = Iomega Corporation
idProduct: 0x0470
bcdDevice: 0x0000
iManufacturer: 0x01
*!*ERROR: no String Descriptor for index 1!
iProduct: 0x0B
*!*ERROR: no String Descriptor for index 11!
iSerialNumber: 0x03
*!*ERROR: no String Descriptor for index 3!
bNumConfigurations: 0x01



The actual SN on the front of the drive is 5SX1H5AK, PN: 9EV134-500, FW: SD03

I can take the drive out of the enclosure but I would need to buy separate sata power and data cables as I have none to test with.

Thanks for this info pal, it is much appreciated

fzabkar :

ISTM that the drive does in fact have internal problems, possibly a damaged firmware module.

What do UVCView or USBDeview tell you?

http://www.nirsoft.net/utils/usb_devices_view.html
http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281- 92cdfeae4b45/UVCView.x64.exe
http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe

The usual advice would be to remove the drive from its enclosure and retest it via a SATA port on your computer's motherboard. However, some USB powered drives integrate the USB electronics on the HDD PCB, in which case a SATA test would not be possible. UVCView should tell us if this is the case, though.

What is the model number of your drive?



 

1 Comments

Leave a Comment