Can't Boot into Cloned Drive to Delete Old Drive

jlay529 · 15 Mar 2021

Hi I recently cloned my SSD using Clonezilla and was trying to boot into the new cloned drive to reformat the old drive so I can use it for normal storage. Both SSD's use the NVMe M.2 format but my motherboard only has space for one of them so I bought a PCIe adapter for the other one. My current setup is new bigger SSD in motherboard M.2 slot and my old SSD is in the PCIe adapter.

I have tested that the new drive works by booting into it but I am having an issue when plugging both SSD's into the motherboard. Even if I change the boot order in UEFI settings, it is still booting to original SSD. On disk management the original disk was Disk 0 and the cloned disk was offline as Disk 1. I found some threads about disk collision signatures and cloned drives so I brought Disk 1 online and it became a D: drive. But now when I remove the old drive and only try to boot into the new drive I get a Windows Error

Current disk management screen:

Can't Boot into Cloned Drive to Delete Old Drive-disk-210305.png

I am running Windows 10 Build 19041.867.

Macboatmaster · 15 Mar 2021

There are MANY ways to do this
Before I detail the first one - I would NOT format/clean the original M2 Drive until I was absolutely certain all is OK
I do not know how long it is since you made the clone, - recently you say.
I always leave any new drive running for at least a week, while I make full checks.
First way
1. In Disk management - the lower window right click on the left column of disk 1 - the new M2 - where it lists basic 931Gb and online
Take it offline.

boot the computer from a Windows 10 installation USB
cmd prompt
diskpart
list disk
select disk - the original M2
clean
then format as you wish

It must be done from the cmd prompt at boot, as you cannot do it on the cmd prompt on a running windows.

That is the risky way as diskpart is immediate and does not give you a second chance and of course you may still have the problem of booting from the new drive, but that I think is the minor issue of you making the drive online and therefore the letter change to D - is not in keeping with the BCD - boot configuration data on the drive - from the clone.
=================================================================================
The safer way and the way I would go is to use Macrium Reflect free
Make the Macrium recovery media on a usb, check you can boot from it.
make an image of the original M2 drive, with ONLY that drive connected - to an external drive connected USB

Shut down - take out the original M2
insert the new M2
shut down
boot to the Macrium recovery media
restore the image to the new M2
Come out of the recovery media and boot as usual and check all is Ok with the new M2
Shut down

Insert the old M2 into the adapter
Boot back to the recovery media
open the cmd prompt - lower part of recovery media window
diskpart it from there.

Same procedure as diskpart from the windows 10 installation usb.

If you wish to do that I can send you the Macrium details in full
Macrium Software | Macrium Reflect Free

Imaging is safer than cloning.
Firstly it does NOT clean the drive to which the image is made
The image is explorable
all or parts of it can be restored
or indeed individual files can be obtained and placed in the newly restored image, if something currently goes wrong.

Megahertz · 15 Mar 2021

Make sure the new M.2 drive can boot without the old one. To check remove the original drive in the PCIe adapter and boot.
If it boots normally, reinstall the original drive in the PCIe adapter, boot from a Win 10 installation drive, launch a CMD window (Shift+F10) and clean the drive as Macboatmaster instructed.
diskpart
list disk (take note of the disk number you want to clean)
select disk n (replace n with the disk number)
clean
create part primary
select part 1
format fs=ntfs quick
assign
exit (to exit diskpart)

Macboatmaster · 15 Mar 2021

Well at the present time it does not - according to this

I found some threads about disk collision signatures and cloned drives so I brought Disk 1 online and it became a D: drive. But now when I remove the old drive and only try to boot into the new drive I get a Windows Error

but I think that is only because it was brought online in disk management, given letter D, so that even when the old drive is removed there is no boot to and load of Windows.
Should be a very minor problem

However I think I would go for the Macrium, unless as you say - jlay529 - can get that new drive to boot, with the old one NOT installed.

topgundcp · 15 Mar 2021

When cloning the disk. You also clone the EFI System partition which both from disk 0 and disk 1 are the same and will cause conflict because they contains the same BOOT info.
From the screen shot, you are currently booting from disk 0 so you can rebuild the EFI system partition for disk 1, you don't need to boot from winpe.
Open the admin command prompt and type :

diskpart
select disk 1
select partition 2
delete partition override
create partition EFI
format fs=FAT32 quick
assign letter=A
exit

bcdboot D:\windows /s A: /f UEFI ======> This will create a brand new BCD store and a new set of identifiers assigned to each device.
mountvol A: /D ===> remove letter A from mount point

