Cloned disk and now disk management won't run

[Bob H]

I have just finished cloning my C:\WinXP IDE drive to a new SATA drive
using Acronis. All seems well so except that the Disk Managment console
won't run and throws up an error message:
The Disk Management console failked to connect because the Disk
Management remoting service is not in the Windows Firewall exception list.

I added dmremote to windows firewall, then got another error message:
I can't recall the exact words, but it was about adding RPC port (tcp
135) to windows firewall exception list.
I did that and now Disk Management tells me 'The service database is locked'
Ok, so how do I unlock that please?

Thanks

 

[JS]

Instead of cloning the drive use Acronis to create
an 'Image Backup' and restore the image to the
new drive.

 

[Anna]

Instead of cloning the drive use Acronis to create
an 'Image Backup' and restore the image to the
new drive.

Bob:
In many cases a simple reboot will correct the problem (actually, it's even
better to power-off the PC and then fresh-boot the system). I suppose you've
already tried that and the same problem exists.

It may simply be that a glitch occurred during the disk-cloning process. If
you haven't done so already, give it another shot. And, of course, we're
assuming there was (and is) *no* problem accessing the Disk Management
snap-in on your source HDD.

Note to JS - Why do you think the disk-imaging process would avoid the
problem as opposed to the disk-cloning process? Have you run into problems
with the Acronis True Image program re this or similar problems? Any
particular version of ATI?
Anna

 

[JS]

Not with True Image but other clone software
I've used in the past did not work 100%.

That's why I create Image backups and have moved
Windows XP OS without problems to a new
drive several times (actually more than several)
using the image file.

In this specific case I'm not 100% certain that the
problem is specific to cloning the drive which is why
I suggested the Image Backup method.

If the problem still exist, then it's not related to either
cloning or imaging but something else.

 

[Bob H]

After doing as you suggested, I hav eran into further problems. Grrrr!
Since restoring an image from my original C: drive to my new C: drive,
the system still thinks I want the original C: drive and even tho' I
have specified in the BIOS to boot from my new SATA drive as the first
disk, it won't.

Any ideas on how to correct that?
Oh I did remove the power lead to the old drive, but then on attempting
to boot it complained it couldn't find the boot system

 

[JS]

Did you install the SATA drivers for your motherboard?

 

[Bob H]

Did you install the SATA drivers for your motherboard?

Yes, because I am running sp3 and I already have a SATA drive which I am
using.

 

[Bob H]

Did you install the SATA drivers for your motherboard?

Yes, because I am running sp3 and I already have a SATA drive which I am
using.

 

[Anna]

Bob H.
First, excuse me for not posting the various posts re this thread...

Do this...

Start over by using your Acronis True Image program to clone the contents of
your "source" PATA HDD to your new SATA HDD. Naturally we're assuming that
the source HDD is non-defective; it boots without incident; and it functions
without any problems, right? And we're assuming that you've properly
connected the SATA HDD to the first SATA connector on your motherboard,
either designated SATA(0) or SATA(1).

We'll assume that the disk-cloning operation proceeds successfully with no
error messages or untoward messages along the way, right?

Immediately following the disk-cloning operation, shutdown the machine and
disconnect your source HDD from the system and also disconnect any other
storage devices that may be connected, e.g., another HDD. So the only HDD
connected at this point is your SATA HDD.

Boot directly to the SATA HDD, checking the BIOS along the way that the SATA
HDD is first in boot priority order (or second if the first boot is to an
optical drive). Presumably the SATA HDD will boot without incident and
properly function.

After shutting down the machine, reconnect the old PATA HDD and boot with
both drives connected. Again, as you do, verify that the boot priority order
in the BIOS is correct.

If you run into any further problems, indicate what they are and also
indicate the make/model of your motherboard.
Anna

 

[Bob H]

Hi Anna,
I decided the best thing would be to just do a re cloning as I
did before using Acronis. This time after it was completed I went into
the BIOS to check the boot order after I made sure the SATA connections
were ok on the board. Actually I swapped the connections over, from SATA
1 of the original SATA drive to SATA 2 on the board then the new SATA
drive was connected to SATA 1.
I then booted up into my WinXP system without errors and then checked
The Disk Mangement console, which ran without any of the previous errors.

Thanks for your reply, but I think I just beat you to it