Bug 934309

Summary: Installer sets "/boot" as EFI partition (formatted "ext2") - snapshot 20150608
Product: [openSUSE] openSUSE Tumbleweed Reporter: Neil Rickert <nwr10cst-oslnx>
Component: InstallationAssignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: aschnell, jreidinger
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Yast logs (compressed tar of /var/log/YaST2)

Description Neil Rickert 2015-06-11 01:57:11 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) rekonq/2.4.2 Safari/537.21
Build Identifier: 

I did a clean install to an external drive, using snapshot 20150608 (DVD installer written to a USB).

Before I started the install, I prepared the disk.  I partitioned with GPT.  Then I created a partition for "/boot" (ext2), and most of the 80G disk to an encrypted LVM.

Note that this is a legacy BIOS computer.  There is no UEFI support.

After starting install, I provided the encryption key as requested.

In the partitioning section, I chose "create partitioning" followed by "custom partitioning", then set the partition as I wanted them.

I later looked at the boot settings.  The installer wanted to install grub2 to "/boot", and wanted to install generic boot code in the MBR.  It also wanted to flag the boot partition as active (probably where it went wrong).

This all looked fine.  I made a couple of changes (changed the menu timeout, and turned of probing other operating systems).

The install itself seemed to go well.

Reboot into the system also seemed okay (telling the BIOS to boot the USB drive).

While running the newly installed system, I checked "/boot" to see what it had done by way of setting the active flag on a GPT drive.

I was surprised to see that "/dev/sdb2" was listed as an EFI partition, though it had been formatted as "ext2".  "parted" showed that partition as having the boot flag, the legacy boot flag, and EFI.  I think it should have only the legacy boot flag.

Note that the system continued to boot without a problem, in spite of this.  However, I then used "gdisk" to change it back to a linux partition instead of an EFI partition.  That removed the boot flag and the efi flag.  It still booted after those changes.

I will attach yast logs shortly.

Since the system still worked, this is a minor problem.  But I suspect that this could lead to future problems and confusion.

Reproducible: Didn't try
Comment 1 Neil Rickert 2015-06-11 01:58:47 UTC
Created attachment 637414 [details]
Yast logs (compressed tar of /var/log/YaST2)
Comment 2 Josef Reidinger 2015-06-18 12:34:04 UTC
Thanks for report. It already exists bug report for it, that yast2 bootloader set too much flags and should respect different types of partition tables.

*** This bug has been marked as a duplicate of bug 930903 ***