Hi again, playing with updates, I maneuvered the EBG envs on a system into this weird state:
---------------------------- Config Partition #0 Values: in_progress: yes revision: 4 kernel: C:BOOT1:linux.efi kernelargs: watchdog timeout: 0 seconds ustate: 3 (FAILED) user variables: recovery_status = failed ---------------------------- Config Partition #1 Values: in_progress: no revision: 3 kernel: C:BOOT1:linux.efi kernelargs: watchdog timeout: 0 seconds ustate: 2 (TESTING) user variables: To get there, I started an upstate with swupdate and booted into testing path #1. But then didn't confirm this update and rather started it again, using the same swu. That didn't complete because the UUID clash was detected. swupdate terminated, and I was left with the above. I can still boot this constellation, EBG will select path #1 (endless testing, so to say). OTOH: # bg_printenv -c Using latest config partition Values: in_progress: yes revision: 4 kernel: C:BOOT1:linux.efi kernelargs: watchdog timeout: 0 seconds ustate: 3 (FAILED) user variables: recovery_status = failed That is not quite correct. To be fair, bg_printenv deals with an illegal state here. Still... The key question is where to avoid best entering this state in the first place? Jan -- Siemens AG, Technology Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/934a4d61-ed5c-cb5b-82af-86d9e3353120%40siemens.com.
