MCMTFileHandler: EXCEPTION: Failed MCMT not getting success

[terminator2]

I am stuck up with Seagate Barracuda which is having MCMTFileHandler: EXCEPTION: Failed MCMT issue ( DWF register is red ) .
I have read that I have to replace system file 346 , Reset Media cache and disable it with congen.
So I am trying to read this file ,reading process starts but nothing comes up on screen (file is not getting read).
What I should do now
here is what exactly happening.

Attachments

[terminator2]

I am getting "DiagError 0000000E " in terminal. File reading process starts but nothing happens afterwards

Terminal shows ---
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
End parsing container segment... BOOTFW_CONT_0
Segment: BOOTFW_CONT_1
Parsing container segment....... BOOTFW_CONT_1
Segment: BOOTFW_DIR
Parsing segment....... BOOTFW_DIR
End parsing segment... BOOTFW_DIR
Segment: GENERAL_DATA
Parsing segment....... GENERAL_DATA
End parsing segment... GENERAL_DATA
Segment: IAP
Parsing segment....... IAP
End parsing segment... IAP
Segment: BOOTFW
Parsing segment....... BOOTFW
End parsing segment... BOOTFW
End parsing container segment... BOOTFW_CONT_1
End parsing container segment... Flash ROM image
Table code segment is not found!
Detecting SA Phys Sct Size...
Result.................................. : 512
Rd Sys File: vol = 3, FID = 346, Copy = 000...
Receiving file FILE_3_346_0, length = 321536
Terminal: modem transfer unexpected code 0xD!

Attachments

[terminator2]

Case Solved = 100% data recovered.

[DeVlL]

Hi.
What has been the solution to solve the problem? I have a drive with the same problem.
Thank you

[terminator2]

Its related to system file 346 , Just try to copy original file first. Else simply copy this file from any other same family disk and write it in hard disk & your hard disk will become ready . If disk has defects in SA then possibly I dont know the solutio.

[pepe]

writing a foreing copy will render MC a pile of sht, so you practically loose what was inside, plus corrupt other data that would have been otherwise OK.
The rate of the corruption depends on how much both drives' MC was used.

pepe

[DeVlL]

Its related to system file 346 , Just try to copy original file first. Else simply copy this file from any other same family disk and write it in hard disk & your hard disk will become ready . If disk has defects in SA then possibly I dont know the solutio.

I understand that you were unable to read module 346 from the original unit and what you did was look for the module in a donor unit of the same family and model and rewrite it in its original unit. So you have access to the unit again. Is that so?

Regards

[pepe]

yes, but this solution can lead to a disaster when drives have lotta data in MC. So don't do that.
pepe

[colanco]

writing a foreing copy will render MC a pile of sht, so you practically loose what was inside, plus corrupt other data that would have been otherwise OK.
The rate of the corruption depends on how much both drives' MC was used.

pepe

+1

Surely the most important data (all those that were modified in the last sessions) have gone to the trash, I do not believe that many customers are satisfied with this type of "recovery" unless the task is not to recover but to erase safely the most important data from the disk....

[colanco]

+1

Surely the most important data (all those that were modified in the last sessions) have gone to the trash, I do not believe that many customers are satisfied with this type of "recovery" unless the task is not to recover but to erase safely the most important data from the disk....

I was wrong .... it is a grenada......

[pepe]

hm, yes, don't know why i thought it is some kind of rosewood...

[DeVlL]

yes, but this solution can lead to a disaster when drives have lotta data in MC. So don't do that.
pepe

And what would be the alternative to solve the module?

[colanco]

And what would be the alternative to solve the module?

According to what you published in another thread you have MRT... Well, MRT (and PC-3000) have a solution to this problem and for this family with only one click (or two...)

[DeVlL]

I know MRT has it, but it has never worked for me. It always gives me error. I told the MRT support and to this day they have not told me anything about why the error. So I ask if there is any way to repair the error.

[terminator2]

writing a foreing copy will render MC a pile of sht, so you practically loose what was inside, plus corrupt other data that would have been otherwise OK.
The rate of the corruption depends on how much both drives' MC was used.

pepe

Even Pepe' non relevant posts are having vital important information.
Now from this post I have learnt that on Rosewood doing anything with MC is dangerous.

Solution for one family may turn out dissasterous for other family.

[pepe]

and credit goes to Colnaco too for noticing this one is a grenada

pepe

[colanco]

:good:
and credit goes to Colnaco too for noticing this one is a grenada

pepe

Thanks pepe,

By the way... I still haven't received that extensive and precise manual in details, of ROM regeneration in Seagate F3..... maybe you forgot?......

[terminator2]

:good:
and credit goes to Colnaco too for noticing this one is a grenada

pepe

Thanks pepe,

By the way... I still haven't received that extensive and precise manual in details, of ROM regeneration in Seagate F3..... maybe you forgot?......

I think it must be prices $USD 1 million at least

[pepe]

Code:

maybe you forgot?

surely i did