Skip to main content

AFTER HD TO SSD CLONING, SSD DOES NOT BOOT

Thread solved
Beginner
Posts: 1
Comments: 10

HI

 

USING ACRONIS TRUE IMAGE OEM (comes with ssd kingston)

My internal hd 1000GB  (SATA INTERFACE) on motherboard asus z390-h was cloned to kingston ssd  A1000 960GB NVMe PCI-Express. After cloning process concluded, the SSD is not able to boot. There is windows error when windows 10 is starting.  The HD interface sata is disk 0, and the ssd is disk 2. The boot order was configured to SSD boot first and older HD second boot priority. If I try boot with older hd boot suceeds.

Is it necessary to  remove older hd cloned in order to ssd boot has sucess?

HD (original windows C: system)  was clonned  is associated to disk 0 (sata)

Backup HD is associated to disk 1 (sata)

SSD is associated to disk 2 (PCI-EXPRESS NMVe)

 

After cloning ssd, ssd contents is shown in windows as drive E: The files of windows are present in ssd cloned but the ssd is not bootable: an error is presented during windows starting (blue screen windows stop code).,

At bios setup is shown UEFI BOOT Windows Boot Manager of both ssd and hd. When ssd Windows Boot Manager is setup for first boot, the boot fails with windows error.

Any help about this issue?

 

 

0 Users found this helpful
Legend
Posts: 81
Comments: 17669

#1

welcome to these public User Forums.

The first check here is to try disconnecting or removing the original source HDD drive, then check that you are still seeing the 'Windows Boot Manager' from the SSD as the primary boot device in the UEFI BIOS.

After this, there are questions that need to be asked if the system does not boot correctly?

How exactly did you perform the clone from the HDD to the SSD?
Was this done from within Windows, or did you boot the Acronis Rescue Media to do it?
If you booted from the Rescue Media, did you boot in UEFI or Legacy boot mode?

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

The good news here is that your HDD is still able to boot correctly into Windows, so I would strongly recommend that you make a Disk backup of the HDD to an external backup drive before doing anything else - this is your safety net against any further problems that could potentially leave you with a totally unbootable system.

Beginner
Posts: 1
Comments: 10

#2

 

At UEFI Bios setup it is possible to see two boot  options: Windows boot manager associated to HD and 'Windows Boot Manager' associated to SSD.  I have changed boot priority to 'Windows Boot Manager' associated to SSD

 

The boot was tried without disconecting the HD. Windows beggins start and end with stop code error windows 10 error code 0xc000007b

The Hd was cloned to SSD using ACRONIS TRUE IMAGE OEM licence comes with Kingston SSD SA1000/960GB

The cloning process is iniciated by Acronis software installed on  windows 10 HD drive C:. After cloning process started, the windows is restarted and Acronis starts in linux like mode and phases preparation and cloning partitions goes on until end. At finished the computer is turn off. The cloning process starts initially within windows 10 and reboot to linux like boot

I start computer and I enter bios setup to change boot priority to Windows Boot Manager' associated to SSD.

Rescue media was not used in this process.

 

I have a second HD drive internal to backup file, the computer Msconfig is 

Disk 0 - HD windows 10 system C: to be cloned (interface sata)

Disc 1 -  HD used to backup windows weekly (interface sata)

Disc 2 - SSD M.2 NMVe (interface NMVe Pci-express)

 

It is recommed backup windows system to external USB HD, considerating the computer has internal HD to store backup from fisrt windows 10 Drive C:?

I did not do test disconecting HD cloned to SSD before boot. The error is presented at windows start stop code error code 0xc000007b

Thanks you

Legend
Posts: 81
Comments: 17669

#3

The error stop code 0xc000007b has the following meaning:

The error code means an invalid image format. Specifically, you are attempting to start an application which is designed to run on 64-bit operating system. But your computer is running 32-bit Windows. The 32 bit application cannot load a 64 bit dll, thus the mixing up 32 bit with 64 bit environment brings about problem.

See webpage: Fix "The application was unable to start (0xc000007b)" error in Windows where this is described.

See also webpage: Cloned a disk, now problems where other users look to have encountered the same issue after booting with 2 drives connected following cloning.

Also:  0x0000007b BSOD after cloning HDD including OS

It is recommed backup windows system to external USB HD, considerating the computer has internal HD to store backup from fisrt windows 10 Drive C:?

