http://bugzilla.suse.com/show_bug.cgi?id=953007 http://bugzilla.suse.com/show_bug.cgi?id=953007#c8 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal --- Comment #8 from Stefan Hundhammer <shundhammer@suse.com> --- Now my (as of yet unconfirmed) impression is that there was a small amount of unused space on that disk /dev/sdb, the YaST storage proposal found it and wanted to put it to good use, but it was too small for 'parted' to handle it in that context. It might have been an alignment problem. As bad as that sounds, I am not sure if there is a 100% proof way to fix this kind of situation. Alignment can be tricky, and we only can make an educated guess what 'parted' will do; it might or might not behave exactly as we think in every given case. One workaround in this special case would be to not use an LVM based proposal and just use /dev/sdb2 as a plain partition; this would avoid automatically adding /dev/sdb8 to that logical volume. Another workaround would be to use the expert partitioner to modify that proposal and to remove /dev/sdb8 from the logical volume and from the partition list (i.e. it doesn't get created in the first place). Downgrading this to a normal bug; this is not a common problem affecting a large number of users. -- You are receiving this mail because: You are on the CC list for the bug.