My Cloned SSD is no longer booting.

Before you mess things up:
1. First check your BIOS boot section if it is looking for the correct drive respectively "Windows boot manager"
2. Is the boot drive partition set to "active"? So the system knows on which drive to look for the boot information.
3. What is the error message on the screen?

Disc enumeration really doesn't matter if above 1) & 2) is correct.

dorcom said:

2. Is the boot drive partition set to "active"? So the system knows on which drive to look for the boot information.

This is not applicable in this situation because the SSD in question is GPT partitioned which cannot have an active partition and must be booted in UEFI mode.

Disagree. How would the system then know from all the SSD's and/or HDD's installed which one to look for boot information?
There needs to be a "active" partition flag. Remove it and it does not boot.

From the system I'm currently on typing this post:

I take it these are just information seeking batches, since i'm so bad at describing my condition?

When available upload results for post #10.

If you cannot boot another drive windows RE commands can be posted.

dorcom said:

Disagree. How would the system then know from all the SSD's and/or HDD's installed which one to look for boot information?
There needs to be a "active" partition flag. Remove it and it does not boot.

From the system I'm currently on typing this post:

You can disagree all you want to. It doesn't change facts. You cannot mark any partition as active on a GPT partitioned drive, it is impossible to do so.

Code:

Microsoft DiskPart version 10.0.19041.610

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

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> select part 1

Partition 1 is now the selected partition.

DISKPART> active

The selected disk is not a fixed MBR disk.
The ACTIVE command can only be used on fixed MBR disks.

DISKPART> detail disk

THNSN5512GPUK NVMe TOSHIBA 512GB
Disk ID: {2D1BDC36-0E5D-4F13-8127-5364B7C757E3}
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  : 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   20H2         NTFS   Partition    412 GB  Healthy    Boot
  Volume 1     T   Home         NTFS   Partition     64 GB  Healthy
  Volume 2                      FAT32  Partition    100 MB  Healthy    System
  Volume 3                      NTFS   Partition    552 MB  Healthy    Hidden

DISKPART>

You may want to read up more on UEFI booting and GPT partitioned drives. UEFI determines bootable partitions by looking for specific folder structures and files, not by looking for an active partition, because there is no active attribute available to set for partitions on a GPT disk. The "active" tag that you are seeing in AEOMI partition wizard is only telling you which partition the computer booted from. It is not indicated the partition has an attribute for active set on it. Don't believe me, try setting one of the other partitions as active on that GPT disk.

My computer boots from disk 0, partition 1 because it is a FAT32 partition that contains the proper folder structure and files for UEFI booting. It is not set as active because it can't be.

@NavyLCDR
I'm initiating batches with a measure of caution but deciding to trust. It does seem like the tuneup batch is for the current booted drive only. Is that really necessary?

- - - Updated - - -

Heres the Diskpart info
The unbooting SSD drive is Disk 2. I currently have the boot drive (Disk 0) the old reformated 500G (Disk 1) and SSD (Disk 2) installed on this asus. And yes I was confused earlier about the MB that was intended for the SSD. That was an older Asrock. (Cant pull up the model at the moment but it must have been an UEFI capable bios since it was booting earlier just after cloning).

********************************

Disk 0 : HDD. It has 3 partition(s). Model: ST1000DM003-1SB10C
Disk 1 : HDD. It has 2 partition(s). Model: ST500DM002-1BD142
Disk 2 : SSD. It has 5 partition(s). Model: CT1000MX500SSD1

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

Microsoft DiskPart version 10.0.19041.610

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

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 931 GB 1024 KB
Disk 1 Online 465 GB 1024 KB *
Disk 2 Online 931 GB 1024 KB *

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 D DVD-ROM 0 B No Media
Volume 1 System Rese NTFS Partition 100 MB Healthy System
Volume 2 C NTFS Partition 930 GB Healthy Boot
Volume 3 NTFS Partition 563 MB Healthy Hidden
Volume 4 E Data Drive NTFS Partition 465 GB Healthy
Volume 5 F NTFS Partition 464 GB Healthy
Volume 6 G Local Disk NTFS Partition 465 GB Healthy
Volume 7 FAT32 Partition 100 MB Healthy Hidden
Volume 8 NTFS Partition 567 MB Healthy Hidden