The key point here is to have a full disk backup of the working HDD OS - if this can go to a 2nd internal HDD, that is fine.

Forum Hero
Posts: 68
Comments: 8150

#4

The boot was tried without disconecting the HD.

This is also playing with fire. Although it may seem harmless and/or faster, it's a really bad approach.  Depending on how your bios behaves, if it sees to "identical" disk signatures, it may automatically try to fix the disk ID collision by modifying the bootloader(s) of one or both disks.  Then you may end up with no bootable drives as a result.

https://www.thewindowsclub.com/disk-signature-collision-problem

Beginner
Posts: 1
Comments: 10

#5

The question is  the HD to be cloned is installed on physical address associated to a slot SATA 1 and the SSD NMVe PCI-EXPRESS has other different  physical address. After cloning the SSD continues on same physical hardware address that is not the same of HD. The system image cloned to SSD points to HD hardware  physical address.

In some case the SSD SATA is installed on same port and physical address wherein previously HD was installed.

This is not my case because HD sata and SSD NMVe has different interfaces and they can not be installed in same physical address location.

Could it cause any issue?

 

 

Forum Hero
Posts: 68
Comments: 8150

#6

It could be an issue. What's the version of Acronis that came with the drive? We're in the 2019 forum thread, but of it is 2018 or older, native support for pcienve may have some bugs.

When I migrated from my ssd to my first pcienvme I had boot issues too. Turned out the disk was locked in the process. I had to let it fail to boot 3 times and then it let me try safe mode which unlocked the drive and booted in safe mode. After that I could boot it normally.

I also wouldn't try cloning in this case since it's not the same interface. You might want to try a backup and restore as another test to see if it goes better. 

Either way, I would definitely not leave the original drive in the system with both drives attached when trying to boot. No idea how your bios may be trying to handle this, even though they are on different interfaces I'd the clone is presenting them as the same disk by UUID.

On my old gigabyte motherboard, i had to reset the bios at one point because it kept seeing 2 disks as the same one and the only thing that fixed that was to have one disk installed (newly restored one), then reset the bios to default, then go back in and update my bios settings all over and pick the NVMe as the priority boot with "windows boot manager". And then it worked... Keeping in mind the method to also get a safeboot on it too.

2019 has been muuuuch better at all this, but that was with the full version too when I was doing my later upgrades that went smoothly.

 

Beginner
Posts: 1
Comments: 10

#7

ACRONIS TRUE IMAGE OEM. This cloning software license comes with SSD KINGSTON. The Software name does not contain year version but in Windows painel control unistall program is shown version 19.0.5128. Would it be a 2019 version?

Beginner
Posts: 1
Comments: 10

#8

New information I have installed new motherboard intel drivers. The motherboard was upgraded  to new one that support 9th generation intel processor also replaced. I didnt have insttaled new drivers. Old and new motherboard are from ASUS. Old asus z270-h and new one asuz z390-h

After install drivers for new motherboard the hard disk have changed their position.

Now ssd is first disk associated to 0 at system and partitions at windows

DisK 0 - now is  SSD M.2 NMVe (interface NMVe Pci-express) [before was hd c: system]

Disk 1 - HD windows 10 system C: to be cloned (interface sata) 

Disc 2 -  HD used to backup windows weekly (interface sata)

After this new arragement  I redo cloning ssd but I did not get success. I did not try boot  with hd disconnected yet. This test was not realized yet. At moment I am doing a Windows full backUp  to external Hd for data security

I believe physical address can be relationated to this issue due to above changes.

 

 

Beginner
Posts: 1
Comments: 10

#9

When I migrated from my ssd to my first pcienvme I had boot issues too. Turned out the disk was locked in the process. I had to let it fail to boot 3 times and then it let me try safe mode which unlocked the drive and booted in safe mode. After that I could boot it normally.

I will try as you explaneid in this comment. In fact I have oberved in previous tries, after third boot failure, windows execute diagnostic and enter in repair system mode. I did not try boot in safe mode. This can solve the problem. I see a youtube video indicating boot in safe mode.

Beginner
Posts: 0
Comments: 5

#10
agmedeiros@uol.com.br wrote:
DisK 0 - now is  SSD M.2 NMVe (interface NMVe Pci-express) [before was hd c: system]

If you have replaced a SATA drive with an M2 NVMe you may have to mess around in the BIOS.

I did the same move last weekend.

