<div>
If I do step#5 &quot;unmount&quot;, will it shut down all VMs that are currently running?
</div>


<div>
is that a problematic datastore?
</div>


<div>
&quot;is that a problematic datastore?&quot; --&gt; No, but there are several virtual machines that are running on that datastore.
</div>


<div>
I have a question. In the vCenter screenshot, 192.168.1.8 is under DataCenter. Is it normal that every host be listed under Datacenter?
</div>


<div>
yes thats normal all objects in vcenter are under datacenter. &nbsp;can you check in the vcenter about this problematic datastore?
</div>


<div>
&quot;can you check in the vcenter about this problematic datastore?&quot; --&gt; Can you be more specific as to what I need to do?<br />
<br />
Like I said, vCenter used to have two hosts (192.168.1.2 &amp;&nbsp;192.168.1.8). After some updates, I could not start 192.168.1.2 host and I ended up re-making ESXi USB Key again from the scratch (and added virtual machines to inventory). &nbsp;Meanwhile, I removed 192.168.1.2 because it became inaccessible from vCenter. Since 192.168.1.2 is now operational, I wanted to add it to vCenter, but I think vCenter sees &quot;leftover&quot; datastore information of old 192.168.1.2 host.
</div>


<div>
<a href="https://filedb.experts-exchange.com/incoming/2017/03_w11/1150843/Options-for-Datastore---TS3--inacces.png" target="_blank" title="Options for Datastore - TS3 (inaccessible) (121 KB)"><img alt="Options for Datastore - TS3 (inaccessible)" class="file-block lazyload" style="max-width: 793px;" data-src="https://filedb.experts-exchange.com/incoming/2017/03_w11/1150843/Options-for-Datastore---TS3--inacces.png" /></a><a href="https://filedb.experts-exchange.com/incoming/2017/03_w11/1150845/Renamed-Datastore-in-192-168-1-2.png" target="_blank" title="Renamed Datastore in 192-168-1-2 (38 KB)"><img alt="Renamed Datastore in 192-168-1-2" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2017/03_w11/800_1150845/Renamed-Datastore-in-192-168-1-2.png" /></a>&quot;unmount this inaccessible datastore. We'll see if vcenter accept.&quot; --&gt; in vCenter, when I right click, I do not see the option to unmount this. It is rather strange as to why I can not remove this datastore - &quot;datastore1 - TS3 (inaccessible).<br />
<br />
In vSphere client of 192.168.1.2, I renamed &quot;datastore1-TS3&quot; with &quot;datastore1 - VM1&quot; and tried to add 192.168.1.2 in vCenter, but it did not work.
</div>


Options for Datastore - TS3 (inaccessible)

Options-for-Datastore---TS3--inacces.png

Renamed-Datastore-in-192-168-1-2.png

<div>
&quot;I would not have ESX to run on usb key in production environment&quot; --&gt; In earlier days, I just installed ESXi on the hard drive on RAID. But then I read articles/recommendations about installing USB Keys (and make a backup USB key).<br />
I kind of like this because, in my case, during ESXi updates, I think the USB key went bad. If I had made a backup USB key, it would have been a non story, but since I did not, I had to re-install ESXi on a new USB key, ran vShpere Client to attach existing datastore and add existing VMs to Inventory. It worked out pretty well.<br />
&nbsp;Now if I can allocate two HDs (in RAID 1) just for ESXi, that would have been good too, but sounds a bit like going overboard.<br />
Although I like to learn more about &quot;dual SD internal card&quot; except that I really do not take this RACK servers out of the rack cabinet if I don't have to.
</div>


<div>
What is your storage, internal disk on each ESX host, or shared storage ?<br />
If shared, iSCSI or FC VMFS, or NFS datastores ?<br />
And your vcenter version ?<br />
<br />
Do you have the same options on the datastore if you select the vcenter instead of datacenter in the vmware inventory ?
</div>


<div>
<a href="https://filedb.experts-exchange.com/incoming/2017/03_w11/1150916/VSphere-Web-Client.png" target="_blank" title="VSphere Web Client (123 KB)"><img alt="VSphere Web Client" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2017/03_w11/800_1150916/VSphere-Web-Client.png" /></a>What is your storage, internal disk on each ESX host --&gt; Yes. <br />
vcenter version ? 6.5.0 Build 4944578<br />
Do you have the same options on the datastore if you select the vcenter instead of datacenter in the vmware inventory ? --&gt; No dismount option here either. &nbsp;Can I rename this here or move to another datastore (after creating a new datastore)?
</div>


VSphere-Web-Client.png

<div>
I mis-spelled. Can I move &quot;Datastore 1 - TS3&quot; to another Datacenter (after creating a new Datacenter)?
</div>


<div>
Well, I created new Datacenter and tried to move &quot;Datastore 1 - TS3&quot; into it, but it failed. It is &quot;not an option&quot;.
</div>


