http://bugzilla.suse.com/show_bug.cgi?id=1056970 http://bugzilla.suse.com/show_bug.cgi?id=1056970#c2 José Iván López González <jlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez@suse.com, | |taltamirh@gmail.com Flags| |needinfo?(taltamirh@gmail.c | |om) --- Comment #2 from José Iván López González <jlopez@suse.com> --- (In reply to Tal Tamir from comment #1)

To clarify a point. in all cases (both working and the bug), it deletes the original partitions on the drive (as it should, since you select "use whole disk").

The unused space is left unallocated. it does not contain any previous OS.

Do you actually mean unallocated space or not still assigned to a LVM LV? In the case of LVM, not used space is assigned to the VG, that is, you should have obtained an unique partition (Physical Volume) with all the disk space. For a 80 GiB disk the expected layout should be: With LVM + Separate home LVM VG: 80 GiB LVM LV root: 31 GiB LVM LV home: 47 GiB LVM LV swap: 2 GiB With LVM LVM VG: 80 GiB (38 GiB unassigned) LVM LV root: 40 GiB LVM LV swap: 2 GiB With Partitions root: 31GiB home: 47GiB swap: 2GiB As you can see, when using LVM, it tends to leave unassigned space, but that space belongs to the VG, so you could increase the size of your LVs or create new ones. Anyway, we are redesigning the storage stack, so this behavior is being revised. You can find more info here: https://github.com/yast/yast-storage-ng/blob/master/doc/old_and_new_proposal... And to be sure any error is happening, could you please attach the logs? Here you have a guide to obtain it: https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Attachments_-_y2logs.2C_h.... -- You are receiving this mail because: You are on the CC list for the bug.