http://bugzilla.suse.com/show_bug.cgi?id=957786 Bug ID: 957786 Summary: Boot partition on "gpt_sync_mbr" with "legacy_boot" flag results in "Invalid Partitiontable !" on Dell T5810 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: svollath@suse.com QA Contact: jsrain@suse.com CC: duwe@suse.com, rw@suse.com, snwint@suse.com Found By: --- Blocker: --- Created attachment 658244 --> http://bugzilla.suse.com/attachment.cgi?id=658244&action=edit yast logs I installed Leap to my workstation (Dell Precision Tower 5810). The BIOS (latest version, A09) is set to Legacy Boot Mode. I reused the existing partition table (gpt_sync_mbr), but removed former partitions, and newly added a boot and root partition (ext4). With these settings the disk was configured like this: Number Start End Size File system Name Flags 1 1049kB 272MB 271MB ext4 primary legacy_boot 2 272MB 27.1GB 26.8GB ext4 primary This resulted in the following behaviour: On reboot, system gets reproducibly stuck with the "Invalid Partitiontable !" Error. However, if one hits "Return", it will boot into grub2, and into the system afterwards. It turned out, that the DELL bios is just missing a normal "boot" flag (btw. doesn't matter on which partiotion on that disk). The following disk configuration boots flawlessly: Number Start End Size File system Name Flags 1 1049kB 272MB 271MB ext4 primary boot, legacy_boot 2 272MB 27.1GB 26.8GB ext4 primary So we should set "boot" flag (at least in addition), if there's no reason to set "legacy_boot" (only) in this case. -- You are receiving this mail because: You are on the CC list for the bug.