Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Issues with a Red WD30EFRX-68AX9N0

November 10th, 2017, 11:47

Drive comes ready on normal mode but does not ID correct.

Model : WDC WD30EFRX-68AX9N0
Serial : WDC-ROM SN# XYZ----
Firmware : 80.00A80
Capacity : 0 MB (!) (1)

Heads number............................ : 6
Cyl Count............................... : 256

Zone allocation table................... : Ok
SA SPT.................................. : 1714

ROM:
Read ROM................................ : Ok
ROM Data size........................... : 256 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 235 833
SA regions address...................... : by default
Module 02 access........................ : Granted
SA Translator loading................... : Ok

ROM Modules:
ROM version............................. : 04.27B
ROM F/W version......................... : 00040027
Overlay F/W version..................... : 04.28B
Servo F/W version....................... : 05.2V

Heads configuration..................... : by map
Heads number............................ : 6
Heads number in use..................... : 6
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5

Service area:
Permanent overlay....................... : Loaded
SA dir reading (ID)..................... : Ok
SA Access............................... : Copy 0,Copy 1

Configuration reading................... : Ok
Master Password......................... : has not been set
User Password........................... : has not been set

All modules modules were saved with no errors on any of the copies, tried to rebuild translator and I get this failed message


Translator regeneration
Regeneration method..................... : Use P-List only
P-List Copy 0........................... : Ok
P-List Copy 1........................... : Ok
Translator regeneration error Device Error Detected: "FM ERR CHECKSUM"

I swapped the PCB just to make sure is nothing wrong with it and rebuild ROM from SA, wrote the ROM to a new ROM chip also and still have the same error message when trying to rebuild translator

Any ideas please...

TIA

Re: Issues with a Red WD30EFRX-68AX9N0

November 10th, 2017, 12:41

hdd_sand wrote:Drive comes ready on normal mode but does not ID correct.

Model : WDC WD30EFRX-68AX9N0
Serial : WDC-ROM SN# XYZ----
Firmware : 80.00A80
Capacity : 0 MB (!) (1)

Heads number............................ : 6
Cyl Count............................... : 256

Zone allocation table................... : Ok
SA SPT.................................. : 1714

ROM:
Read ROM................................ : Ok
ROM Data size........................... : 256 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 235 833
SA regions address...................... : by default
Module 02 access........................ : Granted
SA Translator loading................... : Ok

ROM Modules:
ROM version............................. : 04.27B
ROM F/W version......................... : 00040027
Overlay F/W version..................... : 04.28B
Servo F/W version....................... : 05.2V

Heads configuration..................... : by map
Heads number............................ : 6
Heads number in use..................... : 6
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5

Service area:
Permanent overlay....................... : Loaded
SA dir reading (ID)..................... : Ok
SA Access............................... : Copy 0,Copy 1

Configuration reading................... : Ok
Master Password......................... : has not been set
User Password........................... : has not been set

All modules modules were saved with no errors on any of the copies, tried to rebuild translator and I get this failed message


Translator regeneration
Regeneration method..................... : Use P-List only
P-List Copy 0........................... : Ok
P-List Copy 1........................... : Ok
Translator regeneration error Device Error Detected: "FM ERR CHECKSUM"

I swapped the PCB just to make sure is nothing wrong with it and rebuild ROM from SA, wrote the ROM to a new ROM chip also and still have the same error message when trying to rebuild translator

Any ideas please...

TIA



Hello,
Is a SA Structure Test All OK Or You Have Some Checksum Issues In Few Modules ? .

Re: Issues with a Red WD30EFRX-68AX9N0

November 10th, 2017, 12:48

Thank you Amarbir, but I had checksum all modules already this morning and all checks good even ROM modules checked ok. Kind of baffle :?

Re: Issues with a Red WD30EFRX-68AX9N0

November 10th, 2017, 13:09

Well,
i will pm you in morning i have one thing in my brain

Re: Issues with a Red WD30EFRX-68AX9N0

November 10th, 2017, 13:16

thank you, have a good night :cool:

Re: Issues with a Red WD30EFRX-68AX9N0

November 11th, 2017, 3:03

Hi,
Send Me a Request on Skype on lynx-india

Re: Issues with a Red WD30EFRX-68AX9N0

November 15th, 2017, 19:11

it's Case of Undetected HDD , u have 0 MB HDD
this error have many Reason like key Modules Corruption , Bad Sector in SA , ROM Corruption , ...

Can Solved Online , you Can Try with Amarbir .
and Update Here

Re: Issues with a Red WD30EFRX-68AX9N0

November 15th, 2017, 19:15

Amarbir[CDR-Labs] wrote:i have one thing in my brain

That one thing more than normal :P :P :P

Re: Issues with a Red WD30EFRX-68AX9N0

November 16th, 2017, 11:27

hpw333 wrote:it's Case of Undetected HDD , u have 0 MB HDD
this error have many Reason like key Modules Corruption , Bad Sector in SA , ROM Corruption , ...

Can Solved Online , you Can Try with Amarbir .
and Update Here



Hi,
I was not contacted yet ,I had solved a few cases like this few times

Re: Issues with a Red WD30EFRX-68AX9N0

November 27th, 2017, 16:57

Head swap fixed the issue
Post a reply