Hi all, total newbie to HDD editing, so reaching out for someone to fix this.

I have a Seagate 5TB - ST5000DM00 with my wedding pics and other personal stuff on it, which has a failed board or ROM.
I have purchased another good working ST5000DM00 (exact same part number and firmware etc). But a simple board swap didnt work as expected, it shows 3GB instead of 5TB, and I couldn't see any data.
So I swapped over the ROM chips, and it didnt want to spin up at all. Something to with CRC.
So, I have both DUMP files of the ROM (labelled Good and Bad, respectively).

Can someone please help me out here. Can you copy over the Serial number from the bad ROM to the new ROM and adjust the CRC ? I have no idea how to mess with CRC.

Seriously appreciate if someone can help me out here.

What makes you think the board has failed?

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

I said board or ROM.

I'm a hardware guy, not a coder/programmer.
I've swapped over the board etc, and it semi works, as explained in 1st post.
I've carried out the hardware tasks, so Im thinking its a bad ROM.
Files attached in 1st post.

If anyone is nice enough to do that task for me. I cant afford to lose my wedding pics.
No they're not backed to the cloud, I dont trust cloud services with my personal stuff like this.

Thanks.

now that would be funny

Code parts match, adaptives have proper crc. A terminal output would be useful to see...

_________________
Adatmentés - Data recovery

Sigh.... I'll rephrase. What was wrong with the drive that made you think it was the pcb or the rom. FWIW you might like to drop the attitude when you're asking for help.

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

Sorry I dont know what you mean by Terminal Output.
I have no idea about CRC or how HDD codes work.

The drive failed to be detected by any OS I connect it to. Other drives work fine.
This drive only spins, nothing else. So I did the hardware swaps.

Not showing attitude. Sorry you think that. It's called PANIC ad desperation. Crying out for help.

Get a copy of The Hitchiker's Guide to The Galaxy and keep looking at its cover.


now you are saying contradicting statements.
If it was spinning then it wasn't a pcb issue most probably. If it wasn't, it could be, but we don't now, at least i don't.

Making assumptions with no knowledge will lead you to very false conclusions.
You'd probably better contact a pro in your area to sort this out.

The rom looks fine, if you did a good soldering job, drive should be spinning with the donor board.
I will make a test tho.

_________________
Adatmentés - Data recovery

your rom is fine. Tested.

pepe

_________________
Adatmentés - Data recovery

Thanks for confirming that Pepe. So probably the MCU is bad.

The bad hard drive doesnt get detected in Device Manager. But the good drive works fine.
I put the good board in the faulty drive, and Device Manager detects it but only shows up as 3.4GB instead of 2TB.

So my conclusion is either faulty board or ROM.
I'm out of ideas of which component on the board is bad, can only think of MCU now.
I'll probably swap it over from the working board.

I do a lot of board repairs, but never done hard drive repairs. I know my soldering jobs are top notch.

There were 2 ROMs in the zipped file. Did you check the one labelled Bad ?

Ive got too much going with my day job, my personal repair business, and family. I cant remember exactly the steps I took.
I'll have to get back to the drive on Monday and give you guys more accurate of what I did and if it spins now or not.
It's Friday and my brain is burnt out.

yes, tested both.

_________________
Adatmentés - Data recovery

Have you written something nice or are you burning them back? I had pushed them through pc3K but I'm always a little bit skeptical.


As before if the drive is spinning the likelihood of it being any kind of board fault is very low. If you're doing this for a client I suggest you refer them on to a recovery lab before something happens to their data.

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

i guess Franc's F3RomExplorer could test it too, but i wrote them to a donor board for simplicity and found no complaints from neither PC3k nor the board. No error msgs on terminal, just the spinup related srv failures which is normal if no hda installed.
Just as i expected (tested CRCs of Adapts prior this and code fully matched the donor rom).

_________________
Adatmentés - Data recovery

I didn't write it, although I wish I could.

_________________
A backup a day keeps DR away.

Author E123.
But this does not reduce the value of Frank.

you could... anybody could. just a matter of time...

but thx for the info, i did not follow its history...
Started to write something similar for my own purposes, but i am always in delay with my jobs and this wasn't on prioirity. I can do everything in winhex, just a bit slower. But i don't need to do tens of these per day so it's ok for now.

_________________
Adatmentés - Data recovery

Hi guys. Sorry it's been a while, had important things to do.
So I finally managed to figure out what was wrong, the BIOS chip was faulty. Used eeprom R/W to copy to new chip, and drivd works fine now.

However, I do have another identical drive which works fine, but says Health Unknown, Temperature Unknown, Power On Count Unknown, Power On Hours Unknown.
Anyone know what's wrong and how to fix it ? BIOS attached. Serial W4J16T2T

Are you saying that you have access to user data, but you can't access the SMART info?

Is the drive connected via SATA? Is it behind a RAID controller?

_________________
A backup a day keeps DR away.