Skip to main content

WD version running for 30 hours

Thread needs solution
Beginner
Posts: 1
Comments: 2

I called Western Digital support and they were clueless.  I have a Dell with a 1 TB drive that I am cloning to a new WD Blue SSD 1 TB drive.  Both internal.  Program installed OK, saw the drives, restarted and it looked OK.

 

All I can see is a black screen and a mouse pointer.  Activity wheel does come on, drive activity lights show activity, but it has been running for 30 hours.  Something is obviously not working right.

 

Unfortunately I don't know how to exit it.  Acronis modifies the MBR to boot right back into where it left off.  I'd like to just boot back into windows and abort the attempt for now and then run drive tests on the original and new SSD drive to see if there's something up.  But I'm stuck!

 

Any help would be appreciated.

0 Users found this helpful
Beginner
Posts: 1
Comments: 2

And yes, I ran it from windows.  I didn't see the recommendations to boot from rescue media to clone.  It would sure be nice if Acronis would make this blindingly obvious in the program.  I would have cloned from a CD or USB had I known.

Legend
Posts: 79
Comments: 16726

Rick, welcome to these public User Forums.

Please see KB 2201: Support for OEM Versions of Acronis Products - as this is directly relevant to the fact you are running a WD version of an Acronis product, where it is for WD to provide adequate product documentation.

The above aside, no clone should run for such an excessive time, so suggests one of a number of  possible outcomes!

1 - the clone has completed successfully but you have not been advised of this result.

2 - the clone failed with no change made to either source or target drive.

3 - the clone failed and made changes to both drives.

4 - the clone aborted for some reason but didn't communicate the fact!

etc.

The next action I would suggest is to force the computer to power off, which you can normally do by pressing & holding the power button for a period of around 30 seconds.

After powering down, disconnect the target drive then check whether you are able to boot into Windows on the computer from the original source drive.

If the computer boots OK into Windows, then reconnect the target drive and check what contents are shown for that drive in Windows Disk Management & Explorer.

If the computer doesn't boot into Windows, then the next question is:  have you make a good backup of the original drive before starting this clone action?  If yes, then you may need to consider recovering your system from that backup.  The degree of recovery required will depend on how your computer is setup, i.e. if you have a separate EFI System or Microsoft System partition holding the Windows Boot Configuration Data store, then you could just recover this small partition.

Beginner
Posts: 1
Comments: 2

The cloning looks like it got much of the way but obviously it shouldn't take that long.  I was able to boot to a Windows 10 media, choose repair and able to fix the booting issue.  So I got back to square 1.  And then quickly ran away from Acronis.  I've had success with it before, this was a mess.

I was able to clone the drives with another program in about an hour or so.  I'm now up on the cloned SSD.

 

Legend
Posts: 79
Comments: 16726

Rick, the end result is the main thing for all users, so pleased to read that you have achieved this and are up & running on the new SSD.