VMware Communities
ashley2019
Contributor
Contributor
Jump to solution

Workstation: The parent of cannot open the disk *.vmdk or one of the snapshot disks it depends on.

First, I'm using linux-vmware, and the vmwre warning there is not enought disk space and the virtual machine should be suspend or shutdown. For there are some data in the machine , i choosed suspending the machine.
Second, expected to free some space, i delete one old snapshot 5 . Then the error happens, I cannot start the virtual machine for the error like:

The parent of this virtual disk could not be opened
Cannot open the disk
'/media/root/DISK1/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-00008.vmdk' or one of the snapshot disks it depends on.
Module 'Disk' power on failed.
Failed to start the virtual machine.

Third, sadly i revert the machine back to the most recent snapshot, but the error still

The parent of this virtual disk could not be opened
Cannot open the disk
'/media/root/DISK1/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-00009.vmdk' ..
Module 'Disk' power on failed.
Failed to start the virtual machine.

Forth, i think the virtual machine setting must get something wrong. And the machine can revert to the snapshot, which older than the deleted one.
My environment is,Kali - Linux, and the vmware workstation Pro 17.

Following the suggestion in stakoverflow, i tried delte log\lck\nvram files ,but the machine still cannot work.
Below,i attach the detailed files related hoping would help.
Thanks for any suggestion on retrive my files or correct the machine!
Much Appreciate !

ps. After studying the knowledge about vmdk delete process, i think the error happened at the time when vmware try merge the to be delted vmdk while there is not enough space for doing such space-consuming jobs.

0 Kudos
2 Solutions

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

It looks like the metadata itself is ok, and it's just the file size which needs to be reduced to the expected size of 139,001,856 Bytes.
Please backup the original file prior to running the following command.

dd if=/dev/null of="Windows 7 x64-cl1-000005-s001.vmdk" bs=1 seek=139001856 count=1

André

View solution in original post

0 Kudos
ashley2019
Contributor
Contributor
Jump to solution

After command

dd if=/dev/null of="Windows 7 x64-cl1-000005-s001.vmdk" bs=1 seek=139001856 count=1

i try another command

vmware-vdiskmanager -R '/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005.vmdk'

and has the result

The virtual disk, '/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005.vmdk', was corrupted and has been successfully repaired.

YES!The machine repaired!

THANKS A LOT!

 

 

View solution in original post

Tags (1)
0 Kudos
10 Replies
ashley2019
Contributor
Contributor
Jump to solution

more vmdk settings attached

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Errors due to out of disk space issues are difficult to solve in most cases.
It would be helpful to have a complete file listing to get a first overview.

For this, please run ls -lisa > filelist.txt in the VM's folder, and attach the filelist.txt file to your next reply.

Some additional questions:

  1. How much free disk space do you currently have?
  2. When did you last backup the VM's files/folder?

André

Hint: The number of files that can be attached to a single post is limited, but you can always simply compress/zip a number of files, and attach the .zip archive instead.

0 Kudos
ashley2019
Contributor
Contributor
Jump to solution

Thanks for suggestion. I upload the filelist.txt in the attachment.

After the error happened , I delete several older virtual machines. So now there are enought spaces. The snapshot 4 backup 4 months ago can be reverted to , but may have many files not writen.

One point attract my attention: In .vmsd ,there snapshot 7 (with 000006-vmdk ) has parent snapshot 4 (with  000004-vmdk). when looking into the 000006.vmdk and its parent, I found a loog dependet link.

000006.vmdk-> 0000003.vmdk -> 000005.vmdk -> 000004.vmdk

Maybe this indication can help investigation.

 

0 Kudos
ashley2019
Contributor
Contributor
Jump to solution

I try the command:

/usr/bin/vmware-vdiskmanager -R '/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Win7 x64 for Program.vmx' 

but the command finished immediately with no output. The machine still not work

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Let's see whether the corrupted metadata in can be fixed, and already solve the issue.
If the corruption can be fixed, but there's still an issue with the VM, I will request more files to get a complete overview.

Please run the following command to extract the metadata (no user data) from the corrupted .vmdk file. Then compress/zip the .bin file, and attach the .zip archive to your next reply.

dd if="Windows 7 x64-cl1-000005-s001.vmdk" of="Metadata-000005-s001-264306688.bin" bs=512 count=1664

André

0 Kudos
ashley2019
Contributor
Contributor
Jump to solution

Much Thanks  for your working.

Even A conclusion saying impossible from an expert will save me much time.

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

It looks like the metadata itself is ok, and it's just the file size which needs to be reduced to the expected size of 139,001,856 Bytes.
Please backup the original file prior to running the following command.

dd if=/dev/null of="Windows 7 x64-cl1-000005-s001.vmdk" bs=1 seek=139001856 count=1

André

0 Kudos
ashley2019
Contributor
Contributor
Jump to solution

well, vmware still has the error

Unable to change virtual machine power state: The parent of this virtual disk could not be opened Cannot open the disk '/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000010.vmdk' or one of the snapshot disks it depends on. Module 'Disk' power on failed. Failed to start the virtual machine.

The log file was uploaded, the error seems:

2023-07-03T01:01:48.255Z In(05) vmx DISKLIB-SPARSE: "/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005-s001.vmdk" : failed to open (14): Disk needs repair.

2023-07-03T01:01:48.255Z In(05) vmx DISKLIB-LINK : "/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005.vmdk" : failed to open (The specified virtual disk needs repair).

2023-07-03T01:01:48.255Z Er(02) vmx DISKLIB-CHAIN : DiskChainOpen: "/media/root/Angela/vmware workstation/Win7 x64 for Program

20230306 (copy 1)/Windows 7 x64-cl1-000010.vmdk": Failed to open parent "/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005.vmdk": The specified virtual disk needs repair

2023-07-03T01:01:48.255Z Er(02) vmx DISKLIB-CHAIN : DiskChainOpen: "/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005.vmdk": failed to open: The parent of this virtual disk could not be opened. 2023-07-03T01:01:48.256Z In(05) vmx DISKLIB-LIB : Failed to open '/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000010.vmdk' with flags 0xa The parent of this virtual disk could not be opened (23).

0 Kudos
ashley2019
Contributor
Contributor
Jump to solution

After command

dd if=/dev/null of="Windows 7 x64-cl1-000005-s001.vmdk" bs=1 seek=139001856 count=1

i try another command

vmware-vdiskmanager -R '/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005.vmdk'

and has the result

The virtual disk, '/media/root/Angela/vmware workstation/Win7 x64 for Program 20230306 (copy 1)/Windows 7 x64-cl1-000005.vmdk', was corrupted and has been successfully repaired.

YES!The machine repaired!

THANKS A LOT!

 

 

Tags (1)
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Sorry, my bad, I forgot to reset the "uncleanShutdown" flag, which however vmware-vdiskmanager took care of now.
Glad to see that the issue could be solved.

André

0 Kudos