I also had issue persuading the new drive to boot. (I also had a new motherboard.) It can take a few BIOS tweaks to get the setting right, not to mention using the right NVMe slot. (My Asus board has two.)

I fixed it by removing all other drives, including USB drives. Then boot from the new drive.

At one stage I had to boot from the Acronis recovery disk to get it to work. Simply booting from that disk persuaded the PC to boot from the NVMe drive.

I had the MVP version of Acronis 2019, which makes life a lot easier.

 

 

 

 

 

 

Legend
Posts: 81
Comments: 17669

#11
agmedeiros@uol.com.br wrote:

ACRONIS TRUE IMAGE OEM. This cloning software license comes with SSD KINGSTON. The Software name does not contain year version but in Windows painel control unistall program is shown version 19.0.5128. Would it be a 2019 version?

Version 19 is an old build of ATI 2016 for which the final build was 6595) so not ATI 2019 which shows as version 23.

New information I have installed new motherboard intel drivers. The motherboard was upgraded  to new one that support 9th generation intel processor also replaced. I didnt have insttaled new drivers. Old and new motherboard are from ASUS. Old asus z270-h and new one asuz z390-h

From the above I conclude that you are not only cloning but moving to new hardware regardless of this being for the same ASUS type - this would require using Acronis Universal Restore after doing a Backup of the old system then Restore to the new one.

Beginner
Posts: 1
Comments: 10

#12

sataFrom the above I conclude that you are not only cloning but moving to new hardware regardless of this being for the same ASUS type - this would require using Acronis Universal Restore after doing a Backup of the old system then Restore to the new one.

 

Not exactly. Considerating with old hd is running with new motherboard and new drivers upgraded,  this composes the set is being transferred to new ssd. From this point of view there is not system changes. The system being cloned is a image working with new hardware and drivers on same machine. The aim is transfer this set from internal hd to ssd. 

The acronis documentation lacks  information concerning cloning drivers connected to different interfaces. This is not same to replace a sata device to another sata device cloned to be used in same interface/port physical address from previous..

Beginner
Posts: 1
Comments: 10

#13

From the above I conclude that you are not only cloning but moving to new hardware regardless of this being for the same ASUS type - this would require using Acronis Universal Restore after doing a Backup of the old system then Restore to the new one.

 

 

Usually  New ssd M2 NMve are purchased to replace old SATA devices. Devices M2 NMVe are new technology comparing with old SATA interface. The Kingston SSD includes ACRONIS TRUE IMAGE OEM licence exactly to replace old sata devices for this ssd with M2 NMVe interface. Thus Acronis to be suitable to this work should be prepared to this change sata interface to  M2 NMVe. In the other hand, the software would not suitable to this cloning process involving devices connected to different interfaces. 

Legend
Posts: 81
Comments: 17669

#14

Usually  New ssd M2 NMve are purchased to replace old SATA devices. Devices M2 NMVe are new technology comparing with old SATA interface. The Kingston SSD includes ACRONIS TRUE IMAGE OEM licence exactly to replace old sata devices for this ssd with M2 NMVe interface. Thus Acronis to be suitable to this work should be prepared to this change sata interface to  M2 NMVe. In the other hand, the software would not suitable to this cloning process involving devices connected to different interfaces. 

The Kingston ATI version is OEM and can lack support for newer technology when using the rescue media which is Linux based.  It is usually an older build of ATI 2016.

M2 NVMe normally uses RAID on the controller interface which is different to your source HDD on SATA with AHCI.  The recommendation would be to use WinPE rescue media with extra Intel RST drivers injected for RAID support.

Beginner
Posts: 1
Comments: 10

#15

Hi

IT WORKS

I redo cloning process and disconnect all drives  except SSD. The boot goes on without any problem.

I will reconnect backup HD and work done.

. IT IS NECESSARY REMOVE HD CLONED SO THAT ANY CONFLICT ISSUE BETWEEN NEW SSD AND OLD HD CLONED CAN BE AVOID

Thanks all of you very much for helpfull support

Legend
Posts: 81
Comments: 17669

#16

Good to hear that the cloned SSD is working correctly - thank you for the feedback.

Beginner
Posts: 1
Comments: 10

#17

Good to hear that the cloned SSD is working correctly - thank you for the feedback.

 

Thank you

Forum Hero
Posts: 68
Comments: 8150

#18

That's why it's in the instructions 😂. 

Beginner
Posts: 1
Comments: 10

#19

Yes. It is necessary remove HD before booting by SSD