New
#1
why diskpart volume number not match with bcdedit?
I found that diskpart volume# and bcdedit volume# is not match. what is the reason for that?
attach the disk management screenshot in case useful
I found that diskpart volume# and bcdedit volume# is not match. what is the reason for that?
attach the disk management screenshot in case useful
Hello
From my experience defaulting Volume 0 will always come from a DVD Rom or an Extended partition of a Hard Disk. Remove the DVD Rom if it was originally installed to remove Volume 0 or and Extend a HD to a Logical drive and you'll create Volume 0 again.
Ive just had a quick look at your setup, and noticed you are missing the Microsofts Reserved partition, which is part of the EFi boot sequence all depending whether your drives are running in MBR or GPT format?
By the looks i am having a guess here and say your system is running MBR and not UEFI?
Going back to the Volumes.
Say if you originally start with a Hard Drive being Volume 0, then install a DVD Rom, it will bully its way to the first pecking order and take over Volume 0 and then your Disk will become Volume 1. Extended drives do the same thing.
You need to establish whether youre running BIOS or UEFI, MBR or GPT. Run Diskpart and see which drives are what and which Volumes are extended and write down all the drive letters and sequence.
Edit to add sorry old chap
I know running a dual boot can have a similar effect when you switch operating systems, it'll switch all the drive letters but the two boot partitions stay the same, the microsoft reserved and the EFi dont have drive letters. They are still volumes but they will always reside infront of the operating system in DiskManagement and after the last Partition created on a given hard drive in DiskPart.
Sorry if thats not much help. Let us know any more information if you can
thank you for the detail explanation.
I manually delete the Microsoft Reserved partition.
Just check in the Disk Management, all the disks are GPT.
and according System Information, it is UEFI.
the pc do not have any optical driver/ extend hdd at the moment.
I use separate os(win 10) to backup and restore the primary os(Macrium Reflect).
I think the restoration cause this issue.
- - - Updated - - -
Actually my pc having booting issue, only the primary os is bootable now.Even the boot manager seems not bootable.(but some times able to boot into boot manager, maybe another boot manger in the os partition?)I believe that EasyBCD or Macrium Reflect rescue disk can solve this problem.But just want to know what is happening and try to fix manually in bcdedit, and find out the volume# is not matching with the diskpart.
if I use the following command to assign osdevice partition to Volume 13,
it will assign or display as volume 13(V:), like the following image.Code:bcdedit /set {612b7ff8-da2d-11eb-a34f-8abac159c9d9} osdevice partition=\Device\HarddiskVolume13
yes. I am using GPT, so it is not suitable for my case.
- - - Updated - - -
I have 3 win10 os installed.
My default os is in volume 6, my pc always boot into it, and it is still working.
some times when using other os, I use command line
for one time boot, but it is not working now.Code:bcdedit /bootsequence {612b7ff8-da2d-11eb-a34f-8abac159c9d9} /addfirst
Using my own computer, this is the only way I found to add a boot menu entry with having a drive letter assigned to volume the second OS is installed on. I want to add Win11Temp to my boot menu. It is volume 1. I know that volume 1 is on disk 0. Then I find out that it is partition 2 on disk 0. Then I use the bcdboot command to add harddisk 0 partition 2 to my boot menu. I have not found a way to use just the volume number with bcdboot.
Code:C:\Windows\system32>diskpart Microsoft DiskPart version 10.0.22000.1 Copyright (C) Microsoft Corporation. On computer: RAIDER DISKPART> lis vol Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 D Data NTFS Partition 881 GB Healthy Volume 1 Win11Temp NTFS Partition 64 GB Healthy Volume 2 R RECOVERY FAT32 Partition 8191 MB Healthy Volume 3 C Windows NTFS Partition 443 GB Healthy Boot Volume 4 FAT32 Partition 100 MB Healthy System Volume 5 WinRE tools NTFS Partition 980 MB Healthy Hidden Volume 6 BIOS_RVY NTFS Partition 21 GB Healthy Hidden DISKPART> sel vol 1 Volume 1 is the selected volume. DISKPART> det vol Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- * Disk 0 Online 953 GB 0 B * Read-only : No Hidden : No No Default Drive Letter: No Shadow Copy : No Offline : No BitLocker Encrypted : No Installable : Yes Volume Capacity : 63 GB Volume Free Space : 29 GB DISKPART> lis dis Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 953 GB 0 B * Disk 1 Online 465 GB 0 B * DISKPART> sel dis 0 Disk 0 is now the selected disk. DISKPART> lis par Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 881 GB 1024 KB Partition 2 Primary 64 GB 881 GB Partition 3 Primary 8191 MB 945 GB DISKPART> exit Leaving DiskPart... C:\Windows\system32>bcdboot \\?\GLOBALROOT\device\harddisk0\partition2\Windows /d Boot files successfully created. C:\Windows\system32>
Last edited by NavyLCDR; 12 Feb 2022 at 14:59.