once done, reboot your PC and set the boot priority to disk 1 or you can select from the Boot Menu.

NavyLCDR · 16 Mar 2021

topgundcp said:

When cloning the disk. You also clone the EFI System partition which both from disk 0 and disk 1 are the same and will cause conflict because they contains the same BOOT info.
From the screen shot, you are currently booting from disk 0 so you can rebuild the EFI system partition for disk 1, you don't need to boot from winpe.
Open the admin command prompt and type :

diskpart
select disk 1
select partition 2
delete partition override
create partition EFI
format fs=FAT32 quick
assign letter=A
exit

bcdboot D:\windows /s A: /f UEFI ======> This will create a brand new BCD store and a new set of identifiers assigned to each device.
mountvol A: /D ===> remove letter A from mount point

once done, reboot your PC and set the boot priority to disk 1 or you can select from the Boot Menu.

Since disk 1 has a bunch of unallocated space, personally I would not delete the EFI and try to recreate it as the new EFI system partition may attempt to be created in the unallocated space at the end of the drive. I would just write new boot files to the existing EFI system partition on disk 1. Also there is a problem in that the screenshot shown in post #1 is from disk management. There is probably an MSR partition on the disks which is not visible in disk management, so we can't verify for sure what partition number the EFI system partition is. Deleting partition 2 above may actually be deleting the MSR partition. We need to start with:

diskpart
select disk 1
list part
list vol
detail disk

Then we will find out where the MSR partition is, and which partition number is the EFI system partition. Indeed, though, the easiest solution is simply to fix the existing EFI system partition which is simple to do.

topgundcp · 16 Mar 2021

Since disk 1 has a bunch of unallocated space

Good catch and it will create new partition at the end.

Also there is a problem in that the screenshot shown in post #1 is from disk management. There is probably an MSR partition

MSR is always before the C drive. However, To make sure we have a brand new EFI system partiton, open disk management to create
a new FAT32 simple volume on the deleted EFI partition, go back to diskpart, select the partition then type
set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b

NavyLCDR · 16 Mar 2021

topgundcp said:

Good catch and it will create new partition at the end.

MSR is always before the C drive.

On disk 1, is the MSR partition #1, #2, or #3? D drive on disk 1 is likely partition #4.

zbook · 16 Mar 2021

Please run:
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

jlay529 · 17 Mar 2021

Sorry if it was unclear, right after cloning the drive I was able to unplug the old drive and use just the new drive and everything functioned perfectly fine.

Macboatmaster, I did as you suggested, put the new drive back offline, remove the old drive and try to boot into the just new drive. That didn't work so I am back on the old drive and now in disk management the new drive is back online. If I try to put it offline again I get this dialog box:

Can't Boot into Cloned Drive to Delete Old Drive-disk-20210317.png

- - - Updated - - -

I did run the diskpart commands and here is what came out:

Code:

DISKPART> list part

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           450 MB  1024 KB
  Partition 2    System              99 MB   451 MB
  Partition 3    Reserved            16 MB   550 MB
  Partition 4    Primary            237 GB   566 MB
  Partition 5    Recovery           535 MB   237 GB

DISKPART> list vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    237 GB  Healthy    Boot
  Volume 1         Recovery     NTFS   Partition    450 MB  Healthy    Hidden
  Volume 2                      FAT32  Partition     99 MB  Healthy    Hidden
  Volume 3                      NTFS   Partition    535 MB  Healthy    Hidden
  Volume 4     D                NTFS   Partition    237 GB  Healthy
  Volume 5         Recovery     NTFS   Partition    450 MB  Healthy    Hidden
  Volume 6                      FAT32  Partition     99 MB  Healthy    System
  Volume 7                      NTFS   Partition    535 MB  Healthy    Hidden
  Volume 8     I   Media Stuff  NTFS   Partition   7452 GB  Healthy
  Volume 9     H   Hybrid       NTFS   Partition   1862 GB  Healthy

DISKPART> detail disk

SHGP31-1000GM-2
Disk ID: {2D402218-8511-11EB-9566-6C6A77E68F2E}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1D00)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 4     D                NTFS   Partition    237 GB  Healthy
  Volume 5         Recovery     NTFS   Partition    450 MB  Healthy    Hidden
  Volume 6                      FAT32  Partition     99 MB  Healthy    System
  Volume 7                      NTFS   Partition    535 MB  Healthy    Hidden

- - - Updated - - -

