Disk clone problem

[Tim]

Hi,

Yesterday I cloned by hard disk to a bigger disk. Since I did this system
won't boot on the bigger drive and hangs at the stage "reporting-system
resume or choose to continue with "delete restoration data and proceed to
system boot menu." The problem then is that my usb keyboard won't respond
and neither will a ps2 keyboard.


Any ideas?

Thanks,
Tim Vieweg.

 

[Mark L. Ferguson]

If you can burn a disk, this .iso (120 megs)will help.
Windows Vista Recovery Disc Download:
http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/

--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
..

 

[John Barnes]

After you make your copy, you should always plug the new copy into the same
connector on the MOBO as the one you copied from, BEFORE you first boot.

 

[Timothy Daniels]

John - Can you explain what happens on the first boot of a Vista clone?

*TimDaniels*

 

[Tim]

Many thanks for your reply. I did plug the new copy into the cloned disk
connector. On the first boot the system hangs on the "windows resume loader
screen" reporting " the last attempt to resume the system from its previous
location failed- attempt to resume again?"

Then it gives you two options "continue with system resume or delete
restoration data and proceed to system boot"

The problem is that the keyboard doesn't work at this stage and I can't
select either option.

 

[John Barnes]

The registry has a mount entry for each mounted (whether currently or past)
device. I have not tested a cloned system with Vista, but it has been a
problem with XP and it avoids possible conflicts. You can plug in the old
drive after the first boot and resolve any conflicts and use as desired.

 

[Timothy Daniels]

What is required for successful Vista cloning is still a mystery
to me, that's why I asked.

But I do have lot of experience in cloning XP, and with XP
I have found that one need not re-position the clone HD after
the cloning process. All that one must do is to make the
"parent" OS invisible to the clone OS when the clone OS is
first run. That can easily be done by merely disconnecting the
data cable from the "parent's" hard drive (IF the "parent" and
the clone are on different HDs, AND if the 2 HDs are not on
the same IDE cable.) (Actually, the 2 HDs *can* be on the
same IDE cable as long as the disconnected HD is at the
middle connector so that the lone connected HD is at the end
connector. That would be the case in which the cloning were
from a Slave HD to a Master HD - something completely
allowable, as Slave HDs can control booting and contain
running OSes just as well as Master HDs.)

This procedure does not even require changing the jumpers
(for IDE HDs) since in the absence of the previous head of
the Hard Drive Boot Order (i.e. the previous "boot drive"),
the next HD in the Hard Drive Boot Order moves to the head,
i.e. becomes "rdisk(0)", and the clone's HD will receive boot
control.

By putting the clone HD in the position previously held by
the copied HD, the same thing is accomplished, but it feeds
the erroneous belief that there is something significant in the
cable positioning of the clone, whereas all that is necessary is
that the clone OS not "see" its "parent" on its very first run.

*TimDaniels*

 

[John Barnes]

That is another way of accomplishing the same thing. The mount manager will
make the change if it doesn't find the original OS connected to the original
mount point. If both are still connected when the first boot is made to the
new system, there are often problems with %root% especially services.
Another consideration would be to make the new drive remount as the same
letter, per mount enumeration. This is a necessity when, for instance you
are cloning a system from say partition 1 of an old drive to a different
partition on another drive (say partition 3).
In any case, what I suggested was a way to easily avoid problems without
having to know the intricacies of the enumeration process for someone who is
simply moving a system from partition 1 of one drive to the same partition
on another.
There are numerous KB articles on the process that one can read if one is
trying some other more complex cloning processes.

 

[Timothy Daniels]

That is another way of accomplishing the same thing. The
mount manager will make the change if it doesn't find the
original OS connected to the original mount point. If both
are still connected when the first boot is made to the new
system, there are often problems with %root% especially
services.

OK, I'll take your word for that, seeing that I'm not familiar
with what "mount" does.

Another consideration would be to make the new drive
remount as the same letter, per mount enumeration. This
is a necessity when, for instance you are cloning a system
from say partition 1 of an old drive to a different partition
on another drive (say partition 3). In any case, what I
suggested was a way to easily avoid problems without having to know the
intricacies of the enumeration process
for someone who is simply moving a system from partition 1
of one drive to the same partition on another.

I'm not sure I understand what you mean by "Another
considertaion would be...". In my normal cloning procedures,
I typically clone an OS that is on partition 1 of my main HD,
and I put it in a position on another HD where it could become
any partition from 1 to 3 (if I put it in a Primary partition), or
more (if I include logical partitions). The clone will *always*
refer to its own partition by the same letter name that the "parent"
OS did - usually "C:" - and when the clone is running, it will refer
to the other partitions that it sees by whatever names it feels is
right when it starts up - not by what the OSes in those partitions
may call them when they are running. Thus, a partition's letter
name depends on which clone is running. A partition that may
be called "F:" by one clone, may be called "G:" by another clone,
and when the clone in that partition is running, that partition will
be called "C:". And this is despite that all OSes are clones of the
same "parent" OS.

I have no idea whether this contradicts what you wrote, but it
should be made clear to readers that partitions can be "renamed"
by the running OS and that there appears to be no inate letter
name identity for a partition that exists independently of its
*running* OS IN WINDOWS XP. (Vista, as I have said, may
handle partition naming completely differently.)

There are numerous KB articles on the process that one can
read if one is trying some other more complex cloning processes.

Do these Microsoft Knowledge Base articles specifically
address cloning and the first startup of a new clone? If so,
I'd like to read them.

*TimDaniels*

 

[John Barnes]

There are numerous articles in the KB for you to learn specific details of
how various processes are performed. This is a forum to provide the least
complicated solution for non technical users where possible.

 

[Timothy Daniels]

OK, brush it aside. I thought you'd be up to acknowledging
that XP partitions are named by the running OS.

*TimDaniels*