`v1.8.2` having EFI issues ?

[BastienM]

Bug Report

Description

After flashing the v1.8.2 raw image on the NVMe, RK1s can no longer boot properly. u-boot complains about a missing EFI partition, which exists. I also went on with flashing the u-boot-spi.bin from the latest release ( v1.8.2-2-g2f6b258), without any apparent changes.

Then flashed 1.7.6 back on the NVMe, and it booted correctly.

~Only really difference I could see at glances, is an offset of 1Mb between partition 0 (unformatted) and partition 1 (EFI).~ ~Unsure about the real impact since u-boot should not really care about the partition sizes...~

Logs

dmesg with 1.8.2:

U-Boot 2024.01 (Mar 17 2024 - 09:36:05 +0000)

Model: Turing Machines RK1
DRAM:  8 GiB (effective 7.7 GiB)
Core:  317 devices, 28 uclasses, devicetree: separate
MMC:   mmc@fe2e0000: 0
Loading Environment from nowhere... OK
In:    serial@febc0000
Out:   serial@febc0000
Err:   serial@febc0000
Model: Turing Machines RK1
Net:   eth0: ethernet@fe1c0000
Hit any key to stop autoboot:  0
pcie_dw_rockchip pcie@fe180000: PCIe-0 Link Fail
** Booting bootflow 'nvme#0.blk#1.bootdev.part_1' with efi
Booting /efi\boot\bootaa64.efi
error: no such partition.
Entering rescue mode...
grub rescue>

dmesg with 1.7.6:

U-Boot 2024.01 (Mar 17 2024 - 09:36:05 +0000)

Model: Turing Machines RK1
DRAM:  8 GiB (effective 7.7 GiB)
Core:  317 devices, 28 uclasses, devicetree: separate
MMC:   mmc@fe2e0000: 0
Loading Environment from nowhere... OK
In:    serial@febc0000
Out:   serial@febc0000
Err:   serial@febc0000
Model: Turing Machines RK1
Net:   eth0: ethernet@fe1c0000
Hit any key to stop autoboot:  0
pcie_dw_rockchip pcie@fe180000: PCIe-0 Link Fail
** Booting bootflow 'nvme#0.blk#1.bootdev.part_1' with efi
Failed to load EFI variables
Booting /efi\boot\bootaa64.efi

                             GNU GRUB  version 2.12

 ┌────────────────────────────────────────────────────────────────────────────┐
 │*A - Talos v1.7.6                                                           │
 │ Reset Talos installation and return to maintenance mode                    │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 │                                                                            │
 └────────────────────────────────────────────────────────────────────────────┘

      Use the ▲ and ▼ keys to select which entry is highlighted.
      Press enter to boot the selected OS, `e' to edit the commands
      before booting or `c' for a command-line.
   The highlighted entry will be executed automatically in 0s.
  Booting `A - Talos v1.7.6'

[nberlee]

please flash a full disk image to the emmc and afterwards directly the spi image. That should fix it, and was tested extensively before releasing 1.8.2

[BastienM]

Yes, I did that the first time around (when I installed v1.7.6). Even tried it once more with the 1.8.2 img, without more success.

In the end, I flashed back 1.7.6 and went along with a talos upgrade. Which worked.

[nberlee]

There where partition problems in 1.8.2, see : https://github.com/siderolabs/talos/issues/9701

Not sure if its related as I cannot replicate your report as is.

[BastienM]

I will see if I can make time this weekend to try to reproduce the issue.