lwsamcn01
Enthusiast
Enthusiast

could not power on VM

Jump to solution

Dear Support,

power on VM failure. please see below:

===

Task

Power On VM

Key

haTask-2-vim.VirtualMachine.powerOn-128605104

Description

Power On this virtual machine

Virtual machine:

VSA02

State

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

Errors

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

The specified device is not a valid physical disk device

Cannot open the disk '/vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c/VSA02/VSA02_00.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on 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

The specified device is not a valid physical disk device

Cannot open the disk '/vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c/VSA02/VSA02.vmdk' or one of the snapshot disks it depends on.

Failed to start the virtual machine.

also attached vsa02.vmx file for your check.

0 Kudos
2 Solutions

Accepted Solutions
lwsamcn01
Enthusiast
Enthusiast

uploading file to SR. service ID is cesm-20171219.

View solution in original post

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

sorry, i delete the host and centre. rebuilt VMware.

thanks for your help!

Liu Wei

View solution in original post

0 Kudos
19 Replies
daphnissov
Immortal
Immortal

Please attach vmware.log file for inspection.

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

I bundled both host. 192.168.14.1 is OK. but for your reference. depoy vsa used:HPE_StoreVirtual_VSA_2014_for_vSphere_OVF_TA688-10542.

vsa02/for host 192.168.14.3 failure. 

i try deply OVF from file VMware-vCenter-Server-Appliance-6.5.0.10000-5973321_OVF10. vsa could not created.

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

sorry. but how can i upload log? very big about 58MB. very strange now could not find attachment access port.

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

uploading file to SR. service ID is cesm-20171219.

View solution in original post

0 Kudos
msripada
Virtuoso
Virtuoso

Can you check this KB as it is same as this error " The specified device is not a valid physical disk device"

This issue occurs when you have configured the ScratchConfig.ConfiguredScratchLocation setting to point to the base of your ESXi host's local storage and you have virtual machines running on the same local storage. This also occurs when you have the scratch partition on the base of the local storage and have put virtual machines in a sub-directory under the configured scratch partition. This is not supported with ESXi and any such virtual machine vmdk's are marked as insecure.

Note: This issue can occur on NFS storage where the scratch directory is the base directory of the datastore, and in the same directory as virtual machines directories, or virtual machine directories are in a subdirectory of the directory containing the scratch directory.

VMware Knowledge Base

Thanks,

MS

0 Kudos
daphnissov
Immortal
Immortal

Compress vmware.log (located in the home directory of the VM) and attach it here.

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

sorry, how can i put attachment? see screenshot below.

how to put  attachment.PNG

0 Kudos
daphnissov
Immortal
Immortal

Open the full thread (not the quick reply) and find the attach button in the lower left-hand corner.pastedImage_0.png

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

I  just add one VM. attached is log.

I could not deploy VSA any longer. It sounds data store error.

at very beginning. when i add host 2 to VC. VC give warning: System logs on non-persistent storage

i change path as /vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c and warning disappeared.

There is not any other error and warning coming until VSA deploy failure.

thanks!

Liu Wei

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

No, could not solved.

when i  try change  directory /vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c to /vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c/scratch. system  give alert: wrong parameter.

thanks!

Liu Wei

0 Kudos
daphnissov
Immortal
Immortal

It sounds like you have a device failure if you're getting that message.

0 Kudos
daphnissov
Immortal
Immortal

This is the message the kernel is throwing when trying to open the disk

2017-12-20T02:08:49.060Z| vmx| I125: DISKLIB-VMFS  : VmfsExtentCommonOpen: DiskLibIsExtentPathSecure claims extent path "/vmfs/volumes/5a372d98-c11be218-1176-98f2b302b20c/WEN-PC12/WEN-PC12-flat.vmdk" is insecure, failing disk open.

Where is this stored? ESXi seems to think it's on scratch.

Open your ESXi host in the host client and past a screenshot of the Events pane.

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

please check.

Liu Wei

0 Kudos
daphnissov
Immortal
Immortal
0 Kudos
lwsamcn01
Enthusiast
Enthusiast

event pane 01.PNG

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

events 01.PNG

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

events 02.PNG

0 Kudos
daphnissov
Immortal
Immortal

What type of device is backing DS02? Those USB configuration messages shown in the event log are strange. Is this a USB device?

From a SSH session on your ESXi host, paste the output of df -h

0 Kudos
lwsamcn01
Enthusiast
Enthusiast

sorry, i delete the host and centre. rebuilt VMware.

thanks for your help!

Liu Wei

View solution in original post

0 Kudos