Keep existing Win10 in dualboot installation with Leap 42.3

English Install/Boot/Login
1

I had a dual boot setup with 42.3 and Tumbleweed installed on my newest workstation with SSD (and legacy sata and scsi discs) using Grub2. Would then add Win10 on some free, pre-formatted disc slices with ntfs, but Win10 would not install on any of them due to not being “GPT discs” or being lesser than the recommended 52.5 GB size (?).

At last I tried what I think I read in the past that Windows needs to be installed first, and second the Linux installation and boot loader would then customize itself for a dualboot setup with Windows.I had to delete the leap root partition on the SSD and extend it to a 60 GB partition before Win10 installtion accepted it. But I kept my ext4 Leap /home partition and data partitions on other discs, with plan to re-mount them again later during a re-installation of Leap.

What surprise me now is that a test to re-install Leap from DVD, just suggest to delete the Windows installation, and slice up and format the SSD with new partitions and file systems UEFI included for leap. Previous I have always been able to select the Expert Partioner and imported exising mount points. But now the Leap installation does not discover the preserved ext4 partition for /home or keep the Wind10 partition as is…? Possibly I have happened to miss the old partion table(?)
If I try to install Leap root on another disc, the installation warns there will be serious problem to boot it later.

I need a help procedure to solve this issue.

(just to mentione that I have a functional dualboot Win10/Leap42.2 (also upgraded to 42.3 now) setup that I previous succeeded to install on an older laptop using grub2)

Thx Terje

2

You either need to leave free space to install to or tell it which partition to install to and also set which is to be home. It really can’t guess what you want you must tell it. The installer would not recognize just a home partition as such it is just data to it (ie no Linux kernel you blew it away) and thus you need to tell it where it is to be mounted ie /home and not formatted.

If EFI be sure to boot the installer in EFI mode. It should see and use any existing EFI boot partitions. If not be sure that the partition is mounted as /boot/efi. Also be sure that grub2-efi and not grub2 is set to be boot manager. Should be the default if you booted the installer in EFI mode. All OS must use the same boot method for them to work together.

If installing system to an existing partition it should be mounted as / and formatted using your chosen file system.