talos: [SBC/rk1] can't upgrade from v1.10.1 => v1.10.2

Bug Report

Description

i’ve flashed my node to v1.10.1 when the talos released this version, i dit not install the v1.10.0 to avoid https://github.com/siderolabs/talos/issues/10859 on bootloader stuff but it’s seems that the issue is stil present

Logs

192.168.1.211: user: warning: [2025-05-23T20:35:20.713909882Z]: [talos] phase upgrade (9/13): 1 tasks(s)
192.168.1.211: user: warning: [2025-05-23T20:35:20.719536882Z]: [talos] task upgrade (1/1): starting
192.168.1.211: user: warning: [2025-05-23T20:35:20.724728882Z]: [talos] task upgrade (1/1): performing upgrade via "factory.talos.dev/metal-installer/c8cabfff8d28043c7e8e80190e6c8c890ac53b9744ebe390fd315d6589d07fe7:v1.10.2"
192.168.1.211: user: warning: [2025-05-23T20:35:20.891440882Z]: 2025/05/23 20:35:21 running Talos installer v1.10.2
192.168.1.211: user: warning: [2025-05-23T20:35:20.910395882Z]: 2025/05/23 20:35:21 system disk wipe on upgrade is not supported anymore, option ignored
192.168.1.211: user: warning: [2025-05-23T20:35:20.924002882Z]: 2025/05/23 20:35:21 running pre-flight checks
192.168.1.211: user: warning: [2025-05-23T20:35:20.930798882Z]: 2025/05/23 20:35:21 host Talos version: v1.10.2
192.168.1.211: user: warning: [2025-05-23T20:35:20.937081882Z]: 2025/05/23 20:35:21 host Kubernetes versions: kubelet: 1.33.0, kube-apiserver: 1.33.0, kube-scheduler: 1.33.0, kube-controller-manager: 1.33.0
192.168.1.211: user: warning: [2025-05-23T20:35:20.952621882Z]: 2025/05/23 20:35:21 all pre-flight checks successful
192.168.1.211: kern:    info: [2025-05-23T20:35:20.957345882Z]:  nvme0n1: p1 p2 p3 p4 p5
192.168.1.211: user: warning: [2025-05-23T20:35:20.959416882Z]: Error: failed to probe bootloader on upgrade: file does not exist
192.168.1.211: user: warning: [2025-05-23T20:35:20.971426882Z]: Usage:
192.168.1.211: user: warning: [2025-05-23T20:35:20.973694882Z]:   installer install [flags]
192.168.1.211: user: warning: [2025-05-23T20:35:20.978006882Z]: 
192.168.1.211: user: warning: [2025-05-23T20:35:20.979687882Z]: Flags:
192.168.1.211: user: warning: [2025-05-23T20:35:20.981946882Z]:   -h, --help   help for install
192.168.1.211: user: warning: [2025-05-23T20:35:20.986650882Z]: 
192.168.1.211: user: warning: [2025-05-23T20:35:20.989305882Z]: Global Flags:
192.168.1.211: user: warning: [2025-05-23T20:35:20.992248882Z]:       --arch string                    The target architecture (default "arm64")
192.168.1.211: user: warning: [2025-05-23T20:35:21.001688882Z]:       --board string                   Deprecated: no op (default "none")
192.168.1.211: user: warning: [2025-05-23T20:35:21.010443882Z]:       --bootloader                     Deprecated: no op (default true)
192.168.1.211: user: warning: [2025-05-23T20:35:21.019095882Z]:       --config string                  The value of talos.config
192.168.1.211: user: warning: [2025-05-23T20:35:21.027075882Z]:       --disk string                    The path to the disk to install to
192.168.1.211: user: warning: [2025-05-23T20:35:21.035845882Z]:       --extra-kernel-arg stringArray   Extra argument to pass to the kernel
192.168.1.211: user: warning: [2025-05-23T20:35:21.044794882Z]:       --force                          Indicates that the install should forcefully format the partition
192.168.1.211: user: warning: [2025-05-23T20:35:21.056579882Z]:       --meta metaValueSlice            A key/value pair for META (default [])
192.168.1.211: user: warning: [2025-05-23T20:35:21.065725882Z]:       --platform string                The value of talos.platform
192.168.1.211: user: warning: [2025-05-23T20:35:21.073794882Z]:       --upgrade                        Indicates that the install is being performed by an upgrade
192.168.1.211: user: warning: [2025-05-23T20:35:21.084978882Z]:       --zero                           Indicates that the install should write zeros to the disk before installing
192.168.1.211: user: warning: [2025-05-23T20:35:21.097706882Z]: 
192.168.1.211: user: warning: [2025-05-23T20:35:21.099369882Z]: failed to probe bootloader on upgrade: file does not exist
192.168.1.211: user: warning: [2025-05-23T20:35:21.154375882Z]: [talos] task upgrade (1/1): failed: task "upgrade" failed: exit code 1
192.168.1.211: user: warning: [2025-05-23T20:35:21.162941882Z]: [talos] phase upgrade (9/13): failed
192.168.1.211: user: warning: [2025-05-23T20:35:21.168123882Z]: [talos] upgrade sequence: failed
192.168.1.211: user: warning: [2025-05-23T20:35:21.172918882Z]: [talos] upgrade failed: error running phase 9 in upgrade sequence: task 1/1: failed, task "upgrade" failed: exit code 1

Environment

  • Talos version: [talosctl version --nodes <problematic nodes>]
❯ talosctl version
Client:
	Tag:         v1.10.2
	SHA:         1cf5914b6e9c7ff9ffd1576602e6beafcffc147b

	Built:       
	Go version:  go1.24.3
	OS/Arch:     linux/amd64
Server:
	NODE:        192.168.1.213
	Tag:         v1.10.1
	SHA:         52269e81
	Built:       
	Go version:  go1.24.2
	OS/Arch:     linux/arm64
	Enabled:     RBAC
	NODE:        192.168.1.212
	Tag:         v1.10.1
	SHA:         52269e81
	Built:       
	Go version:  go1.24.2
	OS/Arch:     linux/arm64
	Enabled:     RBAC
	NODE:        192.168.1.211
	Tag:         v1.10.2
	SHA:         1cf5914b
	Built:       
	Go version:  go1.24.3
	OS/Arch:     linux/arm64
	Enabled:     RBAC
  • Kubernetes version: [1.33]
  • Platform: sbc/turinkRk1

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 19 (10 by maintainers)

Commits related to this issue

Most upvoted comments

if you flash from factory with factory version previous to this version

Image

you have to start again and obsviously avoid the 1.10.0 of talos

Indeed I’m getting bootedWithUKI: true. Although I’m pretty sure I flashed 1.10.1 and upgraded from there. I previously had the same issue with 1.10.0 upgrading to 1.10.1 (see #10999), so I started from scratch with 1.10.1. Strange. I’ll re-flash all nodes once again later today and see if it helps. Thanks!

Previous 1.10.1 from factory was buggy, we’ve released new version of factory, so new downloads are fixed

This is should be fixed now, 1.10.1 and above disk images from factory are good