VMware Cloud Community
Kazi-Aminul
Contributor
Contributor

Failed - File system specific implementation of OpenFile[file] failed

VM fails to power on with Error:

File system specific implementation of OpenFile[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of Ioctl[file] failed
File system specific implementation of OpenFile[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
File system specific implementation of LookupAndOpen[file] failed
22 (Invalid argument)
Cannot open the disk '/vmfs/volumes/5feadaba-f2a7116a-b0b5-9418826f9750/FileServer/FileServer-000001.vmdk' or one of the snapshot disks it depends on.
Module 'Disk' power on failed.
Failed to start the virtual machine.

0 Kudos
4 Replies
scott28tt
VMware Employee
VMware Employee

What files do you have in the FileServer folder?

 


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
Kazi-Aminul
Contributor
Contributor

Please have the file list.

-rw------- 1 root root 554 May 12 2021 FileServer.vmdk
-rw-r--r-- 1 root root 431 May 24 2021 FileServer.vmsd
-rw------- 1 root root 162135015424 May 24 2021 FileServer-flat.vmdk
-rw------- 1 root root 1483313 May 24 2021 FileServer-Snapshot1.vmsn
-rw------- 1 root root 8589934592 May 24 2021 FileServer-Snapshot1.vmem
-rw-r--r-- 1 root root 90 Nov 4 13:43 FileServer-372ff292.hlog
-rw------- 1 root root 115343360 Mar 24 06:09 vmx-FileServer-925889170-2.vswp
-rw------- 1 root root 339 Mar 27 13:56 FileServer-000001.vmdk
-rw------- 1 root root 8684 Mar 27 13:56 FileServer.nvram
-rw------- 1 root root 3158 Mar 27 14:03 FileServer.vmxf
-rw-r--r-- 1 root root 88044 Mar 30 18:35 vmware-70.log
-rw-r--r-- 1 root root 62839 Mar 31 07:26 vmware-71.log
-rw-r--r-- 1 root root 84244 Mar 31 09:05 vmware-72.log
-rwxr-xr-x 1 root root 3329 Apr 15 11:37 FileServer.vmx
-rw-r--r-- 1 root root 56989 Apr 15 11:37 vmware-73.log
-rw-r--r-- 1 root root 54511 Apr 15 16:19 vmware-74.log
-rw-r--r-- 1 root root 54425 Apr 15 16:21 vmware-75.log
-rw-r--r-- 1 root root 54425 Apr 15 16:21 vmware.log
-rwxr-xr-x 1 root root 3329 Apr 15 21:48 FileServer.vmx.bak
-rw------- 1 root root 15365439488 May 2 09:33 FileServer-000001-sesparse.vmdk

0 Kudos
4250guilhermeap
Contributor
Contributor

I had the same error, please try this:

1. Take a snapshot;

2. Delete a snapshot created at step 1;

3. Try to power on VM

4. Consolidade disk if necessary.

 

MiroslawGmerek
Contributor
Contributor

Problem solved after this procedure vm

0 Kudos