-
- Aug 27, 2013
-
- 21
-
- 0
-
- 10,510
- 0
-
#1
I recently purchased a new 500gb ssd to replace my 120gb ssd. I purchased Paragon Migrate OS to SSD software for $20 but I keep getting the following errors:
«Failed to copy the partition with the OS. Error: VSS: Can’t read the volume data.»
Does anyone know what I need to do?
Furthermore, If i don’t get to migrate the drive and reinstall Windows, will my other drives in the computer be formatted as well or will they be unharmed? If I unplug them, can I just plug them in after? I have Steam on a 1TB HDD.
-
- Jan 19, 2004
-
- 373
-
- 18
-
- 18,965
- 56
-
#2
This Windows feature allows files that would otherwise be locked to be copied, and also allows live volumes to be copied, even while they are still in use. When VSS works it is a great feature. But it can fail due to file permissions not being correct, or the VSS service not running, or bad sectors, or file system errors.
But in this case I think it is easier to clone the drive from a self booting USB drive or CD. Then VSS isn’t required. There are free open source programs available to clone drives.
-
- Jan 19, 2004
-
- 373
-
- 18
-
- 18,965
- 56
-
#2
This Windows feature allows files that would otherwise be locked to be copied, and also allows live volumes to be copied, even while they are still in use. When VSS works it is a great feature. But it can fail due to file permissions not being correct, or the VSS service not running, or bad sectors, or file system errors.
But in this case I think it is easier to clone the drive from a self booting USB drive or CD. Then VSS isn’t required. There are free open source programs available to clone drives.
-
- Aug 27, 2013
-
- 21
-
- 0
-
- 10,510
- 0
-
#3
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
- Remove From My Forums
-
Question
-
Hi,
trying to integrate this step into my in-place TS Win7 to Win10 but it keeps failing with the «Cannot find OS Partition(s) for disk 0». I have read many articles but nobody offered a clear solution for this.
This is how most of our windows 10 machine’s disks look like. So Windows 1903 version, it should convert without problems but TS fails.
Any suggestions? We need to do this without data loss ofcourse.
Cheers!
All replies
-
Hi,
Have you tried the workaround described the Known issue section of this article? It mentions an issue with win10 v1903 when MBR2GPT.exe runs inside an imaging process such as a System Center Configuration Manager task sequence. And the workaround
is to copy the missing files and then commit the change.For more details, we may refer to:
MBR2GPT.EXE
In addition, is the command line in task sequence is something like this?
cmd.exe /c mbr2gpt.exe /disk:0 /convert /allowFullOS
Hope the above information helps.
Regards,
Alex Zhu
————————————————
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
Hi AlexZhu,
the command ist exactly like you wrote it, but the workaround — I have not seen this and will try it out during the day and report back.
Thank you!
-
Hi Tonito,
It seems there is no update for a couple of days. May we know the current status of the problem? Is there any other assistance we can provide?
Regards,
Alex Zhu
————————————————
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
Hi Alex,
no luck with this. I cannot get it to work.
This is what I get when I do a test run in 1903, and the same (I presume) happens in TS. I apply the step right after the conversion from BIOS to UEFI.
Is this even meant to be used during the in place TS?
Thanks
-
Hi Michael,
I have the three files in the boot image like described in the ms docs link, I also saw the link and followed it but it did not work. To me it seems that the mbr2gpt looks only at the 100MB System Reserved partition which is not bootable, but our machines
which run Windows 7 are setup this way.How can I make mbr2gpt to look at the C: partition?
Thanks
-
Hi Tonito,
Just to confirm with you, have we run mbr2gpt.exe before the firmware conversion or after the conversion. It should before the conversion.
MBR2GPT.exe can be run from the full OS, or in WinPE, however it should be run before the conversion of BIOS to UEFI during an in-place upgrade and most preferably in WinPE.
Hope the above information helps.
Regards,
Alex Zhu
————————————————
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
Hi Alex,
I can confirm that I am running the mbr2gpt before firmware conversion and in winpe. The only thing that i will now test is chaning the boot.wim. I had one from before selected. Will report here after it is done.
Cheers,
I’m trying to use MBR2GPT
to convert an MBR/BIOS disk to GPT/UEFI. I’m getting the error Cannot find OS partition(s) for disk 0
. I found this in setupact.log
:
GetOSDeviceVolume: Cannot get NT path for entry.[gle=0x000000ea]
FindOSPartitions: Cannot get volume name for the recovery boot entry. Error: 0x000000EA[gle=0x000000ea]
Cannot find OS partition(s) for disk 0[gle=0x000000ea]
My OS is a recent Windows 10 version. It might be a Windows 7 upgrade, and the disk has been resized in the past with gparted
. This is in a VM with a snapshot, so I can run risky commands and revert without any problems.
Command I’m running:
C:WINDOWSsystem32>MBR2GPT.EXE /convert /allowfullos
MBR2GPT will now attempt to convert the default book disk.
If conversion is successful the disk can only be booted in GPT mode.
These changes cannot be undone!
MBR2GPT: Attempting to convert disk 0
MBR2GPT: Retrieving layout of disk
MBR2GPT: Validating layout, disk sector size is: 512 bytes
Cannot find OS partition(s) for disk 0
Complete setupact.log
:
2021-09-28 10:10:50, Info MBR2GPT was explicitly asked to run in full OS mode.
2021-09-28 10:10:50, Info MBR2GPT: System disk number is 0
2021-09-28 10:10:50, Info MBR2GPT: Attempting to convert disk 0
2021-09-28 10:10:50, Info MBR2GPT: Retrieving layout of disk
2021-09-28 10:10:50, Info MBR2GPT: Initial partition information
2021-09-28 10:10:50, Info ===========================================================
2021-09-28 10:10:50, Info Partition layout for disk: 0
2021-09-28 10:10:50, Info Partition style : MBR
2021-09-28 10:10:50, Info MBR signature: 53033256
2021-09-28 10:10:50, Info Number of partitions : 3
2021-09-28 10:10:50, Info ===================PARTITION===============================
2021-09-28 10:10:50, Info Number: 1
2021-09-28 10:10:50, Info Type: 7
2021-09-28 10:10:50, Info Boot: Yes
2021-09-28 10:10:50, Info Recognized: Yes
2021-09-28 10:10:50, Info Style: 0
2021-09-28 10:10:50, Info Offset: 1048576
2021-09-28 10:10:50, Info Length: 524288000
2021-09-28 10:10:50, Info Volume: \?Volume{03293928-0000-0000-0000-100000000000}
2021-09-28 10:10:50, Info Drive: None
2021-09-28 10:10:50, Info NT Path: DeviceHardDisk0Partition1
2021-09-28 10:10:50, Info ===================PARTITION===============================
2021-09-28 10:10:50, Info Number: 2
2021-09-28 10:10:50, Info Type: 7
2021-09-28 10:10:50, Info Boot: No
2021-09-28 10:10:50, Info Recognized: Yes
2021-09-28 10:10:50, Info Style: 0
2021-09-28 10:10:50, Info Offset: 525336576
2021-09-28 10:10:50, Info Length: 79455782912
2021-09-28 10:10:50, Info Volume: \?Volume{03293928-0000-0000-0000-501f00000000}
2021-09-28 10:10:50, Info Drive: C:
2021-09-28 10:10:50, Info NT Path: DeviceHardDisk0Partition2
2021-09-28 10:10:50, Info ===================PARTITION===============================
2021-09-28 10:10:50, Info Number: 3
2021-09-28 10:10:50, Info Type: 39
2021-09-28 10:10:50, Info Boot: No
2021-09-28 10:10:50, Info Recognized: Yes
2021-09-28 10:10:50, Info Style: 0
2021-09-28 10:10:50, Info Offset: 79982622720
2021-09-28 10:10:50, Info Length: 542868480
2021-09-28 10:10:50, Info Volume: \?Volume{03293928-0000-0000-00f8-559f12000000}
2021-09-28 10:10:50, Info Drive: None
2021-09-28 10:10:50, Info NT Path: DeviceHardDisk0Partition3
2021-09-28 10:10:50, Info ===========================================================
2021-09-28 10:10:50, Info ESP partition size will be 104857600
2021-09-28 10:10:50, Info MBR2GPT: Validating layout, disk sector size is: 512 bytes
2021-09-28 10:10:50, Info BCD: Opening store. Flags: 0x0
2021-09-28 10:10:50, Info BCD: Store path: "??GLOBALROOTdeviceharddisk0partition1BootBCD"
2021-09-28 10:10:50, Info BCD: Loaded hive at BCD00000000
2021-09-28 10:10:50, Info BCD: Opening object {9dea862c-5cdd-4e70-acc1-f32b344d4795}
2021-09-28 10:10:50, Info FindOSPartitions: Default boot entry: {001E9BBC-213D-11EB-B4BB-F2D0CE0F2B87}
2021-09-28 10:10:50, Info BCD: Opening object {001e9bbc-213d-11eb-b4bb-f2d0ce0f2b87}
2021-09-28 10:10:50, Info VERBOSE: Device path: DeviceHarddiskVolume2
2021-09-28 10:10:50, Info VERBOSE: Dos path: \?GLOBALROOTDeviceHarddiskVolume2
2021-09-28 10:10:50, Info FindOSPartitions: Volume name for the default boot entry: \?Volume{03293928-0000-0000-0000-501f00000000}
2021-09-28 10:10:50, Info BCD: Opening object {1cac28c7-213d-11eb-8bd4-98ea449f7573}
2021-09-28 10:10:50, Error GetOSDeviceVolume: Cannot get NT path for entry.[gle=0x000000ea]
2021-09-28 10:10:50, Error FindOSPartitions: Cannot get volume name for the recovery boot entry. Error: 0x000000EA[gle=0x000000ea]
2021-09-28 10:10:50, Error Cannot find OS partition(s) for disk 0[gle=0x000000ea]
2021-09-28 10:10:50, Info MBR2GPT: Partition information at error point
2021-09-28 10:10:50, Info ===========================================================
2021-09-28 10:10:50, Info Partition layout for disk: 0
2021-09-28 10:10:50, Info Partition style : MBR
2021-09-28 10:10:50, Info MBR signature: 53033256
2021-09-28 10:10:50, Info Number of partitions : 3
2021-09-28 10:10:50, Info ===================PARTITION===============================
2021-09-28 10:10:50, Info Number: 1
2021-09-28 10:10:50, Info Type: 7
2021-09-28 10:10:50, Info Boot: Yes
2021-09-28 10:10:50, Info Recognized: Yes
2021-09-28 10:10:50, Info Style: 0
2021-09-28 10:10:50, Info Offset: 1048576
2021-09-28 10:10:50, Info Length: 524288000
2021-09-28 10:10:50, Info Volume: \?Volume{03293928-0000-0000-0000-100000000000}
2021-09-28 10:10:50, Info Drive: None
2021-09-28 10:10:50, Info NT Path: DeviceHardDisk0Partition1
2021-09-28 10:10:50, Info ===================PARTITION===============================
2021-09-28 10:10:50, Info Number: 2
2021-09-28 10:10:50, Info Type: 7
2021-09-28 10:10:50, Info Boot: No
2021-09-28 10:10:50, Info Recognized: Yes
2021-09-28 10:10:50, Info Style: 0
2021-09-28 10:10:50, Info Offset: 525336576
2021-09-28 10:10:50, Info Length: 79455782912
2021-09-28 10:10:50, Info Volume: \?Volume{03293928-0000-0000-0000-501f00000000}
2021-09-28 10:10:50, Info Drive: C:
2021-09-28 10:10:50, Info NT Path: DeviceHardDisk0Partition2
2021-09-28 10:10:50, Info ===================PARTITION===============================
2021-09-28 10:10:50, Info Number: 3
2021-09-28 10:10:50, Info Type: 39
2021-09-28 10:10:50, Info Boot: No
2021-09-28 10:10:50, Info Recognized: Yes
2021-09-28 10:10:50, Info Style: 0
2021-09-28 10:10:50, Info Offset: 79982622720
2021-09-28 10:10:50, Info Length: 542868480
2021-09-28 10:10:50, Info Volume: \?Volume{03293928-0000-0000-00f8-559f12000000}
2021-09-28 10:10:50, Info Drive: None
2021-09-28 10:10:50, Info NT Path: DeviceHardDisk0Partition3
2021-09-28 10:10:50, Info ===========================================================
bcdedit
:
C:WINDOWSsystem32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=DeviceHarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {001e9bbb-213d-11eb-b4bb-f2d0ce0f2b87}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path WINDOWSsystem32winload.exe
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {1cac28c7-213d-11eb-8bd4-98ea449f7573}
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot WINDOWS
resumeobject {001e9bbb-213d-11eb-b4bb-f2d0ce0f2b87}
nx OptIn
bootmenupolicy Standard