beno74
Contributor
Contributor

Re: module disk power on failed

Hello Peeps,

I have the same issues, removing lck folder did not help.

I got this error :

The file specified is not a virtual disk

Cannot open the disk 'C:\Users\benso\VM\Win7_Pro_Prod\Win7_Pro-0-s001.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine.

Directory listing;

Spoiler
25/04/2022 10:04 am <DIR> .
24/12/2021 10:09 pm <DIR> ..
24/12/2021 03:04 pm <DIR> caches
06/12/2020 05:37 pm 102 Readme.txt
25/04/2022 10:03 am 71,354 vmware-0.log
25/04/2022 10:03 am 71,357 vmware-1.log
25/04/2022 10:02 am 71,268 vmware-2.log
25/04/2022 10:04 am 71,440 vmware.log
24/04/2022 10:09 pm 3,475,832,832 Win7_Pro-0-s001.vmdk
17/01/2022 12:01 am 524,288 Win7_Pro-0-s002.vmdk
17/01/2022 12:01 am 524,288 Win7_Pro-0-s003.vmdk
17/01/2022 12:01 am 524,288 Win7_Pro-0-s004.vmdk
17/01/2022 12:01 am 524,288 Win7_Pro-0-s005.vmdk
20/01/2022 12:53 am 131,072 Win7_Pro-0-s006.vmdk
24/04/2022 03:51 pm 678 Win7_Pro-0.vmdk
10/04/2022 10:18 pm 4,294,967,296 Win7_Pro-7df5d287.vmem
25/04/2022 01:41 am 1,789,665 Win7_Pro-7df5d287.vmss
16/01/2020 09:56 am 31,676 Win7_Pro-Snapshot1.vmsn
24/04/2022 04:13 am 8,684 Win7_Pro.nvram
16/01/2020 09:55 am 26,782,466,048 Win7_Pro.vmdk
16/01/2020 09:56 am 493 Win7_Pro.vmsd
25/04/2022 09:50 am 3,710 Win7_Pro.vmx
25/12/2021 05:11 pm 3,855 Win7_Pro.vmxf
25/04/2022 09:49 am <DIR> [VM] Win7_Pro - Original
24/12/2021 03:04 pm <DIR> [VM] Win7_Pro_Prod

Please help!

Moderator edit by wila: detached from thread: https://communities.vmware.com/t5/VMware-Workstation-Pro/module-disk-power-on-failed/m-p/2314133#M13...

0 Kudos
7 Replies
continuum
Immortal
Immortal

> Cannot open the disk 'C:\Users\benso\VM\Win7_Pro_Prod\Win7_Pro-0-s001.vmdk' or one of the snapshot disks it depends on.

That is expected. Name-s001.vmdk is NOT A VIRTUAL DISK:
A file with that name is  the first part of the vmdk called Name.vmdk.
The fact that you get a message like this simply means that you or somebody else misconfigured the vmx-file so that it points to Win7_Pro-0-s001.vmdk instead of Win7_Pro-0.vmdk

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
DecioHabiro
Contributor
Contributor

I'm having almost same error:

The parent of this virtual disk could not be opened

Cannot open the disk 'C:\Users\...\Windows Server 2019-000003.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine.

0 Kudos
continuum
Immortal
Immortal

Open vmware.log in a texteditor and look up which file exactly fails.
Then compare that with the files you actually have.

 

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
DecioHabiro
Contributor
Contributor

2022-06-03T14:41:03.623Z In(05) vmx DISK: OPEN nvme0:0 'C:\Users\VB\Windows Server 2019-000002.vmdk' persistent R[]
2022-06-03T14:41:03.729Z In(05) vmx DISKLIB-SPARSE: "C:\Users\VB\Windows Server 2019-s018.vmdk" : failed to open (15): Failed to load header.
2022-06-03T14:41:03.730Z In(05) vmx DISKLIB-LINK : "C:\Users\VB\Windows Server 2019.vmdk" : failed to open (The file specified is not a virtual disk).
2022-06-03T14:41:03.730Z Er(02) vmx DISKLIB-CHAIN : DiskChainOpen: "C:\Users\VB\Windows Server 2019-000002.vmdk": Failed to open parent "C:\Users\VB\Windows Server 2019.vmdk": The file specified is not a virtual disk
2022-06-03T14:41:03.730Z Er(02) vmx DISKLIB-CHAIN : DiskChainOpen: "C:\Users\VB\Windows Server 2019.vmdk": failed to open: The parent of this virtual disk could not be opened.
2022-06-03T14:41:03.734Z In(05) vmx DISKLIB-LIB : Failed to open 'C:\Users\VB\Windows Server 2019-000002.vmdk' with flags 0xa The parent of this virtual disk could not be opened (23).
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z In(05) vmx DISKLIB-LIB_MISC : DiskLib_GetStorageBlockSizes: Failed to get storage block sizes, The virtual disk requires a feature not supported by this program.
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain
2022-06-03T14:41:03.766Z Er(02) vmx DISKLIB-CHAIN : DiskChainDBGet: cannot apply to partial chain

0 Kudos
continuum
Immortal
Immortal

Do you have "C:\Users\VB\Windows Server 2019-s018.vmdk" ?
Read the file "C:\Users\VB\Windows Server 2019.vmdk" and check if all referenced files exist and have a non-zero size.
Check your quarantine location of your Antivirus-tool. Consider setting a rule to ignore vmdk-files - otherwise this will happen again and again.

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
DecioHabiro
Contributor
Contributor

YES to all.

NO Antivirus because I'm able to run any other VMs

0 Kudos
continuum
Immortal
Immortal

Whats the size of s018.vmdk ?
Do all the s00*.vmdks exist and have a non zero size ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos