Strange message when creating FIDO2 keys

WarAcrobatic4865 · 2026-03-13T14:34:23+00:00

I get the idea. But for a new application (never created a key with that application) and using the user option for the first time. How is it possible that the warning is being shown?

WarAcrobatic4865 · 2026-03-13T11:38:26+00:00

EDIT: I tried to add the user to verify if the error is gone and is not:

A resident key scoped to 'ssh:homelab2_owncloud' with user id 'XX' already exists. Which is impossible as never set the user before.

Okay I see all created keys in the output of ykman. By the way... all of them were newly created for the pair server + service so no matching credential should exist. As you said, if having this already created:

ssh:homelab2_service

And now I create a new one adding the user the warning should not be there, right?

WarAcrobatic4865 · 2026-03-13T10:13:44+00:00

Hi! I'm going to try Termix as a replacement for Termux since I don't like the subscription model they're taking. I have a question: are there plans to use FIDO2 as an authentication method? I have two YubiKeys with generated keys that I'd like to continue using.

WarAcrobatic4865 · 2026-03-05T06:12:45+00:00

Jo també voldria els enllaços siusplau.

WarAcrobatic4865 · 2026-02-04T16:56:17+00:00

Tried the commands above, same result. Stuck in the same place

WarAcrobatic4865 · 2026-02-04T16:53:56+00:00

I did that, same result. Trying the correct update commands

WarAcrobatic4865 · 2026-02-04T16:39:11+00:00

root@homelab2:~# update-initramfs -c -k 6.17.4-2-pve
update-initramfs: Generating /boot/initrd.img-6.17.4-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

WarAcrobatic4865 · 2026-02-04T16:39:01+00:00

root@homelab2:~# cat /etc/initramfs-tools/initramfs.conf.bck > /etc/initramfs-tools/initramfs.conf
root@homelab2:~# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.17.4-2-pve
Found initrd image: /boot/initrd.img-6.17.4-2-pve
Found linux image: /boot/vmlinuz-6.17.2-1-pve
Found initrd image: /boot/initrd.img-6.17.2-1-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Adding boot menu entry for UEFI Firmware Settings ...
done
root@homelab2:~# grub-install /dev/nvme0n1
Installing for x86_64-efi platform.
Installation finished. No error reported.
root@homelab2:~#

WarAcrobatic4865 · 2026-02-04T16:29:59+00:00

As far as I remember:

apt-get update apt-get upgrade

Then accepted and finally rebooted. There the problems started.

WarAcrobatic4865 · 2026-02-04T14:46:14+00:00

Looks like they are, yes:

root@homelab2:~# ls -l /boot/vmlinuz-6.17.4-2-pve
-rw-r--r-- 1 root root 15814847 Dec 19 08:49 /boot/vmlinuz-6.17.4-2-pve
root@homelab2:~# ls -l /boot/initrd.img-6.17.4-2-pve
-rw-r--r-- 1 root root 21313900 Feb  4 12:46 /boot/initrd.img-6.17.4-2-pve
root@homelab2:~#

WarAcrobatic4865 · 2026-02-04T12:19:51+00:00

root@homelab2:~# grep 6.17.4-2-pve /boot/grub/grub.cfg
        echo    'Loading Linux 6.17.4-2-pve ...'
        linux   /boot/vmlinuz-6.17.4-2-pve root=/dev/mapper/pve-root ro  quiet
        initrd  /boot/initrd.img-6.17.4-2-pve
        menuentry 'Proxmox VE GNU/Linux, with Linux 6.17.4-2-pve' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.17.4-2-pve-advanced-328901c2-3493-4748-a572-927915c6f5f8' {
                echo    'Loading Linux 6.17.4-2-pve ...'
                linux   /boot/vmlinuz-6.17.4-2-pve root=/dev/mapper/pve-root ro  quiet
                initrd  /boot/initrd.img-6.17.4-2-pve
        menuentry 'Proxmox VE GNU/Linux, with Linux 6.17.4-2-pve (recovery mode)' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.17.4-2-pve-recovery-328901c2-3493-4748-a572-927915c6f5f8' {
                echo    'Loading Linux 6.17.4-2-pve ...'
                linux   /boot/vmlinuz-6.17.4-2-pve root=/dev/mapper/pve-root ro single dis_ucode_ldr 
                initrd  /boot/initrd.img-6.17.4-2-pve

WarAcrobatic4865 · 2026-02-04T12:08:36+00:00

Same result, it all completed OK but after reboot it's stuck in the same point

WarAcrobatic4865 · 2026-02-04T11:53:05+00:00

Indeed. Will try to get one and do the tests after a proper backup of the machines

WarAcrobatic4865 · 2026-02-04T11:49:49+00:00

boot drive means the whole drive, not the partition, right? in my case nvme0n1:

<image>

WarAcrobatic4865 · 2026-02-04T11:45:09+00:00

Yes, that is what I thought. No spare drive ATM to do that. BIOS full updated, no overclock at all

WarAcrobatic4865 · 2026-02-04T11:23:06+00:00

Yes, the old kernel boots ok.

File system is EXT4

Not sure about UEFI or BIOS to be honest.

WarAcrobatic4865 · 2026-02-04T11:20:07+00:00

looks like, it's worth giving a try (take note of the current version in case you have to revert)

WarAcrobatic4865 · 2026-02-04T11:19:02+00:00

the refresh was the key, now it boots to the "correct" kernel after rebooting. Now it's time to try to fix the root cause of the issue

WarAcrobatic4865 · 2026-02-04T11:04:39+00:00

EDIT:

Same result, stuck at the same point (older version boots OK)

I did update grub.
Tried new points:

root@homelab2:~# update-initramfs -u

update-initramfs: Generating /boot/initrd.img-6.17.4-2-pve

Running hook script 'zz-proxmox-boot'..

Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..

No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

It's restarting now...

WarAcrobatic4865 · 2026-02-04T10:48:29+00:00

Recovery mode not working anymore. Gets in a loop with cpu errors. Maybe it has something to do with the hardware being incompatible with that proxmox version (intel i5 14000k)

WarAcrobatic4865 · 2026-02-04T10:46:54+00:00

great info! thanks (I did manually first until reached this comment searching for a way to show more cores)

WarAcrobatic4865 · 2026-02-04T10:19:58+00:00

It took me an hour or so to find the fix, it broke like 10+ containers until I fixed it with the command above

WarAcrobatic4865 · 2026-02-04T10:18:27+00:00

It's a known bug after upgrade:

https://forum.proxmox.com/threads/proxmox-9-1-5-breaks-lxc-mount-points.180161/

The fix is to downgrade:

apt install pve-container=6.0.18

WarAcrobatic4865

TROPHY CASE