[Bug 845763] New: UEFI Installation broken
https://bugzilla.novell.com/show_bug.cgi?id=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c0 Summary: UEFI Installation broken Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: gjn@gjn.priv.at QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 On my system ASUS P8B WS it is not possible to install 13.1. The first Problem, most time the Installer have Problem to setup the Drive this is a Intel IMSM Raid 5 and the Installer can't Format VFAT (Error -3000) or have Problem to create the LVM System or afterward to format the Partition (Error -4000) Btrfs. The next Problem, when I have a Partitionen and Formated System the Installation have a Problem to start UEFI. In the Bios I found my UEFI Partition with "opensuse" but it is not possible to start it in stack 2 to configure the system. On a very new System ASUSS P9D WS the Installer crash all drives SSD and also the Windows Installation is gone nothing is after the Installation in the UEFI Bios to Boot. I tell before the the Secure Boot is Broken Beta1.... The 12.3 is Installable and other Distris works fine, but with 13.1 all is broken. 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c Günther J. Niederwimmer <gjn@gjn.priv.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Critical -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c1 Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at AssignedTo|bnc-team-screening@forge.pr |aschnell@suse.com |ovo.novell.com | --- Comment #1 from Martin Vidner <mvidner@suse.com> 2013-10-14 15:37:01 CEST --- Hi Günther, please attach the logs, as usual: 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c2 Günther J. Niederwimmer <gjn@gjn.priv.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at | --- Comment #2 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-14 14:59:39 UTC --- Created an attachment (id=563348) --> (http://bugzilla.novell.com/attachment.cgi?id=563348) The Log from the first Part of Installation After this Installation I have a Entry in UEFI Bios "opensuse" but it is not starting. This is a Test for a Manual configured Drive but it is the same Problem with YaST2 cunfigured Drive -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c3 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com Component|Installation |Bootloader AssignedTo|aschnell@suse.com |jsrain@suse.com --- Comment #3 from Arvin Schnell <aschnell@suse.com> 2013-10-14 15:10:49 UTC --- In the logs the errors mentioned in comment #0 (error -3000 and -4000) do not happen so I cannot analyse them. Instead the partitioning and package installation works fine as far as I can see. Booting is not my area. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c4 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at AssignedTo|jsrain@suse.com |snwint@suse.com --- Comment #4 from Jiri Srain <jsrain@suse.com> 2013-10-15 07:36:46 UTC --- Günther, could you, please, try to find out why the uEFI entry is not starting? Without knowing more details, it is rather impossible to provide a fix... -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#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-10-15 08:56:35 UTC --- Hello Jiri, efibootmgr -v BootOrder: 0000,0004,00002.... Boot0000* opensuse HD(1,800,61800,e7e607fc-8a9d-45e2-b1a0-1a768fde61f6)File(/EFI/opensuse/grubx64.efi Now I clear the NVRAM and make on next Installation a Boot Partition outside the LVM Partition. Hardware this is a ASUS P8B WS Board with a XEON E3-1275 and 16GB Ram (ECC). But I wrote, on a P9D WS with XeonV3 16GB Ram with IMMS active (2x SSD Raid1) the hole Drive System is crashed, afterward no windows and no SUSE. With a LSI 9271-8i config Widows is starting but opensuse not. (Beta1 is sometimes starting) 2 x SSD Raid 1 But from this System I have no more Logs You can found the Logs in Bug 838578 -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c6 --- Comment #6 from Michael Chang <mchang@suse.com> 2013-10-15 09:35:50 UTC --- Hi Gunther, Per the log you provided, your EFI System Partition is on (fake) RAID 5 ? As long as the blocks are stripped, better make sure that your firmware could read files on it without problem. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c7 --- Comment #7 from Michael Chang <mchang@suse.com> 2013-10-15 09:39:13 UTC --- As I remember your setup used to work with IMSM RAID1, but that's without striping so your firmware might be able read file system blocks that only get mirrored. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c8 --- Comment #8 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-15 10:41:02 UTC --- I make a Test installation with Centos, same Hardware same configuration with this it is working. I mean there is a Problem with IMMS driver Grub2-EFI -> YaST2. OK, I Test it now again with 12.3 (?) I start now the KDE Live System but with this I can't mount the LVM2 Partition but I have a extra small Partition /dev/IMSM ?. On "normal" Installation this must be the /dev/md127 ? And the Live system is not EFI Bootable so I can't see the NVRAM (efibootmg) -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c9 --- Comment #9 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-15 11:03:40 UTC --- Hello Michael, I forget to tell one time the Installation is working "Normal",after same Error -3000 Vfat System -4000 LVM System and a Bootloader config Error. I don't remember why I delete this Installation :(. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c10 --- Comment #10 from Michael Chang <mchang@suse.com> 2013-10-15 11:08:12 UTC --- (In reply to comment #8)
I make a Test installation with Centos, same Hardware same configuration with this it is working. I mean there is a Problem with IMMS driver Grub2-EFI -> YaST2.
Sorry what's is IMMS ? I suppose it's typo of IMSM .. If firmware could load Centos loader, why it wouldn't load opensuse loader, did you have any messsage otherwise it's difficult to tell the failure is in bootloader or firmware ..
I start now the KDE Live System but with this I can't mount the LVM2 Partition but I have a extra small Partition /dev/IMSM ?. On "normal" Installation this must be the /dev/md127 ?
Maybe you need to activate the LVM volume ? $ vgchange -ay system
And the Live system is not EFI Bootable so I can't see the NVRAM (efibootmg)
It' odd that live system should be EFI bootable, could you be more elaboration on what's the problem you have ? Thanks. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c11 --- Comment #11 from Michael Chang <mchang@suse.com> 2013-10-15 11:12:53 UTC --- (In reply to comment #9)
Hello Michael,
I forget to tell one time the Installation is working "Normal",after same Error -3000 Vfat System -4000 LVM System and a Bootloader config Error.
Hm .. is this bootloader or yast issue ? I'm really confused. :( As I know we have problem on bootloader not start (see comment#4) and now it get fixed ? -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c12 --- Comment #12 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-15 12:38:44 UTC --- hello Michael, Yes this is a Typo ;) IMSM ... Now I have extra run a Test Installation with fedora 19 clear RAID 5 Drive (IMSM). The installer make a /boot/EFI Partition and a LVM Installation /root /home /swap. the only different is ext4 and not btrfs. The System is booting correct (?) and running. Is it possible that YaST2 have a problem with the new reading IMSM Volume? On fedora I have the correct Drive Name from IMSM "Vol0" on SUSE it is "/dev/md126" but I read, this is changed to the Original Name (Vol0) The next Test is without Btrfs :(. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c13 --- Comment #13 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-15 12:52:47 UTC --- Hello, is this a Problem, I have a small different efibootmgr Entry efibootmgr -v bootorder 0005,........ Boot0005* HD(1,800,64000,ba8e676c-.................)File(\EFI\....) ^^^^^ Now the last installation today without Btrfs.;) -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c14 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at --- Comment #14 from Michael Chang <mchang@suse.com> 2013-10-17 07:30:06 UTC --- Hi Gunther, That is your partition size in unit of sectors and is possible to differ according to your partition map in use. Do you have any results without Btrfs now? Thanks. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c15 Günther J. Niederwimmer <gjn@gjn.priv.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at | --- Comment #15 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-17 08:52:23 UTC --- Created an attachment (id=563830) --> (http://bugzilla.novell.com/attachment.cgi?id=563830) extra Boot Partition This is a Installation with a extra boot Partition the Rest ist LVM Btrfs this is not working -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c16 --- Comment #16 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-17 08:55:00 UTC --- Created an attachment (id=563831) --> (http://bugzilla.novell.com/attachment.cgi?id=563831) The ext4 installation Log With LVM and ext4 the installation is the first time working. I have to do now more test ;) -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c17 --- Comment #17 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-17 09:00:27 UTC --- I make again a clear Disk with GPT Table to install the system. I mean the Installer have also a problem with a existing EFI Partition (?) -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c18 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gjn@gjn.priv.at --- Comment #18 from Michael Chang <mchang@suse.com> 2013-10-17 10:41:23 UTC --- (In reply to comment #15)
This is a Installation with a extra boot Partition the Rest ist LVM Btrfs this is not working
What's "not working" in this case ? Did you end up in grub> rescue mode or .. ? -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c19 --- Comment #19 from Michael Chang <mchang@suse.com> 2013-10-17 10:54:10 UTC --- To get things more clear, try to list your setup (correct me if I'm wrong) "not working" setup /dev/md126 is configured as IMSM RAID 5 '/' => '/dev/server/root', (Btrfs+LVM on /dev/md126p3) '/boot' => '/dev/md126p2', (Btrfs on /dev/md126p2) '/boot/efi' => '/dev/md126p1', (vfat32 on /dev/md126p1) '/home' => '/dev/server/home' (Btrfs+LVM on /dev/md126p3) "working" setup /dev/md126 is configured as IMSM RAID 5 '/' => '/dev/system/root', (ext4+LVM on /dev/md126p2) '/boot/efi' => '/dev/md126p1', (vfat32 on /dev/md126p1) '/home' => '/dev/system/home' (ext4+LVM on /dev/md126p2) And please define what's "not working" to be clear. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c20 Günther J. Niederwimmer <gjn@gjn.priv.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gjn@gjn.priv.at | --- Comment #20 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-17 11:19:27 UTC --- Hello Michael, not working setup /dev/md126 is configured as IMSM RAID 5 '/' => '/dev/server/root', (Btrfs+LVM on /dev/md126p3) '/boot' => '/dev/md126p2', (ext4 on /dev/md126p2) '/boot/efi' => '/dev/md126p1', (vfat32 on /dev/md126p1) '/home' => '/dev/server/home' (Btrfs+LVM on /dev/md126p3) /dev/md126 is configured as IMSM RAID 5 '/' => '/dev/server/root', (Btrfs+LVM on /dev/md126p3) '/boot/efi' => '/dev/md126p1', (vfat32 on /dev/md126p1) '/home' => '/dev/server/home' (Btrfs+LVM on /dev/md126p3) /dev/md126 is configured as IMSM RAID 5 '/' => '/dev/server/root', (Btrfs+LVM on /dev/md126p3) '/boot' => '/dev/md126p2', (Btrfs on /dev/md126p2) '/boot/efi' => '/dev/md126p1', (vfat32 on /dev/md126p1) '/home' => '/dev/server/home' (Btrfs+LVM on /dev/md126p3) C#18 NO, uEFI can't found the start Partition. The only way to start the system is without Btrfs. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c21 --- Comment #21 from Michael Chang <mchang@suse.com> 2013-10-18 11:14:41 UTC --- (In reply to comment #20)
NO, uEFI can't found the start Partition.
Could it be the -F32 option that made the trouble ? In your btrfs log there's some warning on formatting /dev/md126p1 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/mkdosfs -F32 '/dev/md126p1'" 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "WARNING: Not enough clusters for a 32 bit FAT!" 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:4036 added lines:1 stderr:true 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "mkfs.fat 3.0.22 (2013-07-19)" 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:4036 added lines:1 stderr:false 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 0.020440s for "/sbin/mkdosfs -F32 '/dev/md126p1 2013-10-15 10:54:45 <1> linux(2717) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:0 However your ext3 log didn't use -F32 and looked fine. 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/mkdosfs '/dev/md126p1'" 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(addLine):592 Adding Line 1 "mkfs.fat 3.0.22 (2013-07-19)" 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(getUntilEOF):558 pid:3941 added lines:1 stderr:false 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 0.011264s for "/sbin/mkdosfs '/dev/md126p1'" 2013-10-17 08:23:56 <1> linux(2718) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:0
The only way to start the system is without Btrfs.
I have no idea on how Btrfs would be related. :( -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c22 --- Comment #22 from Michael Chang <mchang@suse.com> 2013-10-18 11:26:34 UTC --- Hm.. it looks very promising that above warning is the cause to UEFI boot fail .. https://bbs.archlinux.org/viewtopic.php?id=168014 https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#F... Although UEFI spec stats FAT32 is official filesystem for ESP (SMH) ... "EFI encompasses the use of FAT32 for a system partition, and FAT12 or FAT16 for removable media .." -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c23 --- Comment #23 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-20 19:27:58 UTC --- I have tested now more, I mean th big Problem is the vFat creation on the Partition. I make now with diskpart (windos) a system Partition (uEFI) with 256 MB und format it with FAT32 and set the partition active. Afterward I install 13.1 with LVM/Btrfs. And the system is booting correct?. I attach the Log. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c24 --- Comment #24 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-20 19:29:34 UTC --- Created an attachment (id=564155) --> (http://bugzilla.novell.com/attachment.cgi?id=564155) The Last Installation Log with extra created EFI Partition -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c25 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jsrain@suse.com --- Comment #25 from Michael Chang <mchang@suse.com> 2013-10-21 07:14:07 UTC --- I dumped setup from your log, which was using ESP created on your own by the steps you described in comment#23. Create volume /dev/md126p2 (1.36 TB) Create volume group system (1.36 TB) from /dev/md126p2 [destructive] Create volume /dev/system/home (100.00 GB) for /home with btrfs Create root volume /dev/system/root (50.00 GB) with btrfs Create swap logical volume /dev/system/swap (2.00 GB) Set mount point of /dev/md126p1 to /boot/efi ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If your system is working, then the problem is really on vfat creation. I don't know why -F32 is not globally applied and could absent in your ext3 log, and we might have to use -F32 -u2 if the ESP is really small, but I can't tell the what the boundary is. Hi Jiri, could YaST team make some comment about vfat creation issue, specifically for ESP ? -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c26 --- Comment #26 from Günther J. Niederwimmer <gjn@gjn.priv.at> 2013-10-21 07:45:35 UTC --- I like to tell. On Installation the existing vFAT (FAT32) in in Yast only a "FAT" Partition. Is this relevant ? -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c27 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com InfoProvider|jsrain@suse.com |aschnell@suse.com --- Comment #27 from Jiri Srain <jsrain@suse.com> 2013-10-22 06:44:37 UTC --- Perhaps Arvin can provide more info on VFAT creation. However, as I understand the list of action, there should be no filesystem creation involved - the filesystem should have been used as it was before installation. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c28 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|aschnell@suse.com | --- Comment #28 from Arvin Schnell <aschnell@suse.com> 2013-10-22 07:28:40 UTC --- YaST only knows about VFAT. It does not distinguish between VFAT12, VFAT16 or VFAT32. -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c29 --- Comment #29 from Michael Chang <mchang@suse.com> 2013-10-23 10:55:58 UTC --- (In reply to comment #28)
YaST only knows about VFAT. It does not distinguish between VFAT12, VFAT16 or VFAT32.
Indeed. And also checked factory's libstorage has no sign of any -F32 keyword. It's really weird how come that log would format with that option. :( -- 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=845763 https://bugzilla.novell.com/show_bug.cgi?id=845763#c30 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #30 from Bruno Friedmann <bruno@ioda-net.ch> 2014-09-15 17:45:00 UTC --- For information, this is the mail that I've forwarded to efibootmgr maintainer. I suspect we have a "big" trouble in the way EFI is handled on factory actually. For the last two weeks, I'm trying to get my new apple macbook pro 11.4 to load openSUSE Factory and face one issue. If the install goes smoothly, once it reboot the nvram is totally destroyed whenever there's or not a partition vfat for EFI. The firmware load by telling there's no more bootable harddrive, you have to boot an efi usb key, and remake apple osx okay for reboot. I've dig the internet to find a why this happen all the time ( installation of 13.1 works on it ) then I found two things which seems important for openSUSE: https://bugzilla.redhat.com/show_bug.cgi?id=1114775 on this bug I've seen that fedora version was 0.7.x version when our stick very old. then I discover on koji.fedoraproject.org that the efibootmgr has a new development home located at https://github.com/vathpela/efibootmgr and there's just a new release https://github.com/vathpela/efibootmgr/releases/tag/efibootmgr-0.8.0 which seems to contain bugfixes for the issue I'm having. - Re-encorporate workaround for Apple machines And a lot of more fixes that could help on the long description found in this bug. -- 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