https://bugzilla.novell.com/show_bug.cgi?id=807090 https://bugzilla.novell.com/show_bug.cgi?id=807090#c1 --- Comment #1 from Jon Nelson 2013-03-01 22:05:46 UTC --- I mis-spoke and mis-filed. This is RC2 and the error is: Failure (dbus fatal exception) The y2logs say that the boot device is tmpfs (which it is - this is a rescue environment), perhaps that's a clue. Adding y2log and re-installing. -- 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=807090 https://bugzilla.novell.com/show_bug.cgi?id=807090#c Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Version|RC 1 |RC 2 -- 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=807090 https://bugzilla.novell.com/show_bug.cgi?id=807090#c4 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jnelson-suse@jamponi.net | --- Comment #4 from Jon Nelson 2013-03-04 15:15:51 UTC --- There are a few issues here. 1. Previously, the machine had Fedora 17 on it. It was UEFI booting. 2. For the install, I used PXE boot. Is there a chicken-and-egg situation with pxe booting and efi bootloading? 3. In the bootloader config, I chose grub2-efi. I would have expected it to create the appropriate boot partition or - at least - grump that there wasn't one (and ideally, suggest a modification). 4. I *did* get a GPT partition table. I ended up using the rescue environment (which doesn't have gptfdisk!) to chroot into the install, change the partition type to MBR, and then install grub2 (no efi). Lastly, regarding the ext2 vs. whatever for /boot, I've used ext3 or ext4 on /boot (if I even have a /boot) for the better part of 5 years without issue, but that's not relevant to this issue. In my opinion, the issue here boils down to, mostly, point 2 above. I don't believe that the bug is invalid because the bootloader config should have grumped that a /boot/efi partition was not present. Instead, I got no such warning. Have a nice day! -- 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=807090 https://bugzilla.novell.com/show_bug.cgi?id=807090#c Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|snwint@suse.com |mchang@suse.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=807090 https://bugzilla.novell.com/show_bug.cgi?id=807090#c7 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #7 from Jon Nelson 2013-03-07 16:18:54 UTC --- With all due respect, I believe that there is a bug here, but I'm not suggesting that it's in grub2. My belief is that the issue is in the yast2 interface/installer. If one chooses 'grub2-efi' believing (as I did) that - since this machine has a UEFI BIOS that it should use an EFI bootloader - then *at that time* if the proper partitioning cannot be detected that an error message should be popped up. Ideally, at that time, the partitioner would offer something like "adjust partitioning to add or remove an EFI boot partition" taking the partitioning *as it is* and making some adjustments. Since no error message popped up, I didn't believe that there was an issue. Now I know better, having educated myself on the issue, but please consider the situation where users are not EFI experts. -- 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=807090 https://bugzilla.novell.com/show_bug.cgi?id=807090#c8 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |jnelson-suse@jamponi.net --- Comment #8 from Michael Chang 2013-09-27 09:33:00 UTC --- Jon, If you tweak the default proposed settings then your're expert. ") It seems like your bios supports both UEFI and legacy booting and you configured it as UEFI. The YaST detects it as legacy, did the proposed settings for legacy bios partition layout and bootloader ? Therefore you have to change the partition and bootloader in order to install ? If that's the case, we can try to better detecting on such type of firmware and make right proposal in the first place. -- 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.