http://bugzilla.opensuse.org/show_bug.cgi?id=1087918 Bug ID: 1087918 Summary: Problems with partitioner of installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: zhx@cnzhx.net QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 765803 --> http://bugzilla.opensuse.org/attachment.cgi?id=765803&action=edit Log of YaST2 from save_y2logs Short description of the problems: 1. Leap 15 installer cannot use un-allocated disk space for installation of Leap 15 Beta build 182.1 2. Leap 15 proposed to delete Windows 7 recovery partition when preparing the installation partition scheme 3. When Expert mode is used to build custom partition scheme, the resulted subvolumes of BtrFS system for the root (/) partition are not leaded by "@" but instead by "/", which is not like the ones in the automatically proposed layout. At the same time, manually add "@" subvolume or use "@" as leading when manually edit the subvolumes is not possible. In my opinion, problem 1 causes inconvenience but is acceptable; problem 2 is dangerous to user's asset; problem 3 is a new thing to me but I think the layout should be consistent between different partition schemes because the subvolume layout is for root(/). I saved y2logs from the installed Leap 15. But to be noted, I only upload the YaST2 folder because I had a quick look and found this is the relevant part and other parts contain information of system user creation. Also, it may contain log from 1 - 2 times of update/upgrade of system. If full log from save_y2logs is required, I could upload it on request. In detail: ========== I tried to install Leap 15.0 Build 182.1 from scratch in parallel to existing Windows Vista and Windows 7 OSes on an old laptop. The partition layout looks like this in Linux fdisk format (Edited from fdisk output after installation of Leap 15; so, please focus only on the layout; "--> xxxx" is my comment): ``` Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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 Disklabel type: dos Disk identifier: 0xdff8c95f Device Boot Start End Sectors Size Id Type /dev/sda1 2048 3074047 3072000 1.5G 27 Hidden NTFS WinRE /dev/sda2 * 3074088 107940734 104866647 50G 7 HPFS/NTFS/exFAT --> Windows Vista /dev/sda3 107940735 477724904 369784170 176.3G 5 Extended /dev/sda4 477736960 488396799 10659840 5.1G 17 Hidden HPFS/NTFS --> Windows Recovery Partition /dev/sda5 107940800 226050614 118109815 56.3G 7 HPFS/NTFS/exFAT --> Windows 7 /dev/sda6 226050680 393817409 167766730 80G 7 HPFS/NTFS/exFAT --> NTFS data partition for Windows OSes /dev/sda7 393818112 435761151 41943040 20G 83 Linux /dev/sda8 435763200 469317631 33554432 16G 83 Linux /dev/sda9 469319680 477724904 8405225 4G 82 Linux swap / Solaris Partition table entries are not in disk order. ``` (sda7-9 are split from sda6 which is about 120GB for installation of Leap 15.) Problem 1: Cannot use un-allocated space for installation. ---------- Prior to the installation, I resized the existing partition (sda6) to leave about 40GB space un-allocated (it might not lie at the end of the sectors). During the installation, YaST do not let me to create new partition with the unallocated space. (Maybe, to create a new Table could work around this, but I do not know for sure.) Unfortunately, I have not kept the y2logs. Problem 2: ---------- Then, I rebooted into Windows, created a new partitionwith the un-allocated space (40GB) and tried to install again. This time, the proposed partition scheme included deletion of a hidden (in Windows) partition (sda4) which is the rescue or recovery partition or something like that created by laptop manufacturer. Problem 3: ---------- So, I cannot use the proposed partition scheme in fear of loosing the Recovery partition. The proposed partition has a subvolume layout like this, ``` @ @/var (no Copy on Write) @/usr/local @/tmp @/srv @/opt @/boot/grub2/x86_64-efi @/boot/grub2/i386-pc ``` I have to create a new partition scheme using Expert mode based on existing partitions. Delete the empty partition (40GB), create partitions /, /home, /swap on it. Then the summary of partitions shows a different layout of subvolumes, ``` @ /var (no Copy on Write) /usr/local /tmp /srv /opt /boot/grub2/x86_64-efi /boot/grub2/i386-pc ``` Hopefully the Y2Partitioner could be improved for robust and friendly to end-user. -- You are receiving this mail because: You are on the CC list for the bug.