I installed openSUSE Leap 15 without problems but NO other installed OS was detected by grub2-mkconfig though I enabled “test foreign OS”. There are various different ext4 partitions with Arch, Ubuntu, Fedora and others. I can mount each of them without problems. eg:
mount /dev/mapper/Hitachi_HDT721010SLA360_STF6L7MS281K9K-part1 /mnt
(this partition contains Antergos)
grub.cfg contains only Leap 15 entries, even Tumbleweed was not detected.
Does anyone have an idea?
What’s the output from
grep PROB /etc/default/grub
grep PROB /etc/default/grub
GRUB_DISABLE_OS_PROBER=“false”
That should be okay. But perhaps as a check, can you try commenting out that line (insert ‘#’ at the beginning) and then rerun “grub2-mkconfig”.
I usually see:
% grep PROB /etc/default/grub
#GRUB_DISABLE_OS_PROBER="true"
Have you modified the script in “/etc/grub.d” that is used with os-prober?
That line does not exist in the file, only the line I mentioned above.
No, I didn’t modify anything, That’s why I was so surprised after the installation to only have the Leap 15 entry. Something like that never happened before in any installation of a former openSUSE distro.
I’m also surprised. I don’t have an explanation.
If you mount one of those other partitions, say the ubuntu partition and then run “grub2-mkconfig”, does it find that linux system?
I tried that as well, but it doesn’t work. Somehow the os-prober doesn’t seem to look at any other partition than the Leap 15 one. Beware, my language environment is german 
leap15-pc:/home/leap15 # df
Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
devtmpfs 1970464 0 1970464 0% /dev
tmpfs 2016456 98132 1918324 5% /dev/shm
tmpfs 2016456 10196 2006260 1% /run
tmpfs 2016456 0 2016456 0% /sys/fs/cgroup
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /usr/local
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /opt
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /.snapshots
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /root
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /tmp
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /boot/grub2/i386-pc
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /var
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /boot/grub2/x86_64-efi
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 41943040 9466524 32156164 23% /srv
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part2 503833832 381353808 121439640 76% /home
tmpfs 403288 16 403272 1% /run/user/1000
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part1 50133700 33941856 13615460 72% /run/media/leap15/Antergos
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part5 20511312 9895248 9551104 51% /run/media/leap15/Void
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part6 14286320 9518168 4019404 71% /run/media/leap15/Xubuntu 18.04 u
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part7 19092136 6381056 11718212 36% /run/media/leap15/Pisi
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part8 20511312 9158448 10287904 48% /run/media/leap15/Fedora 28
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part9 20511312 9860648 9585704 51% /run/media/leap15/Arch
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part10 14286320 7944736 5592836 59% /run/media/leap15/Mint
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part11 15053152 12629136 1639632 89% /run/media/leap15/Calculate Linux
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part12 15416264 9186480 5426968 63% /run/media/leap15/Anarchy
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part13 15416140 6233552 8379780 43% /run/media/leap15/Xubuntu 18.04
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part14 15053152 6738796 7529972 48% /run/media/leap15/Solus 3
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part15 15053192 378812 13889996 3% /run/media/leap15/Porteus
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part16 15053152 10260192 4008576 72% /run/media/leap15/Manjaro
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part17 15416264 10859024 3754424 75% /run/media/leap15/Tumbleweed
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part18 9948244 6906656 2513196 74% /run/media/leap15/Linux Lite
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part19 14987656 11827184 2376088 84% /run/media/leap15/Slackware 14.2
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part20 15053192 6662104 7606704 47% /run/media/leap15/ExTiX
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part21 15359524 12177012 3182512 80% /run/media/leap15/Knoppix 8.2
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part23 14351816 3970472 9632596 30% /run/media/leap15/Bunsenlabs
/dev/mapper/Hitachi_HDT721010SLA360_STH607MS1Y918S-part24 15053192 4940380 9328428 35% /run/media/leap15/Archlabs
leap15-pc:/home/leap15 # grub2-mkconfig -o /boot/grub2/grub.cfg
GRUB-Konfigurationsdatei wird erstellt …
Thema gefunden: /boot/grub2/themes/openSUSE/theme.txt
Linux-Abbild gefunden: /boot/vmlinuz-4.12.14-lp150.12.4-default
initrd-Abbild gefunden: /boot/initrd-4.12.14-lp150.12.4-default
Linux-Abbild gefunden: /boot/vmlinuz-4.12.14-lp150.11-default
initrd-Abbild gefunden: /boot/initrd-4.12.14-lp150.11-default
openSUSE Leap 15.0 auf /dev/sda22 gefunden
erledigt
If you run
os-prober
at the root command line, does it find the other systems?
Are you UEFI-booting or CSM-booting (aka Legacy- or MBR-booting)?
If you are UEFI-booting is there a chance that there is more than one EFI systempartition on your system?
Please show
# parted-l
and
# efibootmgr -v
Regards
susejunky
os-prober looks for partitions and device-mapper node is not partition. Someone reported on ML that Leap 15 suddenly is using device-mapper for disks. Please show output of “dmsetup ls --tree” and “dmsetup status”.
On Sat, 09 Jun 2018 15:06:03 +0000, arvidjaar wrote:
> os-prober looks for partitions and device-mapper node is not partition.
> Someone reported on ML that Leap 15 suddenly is using device-mapper for
> disks. Please show output of “dmsetup ls --tree” and “dmsetup status”.
That might explain a related situation I found here with both TW and 42.3
installed on a single drive. If I try to “upgrade” 42.3 -> 15 I am
onlyanomiall offered the 42.3 instance for upgrade while if I try with a
TW upgrade both instances are offered as upgrade candidates.
The 15 installation/upgrade processes also both insist on formatting
the HP diag partition with no way of editing the proposal to not format
that partition. I’m trying to define all the anomalies for a bug report
as there are some glaring issues with Leap 15 installer as it stands.
Well TW to 15 is a down grade since TW keeps moving and current TW is ahead of 15
It does not detect any other OS:
leap15-pc:/home/leap15 # os-prober
/dev/sda22:openSUSE Leap 15.0:openSUSE:linux:btrfs:UUID=23b0e2e1-db59-429d-8220-b7b261404474:subvol=@/.snapshots/1/snapshot
No, it’s an old BIOS system.
leap15-pc:/home/leap15 # parted -l
Modell: ATA Hitachi HDT72101 (scsi)
Festplatte /dev/sda: 1000GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags:
Nummer Anfang Ende Größe Typ Dateisystem Flags
1 1049kB 52,4GB 52,4GB primary ext4 type=83
2 52,4GB 577GB 524GB primary ext4 type=83
3 577GB 581GB 4194MB primary linux-swap(v1) type=82
4 581GB 1000GB 419GB extended type=05
5 581GB 602GB 21,5GB logical ext4 type=83
6 602GB 617GB 15,0GB logical ext4 type=83
7 617GB 637GB 20,0GB logical ext4 boot, type=83
8 637GB 659GB 21,5GB logical ext4 type=83
9 659GB 680GB 21,5GB logical ext4 type=83
10 680GB 695GB 15,0GB logical ext4 type=83
11 695GB 711GB 15,7GB logical ext4 type=83
12 711GB 727GB 16,1GB logical ext4 type=83
13 727GB 743GB 16,1GB logical ext4 type=83
14 743GB 759GB 15,7GB logical ext4 type=83
15 759GB 775GB 15,7GB logical ext4 type=83
16 775GB 790GB 15,7GB logical ext4 type=83
17 790GB 807GB 16,1GB logical ext4 type=83
18 807GB 817GB 10,5GB logical ext4 type=83
19 817GB 833GB 15,7GB logical ext4 type=83
20 833GB 849GB 15,7GB logical ext4 type=83
21 849GB 864GB 15,7GB logical reiserfs type=83
22 864GB 907GB 42,9GB logical btrfs type=83
23 907GB 922GB 15,0GB logical ext4 type=83
24 922GB 938GB 15,7GB logical ext4 type=83
A little correction to my original post: all other partitions are ext4, only one reiserfs partition contains Knoppix 8.2.
leap15-pc:/home/leap15 # efibootmgr -v
EFI variables are not supported on this system.
On Sat, 09 Jun 2018 16:26:03 +0000, gogalthorp wrote:
> Well TW to 15 is a down grade since TW keeps moving and current TW is
> ahead of 15
As far back as I can remember, the “upgrade” also worked to backlevel
versions. Got some weird results the few times I tried it but at least
all installed instances were offered as candidates even if the result was
pretty well doomed to be unsuccessful. Hiding newer versions does make
sense so maybe old age is catching up to me…
There are two identical disks installed, the second is only for backup.
leap15-pc:/home/leap15 # dmsetup ls --tree
Hitachi_HDT721010SLA360_STH607MS1Y918S-part16 (254:25)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part3 (254:12)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part1 (254:2)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part15 (254:24)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part2 (254:11)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part14 (254:23)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part1 (254:10)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part13 (254:22)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part12 (254:21)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part11 (254:20)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part10 (254:19)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part8 (254:9)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part9 (254:18)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part24 (254:33)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part7 (254:8)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part8 (254:17)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part23 (254:32)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part6 (254:7)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part7 (254:16)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part22 (254:31)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part5 (254:6)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part19 (254:28)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part6 (254:15)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part21 (254:30)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part4 (254:5)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part18 (254:27)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part5 (254:14)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part20 (254:29)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part3 (254:4)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part17 (254:26)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STH607MS1Y918S-part4 (254:13)
└─Hitachi_HDT721010SLA360_STH607MS1Y918S (254:0)
└─ (8:0)
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part2 (254:3)
└─Hitachi_HDT721010SLA360_STF6L7MS281K9K (254:1)
└─ (8:16)
leap15-pc:/home/leap15 # dmsetup status
Hitachi_HDT721010SLA360_STH607MS1Y918S-part16: 0 30720000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part3: 0 8192000 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part1: 0 102400000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part15: 0 30720000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part2: 0 1024000000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part14: 0 30720000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part1: 0 102400000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part13: 0 31457032 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part12: 0 31457280 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part11: 0 30720000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part10: 0 29294592 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part8: 0 708622336 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part9: 0 41943040 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part24: 0 30720000 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part7: 0 39059456 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K: 0 1953523055 multipath 2 0 0 0 1 1 A 0 1 2 8:16 A 0 0 1
Hitachi_HDT721010SLA360_STH607MS1Y918S-part8: 0 41943040 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S: 0 1953523055 multipath 2 0 0 0 1 1 A 0 1 2 8:0 A 0 0 1
Hitachi_HDT721010SLA360_STH607MS1Y918S-part23: 0 29294592 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part6: 0 29294592 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part7: 0 39059456 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part22: 0 83886080 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part5: 0 41943040 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part19: 0 30720000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part6: 0 29294592 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part21: 0 30720000 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part4: 0 2 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part18: 0 20480469 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part5: 0 41943040 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part20: 0 30720000 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part3: 0 8192000 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part17: 0 31457280 linear
Hitachi_HDT721010SLA360_STH607MS1Y918S-part4: 0 2 linear
Hitachi_HDT721010SLA360_STF6L7MS281K9K-part2: 0 1024000000 linear
As expected. Well, that’s probably a bug. If this is intentional behavior, I’m afraid that quite some programs will need fixing. Do you have /etc/multipath.conf? What is output of
systemctl status multipathd.socket multipathd.service
multipath -ll
?
Here are the outputs:
leap15-pc:/home/leap15 # systemctl status multipathd.socket multipathd.service
● multipathd.socket - multipathd control socket
Loaded: loaded (/usr/lib/systemd/system/multipathd.socket; enabled; vendor preset: disabled)
Active: active (running) since Sat 2018-06-09 18:13:41 CEST; 3h 4min ago
Listen: @/org/kernel/linux/storage/multipathd (Stream)
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2018-06-09 18:13:58 CEST; 3h 4min ago
Main PID: 1282 (multipathd)
Status: "up"
Tasks: 8
CGroup: /system.slice/multipathd.service
└─1282 /sbin/multipathd -d -s
Jun 09 18:13:58 leap15-pc systemd[1]: Starting Device-Mapper Multipath Device Controller...
Jun 09 18:13:58 leap15-pc multipathd[1282]: --------start up--------
Jun 09 18:13:58 leap15-pc multipathd[1282]: read /etc/multipath.conf
Jun 09 18:13:58 leap15-pc multipathd[1282]: path checkers start up
Jun 09 18:13:58 leap15-pc multipathd[1282]: Hitachi_HDT721010SLA360_STH607MS1Y918S: event checker started
Jun 09 18:13:58 leap15-pc multipathd[1282]: Hitachi_HDT721010SLA360_STF6L7MS281K9K: event checker started
Jun 09 18:13:58 leap15-pc systemd[1]: Started Device-Mapper Multipath Device Controller.
leap15-pc:/home/leap15 # multipath -ll
Hitachi_HDT721010SLA360_STF6L7MS281K9K dm-1 ATA,Hitachi HDT72101
size=932G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
`- 4:0:0:0 sdb 8:16 active ready running
Hitachi_HDT721010SLA360_STH607MS1Y918S dm-0 ATA,Hitachi HDT72101
size=932G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
`- 2:0:0:0 sda 8:0 active ready running
leap15-pc:/home/leap15 # cat /etc/multipath/wwids
# Multipath wwids, Version : 1.0
# NOTE: This file is automatically maintained by multipath and multipathd.
# You should not need to edit this file in normal circumstances.
#
# Valid WWIDs:
/Hitachi_HDT721010SLA360_STH607MS1Y918S/
/Hitachi_HDT721010SLA360_STF6L7MS281K9K/
/etc/multipath.conf doesn’t exist.
So both units were explicitly enabled. Did you do it? What is your system? Is it laptop, desktop, server? How are disks connected? Was it new installation or upgrade from previous version? If it was upgrade, was multipath enabled before?