Page 1 of 1

HTS547550A9E384 No SA access / No ID

Posted: 01.07.16, 08:55
by zeroalpha
We have changed PCB and Heads with suitable donor on this drive but can't get any access. ROM is readable but no crucial modules. Drive spins up and we can hear heads come out. Drive continues to spin. Comes ready quickly. Same symptoms with new heads and new pcb.

Selected family......................... : 5475A9
Model by ID............................. : <ID IS NOT READ>

Techno mode key......................... : Ok

Error startintg command: Reading SA [0x3F0000004, 0x4]
Device error detected (ABR)
Error startintg command: Reading SA [0x3F0000004, 0x1]
Device error detected (ABR)
Error reading module USAG(0): Error startintg command: Reading SA [0x3F0000004, 0x1]
Device error detected (ABR)
Error startintg command: Reading SA [0x3F0100004, 0x4]
Device error detected (ABR)
Error startintg command: Reading SA [0x3F0100004, 0x1]
Device error detected (ABR)
Error reading module USAG(1): Error startintg command: Reading SA [0x3F0100004, 0x1]
Device error detected (ABR)
Loading modules table................................................. : Error
Error : .............................................................. : Module USAG: no copies read!
Loading the table of "open" modules................................... : Error
Error : .............................................................. : Error executing loading "open" modules dir command

Re: HTS547550A9E384 No SA access / No ID

Posted: 19.07.16, 20:00
by Filipp_TS
Hello,

Looks like this is problem directly with USAG module.
As result drive can't to recognize SA modules table.

Re: HTS547550A9E384 No SA access / No ID

Posted: 29.07.16, 09:09
by zeroalpha
Filipp_TS wrote:Source of the post Hello,

Looks like this is problem directly with USAG module.
As result drive can't to recognize SA modules table.

Hi Filipp,

Any solution to this?

Re: HTS547550A9E384 No SA access / No ID

Posted: 06.08.16, 08:36
by lifeguard
NO Solution so far i think from ACE about this Problem...

Re: HTS547550A9E384 No SA access / No ID

Posted: 12.09.16, 18:43
by Filipp_TS
zeroalpha wrote:Source of the post
Filipp_TS wrote:Source of the post Hello,

Looks like this is problem directly with USAG module.
As result drive can't to recognize SA modules table.

Hi Filipp,

Any solution to this?


Hitachi drives haven't a something alternative reading mode (like HotSwap, Kernel etc) except original ATA mode.
That's why we can't to get SA access for checking SA modules and the only way is test drive with the donor parts from the donor Drive(s).
Try to set the donor PCB with the patient ROM and take a look on drive behavior.
Also you can check this drive inside and set the donor Heads.

Re: HTS547550A9E384 No SA access / No ID

Posted: 24.11.16, 18:34
by dataq
Hi zeroalpha,

Did you get anywhere with this drive. Or does anyone have a solution. We have a HTS545050A7E362 with same symptom and have carried out the same rework with no success. I would appreciate any ideas.

Re: HTS547550A9E384 No SA access / No ID

Posted: 28.11.16, 18:11
by Filipp_TS
Hello,

Possible way has been provided in my previous message.
Unfortunately no other solutions.

Re: HTS547550A9E384 No SA access / No ID

Posted: 22.01.17, 22:10
by avalanche
I currently have a one of these in; same symptoms of failure. Drive sounds good, enters RDY quickly but just gives ABORT errors. USAG is not readable. Donor PCB and/or donor heads make no difference.

Has anyone come to a solution for this ? I presume not due to the limits of the Hitachi architecture.

Thanks,
J

Re: HTS547550A9E384 No SA access / No ID

Posted: 01.05.18, 04:31
by Trouse
Hello,
Is there any updated solution for this issue? Thanks!

Re: HTS547550A9E384 No SA access / No ID

Posted: 11.05.18, 16:23
by Maxim_TS
Trouse, if SA and NV-RAM are good, there is a way to initialize the patient using the resources from same FW donor drive described here: http://blog.acelaboratory.com/hitachi-i ... -mb-2.html

Re: HTS547550A9E384 No SA access / No ID

Posted: 07.10.19, 17:12
by jojo2012
Maxim_TS wrote:Source of the post Trouse, if SA and NV-RAM are good, there is a way to initialize the patient using the resources from same FW donor drive described here: http://blog.acelaboratory.com/hitachi-i ... -mb-2.html

Maxim, I have a similar case, but I think the method described in the blog is useless if the patient cannot reach the SA and therefore read the most important modules and save them (as described in the article).