How to resize physical partition?

[maximI5]

How to resize physical partition?

I have installed VM on individual partition on physical disk.

When I resized it from host, I got an error.

The partition table on the physical disk has changed since the disk was created. Remove the physical disk from the virtual machine, then add it again

Cannot open the disk 'D:\Windows2021\Windows 10 x64.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine.

When I resized it from VM, I got an error.

And how can I copy VM on a physical disk?

[continuum]

> Remove the physical disk from the virtual machine, then add it again
That indeed is the trick.

> And how can I copy VM on a physical disk?d
I usually do that with Linux dd or better ddrescue

Ulli

[maximI5]

Thanks for answer. 

> Remove the physical disk from the virtual machine, then add it again
That indeed is the trick.

But it doesn't work. I did it before, after that got  'operating system not found.'

> And how can I copy VM on a physical disk?d
I usually do that with Linux dd or better ddrescue

I do that with Paragon, but had 'operating system not found.', when adding a new partition. 

[continuum]

Please show the partitiontable of the physical disk.
Please use Diskmanagement from Windows and/or gparted from Linux.

We also need to see the new vmdk - it probably shows invalid UUIDs.
If possible also attach the original vmdk-file

[maximI5]

Thanks for your help.

I see it some disadvantages with managing the physical disk.

I made only this and VM doesn't start. 

1 Working good VM W10 x64

2. Removing disk. 

3. Adding this same partition again

4. Same

5 System does not start from disk. 

6. Deleting files on host

7. Restoring from backup

Again looks identical 

8 VM starts normally. 

[maximI5]

Difference Before and After in 

In new file Windows 10 x64-1.vmdk

# Disk DescriptorFile
version=1
encoding="windows-1250"
CID=fffffffe
parentCID=ffffffff
createType="partitionedDevice"

# Extent description
RW 63 FLAT "Windows 10 x64-1-pt.vmdk" 0
RDONLY 1985 FLAT "\\.\PhysicalDrive5" 63 partitionUUID \\?\scsi#disk&ven_nvme&prod_ct500p2ssd8#5&2c4f139f&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
RW 716800 ZERO
RW 306743296 ZERO
RW 210747392 FLAT "\\.\PhysicalDrive5" 307462144 partitionUUID \\?\scsi#disk&ven_nvme&prod_ct500p2ssd8#5&2c4f139f&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
RW 458563584 ZERO
RW 48 ZERO

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.biosCylinders = "60801"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosSectors = "63"
ddb.geometry.cylinders = "60801"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "090d8ee173c3ebdd526a0656fffffffe"
ddb.uuid = "60 00 C2 9e 23 83 20 ff-40 82 44 ec de 0f b9 cd"
ddb.virtualHWVersion = "18"

In old file Windows 10 x64-0.vmdk

# Disk DescriptorFile
version=1
encoding="windows-1250"
CID=b8600966
parentCID=ffffffff
createType="partitionedDevice"

# Extent description
RW 63 FLAT "Windows 10 x64-0-pt.vmdk" 0
RDONLY 1985 FLAT "\\.\PhysicalDrive5" 63 partitionUUID \\?\scsi#disk&ven_nvme&prod_ct500p2ssd8#5&2c4f139f&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
RW 716800 ZERO
RW 306743296 ZERO
RW 210747392 FLAT "\\.\PhysicalDrive5" 307462144 partitionUUID \\?\scsi#disk&ven_nvme&prod_ct500p2ssd8#5&2c4f139f&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
RW 458563584 ZERO
RW 48 ZERO

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.biosCylinders = "60801"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosSectors = "63"
ddb.geometry.cylinders = "60801"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "b3f0da4117ea172ffeba3dbfb8600966"
ddb.uuid = "60 00 C2 95 57 87 1f c9-e8 04 cd 00 b6 2d fd b4"
ddb.virtualHWVersion = "18"

[continuum]

please show screenshot of diskmanagement - we need to know wether the hostOS needs access to disk5.
I assume you launch Workstation as administrator - should be obvious ....

Ulli

[maximI5]

Thank you for your time.

maybe simply I  will use vmdisk instead physicals .

Yes, as administrator.

[continuum]

Looks like the same disk has the 350mb boot partition ! - means you will not be able to use this physical disk.
Use a regular vmdk instead - that will work so much more flawless and more reliable ....

Ulli

[maximI5]

I don't think so, the part. 350MB is not connect to VM,

And most important,  its works before, and it is work after backup this file