Minor anomaly when processing hooks

I attach here a little section from the output on an update. I wonder why it happens - and how to remove it. No urgency, I can't see that it causes any problems - but my OCD gets triggered by error messages :grin:

Found 5 snapshot(s)
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

The odd thing is I have no idea why something called grub-probe is even running when os-prober is disabled (in /etc/default/grub) because it isn't needed. I was hoping grub-probe was a script, but apparently not - so...

Thanks if someone can answer (with minimum effort!) with a pointer in the right direction.

As best I can tell (it happens to me too), it causes no problems. I haven't looked exactly why, but I believe it's tied in with the btrfs snapshots.

Possibly not useful, but:

$ man grub-probe
...
grub-probe - probe device information for GRUB
$ ag probe /etc/grub.d
60_memtest86+
21:    _GRUB_MEMTEST_HINTS_STRING="$(${grub_probe} --target=hints_string ${MEMTEST86_IMAGE})"
22:    _GRUB_MEMTEST_FS_UUID="$(${grub_probe} --target=fs_uuid ${MEMTEST86_IMAGE})"

00_header
158:       prepare_grub_to_access_device `${grub_probe} --target=device "${GRUB_FONT}"`
181:		prepare_grub_to_access_device `${grub_probe} --target=device "${font_path}"`
242:	prepare_grub_to_access_device `${grub_probe} --target=device "$GRUB_THEME"`
283:	prepare_grub_to_access_device `${grub_probe} --target=device "$GRUB_BACKGROUND"`

10_linux
74:	rpool=`${grub_probe} --device ${GRUB_DEVICE} --target=fs_label 2>/dev/null || true`
4 Likes