Hitachi PSHT and RDMT Firmware Question

[ddrecovery]

When uploading the PSHT and RDMT into RAM, is matching firmware important, or just the drive model? In this case its a HTS541075A9E680.

[jono-ats]

Do you know how the P List and G List work?

You upload them into from the patient drive you are working on -- not a related drive.

[shahij]

You need original from the patient

[ddrecovery]

Maybe I am not understanding your responses, or didn't phrase the question well. Jono, yes of course I know about G-List and P-List, I think you know that .

While in the PC3000 Hitachi utility you get the option to upload these from the drive (if possible) or from an external file. Quite often you are able to gain access to a drive by uploading a PSHT and RDMT from a drive of the same family. I have done this many times before. Here is a link to Ace Labs report. My question was just about firmware.

http://blog.acelaboratory.com/pc-3000-h ... lator.html

[pcimage]

Sorry to say, but I don't see how PSHT from another drive will allow proper access.

What Ace are meaning from that post is that if the PSHT (and possibly RDMT) aren't loaded into RAM due to not reading properly (e.g. Bad copy 0 as in their example) you can load into RAM from file, where the module(s) has been extracted from the patient, either by from copy 1 or by composite reading.

Someone please correct me if I'm wrong

[fzabkar]

What Ace are meaning from that post is that if the PSHT (and possibly RDMT) aren't loaded into RAM due to not reading properly (e.g. Bad copy 0 as in their example) you can load into RAM from file, where the module(s) has been extracted from the patient, either by from copy 1 or by composite reading.

That's the way it reads to me.

[jono-ats]

You can get away with loading RDMT from another drive. PSHT (P-List) is, AFAIK, an altogether different prospect.

No disrespect intended, but I don't understand how a foreign P-List would give you access to another drive's data, UNLESS the utility reset the drive's POST flag and you were, in fact, reading from the patient P-List -- not RAM.

If you want to try a little experiment, copy P-List from another drive to an experimental patient drive and tell us if you get LBA access. I'll bet you lunch you won't.

Jon

[data-medics]

Sorry to say, but I don't see how PSHT from another drive will allow proper access.

What Ace are meaning from that post is that if the PSHT (and possibly RDMT) aren't loaded into RAM due to not reading properly (e.g. Bad copy 0 as in their example) you can load into RAM from file, where the module(s) has been extracted from the patient, either by from copy 1 or by composite reading.

Someone please correct me if I'm wrong

Sounds exactly right to me. I can't say I've ever even attempted uploading a foreign PSHT though, never seemed like it made any logical sense to try.

[ddrecovery]

I have seen Ace Labs use a 'donor' PSHT to get LBA access to a drive. I didn't see the full recovery so I do not know what else they did. Perhaps they just got luck or know something I don't. Thanks for the input as always and not making me feel too bad at looking like a fool

[jono-ats]

I have seen Ace Labs use a 'donor' PSHT to get LBA access to a drive. I didn't see the full recovery so I do not know what else they did. Perhaps they just got luck or know something I don't. Thanks for the input as always and not making me feel too bad at looking like a fool

Nobody knows everything, and we are all learning if we are improving. I get my head handed to me regularly, like anyone who asks.