I also ran DiskParInfo.Bat and only copied the information from Disk 0 and Disk 1.

Code:

    Disk 0 : SSD. It has 5 partition(s). Model: Samsung SSD 950 PRO 256GB
    Disk 1 : SSD. It has 5 partition(s). Model: SHGP31-1000GM-2    
    Disk 2 : HDD. It has 1 partition(s). Model: WDC WD80EMAZ-00WJTA0   
    Disk 3 : HDD. It has 2 partition(s). Model: ST2000DX001-1NS164    

    The script has found the above 4 storage device(s) in total.
=======================================================================

Microsoft DiskPart version 10.0.19041.610

Copyright (C) Microsoft Corporation.
On computer: JOHN-PC

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          238 GB  1024 KB        *
  Disk 1    Online          931 GB   693 GB        *
  Disk 2    Online         7452 GB  1024 KB        *
  Disk 3    Online         1863 GB      0 B        *

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    237 GB  Healthy    Boot    
  Volume 1         Recovery     NTFS   Partition    450 MB  Healthy    Hidden  
  Volume 2                      FAT32  Partition     99 MB  Healthy    Hidden  
  Volume 3                      NTFS   Partition    535 MB  Healthy    Hidden  
  Volume 4     D                NTFS   Partition    237 GB  Healthy            
  Volume 5         Recovery     NTFS   Partition    450 MB  Healthy    Hidden  
  Volume 6                      FAT32  Partition     99 MB  Healthy    System  
  Volume 7                      NTFS   Partition    535 MB  Healthy    Hidden  
  Volume 8     I   Media Stuff  NTFS   Partition   7452 GB  Healthy            
  Volume 9     H   Hybrid       NTFS   Partition   1862 GB  Healthy            

Disk 0 is now the selected disk.

Samsung SSD 950 PRO 256GB
Disk ID: {E921B9EF-9834-4659-B77A-4B7428E21339}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0101)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    237 GB  Healthy    Boot    
  Volume 1         Recovery     NTFS   Partition    450 MB  Healthy    Hidden  
  Volume 2                      FAT32  Partition     99 MB  Healthy    Hidden  
  Volume 3                      NTFS   Partition    535 MB  Healthy    Hidden  

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           450 MB  1024 KB
  Partition 2    System              99 MB   451 MB
  Partition 3    Reserved            16 MB   550 MB
  Partition 4    Primary            237 GB   566 MB
  Partition 5    Recovery           535 MB   237 GB

Partition 1 is now the selected partition.

Partition 1
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 1048576

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1         Recovery     NTFS   Partition    450 MB  Healthy    Hidden  

Partition 2 is now the selected partition.

Partition 2
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 472907776

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2                      FAT32  Partition     99 MB  Healthy    Hidden  

Partition 3 is now the selected partition.

Partition 3
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 576716800

There is no volume associated with this partition.

Partition 4 is now the selected partition.

Partition 4
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 593494016

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 0     C                NTFS   Partition    237 GB  Healthy    Boot    

Partition 5 is now the selected partition.

Partition 5
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 255498125312

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3                      NTFS   Partition    535 MB  Healthy    Hidden  

Disk 1 is now the selected disk.

SHGP31-1000GM-2
Disk ID: {2D402218-8511-11EB-9566-6C6A77E68F2E}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1D00)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 4     D                NTFS   Partition    237 GB  Healthy            
  Volume 5         Recovery     NTFS   Partition    450 MB  Healthy    Hidden  
  Volume 6                      FAT32  Partition     99 MB  Healthy    System  
  Volume 7                      NTFS   Partition    535 MB  Healthy    Hidden  

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           450 MB  1024 KB
  Partition 2    System              99 MB   451 MB
  Partition 3    Reserved            16 MB   550 MB
  Partition 4    Primary            237 GB   566 MB
  Partition 5    Recovery           535 MB   237 GB

Partition 1 is now the selected partition.

Partition 1
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 1048576

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 5         Recovery     NTFS   Partition    450 MB  Healthy    Hidden  

Partition 2 is now the selected partition.

Partition 2
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 472907776

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 6                      FAT32  Partition     99 MB  Healthy    System  

Partition 3 is now the selected partition.

Partition 3
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 576716800

There is no volume associated with this partition.

Partition 4 is now the selected partition.

Partition 4
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 593494016

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 4     D                NTFS   Partition    237 GB  Healthy            

Partition 5 is now the selected partition.

Partition 5
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 255498125312

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 7                      NTFS   Partition    535 MB  Healthy    Hidden