Two Opensuse instanses installed - how to clean up?

English Install/Boot/Login
1

I have serious problems after installing Leap 16.0 on a dualboot system that previously was running Leap 15.6 and Windows (the latter for some specific software).

I have probably made some mistakes during install and also installed the system twice, trying to retain all settings etc. on the previous system. Did not find new installer intuitive and was not happy with fact that I did not find a sort of upgrading solution, where user settings were transferred, and also that I did not find a way to isolate the root user from my own account.

Now my situation is as follows.

In the boot menu I have 5 options

Opensuse Leap 16.0
Advanced options for Opensuse Leap 16.0
Opensuse Leap 16.0 (on /dev/nmve0n1p2)
Advanced options for Opensuse Leap 16.0 (on /dev/nmve0n1p2)
Windows Boot Manager (on /dev/sda1)

The 1. Opensuse Leap 16.0 entry boots into command line with loads of permission related errors (refering to systemctl)

The 3. Opensuse Leap 16.0 (on /dev/nmve0n1p2) boots into graphical mode and my old desktop and (some) retained settings. I have to set up printer, scanner, NFS shares etc. this weekend…

I want to get rid of the first two entries and claim eventual space they take. How do I do this?
Looking forward for replies. Thanks!

2

Is this system using UEFI booting? Or is it using legacy MBR booting?

While running the Leap 16.0 on “/dev/nmve0n1p2” you might try:

update-bootloader --reinit

and see if that puts the graphic 16.0 first in boot order.

Run that command as root.

3

Thank You - this worked. Will there then still be two instances of Leap 16.0 installed on /dev/nmve0n1p2 and will it make sense to uninstall/remove the unused instance?

4

You better know that then us, we for sure can not see that :wink:

Can you share the output of lsblk -o +FSTYPE?

Please use the </> to format the command and output of the command.

5

Based on the name, I presume that “/dev/nmve0n1p2” is a single partition. In that case, it likely only has one instance of Leap 16.0 (the most recently installed one). But you might have a “/boot” partition from the other instance, or you might have extraneous files in your EFI partition. The amount of space used is probably small enough that it doesn’t matter.

6 
AME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS            FSTYPE
mmcblk0      179:0    0 116.5G  0 disk                        
|-mmcblk0p1  179:1    0   512M  0 part /boot/efi              vfat
|-mmcblk0p2  179:2    0   114G  0 part /var                   btrfs
|                                      /usr/local             
|                                      /srv                   
|                                      /root                  
|                                      /home                  
|                                      /opt                   
|                                      /boot/grub2/x86_64-efi 
|                                      /boot/grub2/i386-pc    
|                                      /.snapshots            
|                                      /                      
`-mmcblk0p3  179:3    0     2G  0 part [SWAP]                 swap
mmcblk0boot0 179:8    0     4M  1 disk                        
mmcblk0boot1 179:16   0     4M  1 disk

looks like this :wink:

7

Thanks, that looks to me like a ~128 GB phone’s internal memory…

You start post lists /dev/sda1 and /dev/nmve0n1p2 so that does not match. Please find out what is wrong and share the output that includes sda1 and nmve0n1p2