ST9500420AS; Full ID; No LBA; "CFWDC Compatibility Failed" in Terminal.

[300ddr]

Anyone ever seen this message before?

"CFWDC Compatibility Failed"

It was showing many other random messages (i.e. OP=12F; OP=10F; R/W Errors, etc), I couldn't do anything in terminal (Diagnostic Error or LED: xxxEE), and no system file access. Now, it's just:

Rst 0x10M
(P) SATA Reset
CFWDC Compatibility failed
(P) SATA Reset

What I've tried so far:
- I used donor ROM, imported adaptives, used loader, then terminal messages went away. Now, I can clear smart in terminal and regen translator (I backed up all modules, did xlator regen, finishes successfully, problem remains)
- Control+L to verify ROM has correct SN.
- I tried max heads "1" instead of "3" to rule out potential head issues, but that doesn't make any difference (and the heads all "sound" fine anyhow).
- I cleared smart via utility.
- And finally I saved and cleared then wrote back NRGL, problem remains.
- It seems to be impossible to clear A-list. Even after shorting, I get "Invalid Diag Cmd Parameters" (though oddly, I can view alist after shorting). I am able to clear smart in terminal after shorting also.
* Haven't opened yet to check for damage.
* Another note: I CAN read sectors using "Utility" reading method from sector edit (and they look correct). So it seems like a translator issue (right?).
* Perhaps of interest: FW version in ID says "0006" but technically it is 0006HPM1 (not sure if this is a symptom of another problem, or normal).

Anyone have an ideas on this one?

Many thanks,
Brian

 

[jol]

[post]5000[/post] Another note: I CAN read sectors using "Utility" reading method from sector edit (and they look correct). So it seems like a translator issue (right?)

I'm a little confused
if you can access user data using sector edit, then why is the title saying no LBA, and why do you care about "CFWDC Compatibility Failed" error ?
clone the drive charge the client case closed
BTW have you disabled everything in sysfile 93 ?

 

[300ddr]

Only if reading via Utility (Read method: Use Utility: Read in spite of error: NO). I believe this is not recommended as it may provide bad data. And it's also extremely slow.

Yes, all the stuff is off in 93.

 

[jol]

probably translator
what do you get on r28 ? and V1 ?

 

[Amarbir[CDR-Labs]]

Anyone ever seen this message before?

"CFWDC Compatibility Failed"

It was showing many other random messages (i.e. OP=12F; OP=10F; R/W Errors, etc), I couldn't do anything in terminal (Diagnostic Error or LED: xxxEE), and no system file access. Now, it's just:

Rst 0x10M
(P) SATA Reset
CFWDC Compatibility failed
(P) SATA Reset

What I've tried so far:
- I used donor ROM, imported adaptives, used loader, then terminal messages went away. Now, I can clear smart in terminal and regen translator (I backed up all modules, did xlator regen, finishes successfully, problem remains)
- Control+L to verify ROM has correct SN.
- I tried max heads "1" instead of "3" to rule out potential head issues, but that doesn't make any difference (and the heads all "sound" fine anyhow).
- I cleared smart via utility.
- And finally I saved and cleared then wrote back NRGL, problem remains.
- It seems to be impossible to clear A-list. Even after shorting, I get "Invalid Diag Cmd Parameters" (though oddly, I can view alist after shorting). I am able to clear smart in terminal after shorting also.
* Haven't opened yet to check for damage.
* Another note: I CAN read sectors using "Utility" reading method from sector edit (and they look correct). So it seems like a translator issue (right?).
* Perhaps of interest: FW version in ID says "0006" but technically it is 0006HPM1 (not sure if this is a symptom of another problem, or normal).

Anyone have an ideas on this one?

Many thanks,
Brian

Brain ,
I Have Some Counter questions for you ...

1 : I used donor ROM, imported adaptives, used loader, then terminal messages went away. Now, I can clear smart in terminal and regen translator (I backed up all modules, did xlator regen, finishes successfully, problem remains)
Questions : Donor ROM Was Same firmware ? .Why did You Need To Use Loader "Was The Loader Made Using Same HDD SA ? " .

2 : Control+L to verify ROM has correct SN
Questions : This is With Donor ROM Code And Native Adaptives Or Native ROM Code and Adaptives ? ,Same Serial No is a Relief

3 : I tried max heads "1" instead of "3" to rule out potential head issues, but that doesn't make any difference (and the heads all "sound" fine anyhow).
Questions : Were did you do this ?

4 : I cleared smart via utility.
Questions : Contrary To Many DR Guys Who Just Jump To Clear This and That i Rarely fiddle With even Smart ,How Many times in Reality has clearing smart helped ?

5 : And finally I saved and cleared then wrote back NRGL, problem remains.
Questions : You Have NRGL Entries in This Drive ?


6 : It seems to be impossible to clear A-list. Even after shorting, I get "Invalid Diag Cmd Parameters" (though oddly, I can view alist after shorting). I am able to clear smart in terminal after shorting also.
Questions : Why Are you Bothered To Clean It ?

7 : Haven't opened yet to check for damage.
Questions : Kindly Do This to Please And i am 100% Its Not a Head Issue

8 : Another note: I CAN read sectors using "Utility" reading method from sector edit (and they look correct). So it seems like a translator issue (right?).
Questions :To Verify this Try Scanning Media Of this Drive and One Point There Should Be a Full Stop and All Sectors After That Would Be Having a Issue .Specially This is True if You Have NRGL List With entries

9 : Perhaps of interest: FW version in ID says "0006" but technically it is 0006HPM1 (not sure if this is a symptom of another problem, or normal)
Questions : FW Can Kiss My $%$%#$ :mrgreen: .We will Nail This Drive so That It starts Oozing Out DATA

 

[300ddr]

probably translator
what do you get on r28 ? and V1 ?

This is with the original ROM:

Rst 0x10M
CFWDC Compatibility failed
(P) SATA Reset

(P) SATA Reset

ASCII Diag mode

F3 T>r28

Invalid Diag Cmd

F3 T>V1

LED:000000EE FAddr:00104138
LED:000000EE FAddr:00104138

 

[300ddr]

":6sm7ievt]
Questions : Donor ROM Was Same firmware ? .Why did You Need To Use Loader "Was The Loader Made Using Same HDD SA ? " .

Yes. I didn't "need" a loader, just used it for testing. It was the loader from the donor ROM.

":6sm7ievt]
Questions : This is With Donor ROM Code And Native Adaptives Or Native ROM Code and Adaptives ? ,Same Serial No is a Relief

Native.

":6sm7ievt]
Questions : Were did you do this ?

"Work with Flash ROM image file"

":6sm7ievt]
Questions : Contrary To Many DR Guys Who Just Jump To Clear This and That i Rarely fiddle With even Smart ,How Many times in Reality has clearing smart helped ?

It definitely works at times (and may improve imaging speed). And AFAIK, can't ever hurt the drive.

":6sm7ievt]
Questions : You Have NRGL Entries in This Drive ?

Yes, 5 entries. All with "0" flag.

":6sm7ievt]
Questions : Why Are you Bothered To Clean It ?

I can actually see it with V4 after the loader, and it's empty. Just another thing to test, after backing up, that shouldn't make anything worse.

":6sm7ievt]
Questions :To Verify this Try Scanning Media Of this Drive and One Point There Should Be a Full Stop and All Sectors After That Would Be Having a Issue .Specially This is True if You Have NRGL List With entries

I will check this one.

":6sm7ievt]
Questions : FW Can Kiss My $%$%#$ :mrgreen: .We will Nail This Drive so That It starts Oozing Out DATA

 

[300ddr]

SOLVED! PCB swap was solution. So simple!

Edit: also needed a "recover translator."

 

[Jared]

":h22l7y9w][post]5013[/post] "Was The Loader Made Using Same HDD SA ? "

I don't think it matters. All drives of the same family & firmware use the same loader I think. Though I can't say I honestly have even used SG loaders much. I think I only had one or two cases where it was actually necessary and actually helped.

 

[jol]

[post]5018[/post] SOLVED! PCB swap was solution. So simple!

Congrats

Edit: also needed a "recover translator."

didn't thought otherwise