ST31000528AS FW: CC38 Problem -New

gps31

Member
Today i got one hdd without any label with non-detected condition

i tried to read system files through terminal, from that i got the information about HDD

Model: ST31000528AS with CC38 Firmware

i can read many both copies of sysfiles from hdd through hyperterminal except

the important sysfiles 28,35 30A, and 134,135,136,137,138,139,140,143,301,306 when tried i got
"DiagError 000000E"


so i tried write copies of these from other same model hdd with same firmware CC38.

the writing these files goes without error in both copies. But when hdd repowered i m getting same error for all those sysfiles mentioned above.

i tried to write one sysfiles, after successful writing tried to read it then getting the same error

View attachment Sysfiles_readed.rar these are from that hdd

What is the problem ? what i have to do?
 

Jared

Administrator
Staff member
First off, are you trying to refurbish this drive or recover the data? If you want to recover the data, then you shouldn't be indiscriminately writing donor system files to it. Some are drive specific and can't be replaced.
 

gps31

Member
to recover data

1. i have already successfully recovered datas by writing sysfile 28 and 35 from donor drive then regen translator
2. same time 346 also transferred in some drives

No other system files
 

gps31

Member
i tried PCB with ROM trans, now i got the sames error to read those mentioned files.

but now i tried to write 28 & 35, success as previous but now i can read them back again immediately or re-powered without problems.

now i need which of these sysfiles 134,135,136,137,138,139,140,143,301,306 interchangeable

my thoughts pls correct me if it is wrong

134 (mod 0A) contains drive serial number so it should be drive dependent
135 (mod 35) no drive detail
but don't have idea about others

Note: i can use clear smart with success and i4,1,22 with success even can issues translator commands like m0,6,2 & m0,6,3 with success and can issue congen.

waiting for further ideas
 

Jared

Administrator
Staff member
It's really hard to give ideas when you don't have professional equipment to even give a proper diagnosis. For example, without knowing what the drives status registers are reading when you're attempting to read/write modules you really can't know if the modules/SA are damaged, or if the drive is just getting stuck busy and not responding for some reason unrelated to those modules. My first thing I'd go to is to disable all functions in system file 93, just in case that is the issue.
 

gps31

Member
i can sent sysfile 93 can u help me by disabling everything unwanted (if possible disable smart)

View attachment FILE_3_093_0.rar

Note:
1. Drive comes with no label
2. I have no pc3k(My in-ability & local charges given by customer )
3. I had read all 256 tracks without error but only mistake i read it after writing sysfile 28 and 35
4. if need i can upload that tracks
 

lcoughey

Moderator
We understand that you don't have PC3K. The big question is, what tools do you have to work with?
 

lcoughey

Moderator
I suggest you consider outsourcing it to a lab with proper tools and experience rather than risk your client's data while you learn and play with cheap programs.
 
Top