The HDD gets ready but remains busy and is not identified. Does not allow to enter in kernel mode also.
Isolated the head contact. Could enter in kernel mode.
Blocked service area and restarted normal.
Not identified. Uploaded Dir in RAM
Restarted. Could save all modules.
Loaded module 11 and HDD is identified.
But doing anything , it shows Techno Key error.
Any solution please
Peculiar Problem in WD400AAKX
Moderator: Maxim_TS
Re: Peculiar Problem in WD400AAKX
Sorry The Model is WD500AAKX
Re: Peculiar Problem in WD400AAKX
What is Techno Key error.
Also can not save modules by ID.
Can read all modules by ABA
Also can not save modules by ID.
Can read all modules by ABA
- DataMedics
- Advanced user
- Posts: 619
- Joined: 14.12.15
- Reputation: 18 / (177)
Re: Peculiar Problem in WD400AAKX
Techno key is the vendor specific command that PC-3000 first initiates with the drive to put it into "techno" mode so you have advanced functions like reading & writing RAM, SA modules, etc.
Here's what I'd try first. With the SA blocked in ROM, backup the modules (as you already did), then perform slow responding fix to the drive. Re-enable SA access in ROM, and reboot firmware. Then see if it still gets stuck busy when you read ID.
Here's what I'd try first. With the SA blocked in ROM, backup the modules (as you already did), then perform slow responding fix to the drive. Re-enable SA access in ROM, and reboot firmware. Then see if it still gets stuck busy when you read ID.
- Amarbir[CDR-Labs]
- Advanced user
- Posts: 784
- Joined: 03.08.09
- Reputation: 8 / (80)
Re: Peculiar Problem in WD400AAKX
Imnew wrote:Source of the post The HDD gets ready but remains busy and is not identified. Does not allow to enter in kernel mode also.
Isolated the head contact. Could enter in kernel mode.
Blocked service area and restarted normal.
Not identified. Uploaded Dir in RAM
Restarted. Could save all modules.
Loaded module 11 and HDD is identified.
But doing anything , it shows Techno Key error.
Any solution please
Hello ,
Do Test Heads And Once You oad dir module and loader module to ram ,Try to test heads if you see some head is not ok isolate it in ram headmap function ,Soft reset the drive
Regards
Amarbir S Dhillon ,CDR Labs [ Chandigarh ,India ]
DataRecovery - The Affordable Way In India
Visit - > http://www.chandigarhdatarecovery.com My Facebook - > https://www.facebook.com/chandigarhdatarecovery
Amarbir S Dhillon ,CDR Labs [ Chandigarh ,India ]
DataRecovery - The Affordable Way In India
Visit - > http://www.chandigarhdatarecovery.com My Facebook - > https://www.facebook.com/chandigarhdatarecovery
Who is online
Users browsing this forum: No registered users and 13 guests
