Home / server / Questions / 750051
In Process
James White
Asked: 2016-01-19 16:36:03 +0800 CST

Why doesn't the Internal USB port boot ESXi 6 on my Microserver Gen8?

  • 772

I'm trying to run ESXi 6 off the Internal USB 2.0 port on a HP Microserver Gen8. No matter what I try it will not make any attempt to boot the internal USB to load the hypervisor.

I installed ESXi 6 with the customised ProLiant HP image (Jan 2016). The steps I took to do this was burn the ISO to a CD and installed it to a 8 GB Transcend while it was plugged into the internal USB slot of the Microserver Gen8. I pulled all SATA drives before installing. The ESXi setup detected the USB drive no problem and installed without an issues. Upon rebooting it doesn't boot from it at all.

I checked my BIOS and all the USB related options appear to be correct:

  • USB Enabled - Enabled
  • USB Boot Support - Enabled
  • Main Boot order - USB DriveKey is set to first priority
  • Internal drives boot priority - USB DriveKey first
  • USB Enumeration - Enabled

To confirm the USB stick is working I pulled it out of the Microserver Gen8 and booted it on a laptop, which booted no problem.

I had the same problem with another USB drive but thought it might just be bad luck for compatibility, however two USB drives doing the same thing seems a little bit suspect.

What am I missing that's preventing the USB drive from booting on the Microserver Gen8 when using the internal port?

vmware-esxi

2 Answers

  1. For your actual problem:

    Format your USB with MBR and not GPT partitions. That will fix this issue...

    Hit Shift-O during installation and add formatwithmbr:

    enter image description here

    My rant...

    See: HP Proliant Microserver Gen8: OS on a Micro SD or USB drive a good idea?

    Something many people don't understand about HP ProLiant servers is that HP Smart Array controllers are capable of having multiple "Logical Drives" on the same physical "Array".

    This means that you can take a group of disks and separate them into two or more volumes. E.g. 6 x 300GB disks can be 1 x 100GB volume for an operating system and 800GB for data. This is a valuable feature.

    So for the example of the particular HP MicroServer in this question, you have a compact server with four drive bays...

    enter image description here

    The goal is to run VMware ESXi and the OP wants to install it on a USB key. Running VMware on a USB or SD card when you're not operating in a clustered environment with shared storage is a bad idea. Failure of your USB/SD device is a pain to deal with.

    ESXi does not require much space, so an easy approach for this server type is to create a 16GB logical drive to house ESXi, then allocate the rest to your VM storage. This way, you have RAID protection for VMware and your data storage without wasting disk space.

    • 5

  2. Resurrecting the thread...

    The HP MicroServer Gen8 is incredibly picky about which USB formats and ports it will boot from and in what order.

    USB Sticks must be using MBR partitions, not GPT, and must be using a SysLinux-Method of booting, preferably a Fat32 filesystem and of course no sector sizes above 16KB. Also, the 2 USB 3.0 ports (external, blue) cannot be used for booting.

    The only tool that repeatably produced USB sticks usable for the HP MicroServer Gen8 was WinSetupFromUSB_1-7_x64 using the options "Linux ISO Grub4Dos" and "SysLinux Bootsector". This results in a boot menu that has a Grub entry for the ISO provided and one SysLinux entry that is non-functional, but required for the MicroServer to accept the stick and show the menu in the first place. This tool could actually format it as NTFS and it was still bootable in the MicroServer.

    Fast USB sticks recommended. And patience, since the MicroServer takes 2-3min for each boot attempt and if it fails repeatedly due to its pickyness, it's depleting the mental health of everone around it.

    The MicroServer is still extremely complicated to use and it's not recommended IMHO for any group. For SOHO installations, it has a ton of options and stupid little requirements rendering it almost unusable (No booting from on-board SATA port, workaround required. BIOS-MBR only, no UEFI or GPT support, rendering it complicated for most 2016's OS install media - good luck changing a USB stick from GPT to MBR with Windows alone. Typical CPUs delivered with the MicroServer don't have AES-NI, so encrypting HDDs or SSL traffic or SSH file transfers is extremely unusably slow. the iLO-interface constantly on, draws power needlessly in a SOHO setting. iLO-advanced license required to actually use it anyway. BIOS- and firmware updates require a warranty, registration and support contract with HP, too expensive. Using the RAID controller in RAID modes other than mirror, it requires an additional license or a RAID controller that is double the price of the entire server, why? HP-branded RAM required or it will complain. Passive CPU cooler, but a very noisy case fan to make up for it. The list goes on and on. Not recommended.) - and for serious production environments, the puny MicroServer can never satisfy the performance and component redundancy required, with the AES-NI missing, it doesn't even deliver enough power for a SOHO setting.

    • 3