[Bug 818871] New: os-prober not working in a EFI System
https://bugzilla.novell.com/show_bug.cgi?id=818871 https://bugzilla.novell.com/show_bug.cgi?id=818871#c0 Summary: os-prober not working in a EFI System Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: gjn@gjn.priv.at QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=538278) --> (http://bugzilla.novell.com/attachment.cgi?id=538278) The debug log from os-prober User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 On my Systems os-prober is not working in a efi System. os-prober don't found the installed openSUSE 12.3 and also not found the Windows system. I have installed the debug Packages and attachment the debug log Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
FeiXiang Zhang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c1
--- Comment #1 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c2
--- Comment #2 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c3
--- Comment #3 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c4
--- Comment #4 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c5
Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c6
Michael Chang
A Question why it is not possible to Install openSUSE in the existing Windows EFI directory? I have to make a extra Partition for Boot/EFI then it is working.
Because your Windows EFI directory is RAIDed, and as far as I know the EFI System Partition cannot be RAIDed because firmware cannot recognize RAID partition type and cannot handle meta data etc .. I don't know, probably your firmware can do it, but not mean every other firmware can do it as well. The installer don't think that the RAID partition can be a ESP thus proposed new one for installing openSUSE. -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c7
--- Comment #7 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c8
--- Comment #8 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c9
Andrey Borzenkov
Because your Windows EFI directory is RAIDed, and as far as I know the EFI System Partition cannot be RAIDed because firmware cannot recognize RAID partition type and cannot handle meta data etc ..
Well ... ESP can be on any device that is supported by firmware and we likely have software RAID here; it is supported by BIOS and I do not see why it cannot be supported by EFI firmware. @Günther: could you please show cat /proc/mdstat also could you try mv /usr/sbin/efibootmgr /usr/sbin/efibootmgr.orig grub2-install --debug --efi-directory=/windows/efi mv /usr/sbin/efibootmgr.oirg /usr/sbin/efibootmgr and post full output of grub2-install. Also it would be useful to know what grub sees. On grub2 menu press 'c' (single character), issue command 'ls -l' and make a picture of the screen. If output is very long, use "set pager=1" and repeat, making picture of each screen. Attach pictures here. -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c10
--- Comment #10 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c11
Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c12
Andrey Borzenkov
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c13
Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c14
--- Comment #14 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c15
--- Comment #15 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c16
--- Comment #16 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c17
Andrey Borzenkov
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
Andrey Borzenkov
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c18
Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c19
--- Comment #19 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c20
Andrey Borzenkov
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c21
Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c22
--- Comment #22 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c23
--- Comment #23 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c24
--- Comment #24 from Andrey Borzenkov
Windows is booting, with the new os-prober entry in the grub.cfg.
Could you make one more test. Record current boot configuration efibootmgr -v Edit /etc/default/grub and temporary change GRUB_DISTRIBUTOR so as to not overwrite boot entry, like GRUB_DISTRIBUTOR="test_bnc818871" Then mount your Windows ESP as /boot/efi umount /windows/efi umount /boot/efi mount /dev/md126p1 /boot/efi And run update-bootloader --refresh If there is no error, you should now have firmware boot menu entry with name that corresponds to GRUB_DISTRIBUTOR and it will be set as default; try to boot it if it works. If there is error, please attach /var/log/YaST2/perl-BL-standalone-log and /var/log/YaST2/y2log_bootloader. You can then change back mount points and GRUB_DISTRIBUTOR and simply run update-bootloader --refresh again to reset boot configuration to use openSUSE as default. -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c25
--- Comment #25 from Andrey Borzenkov
after this I have to wait near 1,5min for the rest (?) Is this "normal".
I really do not know. Attach os-prober debug output as usual, we'll try to see. -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c26
--- Comment #26 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c27
--- Comment #27 from Andrey Borzenkov
OK, I mean this is working now ;). Did you use update-bootloader to refresh configuration?
The only small Problem is, it is very slow :(.
Please attach new log of os-propber invocation; there is no way to guess. -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c28
--- Comment #28 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c29
--- Comment #29 from Andrey Borzenkov
and here is the latest Debug Log from the os-prober
The delay is in detecting Linux: 14:35:20.830593+02:00 techz 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro 14:37:36.425058+02:00 techz 90linux-distro: result: /dev/sde3:Fedora release 19 (Schrödinger’s Cat):Fedora:linux I do not see how my patch can affect it. Do you say that version that comes with 12.3 does not have this delay? Could you revert to original package and verify? -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c30
--- Comment #30 from Günther J. Niederwimmer
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c31
--- Comment #31 from Andrey Borzenkov
OK, you are right, the "original" is also extreme slow.
Fine, feel free to open separate bug report for it. @Michael (In reply to comment #6)
I don't know, probably your firmware can do it, but not mean every other firmware can do it as well. The installer don't think that the RAID partition can be a ESP thus proposed new one for installing openSUSE.
I think it is pretty safe to assume that "hardware" Intel RAID should be supported by firmware. GRUB2 itself accepts it as valid device (it has explicit checks for IMSM); as have seen, grub2 + pbl work just fine (pbl may need some work for BIOS case though). Would you open feature request so it is not forgotten? -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c32
--- Comment #32 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c33
--- Comment #33 from Andrey Borzenkov
1. hardware raid: ESP on hardware raid is supported by firmware. Grub2 can also consider it as supported as they appear as regular block deviced.
Yes, This case just works and there is nothing that needs to be done here.
2. firmware/fake raid: Safe to say that booting ESP from it is supported, as the two major (external) metadata format (DDF and IMSM) are supported by bootloader (grub2) and kernel (mdadm, dmraid ..). Another quick question is "does it safe to say all offered raid level" ?
I explicitly speak only about IMSM here. The reason is, mdadm won't let you create IMSM unless you have the right hardware (I did not look how it checks for it) but it will allow you to create pure software DDF array (which I use to test MD things). So if we ever need to support DDF fake raid, this probably will need to be on case by case basis and use white lists. And grub2 contains checks for IMSM only. It should be safe for any RAID level supported by underlying controller. At the time of booting it is single device anyway.
3. software raid: ESP on user created (pure) software raid is not supported, as we assume that firmware has no knowledge about metadata created by mdadm's or other means (could apply to other stuffs like lvm or btrfs).
That's true, but we still need to support /boot on MD raid, there are plenty of users who request it. This probably goes together with /boot on LVM as implementation from grub PoV is identical. Returning to this case - os-prober support in this case looks useful irrespectively; should I submit maintenance request? -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c34
--- Comment #34 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c35
--- Comment #35 from Michael Chang
That's true, but we still need to support /boot on MD raid, there are plenty of users who request it. This probably goes together with /boot on LVM as implementation from grub PoV is identical.
Fully agree, I think it will be improved in future yast (now ruby .. whatever .) This is a good reason why jump in grub2 boat, it offers rich and identical features across firmware and architectures. :)
Returning to this case - os-prober support in this case looks useful irrespectively; should I submit maintenance request?
The maintenance request is always welcome. -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c36
--- Comment #36 from Andrey Borzenkov
The fate is filed.
Let's move any related discussion to the fate. :)
I do not have access to 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c37
Andrey Borzenkov
The maintenance request is always welcome.
MR#196125 -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c38
--- Comment #38 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c39
--- Comment #39 from Michael Chang
I do not have access to this :(
Please try this one, thanks. https://features.opensuse.org/316449 -- 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=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c40
--- Comment #40 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c41
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c42
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c43
--- Comment #43 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com