New Install - USB Boot Issue (SOLVED)

[Spatial Disorder]

I'm new to unRAID, and really looking forward to giving it a run...but having a hell of a time getting it to boot on my new server.

Server: HPE ML10 Gen9

USB: SanDisk Cruzer Fit (16GB) & SanDisk Cruzer 4GB

 

I've followed the instructions here: https://lime-technology.com/unraid-server-installation/

So far I've:

• Formatted to FAT32 > Renamed to "UNRAID" > Unzipped the latest (6.3.2) > Copied Contents to USB > Ran make_bootable.bat as administrator on Win10 Pro.
  • I've also formatted an older SanDisk 4GB USB to FAT..then followed the same procedures.
  • I tested both USB drives on two different workstations (laptop and desktop), and both successfully boot to unRAID with no issue
  • At this point, seems the USB drives are not the issue
• On the ML10 Gen9 I've tried the follow (after I've set boot priority to USB)...I'm also manually selecting the USB from the boot menu
  • I/O USB port on the motherboard
  • External (Rear) USB
  • Turned off Quick Boot
  • Set USB to Force FDD
  • Set USB to Force HDD
  • I've tried the above with BOTH of the USBs...with no success
• The installation link above mentions:
  • USB-ZIP (I don't see this as an option in BIOS)
  • Try disabling USB 2.0 support (this will default to USB 1.1). (I don't see this anywhere either)
  • Try switching on or off any “Fast Boot” feature. (Only thing I saw was "Quiet Boot" which I've enabled/disabled)
  • Try Switching on or off “USB keyboard” support. (I do not see an option to disable...I do have a USB keyboard connected...and USB is the only way to connect keyboard. BIOS does show it's recognizing the keyboard properly)

 

Any thoughts or suggestions would be greatly appreciated. I'm out of ideas...I've scrolled through all of the BIOS settings, and nothing caught my eye...but I must be missing something.

[JonathanM]

Turn off UEFI (secure boot), unraid only boots legacy mode.

[Spatial Disorder]

Don't you love it when you look at something for an hour...then someone else spots the issue in 10 seconds...ugh. I knew it was going to be something obvious.

 

Thanks jonathanm, I'm up and running now with a couple of drives preclearing.