Re: Big Al & DL Re: Cloning my hard drive?
- From: "Anna" <myname@xxxxxxxxx>
- Date: Thu, 24 Apr 2008 11:27:54 -0400
jetjock wrote:
Bought new hard drive. Installed it and it was assigned drive "H".Acronis should have forced a reboot and changed the drive H: to C:
Used Acronis True Image Home 11 to clone my "C" drive to the new "H"
drive. Switched the boot order in the BIOS so the "H" drive is now my
boot drive. Everything seems to be working just fine except for an
SVCHOST error with NTDLL.DLL during start up, but haven't found
anything that this is effecting yet. I intend to wipe the old "C"
drive and use it as an additional drive.
My questions are:
Is there any way to change the "H" drive to a "C" drive? If so, how?
I do have an image of "C" that I could have used instead of cloning.
How would I have used this to make the "H" drive my "C" drive?
Should I just leave everything as is? What would be the best sequence
of actions for me to achieve the new drive as my "C" drive?
Sorry to be so long (and ignorant), but I wanted to be as specific as
possible. Thanks.
before loading windows. But that probably assumes you removed the C:
and H: drives, and plugged that H: drive back in as the primary drive so
it could be labeled C: by the reboot.
I see someone else suggested similar swap of drives too.
I swapped HD's in my laptop, and cloned the C: to my F: Turned all
off and swapped hardware and when the laptop rebooted I saw a message
and it did a bit of work before windows started. Scared me, but all was
fine. C:\windows etc.
Many thanks for the advice. I would have thought that when I changed
the boot drive in the BIOS it would have made that drive the "C"
drive, but it didn't. Maybe the fact that these are both SATA drives
and not IDE had something to do with that, since neither was listed as
a "slave".
If I understand everything you've both said, all I have to do is
remove (unplug) my old "C" drive after copying the image (or cloning),
and when I reboot, the old "H" drive will now be the "C" drive.
Correct?
jetjock:
The responses you rec'd from DL & "BigAl" are essentially correct as to what
probably caused your problem and how to avoid it in the future.
This has been one of the problems (or more precisely, potential problem)
that has affected disk-cloning programs such as the Acronis True Image one.
It can be an especially nagging problem when one is using a disk-cloning
program as a routine backup program and the "destination" HDD (the recipient
of the cloned contents of the "source" HDD) is another internal HDD, i.e.,
not a USB external HDD for example.
If immediately following the disk-cloning operation the user boots with both
drives connected the system will boot without any problems, however, upon
occasion (remember, this is a *potential* problem - it doesn't always occur)
the destination HDD will not reflect that the system-boot files are located
on that drive. Consequently when the user subsequently attempts to boot to
the destination (newly-cloned) HDD it will not boot unless the previous
source HDD (with its system-boot files) is connected. Under those
circumstances the cloned HDD will bear a non-C: drive letter assignment.
Again, I emphasize that this problem does not always arise, but it does with
sufficient frequency that the general advice is for the user to disconnect
the source HDD from the system immediately following the disk-cloning
operation and boot straightaway to the newly-cloned destination HDD.
Thereafter there's no problem booting to either HDD, both of which will
retain a C: drive letter assignment.
Naturally all this is an annoying situation where the source & destination
HDDs are internal drives and the disk-cloning program is being used
routinely.
(We should add that this is a "non-problem" where the recipient of the clone
is a USB external HDD since that device is not ordinarily bootable).
Now, for the good news...
We have found that the Casper 4 disk-cloning program (our disk-cloning
program of choice) avoids this problem. At least we have never run into it
after undertaking hundreds of disk-cloning operations where both the source
& destination HDDs were internal drives. And we've used a wide variety of
different makes & models of PATA & SATA drives in the process. So with the
Casper 4 program there is no need to invoke the disconnect/connect process
referred to above following the disk-cloning operation. The recipient of the
clone (the "destination" HDD) will bear the C: drive letter whenever a boot
is made to that drive.
Anna
.
- Follow-Ups:
- Re: Big Al & DL Re: Cloning my hard drive?
- From: Bill in Co.
- Re: Big Al & DL Re: Cloning my hard drive?
- From: Big Al
- Re: Big Al & DL Re: Cloning my hard drive?
- References:
- Re: Cloning my hard drive?
- From: Big Al
- Re: Cloning my hard drive?
- Prev by Date: Re: NetBT Event ID 4311
- Next by Date: Re: XP/Microsoft Broadband Networking Error Message
- Previous by thread: Re: ATTN: Big Al & DL Re: Cloning my hard drive?
- Next by thread: Re: Big Al & DL Re: Cloning my hard drive?
- Index(es):
Relevant Pages
|
