Thank you for taking the time to report this bug and helping to make Ubuntu better. I failed to reproduce the issue. I took a jammy VM and added a label to the boot device:
``` sudo tune2fs -L somelabel /dev/vda3 ```
Configured fstab to look for the label:
``` $ grep -w / /etc/fstab | grep -v ^# LABEL=somelabel / ext4 errors=remount-ro 0 1 ```
and successfully updated the initrd:
``` $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.5.0-35-generic ```
I checked the call from `resolve_device`:
``` $ blkid -l -t LABEL=somelabel -o device /dev/vda3 ```
Can you let mkinitramfs run with `set -x` to get some log messages?
Thank you for taking the time to report this bug and helping to make Ubuntu better. I failed to reproduce the issue. I took a jammy VM and added a label to the boot device:
```
sudo tune2fs -L somelabel /dev/vda3
```
Configured fstab to look for the label:
```
$ grep -w / /etc/fstab | grep -v ^#
LABEL=somelabel / ext4 errors=remount-ro 0 1
```
and successfully updated the initrd:
``` img-6.5. 0-35-generic
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.
```
I checked the call from `resolve_device`:
```
$ blkid -l -t LABEL=somelabel -o device
/dev/vda3
```
Can you let mkinitramfs run with `set -x` to get some log messages?