Disk 0 is now the selected disk.

ST1000DM 003-1SB10C SCSI Disk Device
Disk ID: FB9B0A9F
Type : SATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C00T00L00)
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 1 System Rese NTFS Partition 100 MB Healthy System
Volume 2 C NTFS Partition 930 GB Healthy Boot
Volume 3 NTFS Partition 563 MB Healthy Hidden

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 100 MB 1024 KB
Partition 2 Primary 930 GB 101 MB
Partition 3 Recovery 563 MB 930 GB

Partition 1 is now the selected partition.

Partition 1
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 1 System Rese NTFS Partition 100 MB Healthy System

Partition 2 is now the selected partition.

Partition 2
Type : 07
Hidden: No
Active: No
Offset in Bytes: 105906176

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

Partition 3 is now the selected partition.

Partition 3
Type : 27
Hidden: No
Active: No
Offset in Bytes: 999611695104

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

Disk 1 is now the selected disk.

ST500DM002-1BD142
Disk ID: {CC57611C-A546-47E6-8F2D-AB120046B22F}
Type : SATA
Status : Online
Path : 2
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C02T00L00)
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 E Data Drive NTFS Partition 465 GB Healthy

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Reserved 15 MB 17 KB
Partition 2 Primary 465 GB 16 MB

Partition 1 is now the selected partition.

Partition 1
Type : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden : Yes
Required: No
Attrib : 0000000000000000
Offset in Bytes: 17408

There is no volume associated with this partition.

Partition 2 is now the selected partition.

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

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 4 E Data Drive NTFS Partition 465 GB Healthy

Disk 2 is now the selected disk.

CT1000MX500SSD1
Disk ID: {2BE9920C-8BE0-4315-B93B-5BB0CCE27775}
Type : SATA
Status : Online
Path : 3
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C03T00L00)
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 5 F NTFS Partition 464 GB Healthy
Volume 6 G Local Disk NTFS Partition 465 GB Healthy
Volume 7 FAT32 Partition 100 MB Healthy Hidden
Volume 8 NTFS Partition 567 MB Healthy Hidden

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 100 MB 1024 KB
Partition 2 Reserved 128 MB 101 MB
Partition 3 Primary 464 GB 229 MB
Partition 4 Recovery 567 MB 465 GB
Partition 5 Primary 465 GB 465 GB

Partition 1 is now the selected partition.

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

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

Partition 2 is now the selected partition.

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

There is no volume associated with this partition.

Partition 3 is now the selected partition.

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

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 5 F NTFS Partition 464 GB Healthy

Partition 4 is now the selected partition.

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

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

Partition 5 is now the selected partition.

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

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 6 G Local Disk NTFS Partition 465 GB Healthy

===============================================================================

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: db19d66e-239f-11eb-98a5-f4b123214116
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

===============================================================================

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {95ab2809-239f-11eb-a3bc-8ae3970d5828}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {db19d66e-239f-11eb-98a5-f4b123214116}
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {95ab2809-239f-11eb-a3bc-8ae3970d5828}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {db19d66e-239f-11eb-98a5-f4b123214116}
device ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{db19d66f-239f-11eb-98a5-f4b123214116}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{db19d66f-239f-11eb-98a5-f4b123214116}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {dddf3167-60f6-11e6-84b5-d00a583663e2}
device ramdisk=[C:]\Recovery\dddf3167-60f6-11e6-84b5-d00a583663e2\Winre.wim,{dddf3168-60f6-11e6-84b5-d00a583663e2}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\dddf3167-60f6-11e6-84b5-d00a583663e2\Winre.wim,{dddf3168-60f6-11e6-84b5-d00a583663e2}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {95ab2809-239f-11eb-a3bc-8ae3970d5828}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {db19d66e-239f-11eb-98a5-f4b123214116}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {db19d66f-239f-11eb-98a5-f4b123214116}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume3
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {dddf3168-60f6-11e6-84b5-d00a583663e2}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\dddf3167-60f6-11e6-84b5-d00a583663e2\boot.sdi

- - - Updated - - -

zbook said:

When available upload results for post #10.

