top | item 45464719

(no title)

dachrillz | 5 months ago

Not OP, but when we tested it out it was painful to handle usb disks. The reason being that if you have two they get named sda/sdb randomly. We managed to overwrite the usb we were using to install talos since that one was named sda one boot and sdb the next. This lead ut to develop the “pullout technique” when installing…

This mostly only happened because it was a test cluster where we used usb disks, probably not a problem when one properly provisions.

Otherwise it was great! But it does feel akward not booting into an environment where you have a terminal at first

discuss

vizzier|5 months ago

This does sound like it could be solved with better installDiskSelectors[0]. Talos has done a fair bit of work in improving this and UserVolumeConfigs in the last couple of 1.x revisions.

Alternatively, network booting in some fashion is an option. [1]

[0] https://www.talos.dev/v1.11/reference/configuration/v1alpha1...

[1] https://www.talos.dev/v1.11/talos-guides/install/bare-metal-...

INTPenis|5 months ago

I recognize this from my bare-metal homelab setup. But at work we used VMs for Talos nodes so this was not an issue.

And if I had to deploy it on bare-metal at work I'd most likely use PXE booting instead of USB.

bakies|4 months ago

I use pxe boot for my homelab baremetal :)