Installation Error "Controller runtime block volume manager controller"

[sub2010]

Based on the information provided, here's a template for a GitHub issue:

---

Title: Installation task "upgrade" failed with exit code 1

Description:

I'm trying to perform an installation on my mini PC with the following hardware specifications:

• Mini Forum PC: MS-01
• 1TB NVMe SSD: Samsung SSD 990 PRO 1TB (nvme0n1)
• 4TB NVMe SSD: Samsung SSD 990 EVO Plus 4TB (nvme1n1)
• BIOS settings: Secure Boot and Secure Disks are disabled

Disk Overview

ODE   NAMESPACE   TYPE   ID        VERSION   SIZE     READ ONLY   TRANSPORT   ROTATIONAL   WWID                   MODEL                          SERIAL
       runtime     Disk   loop0     2         77 MB    true
       runtime     Disk   nvme0n1   2         1.0 TB   false       nvme                     eui.0025384c41a085cf   Samsung SSD 990 PRO 1TB
       runtime     Disk   nvme1n1   2         4.0 TB   false       nvme                     eui.0025385b41435ccb   Samsung SSD 990 EVO Plus 4TB
       runtime     Disk   sda       3         128 GB   false       usb         true                                Type-C

The installation is being performed using the following controlplane yaml configuration:

install:
    disk: /dev/nvme0n1 # The disk used for installations.
    image: [ghcr.io/siderolabs/installer:v1.9.5](http://ghcr.io/siderolabs/installer:v1.9.5) # Allows for supplying the image used to perform the installation.
    wipe: true # Indicates if the installation disk should be wiped at installation time.

The installation is failing with the following error message:

task install (1/1): failed: task "upgrade" failed: exit code 1

I've attached a screenshot of the error message for reference.

[smira]

Please disable debug setting in the machine config, and capture the actual error which is outside of the scroll buffer in your screenshot.

[smira]

You're running Talos 1.9 specifically, and what I say below doesn't apply to Talos 1.10 and beyond.

I can see that the installer tries to use vmlinuz.efi.signed and fails to find it (which makes sense, as you're using a default installer image which doesn't have it). The only condition that Talos 1.9 tries to do that is under SecureBoot/UKI scenario.

You can move on to the current version of Talos which is 1.10, and it has installers unified, so I don't think it makes a lot of sense to dig into that.

[sub2010]

Iam sorry, but thats not correct. I use v1.10.3 (metal-amd64.iso).

[smira]

You posted your install image in your original question which is Talos 1.9.5, if you try to boot Talos 1.10, and install 1.9.5, this might be the reason for the failure.

Make sure you use same version.

[sub2010]

"Hey, thanks for saving my deployment! 😊
But I find it quite confusing when generating a Controlplane-YAML file, an older image version is used. The error code is also not very helpful. It would be nice if that were fixed and the documentation made clearer."

[smira]

The default value depends on your talosctl version, it can't read your mind, so it uses its own version.

If you mix one version of talosctl with another version of Talos, and don't pay attention to details, you're certainly going to end up in trouble.