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.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
Günther J. Niederwimmer gjn@gjn.priv.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |gjn@gjn.priv.at Severity|Normal |Critical
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
FeiXiang Zhang fxzhang@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mchang@suse.com |ovo.novell.com |
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c1
--- Comment #1 from Michael Chang mchang@suse.com 2013-05-08 04:33:00 UTC --- Hi Gunther,
Per your log I have no idea where is Efi System Partition (suppose it's /dev/md126p1 and if that's true it's my first time heard of ESP on a raid partition, I have no hardware could test fake raid and efi though), could you please help to attach following output of command ?
$ grub2-probe -t device /boot/efi $ grub2-probe -t abstraction /boot/efi $ grub2-probe -t drive /boot/efi $ find /boot/efi
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c2
--- Comment #2 from Michael Chang mchang@suse.com 2013-05-08 04:38:31 UTC --- If /dev/md126p1 is ESP, the log says pretty much why it's not probed.
2013-05-07T17:39:00.154072+02:00 techz os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/md126p1 2013-05-07T17:39:00.245155+02:00 techz 50mounted-tests: debug: mounted using GRUB 2013-05-07T17:39:00.246082+02:00 techz 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/05efi 2013-05-07T17:39:00.250464+02:00 techz 05efi: debug: /dev/md126p1 is a FUSE partition 2013-05-07T17:39:00.253251+02:00 techz 05efi: debug: /dev/md126p1 is virtual device: exiting
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 gjn@gjn.priv.at 2013-05-08 09:47:52 UTC --- Hello Michael,
I am not a professional, mean you the "mounted"
I tested this with mounted and unmounted Partitions
I tell you my Partitioning
Soft Raid1 (ICH10)
/md125p1 /EFI/Microsoft /md125p2 "Windos7 Special Partition" /md125p3 /windows/C ....
SSD /dev/sde1 /boot/efi
techz:~ # grub2-probe -t device /boot/efi /dev/sde1
techz:~ # grub2-probe -t abstraction /boot/efi
techz:~ # grub2-probe -t drive /boot/efi (hostdisk//dev/sde,gpt1)
techz:~ # find /boot/efi /boot/efi /boot/efi/EFI /boot/efi/EFI/opensuse /boot/efi/EFI/opensuse/grubx64.efi
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c4
--- Comment #4 from Michael Chang mchang@suse.com 2013-08-14 04:49:31 UTC --- Gunther,
Sorry somehow I missed your reply. Your 'find /boot/efi' only lists openSUSE loader that means only openSUSE loader can be found in EFI Sysetm Partition, the os-prober result seems to be correct.
My question is where's your Windows loader and how you boot your Windows system ? `efibootmgr -v` output would be helpful.
And I'm really curious what this is ?
/md125p1 /EFI/Microsoft
Can you list the files in "/EFI/Microsoft"? I have to confirm that your ESP is configured as software RAID1 and bootable by firmware, which is quite fresh news to me. (And of course this is a setup we may have to put into consideration afterward. )
Thanks.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
Michael Chang mchang@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c5
Günther J. Niederwimmer gjn@gjn.priv.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at |
--- Comment #5 from Günther J. Niederwimmer gjn@gjn.priv.at 2013-08-14 09:11:37 UTC --- Hi Michael,
this are the Mountpoints,
techz:~ # df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 12347108 48 12347060 1% /dev tmpfs 12363996 84 12363912 1% /dev/shm tmpfs 12363996 7216 12356780 1% /run /dev/sde2 113562624 17757312 94230792 16% / tmpfs 12363996 0 12363996 0% /sys/fs/cgroup /dev/sde1 173402 9685 163718 6% /boot/efi tmpfs 12363996 7216 12356780 1% /var/lock tmpfs 12363996 7216 12356780 1% /var/run /dev/md126p1 98304 18339 79965 19% /windows/efi /dev/sdd2 303444352 94209468 193820820 33% /data1 /dev/sdc1 307665016 96776704 195259820 34% /data /dev/md126p3 102414332 84395776 18018556 83% /windows/C /dev/md126p5 21503996 88468 21415528 1% /windows/E /dev/md126p4 82941948 12431888 70510060 15% /windows/D /dev/md126p6 54245500 1905656 52339844 4% /home luise:/data 75345920 41772032 29747200 59% /datal luise:/data1 976283648 21275648 955008000 3% /data1l
the /windows/efi is only mounted to find out the Parameter for grub2.
techz:~ # efibootmgr -v BootCurrent: 0001 Timeout: 2 seconds BootOrder: 0001,0000 Boot0000* Windows Boot Manager HD(1,800,32000,c90a8ca7-cbde-42dd-bed5-352602ced2ce)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............... Boot0001* opensuse HD(1,800,56000,750adb7f-aa97-448c-b915-5547c6261e62)File(\EFI\opensuse\grubx64.efi)
techz:/windows/efi/EFI/Microsoft # ls -R : Boot
/Boot: BCD BCD.LOG2 bootmgfw.efi da-DK en-US fr-FR ja-JP nb-NO pt-BR sv-SE zh-HK BCD.LOG BOOTSTAT.DAT bootmgr.efi de-DE es-ES hu-HU ko-KR nl-NL pt-PT tr-TR zh-TW BCD.LOG1 Fonts cs-CZ el-GR fi-FI it-IT memtest.efi pl-PL ru-RU zh-CN
/Boot/Fonts: chs_boot.ttf cht_boot.ttf jpn_boot.ttf kor_boot.ttf wgl4_boot.ttf
/Boot/cs-CZ: bootmgfw.efi.mui bootmgr.efi.mui
/Boot/da-DK: bootmgfw.efi.mui bootmgr.efi.mui
/Boot/de-DE: bootmgfw.efi.mui bootmgr.efi.mui memtest.efi.mui
....
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.
I hope i can help ;)
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c6
Michael Chang mchang@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com
--- Comment #6 from Michael Chang mchang@suse.com 2013-08-14 09:49:38 UTC --- (In reply to comment #5)
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.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c7
--- Comment #7 from Michael Chang mchang@suse.com 2013-08-14 09:52:41 UTC --- I think Andrey may have better idea. :)
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 gjn@gjn.priv.at 2013-08-14 10:16:25 UTC --- Only a hint,
before I have a SSD i have Installed The SUSE System on the same RAID1 from Windows and it also only work with a extra EFI Partition created ? ;-)
I have also installed SUSE on a System with 2 SSD Hardware Raid (LSI 9271) EFI-Installation, on this System it is also not possible to install it on one EFI Partition.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c9
Andrey Borzenkov arvidjaar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at
--- Comment #9 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-14 17:54:36 UTC ---
(In reply to comment #6)
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.
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 gjn@gjn.priv.at 2013-08-16 10:49:42 UTC --- Created an attachment (id=552856) --> (http://bugzilla.novell.com/attachment.cgi?id=552856) The grub2-install debug Log
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c11
Günther J. Niederwimmer gjn@gjn.priv.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at |
--- Comment #11 from Günther J. Niederwimmer gjn@gjn.priv.at 2013-08-16 10:51:21 UTC --- OK, Andrey,
I make all you need ;), but the grub2-install log, was a problem is there no LOG possible ore don't I found the Parameter?.
techz:/ # cat /proc/mdstat Personalities : [raid1] md126 : active raid1 sda[1] sdb[0] 312568832 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive sda[1](S) sdb[0](S) 4520 blocks super external:imsm
The grub-install is attached.
I hope you can read my Picture I have not the Best Camera ;). following quick ;)
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c12
Andrey Borzenkov arvidjaar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at
--- Comment #12 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-16 10:59:38 UTC --- Did you forget to attach picture(s)?
Also could you please attach output of "udevadm info --export-db". Thank you!
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c13
Günther J. Niederwimmer gjn@gjn.priv.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at |
--- Comment #13 from Günther J. Niederwimmer gjn@gjn.priv.at 2013-08-16 12:06:56 UTC --- OK, OK I am working ;)
The new attachment are 2 pictures und udecadm log.
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 gjn@gjn.priv.at 2013-08-16 12:07:50 UTC --- Created an attachment (id=552870) --> (http://bugzilla.novell.com/attachment.cgi?id=552870) The Udevadm Log
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 gjn@gjn.priv.at 2013-08-16 12:09:18 UTC --- Created an attachment (id=552871) --> (http://bugzilla.novell.com/attachment.cgi?id=552871) The first pictue from grub ls -l
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 gjn@gjn.priv.at 2013-08-16 12:10:23 UTC --- Created an attachment (id=552872) --> (http://bugzilla.novell.com/attachment.cgi?id=552872) The second picture from grub ls -l
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c17
Andrey Borzenkov arvidjaar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at
--- Comment #17 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-16 16:30:19 UTC --- OK, I still hesitate to remove any check at all, so could you please test updateed os-prober package:
zypper ar obs://home:arvidjaar:bnc:818871/standard bnc818871 zypper refresh bnc818871 zypper dup -r bnc818871
Try to simply run os-prober, it should detect your windows EFI partition; if yes, run grub2-mkconfig -o /boot/grub2/grub.cfg and test whether you can boot with these new entries.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c
Andrey Borzenkov arvidjaar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|os-prober not working in a |os-prober not detecting EFI |EFI System |System Partition on IMSM MD | |array
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c18
Günther J. Niederwimmer gjn@gjn.priv.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at |
--- Comment #18 from Günther J. Niederwimmer gjn@gjn.priv.at 2013-08-17 10:09:55 UTC --- Hello Andrey, breaking news ;)
On my System it is not working :(techz:~ # os-prober
This is the output
No volume groups found /dev/sde3:Fedora release 19 (Schrödinger’s Cat):Fedora:linux
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 gjn@gjn.priv.at 2013-08-17 11:50:17 UTC --- Created an attachment (id=552960) --> (http://bugzilla.novell.com/attachment.cgi?id=552960) The new OS-Prober Debug Log
With the new os-prober the Program (Debug) can't remove the Directory /var/lib/os-prober/mount. I have to do it per Hand and restart the System. Then I can do again os-prober
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c20
Andrey Borzenkov arvidjaar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at
--- Comment #20 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-18 16:17:00 UTC --- Please update os-prober from the same location and test again. I fixed typo, should work now. I cannot build IMSM without hardware, but I tested it by forcing to accept DDF array.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c21
Günther J. Niederwimmer gjn@gjn.priv.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at |
--- Comment #21 from Günther J. Niederwimmer gjn@gjn.priv.at 2013-08-18 16:52:19 UTC --- Hurraaaaa;
The windows EFI is found ;)echz:~ # os-prober No volume groups found /dev/md126p1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi /dev/sde3:Fedora release 19 (Schrödinger’s Cat):Fedora:linux
But after "No volume groups found"
I have to wait very long, near 2 Min. is this the Debug Package?
So now I hope my computer is starting again and also Windows :)
I tell you later ...
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 gjn@gjn.priv.at 2013-08-18 21:29:27 UTC --- Hi Andrey,
Windows is booting, with the new os-prober entry in the grub.cfg.
and I have a Icon :-).
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 gjn@gjn.priv.at 2013-08-18 22:51:16 UTC --- I have installed the Last os-prober now, the first search is quick
techz:/etc # os-prober No volume groups found /dev/md126p1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
after this I have to wait near 1,5min for the rest (?) Is this "normal".
/dev/sde3:Fedora release 19 (Schrödinger’s Cat):Fedora:linux
I have deleted the debug Packages.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c24
--- Comment #24 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-19 02:37:16 UTC --- (In reply to comment #22)
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.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c25
--- Comment #25 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-19 02:38:22 UTC --- (In reply to comment #23)
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.
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 gjn@gjn.priv.at 2013-08-19 11:05:11 UTC --- OK, I mean this is working now ;).
I can start Windows and Fedora and openSUSE
I changed my "fstab" and it is working
/dev/disk/by-id/ata-ST3320613AS_9SZ438BR-part1 swap swap defaults 0 0 UUID=ba4e0a46-0052-4c9a-a5f2-704fed939504 / btrfs ssd 0 0 # /dev/disk/by-id/ata-OCZ-VERTEX4_OCZ-36N7N3H9VX12AMI8-part1 /boot/efi vfat umask=0002,utf8=true 0 0 /dev/disk/by-id/md-uuid-ec120401:b6ed52e6:3814fac4:48fcf4fc-part1 /boot/efi vfat umask=0002,utf8=true 0 0 /dev/disk/by-id/ata-ST3320613AS_9SZ4X64K-part1 /data ext4 defaults 1 2 /dev/disk/by-id/ata-ST3320613AS_9SZ438BR-part2 /data1 ext4 defaults 1 2 /dev/disk/by-id/md-uuid-ec120401:b6ed52e6:3814fac4:48fcf4fc-part6 /home xfs defaults 1 2 /dev/disk/by-id/md-uuid-ec120401:b6ed52e6:3814fac4:48fcf4fc-part3 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_AT.UTF-8 0 0 /dev/disk/by-id/md-uuid-ec120401:b6ed52e6:3814fac4:48fcf4fc-part4 /windows/D ntfs-3g rw,users,gid=users,fmask=133,dmask=022,locale=de_AT.UTF-8 0 0 /dev/disk/by-id/md-uuid-ec120401:b6ed52e6:3814fac4:48fcf4fc-part5 /windows/E ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_AT.UTF-8 0 0 # /dev/disk/by-id/md-uuid-ec120401:b6ed52e6:3814fac4:48fcf4fc-part1 /windows/efi vfat users,gid=users,umask=0002,utf8=true 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 luise:/data /datal nfs defaults 0 0 luise:/data1 /data1l nfs defaults 0 0 ~ What you like ;)
techz:~ # efibootmgr -v BootCurrent: 0001 Timeout: 2 seconds BootOrder: 0001,0000 Boot0000* Windows Boot Manager HD(1,800,32000,c90a8ca7-cbde-42dd-bed5-352602ced2ce)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............... Boot0001* opensuse HD(1,800,32000,c90a8ca7-cbde-42dd-bed5-352602ced2ce)File(\EFI\opensuse\grubx64.efi)
The only small Problem is, it is very slow :(.
And the Alternate boot Option is not very Clear to read.
Thanks for your work.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c27
--- Comment #27 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-19 11:10:09 UTC --- (In reply to comment #26)
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.
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 gjn@gjn.priv.at 2013-08-19 12:47:06 UTC --- Created an attachment (id=553073) --> (http://bugzilla.novell.com/attachment.cgi?id=553073) The latest os-prober debug log
Hello,
yes I run update-bootloader -refresh.
and here is the latest Debug Log from the os-prober
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c29
--- Comment #29 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-19 13:01:42 UTC --- (In reply to comment #28)
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?
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 gjn@gjn.priv.at 2013-08-19 13:41:09 UTC --- OK, you are right, the "original" is also extreme slow.
I remember on a new Install from OS 12.3, I mean the Computer hang but YaST2 working again after a 2min sleep ;).
This was a computer with only SSD.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c31
--- Comment #31 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-19 13:56:12 UTC --- (In reply to comment #30)
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?
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c32
--- Comment #32 from Michael Chang mchang@suse.com 2013-08-21 03:15:20 UTC --- Hi Andrey,
Sorry my late reponse (I was ill these days), I went through the comments and hopefull that my understanding is correct :
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.
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" ?
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).
Please review my problems and I will file a fate for it. Thanks.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c33
--- Comment #33 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-21 07:22:34 UTC --- (In reply to comment #32)
- 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.
- 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.
- 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?
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c34
--- Comment #34 from Michael Chang mchang@suse.com 2013-08-23 06:49:47 UTC --- The fate is filed.
Let's move any related discussion to the fate. :)
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c35
--- Comment #35 from Michael Chang mchang@suse.com 2013-08-23 07:11:28 UTC --- (In reply to comment #33)
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.
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c36
--- Comment #36 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-23 14:31:27 UTC --- (In reply to comment #34)
The fate is filed.
Let's move any related discussion to the fate. :)
I do not have access to this :(
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c37
Andrey Borzenkov arvidjaar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |maintenance@opensuse.org
--- Comment #37 from Andrey Borzenkov arvidjaar@gmail.com 2013-08-23 14:36:52 UTC --- (In reply to comment #35)
The maintenance request is always welcome.
MR#196125
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c38
--- Comment #38 from Bernhard Wiedemann bwiedemann@suse.com 2013-08-23 17:00:18 CEST --- This is an autogenerated message for OBS integration: This bug (818871) was mentioned in https://build.opensuse.org/request/show/196125 Maintenance /
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c39
--- Comment #39 from Michael Chang mchang@suse.com 2013-08-26 02:38:42 UTC --- (In reply to comment #36)
I do not have access to this :(
Please try this one, thanks. https://features.opensuse.org/316449
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c40
--- Comment #40 from Bernhard Wiedemann bwiedemann@suse.com 2013-08-26 05:00:13 CEST --- This is an autogenerated message for OBS integration: This bug (818871) was mentioned in https://build.opensuse.org/request/show/196332 Factory / os-prober
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c41
Marcus Meissner meissner@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |meissner@suse.com InfoProvider|maintenance@opensuse.org |
--- Comment #41 from Marcus Meissner meissner@suse.com 2013-08-26 14:03:12 UTC --- accepted for nmaintenance
https://bugzilla.novell.com/show_bug.cgi?id=818871
https://bugzilla.novell.com/show_bug.cgi?id=818871#c42
Benjamin Brunner bbrunner@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #42 from Benjamin Brunner bbrunner@suse.com 2013-09-02 13:34:36 CEST --- Update released for 12.3 and checked in into Factory. Resolved fixed.
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 swamp@suse.de 2013-09-02 12:06:04 UTC --- openSUSE-RU-2013:1398-1: An update that has one recommended fix can now be installed.
Category: recommended (moderate) Bug References: 818871 CVE References: Sources used: openSUSE 12.3 (src): os-prober-1.49-7.11.1
-
bugzilla_noreply＠novell.com