Seagate 7200.12 "bricked"

[a novice]

I have the ST3250318AS FW:CC38
with the brick problem.

I looked at the pictures in the other fix post but they don't look like mine
http://qbhn.neostrada.pl/02.jpg


Here is mine, is there a fix for this one?

http://ep.yimg.com/ca/I/yhst-4446369223 ... 4_14347775

[a novice]

Picture of PCB that mine looks like since the other doesn't work.

Attachments

[ROb]

There are solutions in this very forum for Bricked drive
Spend some time

[a novice]

There are solutions in this very forum for Bricked drive
Spend some time

I couldn't find anything on this drive.
I did and update and was asked to reboot, when I did it came up with a black screen "NTLDR" I did another reboot and then it failed to recognize the drive. Can't see it it in the BIOs but the drive makes no noise, but does spin, very smooth and quiet.
Just hoping for some guide lines. My PCB board as stated, doesn't look like the ones pictured.
Thanks for any help

[dick]

Again my crystal ball doesn't seem to be working very well today.
If you want some sort of help or advice you need to be less economical with the details/facts.

First you haven't even mentioned the drive model number, the symptoms, the tests you have carried out and why YOU have decided it is bricked!

First you say it is 'bricked' then you state.......

I did and update and was asked to reboot, when I did it came up with a black screen "NTLDR"

.........which is not a sign of it being bricked though depending what you did it might be now.

I'll give the crystal ball another go in the morning.

[a novice]

Again my crystal ball doesn't seem to be working very well today.
If you want some sort of help or advice you need to be less economical with the details/facts.

First you haven't even mentioned the drive model number, the symptoms, the tests you have carried out and why YOU have decided it is bricked!

First you say it is 'bricked' then you state.......

I did and update and was asked to reboot, when I did it came up with a black screen "NTLDR"

.........which is not a sign of it being bricked though depending what you did it might be now.

I'll give the crystal ball another go in the morning.

At the top of my post......
[I have the ST3250318AS FW:CC38
with the brick problem.]

As I stated "all I did was reboot the second time and now, not recognized in the BIOS"
I have only tried it in a different machine, same results, nothing else.

[dick]

In that case can I suggest you connect the drive directly to a pc motherboard and run Mhdd or Victoria and note if the drive is seen. You might have to select ide or compatibility mode in the pc bios.

What sounds can you hear from the drive. Spinning or clicking? Can you hear the heads moving as the drive tries to reach ready status?

[a novice]

In that case can I suggest you connect the drive directly to a pc motherboard and run Mhdd or Victoria and note if the drive is seen. You might have to select ide or compatibility mode in the pc bios.

What sounds can you hear from the drive. Spinning or clicking? Can you hear the heads moving as the drive tries to reach ready status?

Spinning, heads moving as the drive tries to reach ready status.
No clicking or abnormal sounds.

[michael chiklis]

In MHDD see if you get ID of the drive, then check SMART status by pressing F8 button.
http://hddguru.com/software/2005.10.02-MHDD/

If MHDD can't read ID and even the computer bios, then most likely firmware has been damaged or you have some bad heads.
If you reach ID in mhdd then most likely you have some bad sector on MBR or a firmware issue.

[a novice]

In MHDD see if you get ID of the drive, then check SMART status by pressing F8 button.
http://hddguru.com/software/2005.10.02-MHDD/

If MHDD can't read ID and even the computer bios, then most likely firmware has been damaged or you have some bad heads.
If you reach ID in mhdd then most likely you have some bad sector on MBR or a firmware issue.

As I expected, I can't run MHDD because it can't see the drive in the BIOS,
but I tried.

[dick]

Mhdd will only see a sata drive set to ide mode in the bios do you would have to change the port settings accordingly. If you already did that then you would need to go to the next stage. You would need to make or buy a rs232 ttl adapter. Then you might be able to send a few commands to help diagnose the drive.

I have to point out to you if the data is valuable to you then you should have the drive assessed by a pro. If you send the wrong commands to the drive you could destroy the data. Remember the 7200.12 series has differences from the 7200.11.

[a novice]

Mhdd will only see a sata drive set to ide mode in the bios do you would have to change the port settings accordingly. If you already did that then you would need to go to the next stage. You would need to make or buy a rs232 ttl adapter. Then you might be able to send a few commands to help diagnose the drive.

I have to point out to you if the data is valuable to you then you should have the drive assessed by a pro. If you send the wrong commands to the drive you could destroy the data. Remember the 7200.12 series has differences from the 7200.11.

Are there pins to jump for read chanels like in the other drives?
I only saw that in the 500 750 & 1000 7200.12 directions.

Notice.... the 250 PCB board looks different from the others.

[a novice]

It's not a big deal, I think I have everything backed up.
I was just hoping to find a way to make it work so I could check it.
I saw there were others that were able to get there, so I was willing to try if I could.
I have another drive with exactly the same #'s, so I switched the PCB boards but that didn't work.
I was able to do that once on a Maxtor drive and it did work, but not this time.
Thanks for the help.

[fzabkar]

Switching boards will never work on 7200.11 models and later. That's because each board stores unique, drive specific information in fllash memory.

I would do as advised and obtain a report via the serial terminal port. This will tell us what is wrong with the drive. Don't send any commands that write to the drive.

[a novice]

Switching boards will never work on 7200.11 models and later. That's because each board stores unique, drive specific information in fllash memory.

I would do as advised and obtain a report via the serial terminal port. This will tell us what is wrong with the drive. Don't send any commands that write to the drive.

Gotcha...
Thank you