VMware Cloud Community
Svedja
Enthusiast
Enthusiast

Workaround for "Unable to get Console path for Mount"

Error message:

Error during the configuration of the host: Unable to get Console path for Mount

Envirovment : ESX 3.5 u2 with NFS datastore

We are in the process of moving data between datastores.

I noticed that ESX doesn't behave as expected.

Scenario:

We have a NFS mount called ISO on storage "NFS1"

I rename the storage to ISO_old

I try to create a new storage on "NFS2"

The ESX refuses with the error above.

Workaround:

Instead of creating new storage "ISO" create it with name "ISO_NEW".

In ESX rename "ISO_NEW" to "ISO".

As you see, it isn't exactly what you would expect.

Tags (4)
0 Kudos
1 Reply
Magik
Contributor
Contributor

I can confirm this behavior is still a problem in ESX 3.5 U4. Thank you for the workaround.

I renamed an NFS datastore then attempted to mount a new datastore with the old/original name, but it failed with the error. Mounting an NFS datastore as a completely random name succeeds then you can rename it to the old/original name.

An interesting thing occurs when you are working with clusters. When you go through the process above and have 1 host in the cluster with the proper datastore name then add a datastore with a completely random name, but the same mount path, the result will be the correct datastore name as on the first host. The random name is lost in the process. I guess that part is a good thing.

Thanks, Rick

0 Kudos