VMware virtual machine inaccessible? Find out how to fix it!

Here you will find out:

Are you ready? Let’s read!

What does вЂњinaccessibleвЂќ mean for a VM?

There can be many reasons for this, but most often it is due to the folder being renamed or some error in the storage array. You can handle any issue with VMware being inaccessible on a virtual machine thanks to this article.

Signs of being inaccessible VM VMware

Look out for the following symptoms to make sure that VMware VM is inaccessible:

Why VMware virtual machines become inaccessible

This usually happens due to a failure of the virtual machine configuration files; the cause may also be in the file system or in a damaged disk.

If the storage is online, then VMware VM being inaccessible is likely due to a network failure.

Therefore, depending on the reason, the decision may be different. What precisely it will be discussed below.

Case 1. VMware VM is inaccessible due to configuration files’ failure

Here is how you can fix it:

Use the following step-by-step guide to recover data from VMware server with an inaccessible virtual machine with the help of the recommended program.

Case 2. VMware VM is inaccessible due to disk’s or FS failure

Here is how you can fix a VMware virtual machine being inaccessible in this case:

Источник

Inaccessible vmware что делать

In short, I am looking for help recovering «inaccessible» VMs.

My operating theory is that during maintenance on the UPS connected to our SAN rack, I accidentally tripped the power on one of three fiber channel switches. When this happened, roughly 30 VMs were in vMotion through that switch, and as a result of the power loss several datastores hosted on the SAN were disconnected and listed as inaccessible. The datastores did not reconnect to effected hosts as expected (FC connections are redundant, there was always a path from host to storage array). The roughly 30 VMs previously mentioned were unresponsive. Attempting to open VMRC for any of the affected VMs failed with error: «Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authpipe within retry period.» These VMs reported vmtools not running, 0 bytes allocated storage, but with static CPU load (seemed stuck at whatever the last recorded load was). No commands to the affected VMs completed successfully, most timed out or continued to run indefinitely.

I migrated off unaffected VMs to unaffected hosts. This process completed without issue. Afterwards, all affected hosts were restarted and successfully reconnected to the datastores. At this point, I expected the inaccessible VMs would be identified on the datastores and return to normal operation. This did not happen, and the VMs are still listed as inaccessible.

Brief Version/Config Info:

ESXi 5.5.0 update 3 (VMKernel Release Build 3248547)

vCenter Server Appliance 5.5.0.30500 Build 4180648

All hosts are part of a single cluster which has vSphere DRS enabled (automated)

All datastores are part of a single datastore cluster with Storage DRS enabled (automated) and Storage I/O Control, VMFS5

Thank you for taking the time out of your day to read this. I was fortunate that the failed VMs were not critical, but one of them is important and I would like to understand why I cannot restore it from the datastore.

Источник

Inaccessible vmware что делать

Lost a NFS datastore

On My VM’s the datastore shows as inaccessible. These VMs have no files on this datastore matter of fact the datastore is empty no files at all.

I tried to unmount the datastore but it fails with in use errors

I shutdown the VMS that had this inaccessible datastore made no difference.

How do IU get ride of this datastore?

Many VMs had cdrom mounted to iso files that were on the bad datastore

Once changed the cdrom to host device the inaccessible datastore was not longer there.

The two VMS that still had NFS01

Once I added the updated NFS01 back and migrated those two vm’s to the NFS01 datastore I only had one datastore on the VMS

This has been resolved.

Since there are no error details.

Here are two KB’s that might help you. If you haven’t tried them already.

esxcli storage nfs list

Volume Name Host Share Accessible Mounted Read-Only isPE Hardware Acceleration

NFS06 10.2.8.50 /volume1/NFS06 true true false false Not Supported

NFS05 10.2.8.47 /volume1/NFS05 true true false false Not Supported

NFS04 10.2.8.46 /volume1/NFS04 true true false false Not Supported

NFS02 10.2.8.51 /volume1/NFS02 true true false false Not Supported

NFS03 10.2.8.48 /volume1/NFS03 true true false false Not Supported

NFS01 10.2.8.13 /volume1/NFS01 false true false false Unknown

Need to remove the last one in the list

What error are you receiving when you try to remove it?

I was able to remove the datastore from each esxi host using this

Now all ESXI hosts do not have that NFS datastore.

My problem is it still is in the Datastore cluster

When I go to datastore Clusters and select my datastore cluster I still see NFS01

How to I remove it from the datastore cluster.

when I select unmount datastore I get an empty list which means the esxi hosts do not have the datastore any longer.

I found that several VM’s had a cdrom mounted which was pointing to the datastore

After I changed the cdrom to host client all the the NFS01 datastore disappeared from them

I only have two VM’s that show this datastore still

Once I can figure out how to remove them from the VM then I will be able to move forward with getting my VMs but online.

Any ideas on how to remove the datastore at the VM level?

What part of the VM files could possibly be on that datastore?

Seems like you’ve sorted ISOs, but do those VMs have snapshots?

That datastore was corrupted had to rebuild the volume on the nas device which wiped all files. The Hard drives where fine. Just lost the Volume

I had to use the replica VM from my Veeam B&R to bring up the VMs’ The replicas are stored on the internal drives of the ESXI host as a safety feature. Good thing.

They have replicas from when the get backed up and those files are on the internal disks

Those two VMs’ are they only ones that have that datastore

Источник

Inaccessible vmware что делать

Добрый день! Уважаемые читатели блога pyatilistnik.org, сегодня хочется рассказать, как решить ошибку в ESXI 6 / 5.x Unknown VM (Inaccessible). Столкнулся я с ней уже не первый раз и решил себе на память расписать все это. Хочу отметить, что в подобную ситуацию вы легко можете попасть на любой версии гипервизора, включая самый последний на текущий момент 6.7. Уверен, что данный материал окажется полезным для начинающих администраторов по виртуализации.

Или вот вам пример из Vmware ESXI 6.5

Ошибка Unknown VM (Inaccessible) в ESXI 6-02

Ошибка Unknown VM (Inaccessible) в ESXI 6-03

Rescan в данном случае не помогал. Надо определить какой vmnic имеет подключение к хранилке (iscsi target). В данном случае он оказался в распределенном свитче. Удалил его оттуда. Создал стандартный свитч VMkernel.