what can we do about "device-mapper: reload ioctl on osprober-linux-sdX" failures? #9801
Replies: 11 comments 10 replies
-
|
Not sure if its related, but I saw some random "spammy-ish" logs similar too; sort of a "bulk spam" that occurred in a big chunk (maybe I ran scsi host scan on this day) |
Beta Was this translation helpful? Give feedback.
-
|
Link to the launchpad os-prober issue. Similar to |
Beta Was this translation helpful? Give feedback.
-
|
This issue surfaced again for me in a recent upgrade of an Ubuntu 20.04 system using the experimental ZFS support and ZSYS, which calls It is then also indirectly related to more recent reports we find in the following, where other side effects occur.
It is not possible for common people to regard this warning as purely cosmetical. Do we know if s/o is working on a PR to |
Beta Was this translation helpful? Give feedback.
-
|
The warning is still happening today 9.1.2020 with Ubuntu 20.04's kernel upgrade. |
Beta Was this translation helpful? Give feedback.
-
|
Warning still appearing on Nov, 30th 2020 with Ubuntu 20.10 fully updated. |
Beta Was this translation helpful? Give feedback.
-
|
Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-54-generic x86_64): |
Beta Was this translation helpful? Give feedback.
-
Ubuntu 20.04.1 LTS kernel updateProcessing triggers for linux-image-5.4.0-58-generic (5.4.0-58.64) ... |
Beta Was this translation helpful? Give feedback.
-
|
Have the same issue ubuntu 20.10
|
Beta Was this translation helpful? Give feedback.
-
|
I got also same warnings on Ubuntu 20.04. I have three disk zraid system.
sudo apt updgrade --> device-mapper: reload ioctl on osprober-linux-sdX1 failed |
Beta Was this translation helpful? Give feedback.
-
|
Same issue for me but might be an Ubuntu problem. Just switching from CentOS and I first noticed this now on Ubuntu 20.04 LTS. Not copying the output, exact same as all of the others above. |
Beta Was this translation helpful? Give feedback.
-
|
Just apt remove the |
Beta Was this translation helpful? Give feedback.
-
|
If you do not want to remove # disable grub's os-prober script hook
GRUB_DISABLE_OS_PROBER=trueNote: This has only been tested on Ubuntu, but I assume most distributions have similar options as it does not appear that this flag was added via any Ubuntu-specific patching to the |
Beta Was this translation helpful? Give feedback.
-
^- that does not work as the env gets wiped ^- this would work |
Beta Was this translation helpful? Give feedback.
-
|
Having said that.. setting But I'm not seeing any You simply have many kernels in different snapshots made by autozsys. Is there a problem at all? |
Beta Was this translation helpful? Give feedback.
-
|
Ah thanks for answering. |
Beta Was this translation helpful? Give feedback.
-
|
There are several components interacting here:
The grub zfs code tries to find kernels in various places, including in zfs snapshots. If you're not creating a gazillion snapshots, this is pretty neat. But now that you have a boat load of snapshots, it may be a bit much. I don't know about your boot time. I wouldn't think more kernels should affect that significantly during boot. They're not loaded, only offered. In any case: if you have problems with too many kernels getting into grub.cfg, you should be filing reports at either the grub-zfs-scripts (10_linux_zfs) or at autozsys and not here at openzfs. |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks! Very helpful comment. |
Beta Was this translation helpful? Give feedback.
-
System information
Describe the problem you're observing
With zfsonlinux, every time osprober-linux-sdX runs during
update-initramfsactivity, it always attempts to reloadioctlon all drives, and if that drive is in use byzfsit fails and prints a lovelyCommand failedmessage.To the keen observer, we know this is to be ignored on ZFS owned drives, but many users would see this and be concerned assuming something went wrong.
What I find a bit unexplained too is that on my system it isn't complaining on EVERY drive, only a few.
Ultimately this is probably a bug in
initramfsor related package(s) for device mapper?... (if so mightzfsmaintainers know the best place to fork this issue to?)Describe how to reproduce the problem
Use
zfsonlinux, on Ubuntu 18.04 LTS, run anapt upgradethat involves kernel updates.or, run
apt autoremovethat involves wiping older kernels.Include any warning/errors/backtraces from the system logs
which can result in
All of my drives are whole-disk owned by ZFS except
sdbandsdeAlso
sdeandsdhare owned bymdadmBeta Was this translation helpful? Give feedback.
All reactions