<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Kickstart installation - how to define disk in vSphere Upgrade &amp; Install Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Kickstart-installation-how-to-define-disk/m-p/2838123#M33258</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I need to install 150+ vSAN hosts and therefore set up PXE boot with a kickstart script. We have hardware from two vendors. On the Huawei hosts I see only the disk where the ESXi installation should go, so the ks parameter &lt;FONT face="courier new,courier"&gt;install --firstdisk&lt;/FONT&gt; works. This is because the second controller with the vSAN disks is not yet configured...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the Lenovo hosts however, by default I see also the vSAN cache and capacity disks, and the RAID controller with the disk for ESXi is listed as the last one... so I can't use "firstdisk". (The same applies to the Huawei hosts once the controller has been set to JBOD mode for vSAN)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to the vSphere product documentation I shall be able to address the disks with their device path:&lt;FONT face="courier new,courier"&gt; --disk=/vmfs/devices/disks/mpx.vmhba1:C0:T0:L0&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-61A14EBB-5CF3-43EE-87EF-DB8EC6D83698.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-61A14EBB-5CF3-43EE-87EF-DB8EC6D83698.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;But this does not work (at least not with ESXi 7.0.2), only the device names (naa.1234567890) are available it seems. The kickstart script stops with the error &lt;FONT face="courier new,courier"&gt;"... install --disk= specified, but drive "/vmfs/devices/disks/mpx.vmhba3:C2:T0:L0" was not found on the system. The available disk(s) are: naa.1234567890" &lt;/FONT&gt;etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Even on an installed host, there are no mpx or vmhba devices under /vmfs/devices/disks, only those random naa numbers. How the hell can I make a ks script that finds the correct disk to install?! &lt;FONT face="courier new,courier"&gt;--seventhdisk&lt;/FONT&gt; would be what I need in this case...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Mar 2021 12:13:19 GMT</pubDate>
    <dc:creator>vmjoe</dc:creator>
    <dc:date>2021-03-25T12:13:19Z</dc:date>
    <item>
      <title>Kickstart installation - how to define disk</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Kickstart-installation-how-to-define-disk/m-p/2838123#M33258</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I need to install 150+ vSAN hosts and therefore set up PXE boot with a kickstart script. We have hardware from two vendors. On the Huawei hosts I see only the disk where the ESXi installation should go, so the ks parameter &lt;FONT face="courier new,courier"&gt;install --firstdisk&lt;/FONT&gt; works. This is because the second controller with the vSAN disks is not yet configured...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the Lenovo hosts however, by default I see also the vSAN cache and capacity disks, and the RAID controller with the disk for ESXi is listed as the last one... so I can't use "firstdisk". (The same applies to the Huawei hosts once the controller has been set to JBOD mode for vSAN)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to the vSphere product documentation I shall be able to address the disks with their device path:&lt;FONT face="courier new,courier"&gt; --disk=/vmfs/devices/disks/mpx.vmhba1:C0:T0:L0&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-61A14EBB-5CF3-43EE-87EF-DB8EC6D83698.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-61A14EBB-5CF3-43EE-87EF-DB8EC6D83698.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;But this does not work (at least not with ESXi 7.0.2), only the device names (naa.1234567890) are available it seems. The kickstart script stops with the error &lt;FONT face="courier new,courier"&gt;"... install --disk= specified, but drive "/vmfs/devices/disks/mpx.vmhba3:C2:T0:L0" was not found on the system. The available disk(s) are: naa.1234567890" &lt;/FONT&gt;etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Even on an installed host, there are no mpx or vmhba devices under /vmfs/devices/disks, only those random naa numbers. How the hell can I make a ks script that finds the correct disk to install?! &lt;FONT face="courier new,courier"&gt;--seventhdisk&lt;/FONT&gt; would be what I need in this case...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Mar 2021 12:13:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Kickstart-installation-how-to-define-disk/m-p/2838123#M33258</guid>
      <dc:creator>vmjoe</dc:creator>
      <dc:date>2021-03-25T12:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: Kickstart installation - how to define disk</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Kickstart-installation-how-to-define-disk/m-p/2846166#M33388</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found a solution. You can provide a list with multiple possible device names or model name. During installation the installer tries every entry until it has a match. But you need to know how the name is displayed in esxi. This is different from vendor to vendor, I think Therefore you can install one host manually and then run the following command: esxcli storage core device list | grep Model&lt;BR /&gt;&lt;BR /&gt;In our kickstart file, I have created a list for our two vendor's dell and fujitsu. Sometimes we have a raid controller with two devices in raid1, sometimes we have dual micro sd's or dell boss cards.&lt;/P&gt;&lt;P&gt;install --firstdisk=PRAID\ CP400i,Dual\ microSD0123,Internal\ Dual\ SD,DELLBOSS\ VD,Dual\ microSD --ignoressd --overwritevmfs --novmfsondisk&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Stephan&lt;/P&gt;</description>
      <pubDate>Sun, 09 May 2021 09:46:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Kickstart-installation-how-to-define-disk/m-p/2846166#M33388</guid>
      <dc:creator>stephan87</dc:creator>
      <dc:date>2021-05-09T09:46:20Z</dc:date>
    </item>
  </channel>
</rss>

