SYMANTEC NORTON GHOST 10 - HAVE I GONE MAD?

[ner]

I recently had to do a complete restore of my C: drive using Ghost 10 and the restoring of the drive went ok with no errors.

Once the restore was complete the system restarted and during boot up the system reported that the C: needed to be checked for “disk consistency” and ran through a chkdsk and then started ok into windows.

I am a little concerned to why this has happened, as the original ghost image I did was ok, this was build on the 9th of September. The new build was based on the original build with September’s hot fixes, Symantec updates and a few other updates…

Yet each time the new build is loaded its goes through the same routine of chkdsk on first boot?

Any ideas?, or i am mad....

[CoffeeFiend]

That's perfectly normal, it does that because the NTFS's part's CHKDSK bit isn't set. Not that I'd ever use Ghost 10 though...

[ner]

@crahak -

Thanks for your reassurance, i have always used ghost 2003 and have never seen this before just started using ghost 10 as i got it free with systemworks and internet security.... but i think i may go back to using ghost 2003.....

[CoffeeFiend]

but i think i may go back to using ghost 2003.....

...which is a FAR better choice IMO.

[Acheron]

I think it's an approvement to have your disks checked before usage of the system after ghost image creation.

After all, you wouldn't like it if new written data got corrupt, cause of problems applying the ghost image.

[ner]

@hp38guser -

When you say get the hard drive checked - i trust you mean running chkdsk /f ?, or do you suggest something else/

[ner]

Well have check out the hard drive and all is well no issues or problems, this just leaves me with the question to why the original ghost 10 image was ok, and then the new build always asks to do a chkdsk on rebooting the pc once the ghost restore is complete.

From the help given my "crahak" i understand that may be normal, but i am confused as why dos this not happen on the original build.... this leaves me wondering that maybe the new build was in some way corrupt. Can'nt find anything about chkdsk runnng when the partition is changed...