Hello,
i've this DiamondMax22 STM3500320AS which has an inusual PCB 100475720, usually this kind of hdd have pcb 100466725


Terminal log:




I swapped the pcb with 100466725 and did ROM transfer, log is the same.
But if i insulate both HDA and motor contacts, this is the log:


What does it mean?

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

Not 100% it is accurate, but maybe there is a ROM checksum error?!? or some compatibility issue?!?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

Hi,
so you think that pcb 100466725 is not compatible or rom corruption?

The drive was working fine until yesterday, suddenly the user heard head clicking sounds while he was working on it in windows and the computer hanged.
When he reboot the computer the drive was not working anymore.

When computer boots the drive spins and after 15 seconds about spins down (but i don't head any clicking sounds), after he spins down bios detects it as STM3500320AS but nothing more, the computer hangs in the black boot screen.
Drive has not any operating system, but is full of data

Someone can tell me if the rom is corrupted, please?
ROM backup:

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

Why did you decide to swap the pcb?
What else did you try before the swap?

Nothing, only pcb swap.
But i don't know if user did something, he says he did nothing.

P.S.
Dick i have uploaded the rom

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

The original terminal log looks 'normal' to me.
You might consider applying the 'standard' proceedure to gain access in terminal.
Then maybe you could do some tests.

The serial number, 9QM9QMZD, is located at offset 0x61644.

That said, it does look a bit odd. Does it match the label?

The serial number, 9QM2EG5Q, of the following drive is also located at the same offset:
http://files.hddguru.com/download/PC-30 ... S_MX15.RAR

_________________
A backup a day keeps DR away.

_________________
All went well until I plugged the drive in.

Yes, it does match

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

Do you mean head insulation for standard procedure?
I tried HDA insulate, motor insulate and both, when i reach level T i get error on spin down "Z" command.
I get error also on smart reset "N1" in level 2.

P.S.
I swapped the pcb because with the original the drive doesn't boot, it spins and after few seconds spins down.
I don't hear clicking sounds and the drive is detect in bios as STM3500320AS only after the spindown.

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

I changed the donor pcb again with a new 100466725, now this doesn't appear anymore:


but i always get LED error on spin down and spin up, i tried in all ways (insulation on HDA, motor insulation, both and neither).
I think heads are damaged!!

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

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

I am suggesting to short the read channel. This proceedure has some risk!!!
There are posts on how to do this.

As i know read channel must be shorted if there is any communication with the drive via terminal, but i have communication.
Dick are u a DR pro?

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

Your ROM is damaged. Probably some checksum issue within the ROM file. Does it power well, or does it make a 'poor' attempt to start then stops?

Was this the same symptoms you had when you instantly receive it?

Also, 'MX1A' does not need shorting

Yes, poor attempt to start (some kind of clicking but are not really clicking), seem heads have not enought power to move, then it spins down.
Yes the same symptoms since i received it

So you think it's a rom checksum issue?
How can i solve it?

P.S.
I uploaded the rom in this thread

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

Here is an idea in terms of research:
If 100% sure your donor PCB is good (PCB B), then source another PCB with the same etch code as the patient's (PCB C).
Move the ROM from PCB C to PCB B. Do you get the same error "Bogus ISR"? If yes, then you just replicated the same outcome, indicating incompatibility.

If outcome is different, then you know what's up.

Hope this helps.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

The first pcb donor was not good, second donor is good.

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

With native ROM on the original PCB client sent, do you see same error when PCB is isolated?