Solved Windows startup repair needed after clone backup

[loninappleton]

I'm sitting through one of those long repair routines that Win7 acrtivates.


But there's no reason for this happening. The HD it is repairing was simply cloned using a

Ghost older edition from a working HD that had chkdsk run before starting the clone job.
Mine take a long time.


Next step was test the clone. It started up, ran some programs, then I was going to rerun
chkdsk on the _clone driive_ in order to make another redundant backup (after some
other HD problems.) So on the restart to the chkdsk routine, this Repair Screen kicked in.
I'm stumped.



I expect that repair routine to error out. But this is one of my newer drives-- all of a sudden
I'm having these problems.



Next step if it errors out is I grab that remaining HD which had a quick wipe to low level and I
put the NTFS format on it fresh. I don't know if that will fix any stray info that Windows wants to

"look" at and repair. I can do that overnight.

 

[samuria]

Ghost is a blast from the past I was a beta tester before Norton took it over. I would imagine that it no longer understand updated NTFS system try using a modern free clone system

 

[loninappleton]

Well it's no trip down Memory Lane for me. The Ol' Norton 11.5 or whatevs needs some patience
but for me is less confusing that what you are about to say for Macrium and the rest. Please avoid doing so unless there is something really new.


One adventure leads to another like dominos.


My original question was why does a clone fail on reboot at the point where Win7 says building your
desktop?


For reference I did a fresh Win7 install to a problem drive on the motherboard where I want
to do a clone backup. With all the failures (some cured by running Bootrec) I have a good
HD which is complete but that one is being returned as received 7200 rpm rather than 5400 rpm
which I ordered.


I'm getting to the point. A good Seagate HD developed a problem freom running it on
my backup system to get the load of the Clone job off an always on machine. Because of
those Win7 failures to start, I reinstaalled Win7. That went through without a hitch. I did

not low level it, just let Win7 put all the stuff on which is apparently tied to the motherboard.
I knew some of this from the past.


If all goes well I will use Norton to copy the drive I have temporarily before return to
this Seagate HD with a Win7 bare install on it. To check all this, I'll cold boot the bare Win7
just to make sure it's still "there".

 

[SIW2]

Why would you prefer 5400 to 7200 ?

 

[loninappleton]

5400 over 7200 has (or I'm told) lower noise level. I never bought one before. From brand manufacturers
they are more expensive than the more common 7200. I think they used be called "green" for low power consumption from WD.



The purchase item I did not receive yet is called a While Label. It was worth the $40 to buy new with a year warranty. The vendor has become a trusted source for me for other off brand and used items.


I suppose a clone backup might have some small time difference. But with a full 2Tb it takes hours
anyway.


The White Label 7200 sent in error I loaded up before running any Crystal Disc on it. It runs ok.


I will mark this solved. As I said elsewhere, as long as I am in Win7 I have to be more careful about
swapping bootable HDs between PC's even when it looks like the Win7 is loading but then stops for a
Win7 repair cycle. It rarely fixes anything. I can count the times on one hand.