ERROR Failed to check for OS updates err=resulting buffer size (678) != expected size (679) provider=images

IncusOS
1

Hi all,

I have left my IncusOS server switched off since 2025-12-02. Today after switching it on again, it failed updating the OS:

[2026/02/24 09:53:01 CET] incus-osd: 2026-02-24 08:53:01 INFO Downloading SecureBoot update version=202602240349
[2026/02/24 09:53:01 CET] incus-osd: 2026-02-24 08:53:01 INFO Applying Secure Boot certificate update version=202602240349
[2026/02/24 09:53:01 CET] incus-osd: 2026-02-24 08:53:01 INFO Downloading application update application=incus version=202602240349
[2026/02/24 09:53:13 CET] incus-osd: 2026-02-24 08:53:13 INFO Downloading OS update version=202602240349
[2026/02/24 09:53:36 CET] incus-osd: 2026-02-24 08:53:36 INFO Applying OS update version=202602240349
[2026/02/24 09:53:37 CET] incus-osd: 2026-02-24 08:53:37 ERROR Failed to check for OS updates err=resulting buffer size (678) != expected size (679) provider=images
[2026/02/24 09:53:37 CET] incus-osd: 2026-02-24 08:53:37 INFO Starting application name=incus version=202602240349
[2026/02/24 09:53:39 CET] incus-osd: 2026-02-24 08:53:39 INFO System is ready version=202512022259

I noticed it was also displaying a warning about some recovery keys not having been retrieved, which I ignored after checking I had the copy made after installation on hand.

I then rebooted, which led to a prompt asking me to enter the recovery key. It doesn’t seem to recognize it though.

From my reading of System security - IncusOS documentation this should be working, so I am wondering: do I need to type in the hyphen between the letter groups of the recovery key?

Thanks!

2

I believe you do need to include the hyphens when entering the recovery key; systemd should then be passing that down to the appropriate cryptenroll library call(s) when attempting to unlock the encrypted drive.

The buffer size error you encountered was fixed at the end of December; we actually just had an issue reported about this yesterday, which I’ll point you to for further details. In short, IncusOS is still developing quickly and you should try to apply updates promptly rather than every few months. :slight_smile:

3

Thanks for your reply: I can confirm entering the hyphens was needed – as was using a US layout. That’s done by pressing the ) (right parenthesis) between the 0 and = for other azerty users reading this :wink:

I had searched the forums and the web with variations of the error message without result; next time I’ll include the issue tracker on GH as well (doh)!

I’ll do as the reporter there and reinstall from scratch: this is a test system. I would never leave a production machine going without updates for so long :slight_smile: I’m glad IncusOS is developing at a rapid pace, keep up the great work!

Cheers

4

If I may, I’d suggest adding the info about the hyphens and the Qwerty keymap in System recovery - IncusOS documentation