HTS723232A7A364 who not read after LBA 67472372...

[avenger-fr]

Hi !
I have a HITACHI HTS723232A7A364, the drive is not recognized automaticaly but only when we force the start of utility manualy. Then it's well recognized.
In data extractor we can read from LBA 0 to 67472372 and not after ... (sometimes the drive don't respond and we must restart utility for make a good detection of drive...)
The drive have some problems in FW , maybe the problem is in P-List ?

Can you help me ?

[ACE_Admin]

Three methods to try.

1st try to fix damaged PSHT module in 0th copy
2nd try to load up the PSHT module to RAM (from Tools->HDD Resources view and edit)
3nd method requires heads swap. Hard drive is not able to initalize with current heads stack, so, heads stack from good working drive will most likely work

[ThomasH]

I have a HTS727575A9E364 that sounds like it's experiencing the same.
It came in with stuck and bent / flaked heads.
Headswap goes ready, but no model/sn id.
Playing with it by forcing detect, making sure to uncheck "pcb only" usually detects the drive properly.
I backed up modules, and the recovered group of them seemed about the same or the same as the donor (before i took it apart)...wish I saved log to be sure 100% the same.

When entering DE, when deselecting 'hardware reset and software reset' on the selection screen, it does actually detect. Leaving hardware/software reset enabled stops detection in DE.

All 4 heads image full speed until sector 5,482,007.
Then it's all fast, black ABR errors, like a drive with bad translator.

I saved both copy0 and copy1 of PSHT, and compared them in winhex with 32 differences.
I'm not sure if that's normal, or a likely indicator of a problem / psht corruption. Anyone know?

Haven't tried overwriting copy0 with the saved copy1 yet, mainly because I haven't seen this issue yet, and do have some concern about drive stability.

I can't figure out the option (2) listed above about loading the PSHT to RAM....

Suggestions?

[AJ2008]

This is from ARM based Hitachi?

Problem is non-native heads that are not compatible enough.

Seems heads are compatible that ID can be reached if 'forced' but in all cases where ID is not readily available only partial translator seems to be accessible.

Return donor heads to donor and preserve for other cases, try second headswap with second part that could be more compatible.

As far as I know there is no logic behind the compatibility requirements for these ARM based Hitachi, and no external references to help identify compatibility...

[dobrevjetser]

I have the same model that can only read up to sector 637797.
Module 0 of psht is damaged and cannot be rewritten.
When i try to edit plist drive hangs which is strange since module 1 of psht is ok.
It is also loaded correctly in ram.
I copied this module to a working drive and there i could view its contents, but there doesnt seem to be entries for that sector.
When i try to add a sector to the plist nothing seems to happen. There is no window popping up where i can insert a new entry. 'Add' is in the menu but its not working

Any solution to this case ?

Marc

[dobrevjetser]

Forgot to say that heads can write without problem. I tried it on some good modules.

Marc

[dobrevjetser]

anyone has formula to calculate chs from lba so i can add a bad sector to plist ?

[avenger-fr]

I have made all tests recommended by Roustam. Rewrite many times PSHT : don't work. Upload PSHT directly in RAM : don't work. Change Heads (2 times) : don't work. The drive can't rewrite PSHT modules, I can read the PSHT copy 0 and copy 1, compare and reassemble a good one in hex editor, but can't write !!!
The drive read correctly the start of user area but nothing more (and can write too, I have test it).

Roustam, please, is it possible to make an hotswap for these series ? Or is it possible to reallocate the PSHT copy 0 module somewhere else ?

Apparently the problem exists on this series (we have a 5 differents persons who have the same problem)...

[redlabs]

I have also the same problem any one

Hi !
I have a HITACHI HTS723232A7A364, the drive is not recognized automaticaly but only when we force the start of utility manualy. Then it's well recognized.
In data extractor we can read from LBA 0 to 67472372 and not after ... (sometimes the drive don't respond and we must restart utility for make a good detection of drive...)
The drive have some problems in FW , maybe the problem is in P-List ?

Can you help me ?

[Nick_TS]

Hello,

Try to initialize translator in RAM.

[john]

I have also the same problem .but this model: Hitachi HDS721050CLA362

initialize translator in RAM. not valid

Module RDMT Copy 0...................... : Ok

Module PSHT Copy 0...................... : Ok

Module CHNM Copy 1...................... : Ok

Module PSHT Copy 1...................... : Ok

Module RDMT Copy 1...................... : Ok

Module SRVM Copy 0...................... : Ok

Module SRVM Copy 1...................... : Ok

Module ZONE Copy 0...................... : Ok

Module ZONE Copy 1...................... : Ok

Module RPSH Copy 0...................... : Ok
Module RPSH Copy 1...................... : Ok
Module USAG Copy 0...................... : Ok
Module USAG Copy 1...................... : Ok
Module RAMI Copy 0...................... : Ok
Module RAMI Copy 1...................... : Ok
Module RAM0 Copy 0...................... : Ok
Module RAM0 Copy 1...................... : Ok
Module RPOP Copy 0...................... : Ok
Module RPOP Copy 1...................... : Ok
Module SECI Copy 0...................... : Ok
Module SECI Copy 1...................... : Ok
Module ALTT Copy 0...................... : Ok
Module ALTT Copy 1...................... : Ok
Module SRVP Copy 0...................... : Ok
Module SRVP Copy 1...................... : Ok
Module IDNT Copy 0...................... : Ok
Module IDNT Copy 1...................... : Ok
Module SMRT Copy 0...................... : Ok
Module SMRT Copy 1...................... : Ok
Module SERL Copy 0...................... : Ok
Module SERL Copy 1...................... : Ok
Module IOPS Copy 0...................... : Ok
Module IOPS Copy 1...................... : Ok
Module SSLD Copy 0...................... : Ok
Module SSLD Copy 1...................... : Ok
Module SCTH Copy 0...................... : Ok
Module SCTH Copy 1...................... : Ok
Module FEAT Copy 0...................... : Ok
Module FEAT Copy 1...................... : Ok
Module CNFG Copy 0...................... : Ok
Module CNFG Copy 1...................... : Ok
Module WWNM Copy 0...................... : Ok
Module WWNM Copy 1...................... : Ok
Module SPTR Copy 0...................... : Ok
Module SPTR Copy 1...................... : Ok
Module ELG1............................. : Ok
Module EVLG............................. : Ok
Module PID1............................. : Ok
Module PID2............................. : Ok
Module PIDM............................. : Ok
Module HLR1............................. : Ok
Error startintg command: Reading SA [0x3F0103E95, 0x5]
Device error detected (UNC)
Error startintg command: Reading SA [0x3F0103E95, 0x1]
Device error detected (UNC)
Module HLR2............................. : Error
Module MFGP............................. : Ok
Module AMPM............................. : Ok
Module MFGT............................. : Ok
Module DMP1............................. : Ok
Module SDM1............................. : Ok
Module SVLG............................. : Ok
Error startintg command: Reading SA [0x3F0003E2D, 0x2]
Device error detected (UNC)
Error startintg command: Reading SA [0x3F0003E2D, 0x1]
Device error detected (UNC)
Module DDD0............................. : Error
Module DIAG............................. : Ok
Error transferring command data: Reading SA [0x3F0008800, 0xF]
HDD Data timeout
Error startintg command: Reading SA [0x3F0008801, 0x1]
Device error detected (UNC)
Module WRT0............................. : Error
Error transferring command data: Reading SA [0x3F0108800, 0xF]
HDD Data timeout
Error startintg command: Reading SA [0x3F0108801, 0x1]
Device error detected (UNC)
Module WRT1............................. : Error

[Maxim_TS]

Hello everyone,

Translator initialization procedure in RAM has been improved in last PC-3000 versions, so this problem could be solved now easy.