<div>
What do you think about this idea?<br />
- Remove entire Datacenter. Hopefully it will remove &nbsp;&quot;Datastore 1 - TS3&quot; too.<br />
- Then create a new Datacenter, called it &quot;Datacenter 1&quot;.<br />
- Then add two hosts - 192.168.1.2 first and 192.168.1.8 next.
</div>


<div>
HI,<br />
you could try this yes.<br />
You should first create another datacenter and move your first ESX in it, then try to delete old datacenter object, and finally add second ESX to your new datacenter.<br />
You can try to rename the inaccessible datastore too, but it will surely fail.<br />
Did you try to restart your vCenter service or even vCenter machine ?
</div>


<div>
<a href="https://filedb.experts-exchange.com/incoming/2017/03_w11/1151089/New-Datacenter.png" target="_blank" title="New Datacenter (44 KB)"><img alt="New Datacenter" class="file-block lazyload" style="max-width: 691px;" data-src="https://filedb.experts-exchange.com/incoming/2017/03_w11/1151089/New-Datacenter.png" /></a><a href="https://filedb.experts-exchange.com/incoming/2017/03_w11/1151090/Datacenter-Move.png" target="_blank" title="Datacenter Move (34 KB)"><img alt="Datacenter Move" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2017/03_w11/800_1151090/Datacenter-Move.png" /></a>I was able to rename it from &quot;datastore1 - TS3&quot; to &quot;datastore1 - TS3 - BAD&quot;, but it did not make a difference.<br />
I created a new datacenter called &quot;Datacenter1&quot; and tried to move &quot;datastore1 - TS3 - BAD&quot; to &quot;Datacenter1&quot;, but &quot;Datacenter1&quot; is not even listed, I can't move it.<br />
<br />
Unless there are more things to try, I am ready to un-install this vCenter and re-install it from the scratch. Is there anything that I should be concerned about recreating it and adding two hosts to the vCenter?
</div>


New-Datacenter.png

Datacenter-Move.png

<div>
No there arent any concerns, first remove all the objects from current vcenter server like ESX and datastores. then you can proceed with new vcenter installation.
</div>


<div>
OK. I will do that and report back.
</div>


<div>
or instead of installing a new vcenter, if you have a valid vmware contract support you should better create a support request.
</div>


<div>
I do not have a contract with vmware.
</div>


<div>
It sounds terrible to me to reinstall a vcenter because of this, but also and sadly I don't have a simplier solution at the moment.<br />
Maybe other experts will help, wait and see :-)
</div>


<div>
I agree. There should be a simple solution to this. It is a matter of deleting an object.
</div>


<div>
<div class="content wysiwyg-content">
<a href="https://filedb.experts-exchange.com/incoming/2017/03_w11/1150613/Add-Host-Error.PNG" target="_blank" title="Add Host Error (29 KB)"><img alt="Add Host Error" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2017/03_w11/800_1150613/Add-Host-Error.PNG" /></a> &nbsp;<a href="https://filedb.experts-exchange.com/incoming/2017/03_w11/1150623/DataStore-List.PNG" target="_blank" title="Datastore List (76 KB)"><img alt="Datastore List" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2017/03_w11/800_1150623/DataStore-List.PNG" /></a>Hi,<br />
&nbsp;I used to manage two ESXi hosts (192.168.1.2 &amp;&nbsp;192.168.1.8) in vCenter. After some updates, 192.168.1.2 failed to boot from USB flash drive, so I have to re-install ESXi USB drive again and add existing VMs to the inventory.<br />
&nbsp;Now I can access 192.168.1.2 by using IP address in VSphere client. So I decided to add it to vCenter. But when I tried to add 192.168.1.2 to the Datacenter, it generates an error message. Upon investigation, I found &quot;datastore1 - TS3) &quot;&nbsp;which belongs to 192.168.1.2 still shows up as &quot;inaccessible&quot;. I tried to delete it, but I did not see that option.<br />
&nbsp;What can I do to manage192.168.1.2 in vCenter again?<br />
<br />
Thanks.
</div>
</div>


Add-Host-Error.PNG

DataStore-List.PNG

  
Hi,
 I used to manage two ESXi hosts (192.168.1.2 & 192.168.1.8) in vCenter. After some updates, 192.168.1.2 failed to boot from USB flash drive, so I have to re-install ESXi USB drive again and add existing VMs to the inventory.
 Now I can access 192.168.1.2 by using IP address in VSphere client. So I decided to add it to vCenter. But when I tried to add 192.168.1.2 to the Datacenter, it generates an error message. Upon investigation, I found "datastore1 - TS3) " which belongs to 192.168.1.2 still shows up as "inaccessible". I tried to delete it, but I did not see that option.
 What can I do to manage192.168.1.2 in vCenter again?

Thanks.

Trouble adding ESXu host to vCenter

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.