Hello,
i've this Barracuda 7200.12
Model: ST31000528AS
S/N (3 digits): 5VP.....
FW: CC34
DATE: 09357
PCB: 100536501

The initial issue of this drive was "bad sectors"
I was cloning it in DE, when i was close to finish cloning, suddenly the drive began to cllick, i turned off and powered on again but the drive keeps doing head clicking sounds after good calibration sound.
I'm not sure is a head problem this time, because a bad head drive should do click-click-click and the spin down, but my drive does first calibration sound then double click sounds (cli/click- cli/click-cli/click) and doesn't spin down.

I think is a SA problem, or ROM got corrupt, please can you help me to understanf if the ROM got corrupt?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Is this rom corrupted as i think?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

did you do any test on the headstack to see if they are damaged ??????
which is more likely a yes

if you did check the heads does your device pick up the hardware information of the drive correct lba


these drives fail with headstack issues and just click away

the drive starts then first tries to calibrate with the service area
but as the head has failed
it will click away and keep clicking

no, i can't do any test, it is in busy state and in terminal i get only this:


it doesn't respond at any terminal command

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

If I recall correctly, you may not be able to get terminal response from these drives unless you either 1) isolate PCB from the HDA, or 2) have the drive callibrating and DRDY or at least DSC. Some Seagate drive families have some peculiarities regarding terminal usage, I just can't remember now if this one behaves in such way, but it may. For example, ES.2 drives won't give terminal at all if they don't callibrate (or you cheat them!).

Ok, i isolated the pcb (spindle and HDA), and i connect it again to the drive after "Z"command.



After "x" command it begins to do those head clicking sounds and terminal hangs there

It's the same if i do the smart reset:


Begins to do head clicking when i enter "N1" command and terminal hangs

P.S.
Why i get this on "Z" command?


i have to input the command twice to have the normal response in terminal, same with U command

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

no i don't have the full version of STR
Wish i had it, could be very helpfull, and i would do the firmware backup for the forum.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

You can't dump anything you can't access
Maybe ROM, but almost useless in this case.

Black ST can you tell me if the rom is ok or not?
I think it's strange where it says CUT2 (look the picture in the 1st post), what do u think?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

I would be very surprised if the MCU code didn't first check the ROM for consistency before transferring control to it. In fact I would expect that the ROM would be checksummed.

You could test for this in two ways. One way would be to modify the model number or serial number text strings. Then observe the terminal for a checksum error.

A second, more elegant way, would be to get hold of a working drive and use a tool such as HDAT2 to enable Power Up In Standby (PUIS). Dump the ROM before and after doing this. The difference between the two dumps should be in the PUIS flag and in the checksum byte(s). You would then modify the checksum byte(s) without touching the code. If the terminal now reports a checksum error, then you can be certain that a bad ROM will not go undetected.

_________________
A backup a day keeps DR away.

Unfortunately things run differently.
P.S. the problem in this drive is first elsewhere.
P.P.S. Why not ask for technical support ?

If you mean why don't i ship the drive to a pro, is because data were been almost all cloned in DE, as i wrote on 1st post i was near to finish cloning, what's important is that important data are all cloned.
So you understand that is not necessary to spend a lot of money on DR to get not important data back, for this reason i try to get the rest of the not important data by myself (if possible).

So do you think is a SA issue?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

I meant direct Technical support for PC3000 / DE , not by another end user
IF you already have the most relevant data, then it is pointless to do anything else, isn't it ?
If things went as I suppose the drive is really in bad condition but again it is pointless unless you want to have fun with a post mortem diagnose or with uncertain ways to get data from the drive.

I have just started to analyse a Seagate ROM. It appears that it consists of several modules, each with its own checksum. I can show you the locations of the checksum bytes, if you wish to experiment.

_________________
A backup a day keeps DR away.

I once modified an old Samsung's ROM mannually (for research purposes) and couldn't find out how the checksum was calculated. Last 16-bit word of the whole ROM seemed to be effectively the checksum itself, but I tried so many different algorithms and offsets and couldn't get the right value back. Not to mention my own ROM's checksm value, which is the reason I could never upload it to the drive and test it.

Now that you've done some research, do you know or could you share how is checksum in Seagate drives performed?

Cheers

WD and Seagate ROMs appear to incorporate several modules, and each module has its own checksum.

I have written about the WD ROMs here:
http://malthus.zapto.org/viewtopic.php?f=59&t=225&p=548

I haven't yet worked out how Seagate's checksums are calculated, but I believe I know where they are located. I've been working with someone privately on the subject, and I'm using his ROM code, so it wouldn't be proper to post those results. However, if the OP were to upload his ROM, or if you were to upload yours, I would be happy to go through the same procedure, perhaps in another thread.

_________________
A backup a day keeps DR away.