[Bug 846748] New: Installed system not recognized, UEFI GTP
https://bugzilla.novell.com/show_bug.cgi?id=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c0 Summary: Installed system not recognized, UEFI GTP Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: u.michel@t-online.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 Newly installed system is not offered in boot menu. This is true for the first restart, as well as for all starts from installation dvd or USB stick. This is true for Sony Vaio Ultrabook SVP132 series. Reproducible: Always Steps to Reproduce: 1. 2. 3. Workaround: Linux can be started by selecting "install" and continue installation until language and keyboard are to be selected. Abort installation at this stage, which returns you to a text console. In a later window you are offered "boot installed system". You have to guess the root partition. Start of system proceeds well after this. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c1 Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |u.michel@t-online.de AssignedTo|bnc-team-screening@forge.pr |snwint@suse.com |ovo.novell.com | --- Comment #1 from Martin Vidner <mvidner@suse.com> 2013-10-22 17:42:06 CEST --- Please attach the YaST logs: 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c2 --- Comment #2 from Ulf Michel <u.michel@t-online.de> 2013-10-31 14:49:30 UTC --- RC2 has the same problem. My installed system is still not recognozed when system is booted with RC2-DVD. Where do I find the requested logs when started with Rescue system? -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c3 Ulf Michel <u.michel@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|RC 1 |RC 2 --- Comment #3 from Ulf Michel <u.michel@t-online.de> 2013-11-04 08:20:18 UTC --- When booting with the 64 bit KDE Live DVD RC2, starting the installed system is offered as option but an attempt to start the installed system results in the message error: file '/EFI/Boot/bootx64.efi' not found. But the file does exist in the EFI partition /dev/sda3 (compare bug 841426, comment 72). Where can I find the error logs in this situation? -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c4 --- Comment #4 from Michael Chang <mchang@suse.com> 2013-11-05 03:55:36 UTC --- Hi Ulf, Would you please dump you UEFI variables via "efibootmgr -v" and your block devices "lsblk --fs". -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c6 Ulf Michel <u.michel@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|u.michel@t-online.de | --- Comment #6 from Ulf Michel <u.michel@t-online.de> 2013-11-07 11:18:25 UTC --- # efibootmgr -v BootNext: 000C BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0005,0008,0009,000C,0001,000A,000D,000B Boot0001* Windows Boot Manager HD(3,363800,82000,674c63b1-dc34-4b86-a233-b397a638f5e0)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a............... Boot0005* Sony Original HD(1,800,82000,b1eeeec6-0c0e-4230-a7e4-762fbc0cc576)File(\EFI\Microsoft\Boot\bootmgfw.efi) Boot0008* Windows Boot Manager HD(5,425800,6ec5000,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot0009* Windows Boot Manager HD(5,425800,1a936800,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000A* Windows Boot Manager HD(5,425800,1bed528f,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000B* Windows Boot Manager HD(5,425800,ea60000,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000C* Windows Boot Manager HD(5,425800,1d8cda8f,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000D* Windows Boot Manager HD(5,425800,18ffeafc,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Please consider that I replaced \EFI\Microsoft\Boot\bootmgfw.efi with bootx64.efi to force the computer to the grub menu. (compare bug 841426) It will only boot Linux, which I do not mind at the moment. # lsblk --fs NAME FSTYPE LABEL UUID MOUNTPOINT sda ├─sda1 vfat SONYSYS F8E1-6DFA ├─sda2 ntfs Windows RE tools FCF6E1DEF6E198E2 ├─sda3 vfat A7F2-5FA8 /boot/efi ├─sda4 ├─sda5 ntfs 108AE3548AE3353E /windows/C ├─sda6 ext4 a24f5609-e9e2-4433-ad42-72fe70bf2c8b / ├─sda7 ext4 e277d18b-8484-4dad-905e-ce1534bfd120 /home └─sda8 swap 88791635-bb38-4789-9e84-a6a54c22eb78 [SWAP] -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c7 --- Comment #7 from Ulf Michel <u.michel@t-online.de> 2013-11-22 21:10:27 UTC --- The error still exists with the released version 13.1 -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c8 Jeffrey Cheung <jcheung@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Version|RC 2 |Final AssignedTo|jcheung@suse.com |mchang@suse.com --- Comment #8 from Jeffrey Cheung <jcheung@suse.com> 2013-11-27 06:36:00 UTC --- Thanks Ulf's info and reassign back to Michael again. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c9 --- Comment #9 from Michael Chang <mchang@suse.com> 2013-11-28 06:43:55 UTC --- (In reply to comment #3)
When booting with the 64 bit KDE Live DVD RC2, starting the installed system is offered as option but an attempt to start the installed system results in the message error: file '/EFI/Boot/bootx64.efi' not found.
But the file does exist in the EFI partition /dev/sda3 (compare bug 841426, comment 72).
Per your efibootmgr -v output firmware is expecting it in /dev/sda5, which is your windows partition currently in use. It looks like it used to be an EFI System Partition ... And there's five duplicated entries .. maybe leftover from production phase of windows preload ?? sda5 ntfs 108AE3548AE3353E /windows/C HD(5,425800,6ec5000,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot0009* Windows Boot Manager HD(5,425800,1a936800,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000A* Windows Boot Manager HD(5,425800,1bed528f,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000B* Windows Boot Manager HD(5,425800,ea60000,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000C* Windows Boot Manager HD(5,425800,1d8cda8f,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) Boot000D* Windows Boot Manager HD(5,425800,18ffeafc,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c10 --- Comment #10 from Michael Chang <mchang@suse.com> 2013-11-28 06:48:09 UTC --- The other two entries are for windows booting. It seems to me that /dev/sda3 is used for booting windows and /dev/sda1 is windows recovery system. There's no openSUSE entry in the list .. Boot0001* Windows Boot Manager HD(3,363800,82000,674c63b1-dc34-4b86-a233-b397a638f5e0)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................ Boot0005* Sony Original HD(1,800,82000,b1eeeec6-0c0e-4230-a7e4-762fbc0cc576)File(\EFI\Microsoft\Boot\bootmgfw.efi) -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c11 --- Comment #11 from Michael Chang <mchang@suse.com> 2013-11-28 07:09:51 UTC --- Try $ efibootmgr -c -d /dev/sda -p 3 -L "openSUSE 13.1" -l "\\EFI\\opensuse\\grub.efi" $ efibootmgr -v If you don't have "openSUSE 13.1" entry created, probably your firmware don't support it. We did have some reports on certain shipped laptop refuses creating boot entry other than MS Windows. Or it could be kernel bugs on manipulating efi runtime variable service, but not look likely to me. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c12 --- Comment #12 from Ulf Michel <u.michel@t-online.de> 2013-11-28 20:12:57 UTC --- I tried what you proposed. The entry was added as Boot000. However, booting from the KDE Live stick was still not possible. After rebooting via grub2 the new entry was gone, as follows. # efibootmgr -v BootNext: 0005 BootCurrent: 0007 Timeout: 0 seconds BootOrder: 0005,0007,0008 Boot0005* Sony Original HD(1,800,82000,b1eeeec6-0c0e-4230-a7e4-762fbc0cc576)File(\EFI\Microsoft\Boot\bootmgfw.efi) Boot0007* Windows Boot Manager HD(3,363800,82000,674c63b1-dc34-4b86-a233-b397a638f5e0)File(\EFI\Microsoft\Boot\bootmgfw.efi) Boot0008* Windows Boot Manager HD(5,425800,e9b1000,7b64ff3b-e062-4b75-aec7-b5f8fa073e88)File(\EFI\Boot\bootx64.efi) I have even deleted all entries except Boot0005 with the effect that the entries Boot0007 and Boot0008 are restored. Boot0008 is probably the result of an interim attempt to solve the boot problem by defining a separate EFI partition for openSUSE. But this did not work and I deleted this partition again for the nth installation of openSUSE on my computer. # lsblk --fs NAME FSTYPE LABEL UUID MOUNTPOINT sda ├─sda1 vfat SONYSYS F8E1-6DFA /sda/sda1 ├─sda2 ntfs Windows RE tools FCF6E1DEF6E198E2 ├─sda3 vfat A7F2-5FA8 /boot/efi ├─sda4 ├─sda5 ntfs E8BEF800BEF7C55A /windows/C ├─sda6 ntfs FEB62D85B62D400F ├─sda7 ext4 b7a91d98-6e5c-47b8-807e-d173bba06789 / ├─sda8 ext4 e277d18b-8484-4dad-905e-ce1534bfd120 /home └─sda9 swap 88791635-bb38-4789-9e84-a6a54c22eb78 [SWAP] The following steps seem to be made on my Sony Vaio SV132A1CM: 1. The program \EFI\Microsoft\Boot\bootmgfw.efi on the SONYSYS partition is started first. 2. It transfers the control to \EFI\Microsoft\Boot\bootmgfw.efi on the EFI partition. The BIOS expects the program bootmgfw.efi to Boot Windows there. The only way to take control of the boot process was in my experience to replace bootmgfw.efi with grubx64.efi and rename it to bootmgfw.efi. This fools the program in SONYSYS. The further procedure is explained in https://bugzilla.novell.com/show_bug.cgi?id=846752#c4 I know that this procedure cannot be used by you. But neverlheless it would be nice to be able to start an installed system from an installation of live system on a USB stick. The procedure to find an installed openSUSE would have to look for /boot/efi/opensuse/grubx64.efi or look for a partition with a /boot/grub2 directory and take the required information from there to start the installed system. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c13 --- Comment #13 from Ulf Michel <u.michel@t-online.de> 2013-11-29 04:47:16 UTC --- I checked the grub.cfg file on my USB stick with the KDE live image. The menu entry for booting from hard disk is menuentry "Boot from Hard Disk" --class opensuse --class os { set root='hd0,1' chainloader /EFI/BOOT/bootx64.efi } but it should read in my case with the efi partition on (hd0,3) menuentry "Boot from Hard Disk" --class opensuse --class os { set root='hd0,3' chainloader /EFI/BOOT/bootx64.efi } an even safer version would be menuentry "Boot from Hard Disk" --class opensuse --class os { set root='hd0,3' chainloader /EFI/opensuse/grubx64.efi } To make the boot from hard disk safe, the actual location of the efi partition would have to be determined before. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c14 --- Comment #14 from Michael Chang <mchang@suse.com> 2013-11-29 06:43:31 UTC --- Maybe "search" could be helpful in this case. There's also some discussion about live USB booting from hard disk in bnc#848902. menuentry "Boot (any) openSUSE" --class opensuse --class os { search --set=root --file /EFI/opensuse/grubx64.efi chainloader /EFI/opensuse/grubx64.efi } -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c15 --- Comment #15 from Michael Chang <mchang@suse.com> 2013-11-29 06:58:39 UTC --- (In reply to comment #12)
I tried what you proposed. The entry was added as Boot000. However, booting from the KDE Live stick was still not possible. After rebooting via grub2 the new entry was gone, as follows.
I suppose you have succeeded it (in comment#13).
I have even deleted all entries except Boot0005 with the effect that the entries Boot0007 and Boot0008 are restored.
My guess for the restoration is necessary for firmware update as boot variables recorded in nvram would be erased. But the implementation is too brute to not care about other boot variables.
Boot0008 is probably the result of an interim attempt to solve the boot problem by defining a separate EFI partition for openSUSE. But this did not work and I deleted this partition again for the nth installation of openSUSE on my computer.
OK. Thanks for clarification. But I do not understand why Boot0008 gets love from restoration but others don't ?
The following steps seem to be made on my Sony Vaio SV132A1CM: 1. The program \EFI\Microsoft\Boot\bootmgfw.efi on the SONYSYS partition is started first.
Yes. It looks like so. As your BootNext: 0005 points to it. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c16 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #16 from Michael Chang <mchang@suse.com> 2013-12-02 08:37:25 UTC --- Hi Ulf, I close this one as it's the UEFI firmware not allowing new boot entries established and we can do little for it. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c17 --- Comment #17 from Ulf Michel <u.michel@t-online.de> 2013-12-03 03:53:10 UTC --- I disagree. I have shown in comment 13 that grub.cfg on the KDE Live iso image (and probably also on all the other distributed iso images) has an entry that will only work if the EFI partition is (hd0,1) and will fail for any other partition. This has nothing to do with UEFI firmware. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c18 --- Comment #18 from Michael Chang <mchang@suse.com> 2013-12-03 04:18:11 UTC --- Hi Ulf, comment#13 is the problem we're dealing in bnc#848902. (or should we dup this one to that) ? The original problem (comment#1) is caused by the firmware, that's why I set this one closed. -- 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=846748 https://bugzilla.novell.com/show_bug.cgi?id=846748#c19 --- Comment #19 from Ulf Michel <u.michel@t-online.de> 2013-12-03 04:30:14 UTC --- Agreed -- 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.
participants (1)
-
bugzilla_noreply＠novell.com