Can't get UEFI drive to boot - Chapter 2

OK. With the problem drive connected boot back into legacy. Run:

Code:

diskpart
list disk
select disk 0
uniqueid disk

Then keep selecting each disk and running the uniqueid disk command on each disk. Look for any two that are the same.

Example:

Code:

Microsoft Windows [Version 10.0.22000.318]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>diskpart

Microsoft DiskPart version 10.0.22000.1

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

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          476 GB      0 B        *
  Disk 1    Online          476 GB      0 B        *

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> uniqueid disk

Disk ID: {2D1BDC36-0E5D-4F13-8127-5364B7C757E3}

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> uniqueid disk

Disk ID: {C665D03D-1A0D-44B6-9392-22FD3C6CA0D3}

DISKPART>

I was thinking about backing up the 860 disk, wiping it clean and then restoring it.

- - - Updated - - -

No duplicates:

Code:

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          465 GB      0 B
  Disk 1    Online         1863 GB      0 B        *
  Disk 2    Online         1863 GB      0 B
  Disk 3    Online         1863 GB    15 MB
  Disk 4    Online         2794 GB      0 B        *

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> uniqueid  disk

Disk ID: 23A032A5

DISKPART> sel disk 1

Disk 1 is now the selected disk.

DISKPART> uniqueid  disk

Disk ID: {4EAAEE76-2710-0000-4F03-806E6F6E6963}

DISKPART> sel disk 2

Disk 2 is now the selected disk.

DISKPART> uniqueid  disk

Disk ID: 69924197

DISKPART> sel disk 3

Disk 3 is now the selected disk.

DISKPART> uniqueid  disk

Disk ID: 02E3D5C7

DISKPART> sel disk 4

Disk 4 is now the selected disk.

DISKPART> uniqueid  disk

Disk ID: {4F44875A-6D9A-4BA2-AEAF-7D417ECFDB9F}

Disk 0 and Disk 1 are your two M.2 SSDs?

Open a powershell with admin and run:

Code:

GWMI -namespace root\cimv2 -class win32_volume | FL -property DriveLetter, DeviceID

Look for two ID's that are the same

Example:

Code:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\Windows\system32> GWMI -namespace root\cimv2 -class win32_volume | FL -property DriveLetter, DeviceID


DriveLetter : C:
DeviceID    : \\?\Volume{2ed87502-eb77-4805-962d-7c7b391fcee3}\

DriveLetter : D:
DeviceID    : \\?\Volume{3a25bd8e-ffb6-47c3-8da0-459ba8f1ab92}\

DriveLetter : R:
DeviceID    : \\?\Volume{139b94a8-53d9-4ea8-843b-9507e242e935}\

DriveLetter :
DeviceID    : \\?\Volume{ba929891-4615-40e0-818c-1923f6cbd5e7}\

PS C:\Windows\system32>

As you posted, If you have a backup of the 860 disk, then you could wipe it - I recommend the diskpart, clean command. See if your booting problems exist with the blank disk connected. I would check for collisions with the above powershell command first.

Yes, disk 0 is legacy; disk 1 is EFI. Here is command results:

Code:

PS C:\WINDOWS\system32> GWMI -namespace root\cimv2 -class win32_volume | FL -property DriveLetter, DeviceID


DriveLetter : Z:
DeviceID    : \\?\Volume{23a032a5-0000-0000-007e-000000000000}\

DriveLetter : P:
DeviceID    : \\?\Volume{4fe21367-2710-0000-4f03-806e6f6e6963}\

DriveLetter : E:
DeviceID    : \\?\Volume{4eab1586-2710-0000-4f03-806e6f6e6963}\

DriveLetter : F:
DeviceID    : \\?\Volume{4fe23a77-2710-0000-4f03-806e6f6e6963}\

DriveLetter : D:
DeviceID    : \\?\Volume{69924197-0000-0000-0000-f0e3dd000000}\

DriveLetter : L:
DeviceID    : \\?\Volume{02e3d5c7-0000-0000-0000-000100000000}\

