[sle-beta] Installing RC1 on VM with beta4 partitions: missing bios_boot partition
jlopez at suse.com
Thu Mar 15 02:52:23 MDT 2018
Partitioner in RC1 comes equipped with sanity checks for the
partitioning layout. Before accepting all changes you have done in the
Partitioner, warning/error messages could be shown to indicate what is
wrong in your configuration. In your case, you are getting a warning due
to missing BIOS BOOT partition. Partitioner considers a BIOS BOOT
partition as needed when the BIOS is working on Legacy mode (not UEFI)
and the boot disk is partitioned using a GPT partition table. In that
scenario, you get the BIOS BOOT warning message if there is not a BIOS
BOOT partition with at least 2 MiB of total size. In the case of a
missing BIOS BOOT, the message is only a warning and you can continue
with the installation if you are sure.
Are you testing with a different scenario? In that case, please, report
a bug with corresponding y2log to debug what is happening.
With regard to the resizing error, I am afraid we need a bug report with
> On 12 Mar 2018, at 20:26, Johannes Kastl <kastl at b1-systems.de> wrote:
> Hi all,
> I installed RC1 over the beta4 installed in my Test-VM, just keeping the
> partitions created during installation of Beta4. Formatting / and swap,
> and just keeping /home brings up an error that the bios_boot partition
> is missing.
The yast partitioner and especially libstorage-ng have received a lot of
and enhancement since Beta4 (cf. Highlights of YaST Development Sprint#).
So I would suggest to remove the beta4 existing partitions completely or
your test on a SLE12SP3 migration with a similar partition layout.
> Indeed I have a small 1MB partition in between, no idea if this is
> really used. But I have no bios_boot partition.
> I forced the installer to continue, and everything seems to work.
> Machine boots.
> I'll try to set the machine back to an earlier snapshot and redo the
> Known issue? Worth a bug report?
The only thing similar to your issue that I was able to find is:
bsc#1082349, specially comment#5:
Please note that this is a openSUSE Leap 15 Beta bug.
If you happen to be able to reproduce this issue (without the beta 4 legacy
setup), please create a new SLES 15 bug report.
> Kind Regards,
> Trying to resize the partitions I triggered an error in Yast, asking me
> to start the ruby debugger. I need to look into that and try to
> reproduce it.
Same advice: I would suggest to remove the beta4 existing partitions
or base your test on a SLE12SP3 migration with a similar partition layout.
SUSE Beta Program and SDK Project Manager
More information about the sle-beta