This is where things got weird. Initially the server would not even see our USB thumb drive to boot or install. We had to go into the motherboard settings and enable UEFI booting in addition to the BIOS/CSM methods. Once we did that the server would boot from the USB drive, but would not reboot properly. Once we then disabled UEFI booting the server would then, magically, boot from the internal drive just fine.
Then things got weirder. In order to verify the results, we factory-reset the motherboard's firmware and tried again. We could not recreate the initial out-of-the-box behavior. The server would see the USB thumb drive, install vicibox, and reboot off the internal drive just fine regardless of the UEFI setting.
So... my prevailing theory is that the servers might get shipped with some sort of bugged motherboard firmware settings. The mere act of enabling and disabled UEFI booting in the motherboard seems to have fixed something that I can't duplicate even with a factory reset. So if you are having problems installing ViciBox or getting it to reboot after installing, I would try testing with UEFI booting turned on and then maybe back off. I wish I had something more in-depth and intelligent to add, but whatever is going wrong seems to be a some sort of initial motherboard setting from the factory.
If anyone wants to do your own experiments and finds something, feel free to reply back to this thread so others can benefit from it. The issue seems to present mostly on Dells, although I have ran into an HP server or two that had a similar issue. SuperMicro and Gigabyte servers pretty much seem to just work. Other server vendors and brands I can't comment on as I don't normally see much outside of SuperMicro, Dell, and some HP. I've only ran into 1 Gigabyte server that was running ViciBox but it seemed to run just fine.
However, if anyone wants to ship us free hardware to test with, we won't say no.
