Locked Solved - Error when using Norton ghost in multicast

[casperyc]

Error Number: (25002)
Message: Unhandled condition encountered: Attr translation will result in corruption of MFT table

Was trying to use Ghost Server to multicast, so I can install a batch of 40 identical mechines.

It was running fine for about 30-33%, but then got this error....

anyone got any ideas?

 

[Cyler]

You are a verified member and you should know that having a proper title and not "[]" helps a lot. Added a title and feel free to change if you think it's not good enough, and moved this to Help and request section.

 

[Chuck]

My idea would be to Google "norton ghost Error 25002" which will give you several pages of possible causes and solutions.
Also Google "norton ghost Attr translation will result in corruption of MFT table".
Also download a copy of "Symantec Ghost™ Reference Guide" which has a section on this error.
Another idea would be to ask on some Norton specific user forums where the users are more likely to know about Norton Ghost.

 

[Alessia_Amelia]

Hello, this is a good place to start. Would help if we could get more details, though. OS used, version of software etc...
The community forum has specific answers to this error that can assist like @Charlie_Grimes suggested.

1. Boot from the drive source normally.
2. Open Command Prompt, then type chkdsk /f /r then enter. Choose yes to check disk after restart.
3. Restart your Pc. Wait until check disk complete, then do the cloning again using ghost.

 

[casperyc]

You are a verified member and you should know that having a proper title and not "[]" helps a lot. Added a title and feel free to change if you think it's not good enough, and moved this to Help and request section.

Sorry about that...

Was in a hurry to post this...

Already solved with an extra switch -ntexact.

 

[Cyler]

Glad you did. Was about to recommend that actually cause that error means that the NTFS Files (some small files are actually stored inside the NTFS file tables) were fragmented and needed more space to write on the target disk or the clusters must be placed on the same location to avoid additional redirections.

Since this is resolved, I'm closing the thread with a thank you to all for the comments.