New Proxmox install hangs on reboot when external Thunderbolt drives are attached

[AnalogKid]

Hello,

I just setup a new GMKTech K8 NUC with Proxmox. I had no issues installing or getting Proxmox itself configured. I have a couple of VM's running on it (the local storage) just fine.

The issue comes when I try to connect external Thunderbolt drives to the NUC. The NUC is USB 4 which should, and appears to, recognize Thunderbolt just fine.

I have tried two drive setups:

- An Akitito external with a PCI card with 4 M.2 SSD drives (this setup has worked when connected to a previous Proxmox server, a MacPro using a TB2 > TB3 adapter)
- An OWC Envoy Express with an M.2 SSD drive

I can see that the computer is recognizing the devices and the drives (once the device is authorized). I have also gone through the process of authorizing the Thunderbolt drives using the

boltctl enroll

command. I can run the

lsblk

command and see the drives (I have not gone through the process of trying to connect the drives to Proxmox). The problem comes when I try to reboot. When I reboot the system hangs at loading initial ramdisk.

I have attached some information that I have collected.

Any assistance in getting past this issue will be greatly appreciated.

Thanks,

Robert

 

[AnalogKid]

Hello,

UPDATE: Well the solution was easier than I imagined ... sort of.

It took a fair amount of troubleshooting but the problem appears to have been one of the M.2 SSD drives that would intermittently show itself and intermittently not show itself (when plugged in after boot) but would always cause issues when booting.

At this time I have removed that one M.2 SSD drive from the PCIe card that holds 4 SSD's and the system is booting just fine.

I tested the PCIe card with 4 different M.2 SSD cards with various combinations of drives in different slots and Proxmox would always fail to fully boot when the on Samsung 970 EVO drive was installed (regardless of the slot it was in - the drive also had any partition deleted and was reformatted and appears to be working fine on other systems and passes all smartclt tests).

Strange ... very strange.

All is mostly good now.

Hope this helps someone else in the future.

Thanks!