Unable to Install from USB

[one800higgins]

I've built a new workstation for TrueNAS Scale that I'm planning to migrate my TrueNAS Core server content to, but I have an odd issue that I can't find anyone else reporting online or on these forums.

I can not get beyond the first screen of the installer. After booting from the USB, it loads the blue screen where you choose between "Start TrueNAS SCALE Installation" or "Start TrueNAS SCALE Installation (115200 baud)". After selecting, the screen goes black but remains on. The keyboard is still active and I can force a reboot, but the video just never returns.

For reference, I'm using an ASRock Rack X570D4U-2L2T mobo with AMD 5800x CPU and 64 GB of ECC RAM. I am using the on-board video since the CPU doesn't have integrated graphics. I'm on the latest BIOS. I've tried both with a monitor attached and with it detached and using their IPMI remote access web GUI. I've also tried multiple USB sticks, made on both Mac and Windows systems using various methods. The result is the same every time.

Any suggestions? I have seen several other people report using this mobo without issue before, so I doubt it's a compatibility issue.

 

[one800higgins]

While browsing, I did see someone mention a couple years ago that running the installer over USB 3.0 ports can sometimes be funky, but they didn't explain what issues they encountered. Unfortunately this motherboard doesn't have any 2.0 ports to test if this makes a difference for me, but I have considered picking up a cheap PCIe card with USB 2.0 inputs just to test this idea out.

 

[WI_Hedgehog]

If you search "Ventoy" and User: WI_Hedgehog you'll find several threads on the topic that address "odd" issues, most with solutions.

 

[one800higgins]

If you search "Ventoy" and User: WI_Hedgehog you'll find several threads on the topic that address "odd" issues, most with solutions.

Welp, Ventoy seems to have worked. Thank you for the quick reply! Can’t believe none of the other methods of burning the USB worked out. Never had an issue with bootable USBs in all my years.

 

[etoel]

Welp, Ventoy seems to have worked. Thank you for the quick reply! Can’t believe none of the other methods of burning the USB worked out. Never had an issue with bootable USBs in all my years.

How did you resolve this? I have the same MB and 5900x and have the exact same issue. I do use ventoy and I get to the blue install screen, but then it all goes black. The proxmox installer launches without issues from the same ventoy stick.
I also use the IPMI as I have no VGA monitor on hand.
Did you set anything specific in the BIOS for this?
I have used this ventoy stick many times on other boards. I did check the SHA256 and it was correct.
I tried upgrading to 23.10.1 this morning and had made the mistake of upgrading the boot pool so I need to reinstall :( Now I'm stuck at this..
I did read all the @WI_Hedgehog posts, but was able to locate any options for loading the ISO into ram

 

[WI_Hedgehog]

How did you resolve this? I have the same MB and 5900x and have the exact same issue. I do use ventoy and I get to the blue install screen, but then it all goes black. The proxmox installer launches without issues from the same ventoy stick.
I also use the IPMI as I have no VGA monitor on hand.
Did you set anything specific in the BIOS for this?
I have used this ventoy stick many times on other boards. I did check the SHA256 and it was correct.
I tried upgrading to 23.10.1 this morning and had made the mistake of upgrading the boot pool so I need to reinstall :( Now I'm stuck at this..
I did read all the @WI_Hedgehog posts, but was able to locate any options for loading the ISO into ram

Ventoy can be loaded into RAM, the ISO file is mounted by Ventoy as a "removable drive with media inserted." Depending on how the boot loader of the media is configured (remembering an ISO image is an image of the "actual media" and the virtual mount Ventoy creates makes it appear to the client boot loader that it is running off physical media) the client bootloader may then present an option to load the client OS into RAM, and that's sometimes convenient though should normally be unnecessary.

It sounds (to me, anyway) like you are installing headless (no monitor attached to the machine) and monitoring the system via remote terminal connection. If this is your situation it may be an unsupported screen resolution is causing issues, however you might at that point be able to connect to TrueNAS remotely and continue your installation.