esxi1979
Expert
Expert

Esxi OS running on Local Sata HDD or SD card

Jump to solution

i have most of esxi running on HP server with SD card.

I have esxi servers at mnay locations

as i have not installed these or the person who installed did not do a handover, i have no idea where the OS runs.

Is it possible to do a find the Esxi OS disk info from powercli

vsish or esxcfg-info can have this info somewhere for sure.

thanks

1 Solution

Accepted Solutions
LucD
Leadership
Leadership

Would this help (I'm guessing that the SD card installations will show up as "embedded")

foreach($esx in Get-VMHost){

    $esxcli = Get-EsxCli -VMHost $esx

    $bootDev = $esxcli.system.boot.device.get()

    if($bootDev.BootFilesystemUUID){

        if($bootDev.BootFilesystemUUID[6] -eq 'e'){

            Write-Host "$($esx.Name.Split('.')[0]) Embedded"

        }

        else{

            $mountPoint = $esxcli.storage.filesystem.list() | where{$_.UUID -eq $bootDEV.BootFilesystemUUID} |

                select -ExpandProperty MountPoint

            Write-Host "$($esx.Name.Split('.')[0]) Boot from device $($mountPoint)"

        }

    }

    else{

        if($bootDev.StatelessBootNIC){

   

            Write-Host "$($esx.Name.Split('.')[0]) Stateless, PXE boot from $(bootDev.StatelessBootNIC)"

        }

        else{

            Write-Host "$($esx.Name.Split('.')[0]) PXE Boot from $($bootDev.BootNIC)"

        }

    }

}


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

4 Replies
LucD
Leadership
Leadership

Would this help (I'm guessing that the SD card installations will show up as "embedded")

foreach($esx in Get-VMHost){

    $esxcli = Get-EsxCli -VMHost $esx

    $bootDev = $esxcli.system.boot.device.get()

    if($bootDev.BootFilesystemUUID){

        if($bootDev.BootFilesystemUUID[6] -eq 'e'){

            Write-Host "$($esx.Name.Split('.')[0]) Embedded"

        }

        else{

            $mountPoint = $esxcli.storage.filesystem.list() | where{$_.UUID -eq $bootDEV.BootFilesystemUUID} |

                select -ExpandProperty MountPoint

            Write-Host "$($esx.Name.Split('.')[0]) Boot from device $($mountPoint)"

        }

    }

    else{

        if($bootDev.StatelessBootNIC){

   

            Write-Host "$($esx.Name.Split('.')[0]) Stateless, PXE boot from $(bootDev.StatelessBootNIC)"

        }

        else{

            Write-Host "$($esx.Name.Split('.')[0]) PXE Boot from $($bootDev.BootNIC)"

        }

    }

}


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

esxi1979
Expert
Expert

Thanks i will test it out

BTW yes ur correct LucD

# esxcfg-info -e

You see an output similar to:

boot type: visor-thin

You can determine the ESXi type based on the output of this command.

For example:

    visor-thin indicates an installable deployment

    visor-usb indicates an embedded deployment

    visor-pxe indicates a PXE deployment

==

    Both ESXi embedded and installable are installed with the same installation media/CD and processes

    If you install ESXi on a USB key drive or SD card then you will always end up with ESXi embedded.

    If you install ESXi on a hard disk (or iSCSI/SAN/FCoE partition) that has a size of at least 5 GB then you will end up with ESXi installable.

    If the installation target media (no matter what type) is smaller than 5 GB then you will end up with ESXi embedded.

   

    https://www.reddit.com/r/vmware/comments/2kp3ps/how_to_tell_if_esxi_is_installed_to_sd_card_or/

    https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=20145...

   

===

0 Kudos
AlbertWT
Virtuoso
Virtuoso

LucD ,

Why is that the result of the script above is just the number 10 instead of the server name ?

10 Boot from device /vmfs/volumes/ce033571-36447995-d515-a9d299b9e6e5

10 Boot from device /vmfs/volumes/94037876-40dbed84-0407-c8f48b9ad389

10 Boot from device /vmfs/volumes/83704376-c5ca3624-8e6d-51c7853425ff

10 Boot from device /vmfs/volumes/58e79572-21e46328-699d-e2cb7498f187

10 Boot from device /vmfs/volumes/e51a8871-c9948f56-583c-4e048b1b992c

10 Boot from device /vmfs/volumes/ce7c7879-35306e2f-0b72-88341282e674

10 Boot from device /vmfs/volumes/7d789177-0a1fc7be-2bfa-1dcae92bcd11

10 Boot from device /vmfs/volumes/7e03407e-9a39256c-110f-827216b79bca

10 Boot from device /vmfs/volumes/de1bfc73-40f4b846-de63-63b5ec66c049

/* Any kind of comment or input would be greatly appreciated */
0 Kudos
LucD
Leadership
Leadership

That script derives the hostname as the first qualifier of the VMhost name string.

I suspect your ESXi nodes have VMHost names as IP addresses, all strating with 10


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference