Spot on answer BGman

_________________
All went well until I plugged the drive in.

On IBM native you only need PCB to read/write PBAs as long as you know the PBA + VSC + Super On.

On ARM IBM native you do need a "loader". On both cases as long as you know the PBAs yourself you don't need to have a valid USAG.

So SeDiv can create ini files with "road map" so that you can read/write modules even if the drive no longer properly initialize.

Meaning if you clear SA and if you clear USAG you have no way to gain access to the rest of modules or original module location but if you have INI with definitions of "map" for the SA you can read/write to those spots by PBAs.

This is the same as MRT does with that option to load to the MRT software the definitions to know where MRT should read/write modules.

SeDiv does allow to use the ini file or as alternative you can as well supply a USAG module for SeDiv to use as the directory in case USAG can't be read from the drive.

Since i was "playing" with that ARM based drive i might have done something wrong and i might have dumped the SA using the ini definitions instead of using the USAG of the drive.... SeDiv do support 3 ways... ini file, usag of the drive and external usag. When you do have the valid USAG or when the drive initialize properly you can save the module directory to ini ....

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Spildit,
Please contact me
Whatsapp +79176782880
email Jubtcrussia@gmail.com

HUS724040ALA640-MFAOA8G0

~~~~
I don't understand, who helped me create a LOD?

If you are asking for someone to create a loader for you, then you might like to try this tool:

http://www.hddoracle.com/viewtopic.php?f=59&t=2696&p=20039&hilit=hitachi+loader+tool#p20039

It's untested, so it may not work.

_________________
A backup a day keeps DR away.

The firmware uploaded above is the one click backup firmware of PC3K

I'm talking about generating and creating LDR

Not at Loader LDR

Hi there!
It's a relative old post, but i need help too for creating loader.

The drive came with no ID, spins up, and some head movements puts itself DRDY, but no SA access.
I swap heads, the result is a same, no ID.
After i edited NvRAM from 03-02-01-00 to 02-02-01-00 then had ID, downloaded SA copy 1 and had LBA access with heads 1-2-3.
Now i'm stuck with this case, no matter how i change NvRam, the drive not initialising.
I have tried create loader by own (using SA copy 1) and upload to SeDiv, but the drive still not have ID. Maybe i f.cked up my loader, i think i don't understand right the srtucture of ARM loader file.
I wrote a letter here for drHDD, but as i seen he visited hddguru 3 months ago.
So please somebody help me create a loader to rewrite SA with SeDiv.
I have MRT too, but MRT is not have possibility for upload microcode to RAM.
We tried initialise drive with PC3K using copy 1 source and rewrite SA in my friend's lab, but no luck.
So i think my last hope left using hddguru community asking for help.
I uploaded SA copy here if it helps:


Thank you!

Hi there.
@fzabkar tool won't work for you because you are missing modules on your dump/resource.
You USAG have reference to modules that are missing from your package/attachment :



This was some years ago and i don't remember very well the procedure as well but i can hook a ARM Hitachi to my HRT in a moment to see if i refresh my mind over this ...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

there are some common mistakes in this process, i can probably recover it but the question is wether that one missing surface is worth starting it over...

_________________
Adatmentés - Data recovery

Hi!
Yes, i tried this tool too, with same result as yours.
Comparing the patient USAG module with another same donor drive USAG module and module package (module names/number) are a same.
fzakbar's tool is created for A7E ARM drives. It' not a miracle that tool is not handle CLA3 Hitachi drives.
Strange that PC3K, MRT, and Sediv can't create loader files using module source as theese tools can create loader for WD, Sea, etc....drives.

PC3K should be able to create the loader... In fact that was how I got the first loader to try with ... It was created with PC3K ... Check the start of this thread.

Also my drive was fully working when i extracted the modules so the loader was made with modules native for that drive...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Ok ... This is your USAG ...



So yes.... There are NO RPSP, etc .... so the tool will NOT WORK for you.

I waas thinking that It could had been some sort of firmware tool bug but guess not ...

On IBM/ARM you don't read modules by ID like on WD, you read by location on platter, so you go to USAG and get the location to use on the VSC for reading the next module and so on...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I do have to re-learn this stuff again ... I don't have any CLA here with me but for example this is an HCC545050A7E380, I do send the super on and read the USAG and get this :





So USAG is at 04 00 00 with sector count of 6.

Now if i want for example SECI it would be at A0 8B 00 with a sec. count of 3

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

So ... If you READ all of your modules and pack it on a file with the same format that PC3K uses you then can send it to drive RAM by download microcode and it doesn't matter that the address of modules is not correct on RAM because once you gain access to READ you are going to READ in the platter using physic address and NOT module ID so it's not harmfull to have on RAM table that doesn't match platter. You just need to gain access to READ/WRITE command so that you can check what you trully have on platter.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Maybe try to manualy patch the PC3K built loader with the modules of your drive ? At any rate you told us you have access to PC3K and it can create loader....

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I've been away for many time but i'm starting to remember now .... I need to practice more, during the weekend i will play with this, i will dump all modules of some ARM HGST with HRT and I will try to create a loader using that ones done by PC-3000 by replacing the sections with the modules from my drive, then i will try to block reading and load from loader by sending using download microcode standard ATA and then i will check if loader done by hand does allow reading SA like the ones provided by PC-3000. Need to test with this to start to remember again because I spend almost 4/5 years without even looking at a HDD so it's natural that i did forgot many things.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

But in theory if heads are OK and surface is OK if you do have a correct fully compatible loader you should gain access to SA... I would start by checking if you can make a loader using the modules that you already have with the PC-3000 that you have access to...

If you can't make progress I will ask you to wait for the weekend because i will have time to play with this and i will try to make a loader by hand and test. I do have some CLA3 drives (at least here on my database file it shows that i should still have 3 fully working and refurb. that i fixed on the past and didn't sell so i will have to try to find them as well). I do have a pile of 500 GB HCC ones that I was refurb. 5 years ago to sell on ebay and the majorty of those can still be re-used and i will have to check on those as well so maybe i will start by trying with those as I do have plenty and are here at hand. I will have to go check the pile of boxes with drives that i have lying here to find the CLA ones that aparently i should still have...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Spildit, thank you for your time!
If i understand right, if we create a pcr file with PC3k, and i rename it to LOD extension will it be good for upload to RAM by Sediv?
I have a donor drive with same model number, and fw microcode.
Tried hot swap using this method (with no luck):
1.Donor in sleep mode, and uploaded modules to RAM wich contents are not a same with patient modules:
psht*
rdmt*
rpop*
seci*
altt*
zone*
srvp*
srvm*
chnm*
idnt*
smrt*
feat*
cnfg*
wwnm*
2.Upload patient NvRam to donor PCB (donor PCB is still in sleep mode)
3.Put donor PCB (with contents os patient modules in RAM and NvRAM) to patient drive
4.Wake patient drive with donor PCB
5....after some clicks the patient drive gets DRDY status, but i still can't read or write SA.

I don't understand why, because comparing the patient and donor drives USAG modules are same.

surely not, since pcr is not a loader format, it is for database export/import.
Perfectly no need for hotswap if you can upload loader...

_________________
Adatmentés - Data recovery

1 - IT WOULD HELP if you READ THE ENTIRE THREAD first !!!! Help yourself first sto that we can help you then !!!

This was already posted here :

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.