>>>> "J" == Jarett DeAngelis
J> Hi Roland, Thanks for getting back to me so quickly! I went ahead
J> and reimaged two more drives with the dd command as shown in the
J> instructions. Each of them refused to even start booting. I
J> checked them with the sha256sum command as shown in that post and
J> they both hashed correctly, to the hash ending in fedb1 as shown
J> on the download page. Where should I look next?
is it possible that you're trying to boot via UEFI. Qlustar currently
only supports non-UEFI BIOS setups (Compatibility Boot Mode / CSM). Please
>> On Dec 16, 2019, at 7:15 AM, Roland Fehrenbacher <rf(a)q-leap.de>
>>>> "J" == Jarett
DeAngelis <jarett(a)bioteam.net> writes:
>> Hi Jarett,
>> welcome on board.
J> Hi, I have a small collection of Skylake HP desktops I'm
J> deploying Qlustar onto as a lab environment. I cannot get the
J> system to boot correctly. I'm using the Windows utility "Rufus"
J> to image the USB stick. If I use "dd" mode, when I try to boot it
J> skips right over it as though it weren't bootable. If I use "iso"
J> mode, it gets about six seconds into the boot process, loading
J> modules, before it complains it can't load the vfat module. It is
J> indeed not in /lib! I feel like I must be doing something wrong
J> here, but damned if I can figure it out solo. I have also tried
J> this on a Mac and on a Linux machine with BalenaEtcher; same
J> results as "iso" mode on Rufus.
>> Sorry, but I know nothing about rufus. Please use the default dd
>> route as explained in the installation guide
>> In case you still have problems booting the stick after that, the
>> latter is most likely corrupted (try with another one in this
>> case). Please do the checks as described in
>> to verify it is working correctly.
>> Good luck,