Cannot install Talos to disk.

[kelvinasher]

Hello! I am getting an error and immediate reboot upon trying to run the following:
talosctl apply-config -f ./talosctl/controlplane.yaml -n 192.168.1.123 --insecure

The error failure point reads as:
phase env(1/12): done, 515.344s
phase install (2/12): 1 tasks(s)
task install (1/1): starting
task install (1/1) waiting for the image cache
task install (1/1): failed: not a directory

as you can see, the last line is where the error happens and the machine begins a reboot sequence.

I have not changed anything except for the install path (my internal hdd is listed as /dev/sdb), and I got the iso from Factory with only intel chipset packages installed.

Where should I look? I found an article on enabling image cache, but I felt as though this was the opposite of what I wanted so I updated my talos config file with the appropriate entries to read explicitly 'false' and still no change.

Running bare metal v1.9.2

If there is a way I can get logs from a bare metal machine in the situation I am in, please let me know and I will post them too.

[smira]

Waiting for the image cache is a red herring here, it is not enabled in your case I guess, so it just goes on.

I don't know what is failed: not a directory, but it's best to provide full logs.

You can capture serial console logs (if you have IPMI/BMC) by booting with console=ttyS0 added to the command line.

[kelvinasher]

Thanks for the reply.

I do not have IPMI capabilities AFAIK.

Any other ideas on how to capture the logs before it reboots? I can upload a photo or a video recording of the screen before it reboots on me, but the logs go so quickly that may not be helpful.

There is no way to investigate the install phase/task and find what would generate the not a directory message? I tried do some digging in this repo for anything relevant and could not come up with anything helpful. I am curious what exactly it is fatally informing me that it cannot find.

If it was not stuck in maintenance mode, I assume this would be trivial but unfortunately I'm stuck here.

[kelvinasher]

Well,
this is rather embarrassing, but I found my issue was that I told the installer to look at /dev/sdb/, and didn't even realize that the correct syntax has no following forward slash. Updating it to be just /dev/sdb seems to have fixed the installer issue.

Thank you!

[rothgar]

I wonder if we can add validation to the API to make sure install disks don't end with a /