[Bug 894146] New: What is the Need to create a /boot/efi for UEFI BIOS Expansion
https://bugzilla.novell.com/show_bug.cgi?id=894146 https://bugzilla.novell.com/show_bug.cgi?id=894146#c0 Summary: What is the Need to create a /boot/efi for UEFI BIOS Expansion Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: secure@aphofis.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 With the New UEFI BIOS expansion either the auto partitioner at Installation wants to create a /boot/efi formatted with FAT and a Volume name of GTA with about 1GB of Space. Documentation published and in bug reports I see this requirement discussed often and a bit of technical Information. I have ALL X_64 Hardware and 2 Have the ability to boot in UEFI Mode or 'Turbo X' as its some time referred, as a BIOS boot option. For every PC where I have followed this ALL suffer from instability and I cannot find any real answers as to why this need is to partition a Disk in such a manner. During Installation If I accept the Proposed, options of a separate /home partition a /boot/efi and a FAT format and a further Labelled Partition of GTA is presented. Even if I accept just a /boot/efi with a FAT format and don't worry about a GTA partition ever X64 PC has stability issues during operation. Either a PC hangs during both Installation after the first restart or when a fs check is demand run after n number of perfect boot up start; the systems are unstable. I have also noted that ANY RAID created with the Partitioner with the above leads to problems with any RAID. Its RAID creation often fails completely to be formatted with any RAID5 and RAID0 becomes very unstable requiring file system checks ever time I boot or fails to be formatted with EXT I have had to reinstall both 12.3 and 13.1 without this guided /boot/efi FAT partition and the PC is perfectly stable back to nominal values even if I boot from UEFI I can see no need, nor requirement for the partitioner to propose the Disk by setup with both /boot/efi with FAT and a GTA labelled partition in the first instance and I cannot find any clear guidelines for this reasoning. ALL I know is that If I continue to manually create a HDD partitions as normal the PC works and boot with great stability and any RAID drive is stable. In an upgrade installation I loose the LOT by following the Partitioner’s instructions and after first boot the whole installation never recovers at all Reproducible: Always Steps to Reproduce: 1.100% reproduced on my hardware 6 times but when partitioned normally everything is stable 2. 3. Actual Results: Stability of PC is either failure in creating any RAID or its operation IS unstable and a reason why the proposed /boot/efi FAT is presented is not made clear In an upgrade installation I loose the LOT by following the Partitioner’s instructions and after first boot the whole installation never recovers at all and everything is lost including the Installation revival Expected Results: Can we please have as associated help page during the Installation when the Partitioner is called discussing this and or remove or justifying to the user, the warning in 12.3 and 13.1 that an /boot/efiu partition etc. etc. is required before the user commits to the Part ion setup. We also need further full page info help screen to appear before the partitioner is called during Installation explaining UEFI BIOS requirements and figure out why a PC fails or is unstable when the proposal is followed as is above. In short...WHY???????? If I ignore completely all this stuff the PC creates any RAID perfectly and the system is stable...What's going on here please tell me and the rest of us. I cant find my glasses so please excuse any typo's...:-) -- 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=894146 https://bugzilla.novell.com/show_bug.cgi?id=894146#c1 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com AssignedTo|bnc-team-screening@forge.pr |rw@suse.com |ovo.novell.com | --- Comment #1 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-09-02 04:42:57 CEST --- Hi Scott, the problem is that there are machines built, that have UEFI instead of the classic BIOS and the only way for those to boot is from such a FAT partition, except if the vendor spent extra money on a legacy-compat module (and some don't) I'm not sure how the method of booting can influence the stability of the system maybe through differences in ACPI which vendors usually test with MSWindows and even add hacks for it and it might be worth debugging those instabilities but for that, we would need further info about the type of hardware - e.g. attach output from hwinfo --all and how those instabilities show up, kernel messages during hangup, etc You could also try the openSUSE Factory version, which is much newer than 13.1 so could have fixes for these issues and even if not, it would be easier+faster to get fixes into 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=894146 https://bugzilla.novell.com/show_bug.cgi?id=894146#c2 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |secure@aphofis.com --- Comment #2 from Scott Couston <secure@aphofis.com> 2014-09-02 15:46:25 EST --- I understand but with both machines they already boot with both UEFI services on or off as I can choose either, right now with 12.3 its perfectly stable without and special partitioning????? They are perfectly stable booting with UEFI services on or off. With the PC that has permanent UEFI and I install 13.1 the install fails when booting from Install UEFI BOOT Device. The RAID ID is a bit different. If I use non UEFI PC with has simple HDD set as RAID and use standard CTRL+F that has a RAID 5 install cant see that either. If I use a PC with UEFI BIOS and setup up BIOS as RAID and use ordinary CRTL +F to set a RAID5, install cant see that either. How can I help with logs etc and how can I help test conditions you want to give me as I have the luxury of a test full UEFI BIOS BOOT OR non UEFI BOOT. Tell me how I can help step by step and you tell me how to config and well get this sorted out..:-) -- 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=894146 https://bugzilla.novell.com/show_bug.cgi?id=894146#c3 --- Comment #3 from Scott Couston <secure@aphofis.com> 2014-09-02 17:04:44 EST --- Sorry I confused everything above by bringing RAID into the scenario and I have a bug out on that issues so Ill try again a bit more orderly to get this figured out. This is about 12.3 Installation. Lets not even touch 13.1 as it has more holes in it than Swiss cheese please and in my humble opinion its needs to be withdrawn from download NOW and forgotten about! !!!!!!!!!! When I install 12.3 on a PC running a non UEFI BIOS but X64 bit architecture I format the HDD as I please and go to accept this format and I get a warning its needs a /boot/efi warning formatted with FAT etc. etc. etc. If I ignore the warning and install is as I please everything works and is stable. IF I give this NON UEFI X64 PC what the warning wants as far as a boot /boot/efi formatted with FAT and another partition called GTA etc etc as per the documentation, install falls over when it comes to its first boot from HDD IF I ignore it Install gets to this same stage and does start to initiate its first boot but it hangs loading susefirewall part 2 and I have to force a system reset to continue...I have another bug out of that one as well as NFS issues. Ill attach hardware device output from yast and /var/log yast 2 tomorrow for you. -- 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=894146 https://bugzilla.novell.com/show_bug.cgi?id=894146#c4 --- Comment #4 from Scott Couston <secure@aphofis.com> 2014-09-05 09:08:37 EST --- Created an attachment (id=605103) --> (http://bugzilla.novell.com/attachment.cgi?id=605103) Hardware-list Hardware List -- 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=894146 https://bugzilla.novell.com/show_bug.cgi?id=894146#c5 --- Comment #5 from Scott Couston <secure@aphofis.com> 2014-09-05 09:12:06 EST --- Created an attachment (id=605105) --> (http://bugzilla.novell.com/attachment.cgi?id=605105) ALL /var/logs/yast2 all logs in /var/logs/yast2 -- 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