DriveLetter : H:
DeviceID    : \\?\Volume{9fb951dd-69f6-4f2e-b87c-f825154a1610}\

DriveLetter : G:
DeviceID    : \\?\Volume{69924197-0000-0000-0080-100000000000}\

DriveLetter : J:
DeviceID    : \\?\Volume{69924197-0000-0000-0080-b0b8af000000}\

DriveLetter : I:
DeviceID    : \\?\Volume{69924197-0000-0000-0080-c08dc8000000}\

DriveLetter : C:
DeviceID    : \\?\Volume{23a032a5-0000-0000-0000-e01500000000}\

DriveLetter :
DeviceID    : \\?\Volume{23a032a5-0000-0000-0000-b02a74000000}\

DriveLetter : N:
DeviceID    : \\?\Volume{23a032a5-0000-0000-0000-b04e74000000}\

DriveLetter :
DeviceID    : \\?\Volume{4eab3c96-2710-0000-4f03-806e6f6e6963}\

DriveLetter : K:
DeviceID    : \\?\Volume{c1fd48ff-c833-11e9-81b7-806e6f6e6963}\

- - - Updated - - -

C and Z are the same.

- - - Updated - - -

...and N and the one before N.

- - - Updated - - -

G, J and I are the same. They're on the same disk.

- - - Updated - - -

So if the partitions are on the same disk, they should be the same ID's?

- - - Updated - - -

If that's true, P and E should be the same, but they're not.

- - - Updated - - -

Actually P, E and F are on the same GPT disk, but all 3 have different ID's.

- - - Updated - - -

OK, G, J, I and D all have the same ID and they are all on the same disk. SO what's up with P, E and F being on the same disk with different ID's?

- - - Updated - - -

I was comparing only the first 8 characters of each disk. I see they are all different when looking at the entire ID.

Look closer. They are all different:

DeviceID : \\?\Volume{02e3d5c7-0000-0000-0000-000100000000}\
DeviceID : \\?\Volume{23a032a5-0000-0000-0000-b02a74000000}\
DeviceID : \\?\Volume{23a032a5-0000-0000-0000-b04e74000000}\
DeviceID : \\?\Volume{23a032a5-0000-0000-0000-e01500000000}\
DeviceID : \\?\Volume{23a032a5-0000-0000-007e-000000000000}\
DeviceID : \\?\Volume{4eab1586-2710-0000-4f03-806e6f6e6963}\
DeviceID : \\?\Volume{4eab3c96-2710-0000-4f03-806e6f6e6963}\
DeviceID : \\?\Volume{4fe21367-2710-0000-4f03-806e6f6e6963}\
DeviceID : \\?\Volume{4fe23a77-2710-0000-4f03-806e6f6e6963}\
DeviceID : \\?\Volume{69924197-0000-0000-0000-f0e3dd000000}\
DeviceID : \\?\Volume{69924197-0000-0000-0080-100000000000}\
DeviceID : \\?\Volume{69924197-0000-0000-0080-b0b8af000000}\
DeviceID : \\?\Volume{69924197-0000-0000-0080-c08dc8000000}\
DeviceID : \\?\Volume{9fb951dd-69f6-4f2e-b87c-f825154a1610}\
DeviceID : \\?\Volume{c1fd48ff-c833-11e9-81b7-806e6f6e6963}\

I'm at a loss now too. As you stated earlier, make a backup image of the 860. Wipe it clean. See if you have the same problem booting with it connected when it is blank. (note, if it isn't GPT, convert it to GPT). Then restore the partitions back to it, preferrable one at a time.

860 is MBR. Convert to GPT before I do anything else?

thornev said:

860 is MBR. Convert to GPT before I do anything else?

No. Image the partitions first - or do whatever you are going to in order to backup the files. Then you will do:

Code:

diskpart
select disk #
clean
convert gpt

See if you can boot in UEFI with it connected, but blank. Then restore your files or partitions back to the drive. It will stay as GPT. All but one of your partitions (more correctly volumes) on that drive were logical. It's better to have the drive as GPT and restore those partitions as primary partitions.