If you cannot boot another drive windows RE commands can be posted.

What are Windows RE commands?

- - - Updated - - -

and the tuneup

**********************************

###########################################################
# The following commands will be run in sequence. #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="RONS-PC" get AutomaticManagedPagefile
wmic Computersystem where name="RONS-PC" set AutomaticManagedPagefile=True
wmic Computersystem where name="RONS-PC" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19041.804

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19041.804

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
969472 file records processed.
File verification completed.
Phase duration (File record verification): 34.70 seconds.
22767 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.75 milliseconds.

Stage 2: Examining file name linkage ...
60931 reparse records processed.
1224200 index entries processed.
Index verification completed.
Phase duration (Index verification): 2.42 minutes.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 4.00 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.25 milliseconds.
60931 reparse records processed.
Phase duration (Reparse point and Object ID verification): 161.85 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 118.32 milliseconds.
127365 data files processed.
Phase duration (Data attribute verification): 1.71 milliseconds.
CHKDSK is verifying Usn Journal...
37600640 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 249.44 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

976079122 KB total disk space.
236421896 KB in 567072 files.
372136 KB in 127366 indexes.
0 KB in bad sectors.
1119690 KB in use by the system.
65536 KB occupied by the log file.
738165400 KB available on disk.

4096 bytes in each allocation unit.
244019780 total allocation units on disk.
184541350 allocation units available on disk.
Total duration: 3.08 minutes (184861 ms).

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
TRUE


C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\RONS-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
2


C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\RONS-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>wmic pagefile list /format:list


AllocatedBaseSize=16384
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20160812174049.743200-420
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\WINDOWS\system32>wmic Computersystem where name="RONS-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\WINDOWS\system32>wmic Computersystem where name="RONS-PC" set AutomaticManagedPagefile=True
Updating property(s) of '\\RONS-PC\ROOT\CIMV2:Win32_ComputerSystem.Name="RONS-PC"'
Property(s) update successful.

C:\WINDOWS\system32>wmic Computersystem where name="RONS-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>Echo off
###################################################################################
# How to capture batch file data and post in your thread in the BSOD forum #
# #
# Batch files and instructions for use in BSOD debugging[Part Two-Four] #
# #
# Press [V] to visit the above web page for detailed instructions. #
# Press [C] to close this window. #
###################################################################################

NavyLCDR said:

This is not applicable in this situation because the SSD in question is GPT partitioned which cannot have an active partition and must be booted in UEFI mode.

Then please explain why a partition software reports it and it is the only one reported as "active" and when I set the flag to normal the system won't boot.

Which drive was booted to run the commands?
Which drive needs to become bootable?

Disk 0 :ST1000DM003-1SB10C
Disk 1 :ST500DM002-1BD142
Disk 2 :CT1000MX500SSD1

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Disk 0 = MBR
Disk 1 = GPT
Disk 2 = GPT


Please post an image of the current BIOS settings:
UEFI native (without CSM)
UEFI hybrid (with CSM)
Legacy

dorcom said:

Then please explain why a partition software reports it and it is the only one reported as "active" and when I set the flag to normal the system won't boot.

GPT partitioning has absolutely no capability to mark a partition as active. Period. It is not there. It is impossible.

Take any disk, internal, external, USB, flash drive, SSD, NVME, whatever. Initialize it as GPT, create a partition on it. Then attempt to mark that partition as active. Nothing will actually mark the partition as active because it is impossible. Third party partitioning programs may assign an active label to a partition to indicate the computer booted from that partition, but that is entirely different than the active flag on a partition on an MBR drive.

Code:

Microsoft DiskPart version 10.0.19041.610

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

DISKPART> select disk 2

Disk 2 is now the selected disk.

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART> convert mbr

DiskPart successfully converted the selected disk to MBR format.

DISKPART> create part pri

DiskPart succeeded in creating the specified partition.

DISKPART> active

DiskPart marked the current partition as active.

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART> convert gpt

DiskPart successfully converted the selected disk to GPT format.

DISKPART> create part pri

DiskPart succeeded in creating the specified partition.

DISKPART> active

The selected disk is not a fixed MBR disk.
The ACTIVE command can only be used on fixed MBR disks.

DISKPART>