os-prober doesn't recognize Tumbleweed installation

Yesterday i added a Tumbleweed installation on my Laptop. Currently I’am using the grub2 installed by Tumbleweed, but I want to switch back to 42.1 grub2. But the 42.1 os-prober does’t recognize the Tumbleweed Installation:

 # os-prober
/dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/mapper/system-root2:openSUSE 42.1 (x86_64):SUSE:linux

Blkid shows

/
/dev/sda1: LABEL="ESP" UUID="9CD4-1334" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="742abadb-a7ca-4a10-8389-90001fd972d2" 
dev/sda2: LABEL="DIAGS" UUID="EA3C-F77D" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="ac1256aa-dc46-4f2e-8dfb-68bd7fbb32b3" 
/dev/sda3: UUID="0488-95C5" TYPE="vfat" PARTLABEL="Microsoft reserved partition" PARTUUID="a07023e8-45f5-40ef-bc6a-013ac0d9f8a0" 
/dev/sda4: LABEL="WINRETOOLS" UUID="EA668CA4668C735D" TYPE="ntfs" PARTLABEL="Microsoft recovery partition" PARTUUID="5f858f99-fa70-4b54-a1c4-ac99251d7ac8" 
/dev/sda5: LABEL="OS" UUID="5494078794076AB6" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ae76f448-794c-48ed-aed3-c5b0a6518a2b" 
/dev/sda6: UUID="5ED89A1FD899F58D" TYPE="ntfs" PARTLABEL="Microsoft recovery partition" PARTUUID="3d309fb4-4563-425a-8c01-18d3cd9da655" 
/dev/sda7: UUID="72A29DA0A29D68FD" TYPE="ntfs" PARTUUID="943ca0c5-7ca5-4260-a6d0-3fde0b304d38" 
/dev/sda8: UUID="tMzmsw-dqcW-uJeo-tMAu-bsjn-bLeG-tDkrNL" TYPE="LVM2_member" PARTLABEL="primary" PARTUUID="b621b728-5a54-493a-af96-442a684c3dad" 
/dev/sda9: UUID="E0QouL-14rl-eoQj-iYMU-fQZI-Qu9Q-NWlhsr" TYPE="LVM2_member" PARTLABEL="primary" PARTUUID="0cffd517-6032-4c67-bd34-26704a3160ad" 
/dev/mapper/system-root: UUID="195622b1-cf93-4042-8663-5a1b36b3d1e1" TYPE="ext4" 
/dev/mapper/system-swap: UUID="d2287118-4db8-4fb3-8ae8-34cce0410c91" TYPE="swap" 
/dev/mapper/system-root2: UUID="03a17aec-5e6b-40cc-87b0-22410693cab8" TYPE="ext4" 
/dev/mapper/system-root_tumbleweed: UUID="1fb09d0b-0b2e-4820-9da2-c9e90613c0c7" UUID_SUB="a79c994b-481a-4964-8851-278de8d5d6c6" TYPE="btrfs" 
/dev/dm-2: UUID="76632a1f-c045-4c93-8eb1-39a5e2e7d11b" TYPE="ext4" 
/dev/mapper/system-home--tumbleweed: UUID="2fe7c3bd-628a-41df-b90b-01647007597c" TYPE="xfs" 
/dev/dm-0: UUID="195622b1-cf93-4042-8663-5a1b36b3d1e1" TYPE="ext4" 
/dev/dm-3: UUID="03a17aec-5e6b-40cc-87b0-22410693cab8" TYPE="ext4" 
/dev/dm-5: UUID="1fb09d0b-0b2e-4820-9da2-c9e90613c0c7" UUID_SUB="a79c994b-481a-4964-8851-278de8d5d6c6" TYPE="btrfs" 

The Tumbleweed installation is living in /dev/mapper/system-root_tumbleweed:and /dev/mapper/system-home–tumbleweed ( /dev/mapper/system-root2 is another leap installation)

Looking into syslog ( http://paste.opensuse.org/61710840 ) shows that os-prober is looking into the btrfs partition, but doesn’t recognize the OS installation:

Should I open a new bugreport for this or is this an allready known bug ( couldn’t find it in bugzilla however)

has the cmd

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

been run from within your leap install?

Try package from the repository below - this is being prepared for Leap update. Please tell if it fixes your problem.

https://build.opensuse.org/project/show/home:michael-chang:Leap:42.1:Update

Yes, the updated os-prober-1.61-24.1 recognizes the Tumbleweed installation and (@keellambert) the grub.cfg generated by grub2-mkconfig now has an entry for Tumbleweed, which was lacking before.

# os-prober
/dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/mapper/system-root2:openSUSE 42.1 (x86_64):SUSE:linux
/dev/mapper/system-root_tumbleweed:openSUSE 20151214 (x86_64):SUSE1:linux:btrfs:UUID=1fb09d0b-0b2e-4820-9da2-c9e90613c0c7:subvol=.snapshots/1/snapshot

My GRUB2 doesn’t detect my Windows 10 installation. I ensured that it’s tagged with a BOOT flag. For some reason os-prober doesn’t show me any output.

# blkid
/dev/sda1: SEC_TYPE="msdos" UUID="3A97-2DC3" TYPE="vfat" PARTLABEL="primary" PARTUUID="88562aae-6e24-4238-bd68-38bd8ee7d8ae" /dev/sda2: UUID="hNQuhX-1Ips-oDY2-cmJt-2Ynf-oxHA-NUI8f9" TYPE="LVM2_member" PARTLABEL="primary" PARTUUID="fc8fc588-7f8b-489a-9add-6846362db8da" 
/dev/sdb2: LABEL="Thomas 2TB HDD" UUID="D0F2194AF21935E6" TYPE="ntfs" PARTUUID="0001b738-02" 
/dev/sdc1: UUID="8aac1b8c-0fa8-41e7-8d67-c95835d53d0c" TYPE="ext4" PARTLABEL="VMs" PARTUUID="c3842987-bcdc-4bcd-ba01-c513cea59387" 
/dev/sdc2: UUID="1121D14415A4C374" TYPE="ntfs" PARTUUID="6234d33e-3a3c-476f-8fee-e6503da11d03" 
/dev/sdc3: UUID="1B14F69725BDB19D" TYPE="ntfs" PARTLABEL="Win-Games" PARTUUID="981e9c1e-5d9d-448e-acaf-e0625d98ec5a" 
/dev/mapper/system-swap: UUID="45c048d0-5146-4825-87ac-f1e1d3de317b" TYPE="swap" 
/dev/dm-2: UUID="11421a15-83ac-4544-8bbe-8fd12f5cdd48" TYPE="xfs" 
/dev/dm-1: UUID="86f66b38-17fd-4e6e-834a-bd6ffebdd1ce" UUID_SUB="db2b6186-3434-4d6f-8301-f040a4b5be56" TYPE="btrfs"

I’m running openSUSE 42.1 with all the latest updates installed. Should I still install the package you linked in your post or are the updates already upstream?

How are the OSs installed legacy or EFI? If you mix modes they can not see one another

And how is it related to this discussion? Please open new thread for new problem.

Windows 10 is UEFI and Kubuntu 15.10 (UEFI 64bit) was able to detect it. The Windows partition is sdc2.

It’s probably the same problem. But I was curious if the custom packages where already upstream or not. If so I would have tried this approach.

If you have the latest update for os-prober in leap and still doesn’t recognize the other operating system in your machine, that means it still broken.
You can try to compare it with the link version in previous post.

You can run the os-prober as su and see if it is detecting the other operating systems in your machine.