http://bugzilla.suse.com/show_bug.cgi?id=960074 http://bugzilla.suse.com/show_bug.cgi?id=960074#c1 --- Comment #1 from Michael Chang --- (In reply to Matthias Schünemann from comment #0)

I did a second install of Leap 42.1 in a free partition (since the first one is broken, see bug 958798). After completion of the installation and reboot there was only one entry for Leap 42.1, i.e. the new one.

This should be fixed as bsc#957018, please retest by installing updated os-prober package from maintenance update after the mentioned fix released (which is not yet at the time of writing).

I had to edit grub.cfg to be able to start the old (broken) installation.

Out of curious, how did you do that ? Is it chainloading the btrfs partition ?

I don't know how to reach the old snapshots, since the stanza in grub.cfg calls automatically the snapshots of the new installation. There should be additional menu entries for both, old installation and old snapshots or is it a feature masking double installations?

Please consider it as os-prober limitation, currently it will ignore snapshots except default subvolume. Thanks, -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=960074 http://bugzilla.suse.com/show_bug.cgi?id=960074#c3 --- Comment #3 from Matthias Schünemann --- (In reply to Michael Chang from comment #1) ...

...

I had to edit grub.cfg to be able to start the old (broken) installation.

Out of curious, how did you do that ? Is it chainloading the btrfs partition ?

Well, I added the following lines: ... ### END /etc/grub.d/90_persistent ### ### BEGIN Handarbeit ### menuentry 'openSUSE Leap 42.1 kaputt' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-07808384-262d-4a8a-9c3d-da2ed2ac98f9' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod btrfs set root='hd0,msdos5' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 --hint='hd0,msdos5' 07808384-262d-4a8a-9c3d-da2ed2ac98f9 else search --no-floppy --fs-uuid --set=root 07808384-262d-4a8a-9c3d-da2ed2ac98f9 fi echo 'Loading Linux 4.1.12-1-default ...' linux /boot/vmlinuz-4.1.12-1-default root=UUID=07808384-262d-4a8a-9c3d-da2ed2ac98f9 ${extra_cmdline} resume=/dev/disk/by-uuid/57edc8bb-1fdb-487b-9f33-cef529a46f75 splash=silent quiet showopts echo 'Loading initial ramdisk ...' initrd /boot/initrd-4.1.12-1-default } ### BEGIN snapshot Handarbeit ### if [ -f "/.snapshots/grub-snapshot.cfg" ]; then source "/.snapshots/grub-snapshot.cfg" fi ### END snapshot Handarbeit ### This is the new entry, just changed to the correct UUIDs ... The last few lines after Begin snapshot Handarbeit point to the new snapshots... ...

Please consider it as os-prober limitation, currently it will ignore snapshots except default subvolume.

Would be a nice to have addition but I guess not so many people do dual installs -- yet. This might differ later on when more installations of different releases coexist on more computers. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=960074 http://bugzilla.suse.com/show_bug.cgi?id=960074#c10 --- Comment #10 from Michael Chang --- Hi Matthias, You can update your os-prober package to new version in Leap by following the steps above. Please let me know if it works or not. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=960074 http://bugzilla.suse.com/show_bug.cgi?id=960074#c12 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #12 from Michael Chang --- (In reply to Matthias Schünemann from comment #11)

Well, it works, inasmuch as it now finds the second leap installation.

Great news. Thanks.

In my case that one is broken and perhaps, just perhaps, an older snapshot might have let me boot it again. You wrote in Comment #1 that os-prober can't handle snapshots. Maybe I should scrub it and install Tumbleweed ;-).

Initially it excludes any subvolume that is of type snapshot or readonly. But you really can do "rollback to a snapshot" or even "installation to a snapshot" (to manage all your system states as snapshots in chronological order and also allow to delete it) then your default subvolume becomes a snapshot. That os-prober fixes the problem of default subvolume as a snapshot.

Thanks for your efforts.

Then I consider it's time to mark as a fixed one. Thanks for your help. *** This bug has been marked as a duplicate of bug 954225 *** -- You are receiving this mail because: You are on the CC list for the bug.