Installation on GPT partitioned Harddisk

I´m always failing on Installation of Leap 15.3 on GPT-partitioned Harddisks. I tried several Desktops and Laptops with different BIOS. Tumbleweed is no Problem…but Leap 15.3.

The Scenario was that Win 10 decided that it is Time to Update to 11 and… Blackscrean, horrible Action. Switching the extra harddisk for LINUX from MBR to GPT fixed Windows, but the Installtion
of LEAP 15.3 is not possible anymore. It just ignores the fresh partitioned Harddisk. Even if it is RAW or formatted…too poor, because, as I wrote: Tumbleweed is working.

This post is more a message to SuSE…

But not a useful message. You have not provided any details or even any hints as to what goes wrong. I have not had any problems installing Leap 15.3 to a GPT partitioned disk.

And what is more, you do not need any partitioning on a disk to install to it. The partitioning is done during installation. Partitioning the disk and creating file systems on it are the first things the installer does when it really starts the installation.

In fact having pre-partitioned a disk is a draw-back. because the installer will then see partitions when it looks for free space. And you then have explicitly to tell that those partitions should be deleted, or used for certain purposes at installation.

Same here. Just did it a few days ago, no issues. But, is this actually a UEFI issue? Are you matching the UEFI install with a UEFI BIOS, or Legacy with Legacy, or do you know? I also agree with Henk: If you have no special reason to, then don’t bother making partitions. You can do all that during install.

well, may be I am the most stupid fool (workling with SuSE since 15 years)

Facts Booting with an Installation Image of “Tumbleweed” every Harddisk of the Computer is found! Only Leap 15.3 Installation tells me, that there is not enough Diskspace for an Installation. It shows just the space of that USB-Stick, I bootet from! not even found one Harddisk to be partitioned for Installation.

I really have no Idea, but asiking SuSE

My best guess is that this is a kernel issue. The newer Tumbleweed kernel recognizes your disk devices, while the Leap kernel doesn’t.

The simplest solution would be to go with Tumbleweed for now. Leap would probably work with a newer kernel, but you are stuck with the kernel that is on the install media.

You could maybe try the Leap live media:

https://download.opensuse.org/distribution/leap/15.3/live/openSUSE-Leap-15.3-KDE-Live-x86_64-Build9.258-Media.iso

That will have a newer kernel than DVD installer. If that can see your disks, then using it to install might get you going with Leap.

How many operating system is currently running in that machine right now?

That shouldn’t make a difference if using GPT and there is still unallocated disk space. But, even if there is no unallocated disk space, the installer should show all partitions and make a suggestion.

It is possible to update Leap installer to force it to use newer kernel.

I wouldn’t take things that way. In my mind, there is no such thing as that on this forum, all questions are valid, and not knowing your experience, but knowing the PITA that many of the different BIOSes are with their handling of UEFI, I thought it might be a suggestion.

Message to thirty: https://forums.opensuse.org/showthread.php/554703-Testing-a-new-distribution-The-same-procedure-as-everytime