Skip to main content

source disk no longer bootable after cloning

Thread needs solution

Hi all,

In my metal workshop I have a large CNC press brake (Amada FP8025) which runs on Windows 2000 NT from an industrial ATX board (CA331)
For reasons of security and backup I decided to build an entire hard- and software clone of this machine. I bought a used board on eBay and a new Micron Crucial SSD (MX500) I cloned the original SSD with my HP workstation running windows 10 using "Acronis true image for Micron" which came with the new Micron SSD. But now the original SSD now longer works in the original system. More precise: it tries to start windows but directly after the Windows logo appearing I get a Blue Screen of Death (BOSD) saying "INACCESSIBLE_BOOT_DEVICE" Same thing with the new cloned disk. I then tried to install an image from 2018 (.tib file on USB) with Acronis True Image 2012 (bootable CD that came with the press brake) on to the new SSD on the actual machine I am trying to clone. This had the same result.
Does anybody know what might have changed on the original SSD to stop it from working? And why is the restored drive with the .tib file not working either? I did the first clone on my 64bit HP workstation by plugging both disks in a vacant SATA port. With hindsight this may not have beent the best idea but then why is the solution with running Acronis 2012 on the original 32bit Windows 2000 system with a .tib file known to have worked on previous restores not working either?

Since the press brake is now down this has become a very urgent problem for us so all help is very welcome.

Thanks! Jaap.

0 Users found this helpful

Jaap, welcome to these public User Forums.

There are significant differences with how cloning works when used on Windows 10 systems, especially if that system also uses a different BIOS boot mode such as UEFI with GPT disk partitioning.

You very old Windows 2000 system predates any thought of either UEFI or GPT, plus may also have limitations on the maximum disk size that it can accept.

If you have a valid disk backup of the Win 2000 OS then assuming that the backup was made from the same machine, then you should be able to boot that machine from rescue media to recover the backup back to the original working disk drive.

I saw this thread when I had a very similar problem:

Unable to boot Win2k of both source and copy after imaging drive | Acronis Forum

 

There was no resolution posted but IF there had been, it'd have saved me days of work.

So, for the next guy:

 

I found I needed a Win2k cd that offered the recovery console...not all of mine did.

When you have one, boot into it and type DIR. If you get "an error occurred during directory enumeration",  execute a CHKDSK /R from within the Win2k recovery environment.

This win2k specific CHKDSK fixed disk errors that my Win10 CHKDSK didn't even detect, and allowed the system to not only display a DIR, but boot.

I had to do the same thing to all 3 clones of my HDD and it fixed it every time.

Dan