WD6400BEVT - acess to SA but not data (ERR UNC)

[hddr49]

Hi there

another case where I can't find what's wrong. Maybe heads...

This drive WD6400BEVT is a system disk

Originaly, seems to be slower and slower, windows make f***g scandisk everytime.
Further, no access at all (scandisk says unrecoverable errors)

I have access to SA, backup everything with errors. Here is the log wher errors are :

Code:

Module : 32............................. : Module 0032 reading error ABA 2837 reading error - Device Error Detected: "DISK ECU UNSAFE ERROR"
Module : 32............................. : Module 0032 reading error ABA 235541 reading error - Device Error Detected: "DISK ECU UNSAFE ERROR"

Module : 2E............................. : Module 002E reading error ABA 22698 reading error - Device Error Detected: "DISK ECU UNSAFE ERROR"

Physical read error C/H/S: -231/0/59 - Device Error Detected: "DISK ECU UNSAFE ERROR"
Cyl -231; Head 0........................ : Break
Physical read error C/H/S: -232/0/909 - Device Error Detected: "DISK ECU UNSAFE ERROR"
Cyl -232; Head 0........................ : Ok
Physical read error C/H/S: -253/0/134 - Device Error Detected: "DISK ECU UNSAFE ERROR"
Cyl -253; Head 0........................ : Ok
Physical read error C/H/S: -253/1/113 - Device Error Detected: "DISK ECU UNSAFE ERROR"
Cyl -253; Head 1........................ : Break



When I try DE, partition table is empty, and ERR UNC appears on scan


What I try :
Module 2E : write copy 1 over copy 0 : ok
Module 32 : write copy from another disk (not same FW)

Original WD6400BEVT-60A0RT0-01-01A01 FW 001300CB
Implanted WD6400BEVT-80A0RT0-01-01A01 FW 0014003R

Translator regeneration

Here are errors in SA structure test :

Code:

002D: 0  :    Dr     : 22239: 450:Yes  :Error: Ok  :    6171BFD3     :00020004:Debug Log                                   
002D: 1  :    Dr     : 22239: 450:Yes  :Error: Ok  :    6171BFD3     :00020004:Debug Log                                   
002E: 0  :    B      : 22689: 450:Yes  :Error: Ok  :    7266852E     :00020004:Loaded part of microprogram code             
002E: 1  :    B      : 22689: 450:Yes  :Error: Ok  :    7266852E     :00020004:Loaded part of microprogram code             

006F: 0  :    B      : 23412:2144:Yes  : Ok  :Error:00000000/F64E8F26:AOZ30000:Loaded part of microprogram code             
006F: 1  :    B      : 23412:2144:Yes  : Ok  :Error:00000000/F64E8F26:AOZ30000:Loaded part of microprogram code             



I think of firmware corruption in 2D 2E 6F modules...

and you ?

edit : on power up, the drive is ready, and motor spins normally, no click sound, all seems ok.

[labtech]

I think of firmware corruption in 2D 2E 6F modules...
and you ?

Most failed drives have errors on these modules. Problem is likely somewhere else.

Have you completed any heads testing?

[hddr49]

Yes, I had completed head test on cyl -10 and -100 without any errors

[data-medics]

Open the modules table and run a check on all modules. Could be another module that's tweaked.

[hddr49]

Had several errors for now :

006F CS error (cs value 00000000)
2045 CS error (cs value FE28F2D1)
2043 Header error (size 450)
2044 Header error (size 450)

not finished yet to check then 1 by one, I fist check those with errors on sa check and hardware check.

[hddr49]

I confim that only those 4 modules have errors in individual module check.

for 2043 to 2045, i rewrite module from file (sabackup of original drive) and recheck, and is ok.

6f is not ok and still CS error

do you think I safely can try to rewrite it from another drive ?

Original WD6400BEVT-60A0RT0-01-01A01 FW 001300CB
Implanted WD6400BEVT-80A0RT0-01-01A01 FW 0014003R

[hddr49]

i answer myself : no, it can't.
Writing is ok, but checkin is error (with cs error and cs value not fill with zeros anymore)

So, if somebody has it...

[data-medics]

To be safe when overwriting modules, you should use a drive with the same FW. Also watch the color coding in the table to know whether it's drive specific or can be transplanted. Some modules can be taken from a drive of the same FW, some are drive specific and can't be transplanted, and some you can steal from just about any old drive. It really all depends.

Just make sure to keep a backup of the original. Composite read, and read from each head. That way you can always go back.

You might also be dealing with media damage where it simply can't read the modules. I which case you might have to perform a smart hotswap.

[hddr49]

thanks for advices.

backup of original is first thing I do as soon as i can on every drive comes to me.
Let's try to find a donnor...

[hddr49]

strange thing...

I find a PCB Donnor (a full donnor is on the way), but when I connect it on PC3000, It shows as Jamaica, instead of Mariner for my Patient... and can't do anything with it, of course...

[hddr49]

yes, the drive is on his way to my office right now...

[hddr49]

I receive the drive...

Patient : WD6400BEVT-60A0RT0 Firmware 01.01.A01
ROM Firmware version 001300CB

Donnor : WD6400BEVT-60A0RT0 Firmware 01.01.A01
ROM Firmware version 0014001B

Are those compatible enough to perform hot swap ?

I try to write module 6F from donnor to patient, but by id it says wrong size, and by ABA writing is ok but check is wrong

When I just put donnor PCB on patient drive, it shows RDY but can't read ID

any advice ?

thanks

[thatdellguy]

This post is wrong on so many levels but damn entertaining!

[hddr49]

please to give you some joy...

I accept any kind of advices, so I'm waiting for yours too