vSphere Upgrade & Install

 View Only
  • 1.  Automated KS

    Posted Apr 10, 2024 12:19 AM

    I have a server that has two disk installed on them.  I am trying to create an automated inst that will either install on Disk1 in bios.  Disk0 is a 1.9Tb ssd and disk0 is a M.2 NVMe 256gb drive (this is where I want my install to install on and boot from).  



  • 2.  RE: Automated KS

    Posted Apr 14, 2024 05:19 PM

    you want to install guest os automatically to which disk ?
    are you able to enter boot menu ?



  • 3.  RE: Automated KS

    Posted Apr 14, 2024 05:20 PM


  • 4.  RE: Automated KS

    Posted Apr 14, 2024 06:07 PM

     I am trying to install the ESXi Host OS not guest OS using an automated script.  There are two disk installed on the server however I can't figure out a way to make the install script select the NVMe drive as the install disk.  The other disk is also an SSD so ignore SSD in the script won't work either.  The NVMe is 256Gb and the the other SSD is 1.92Tb disk drive.   



  • 5.  RE: Automated KS



  • 6.  RE: Automated KS

    Posted May 06, 2024 02:33 PM

    I have attached the drives that are installed on my system.  I want to use an automated script that will always use the M.2 Drive as the installation of ESXi and not the SAMSUNG SSD.  Additionally it needs to be universal enough that I can use it on multiple similar servers.  




  • 7.  RE: Automated KS

    Posted May 06, 2024 05:55 PM

    I have reviewed this document but still no luck or understanding.  I have added some information from my environment to maybe assist with my problem.  Here is the output regarding my two disk I am working with.  Again the problem is that the SAMSUNG SSD presents as the firstdisk and I want to exclusively ignore it and install on the M.2 SATA Drive.  I will be installing on several different systems with the exact same hardware so I cant hardcode verbatum of each drive cause the host is presenting them with serial numbers.  





  • 8.  RE: Automated KS

    Posted May 20, 2024 10:42 AM

    Not sure if you got this figured out but the KS file should have your drive name on it. 

    There are other ways to use a device location (IE: PCIE port it is located on) but you would have to have all the same machine, hardware IDs, etc... 

    Here's a snippet of my KS file... pay attention to the single quotes ' ' with drive3 name.

    install --firstdisk=<drive1 name>,<drive2 name>, <'Drive3 name with spaces'> --overwritevmfs --novmfsondisk

    You cannot use wildcards, the name of the drive has to match the name in the KS file. 

    Some drives have the serial number in the name which makes it a little difficult... the only way I've been able to figure this out is trial and error with the drive & installation since I've had no formal training with VMWare / Broadcom software.

    I'm fortunate enough that I have, for the most part, all the same drive names on all of our devices.

    I'm trying to learn a better way to do this that will look for a drive with a specific size using the %PRE section and pull the drive name from it, if I can. I don't know if this is possible but it would make a lot of sense to be able to do it this way.

    I may be over complicating this but, again, no formal training.

    Cheers,

    Nate




  • 9.  RE: Automated KS

    Posted May 20, 2024 01:01 PM

    I have not figured this out yet.  Yes the issue is that each drive is using the serial number as part of the names as well.  I tried some %pre section options as well with no success.  So still manually installing this on each server and using the GUI to install currently.  Very frustrating.  I appreciate your assistance.  I will keep trying.  Thanks!

    Steven