https://bugzilla.novell.com/show_bug.cgi?id=847510 https://bugzilla.novell.com/show_bug.cgi?id=847510#c Xiyuan Liu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847510 https://bugzilla.novell.com/show_bug.cgi?id=847510#c3 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #3 from Neil Rickert 2014-01-31 00:21:32 UTC --- I cannot imagine that this is actually a bug. Rather, it seems like expected behavior for MBR booting to require MBR partitioning. As far as I know, to use MBR booting with GPT partitioning, either: (a) you must create a BIOS boot partition (type flag "ef02"), typically located in sectors 34-2047, and install grub2 into the MBR, or: (b) you must setup hybrid partitioning, where the boot partition is correctly defined in both the MBR and the GPT partition tables. I know that (a) works, because I have that working on an external drive. I have not tested (b). You can create the BIOS boot partition with "gdisk". And you should be able to setup hybrid partitioning with "gdisk", though you will probably be warned that it is a bad idea. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847510 https://bugzilla.novell.com/show_bug.cgi?id=847510#c5 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |aschnell@suse.com InfoProvider| |froh@suse.com --- Comment #5 from Arvin Schnell 2014-03-17 16:26:09 UTC --- Please provide YaST logs of installation that did not boot, see http://en.opensuse.org/openSUSE:Bugreport_YaST. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847510 https://bugzilla.novell.com/show_bug.cgi?id=847510#c6 Susanne Oberhauser changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|froh@suse.com | --- Comment #6 from Susanne Oberhauser 2014-03-20 09:21:51 UTC --- (In reply to comment #3)

I cannot imagine that this is actually a bug. Rather, it seems like expected behavior for MBR booting to require MBR partitioning.

As far as I know, to use MBR booting with GPT partitioning, either:

(a) you must create a BIOS boot partition (type flag "ef02"), typically located in sectors 34-2047, and install grub2 into the MBR, or:

(b) you must setup hybrid partitioning, where the boot partition is correctly defined in both the MBR and the GPT partition tables.

I know that (a) works, because I have that working on an external drive. I have not tested (b). You can create the BIOS boot partition with "gdisk". And you should be able to setup hybrid partitioning with "gdisk", though you will probably be warned that it is a bad idea.

this information is neither used automatically nor displayed in the case of creating a GPT partitioned disk on an MBR booted machine. So in this case "SUSE makes the machine unusable" automatically. (In reply to comment #5)

Please provide YaST logs of installation that did not boot, see http://en.opensuse.org/openSUSE:Bugreport_YaST.

I'm sorry I don't have the logs any more, it's a bit too long ago. But I wonder if we need the logs to create that logic: - machine is booted using MBR, not UEFI - user requests GPT aprtitooning or disk is GPT partitioned --> GPT disk needs to be made bootable via MBR, variant a) or variant b) above -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.