This bug report also applies to Leap 15.4 and Tumbleweed.
I have an HP Spectre x360 Convertible 15t-eb000 laptop with Windows 10 already
installed on it. I want to make this into a dual boot system with OpenSuSE as
the second OS. When I tried to use the OpenSuSE installations for a USB stick I
run into a serious problem when the installation process reaches the point
where it wants to set up partitions on the disks. (My laptop has a 1TB Optane
SSD drive with 32Gb Optane memory which is some sort of very fast cache.) At
this point I get the following error messages -
"An error was found in one of the devices in the system. The information
displayed may not be accurate and the installation may fail if you
continue."
The "Details..." button shows - "cannot delete MdContainer"
I can only choose "OK" to dismiss this error message. The partitioner only
shows two disks, one for the large SSD drive and one for the smaller Optane
memory. No partitions within these drives are shown and any attempt to add or
modify the drives results in an error message saying the device is busy. At
this point the attempts to install Leap 15.3, Leap 15.4, and Tumbleweed fail
and I have to give up.
The Windows 10 partitioner shows the following partitions -
E: 260 MB (EFI System Partition)
515 MB (Recovery Partition)
C: 171.84 GB (Windows NTFS)
781.25 GB Unallocated
Total: 953.85 GB
You can follow a discussion about this problem on the two OpenSuSE mail lists,
one for users with a thread titled "Troubles installing OpenSuSE 15.3 on a HP
Spectre laptop"
https://lists.opensuse.org/archives/list/users@lists.opensuse.org/thread/D3F4YSV6ARHNEVSMU6AE77JTYPB4XTR4/
The other thread is on the factory mail list with a thread titled "Troubles
installing OpenSUSE 15.3 on a HP Spectre laptop - Intel Optane memory"
https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/XWU4RH6JWKZCBQZBNWQROGVKMD6BLFDF/
I created a Live CD for Leap 15.3 and with it I was able to get the information
about what fdisk -l shows:
localhost:/home/linux # fdisk -l
Disk /dev/loop0: 821.1 MiB, 860946432 bytes, 1681536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 4.5 GiB, 4818206720 bytes, 9410560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
The backup GPT table is not on the end of the device. This problem will
be corrected by write.
Disk /dev/nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: INTEL HBRPEKNX0203AH
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B32172FB-2CEE-4E2C-B94B-46DAABE35591
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 360937471 360370176 171.9G Microsoft basic data
/dev/nvme0n1p4 1999337472 2000392191 1054720 515M Windows recovery
environment
Disk /dev/nvme1n1: 27.3 GiB, 29260513280 bytes, 57149440 sectors
Disk model: INTEL HBRPEKNX0203AHO
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sda: 57.8 GiB, 62026416128 bytes, 121145344 sectors
Disk model: USB 3.1 FD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf727289d
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 1886035 1885972 920.9M cd unknown
/dev/sda2 1886036 1916755 30720 15M ef EFI (FAT-12/16/32)
/dev/sda3 1916928 121145343 119228416 56.9G 83 Linux
But any attempt to modify or add new partitions, with the Live USB stick, only
gets my hands slapped with the error message saying the device is busy, and I
am not allowed to make any changes.
I am attaching some additional log files to help show what is going on during
the installation process. Also I am attaching the output from mdadm --examine
/dev/nvme0n1 while using a Tumbleweed Live USB stick.