Hi - I ran into an issue with the script /usr/lib/linux-boot-probes/50mounted-tests (os-prober package) mounting an already mounted btrfs volume and effectively corrupting that volume. This occurred automatically during a "zypper update" on a Leap 15.2 system. /var/log/message outputs indicate the volume was actually mounted. At that time the volume was already in used by a XEN VM. The volume is part of a LVM Volume Group and lvdisplay indicated the volume was already in use. 1. Why is this script needed when dracut/grub is updating the initrd files and why does it touch (rw mount) volumes unrelated to the boot process? 2. Why did the btrfs partition not rejecting any further mount attempts (as it was already opened elsewhere)? 3. In order to prevent this from happening in the future is it safe to remove "os-prober" or can the script be modified to leave certain volumes untouched? Thanks Holger --