[Bug 1084717] New: The Leap 15.0 installation procedure creates a 500 MB EFI partition
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 Bug ID: 1084717 Summary: The Leap 15.0 installation procedure creates a 500 MB EFI partition Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: bugrprt21882@online.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- Executing a default "fresh" Leap 15.0 installation (Build 153) results in a 500 MB EFI partition being created. Attempting to change the EFI partition size to something less than 256 MB results in an error message indicating that, "the partition size is much too small" being raised. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 http://bugzilla.opensuse.org/show_bug.cgi?id=1084717#c3 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh@inai.de --- Comment #3 from Jan Engelhardt <jengelh@inai.de> --- So why is the recommendation 256 MB? Is this a recommendation from a different vendor which SUSE chose to pick up, and if so, who was that vendor? It's not like SUSE puts kernels onto the ESP, so that space seems wasted, at present. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 http://bugzilla.opensuse.org/show_bug.cgi?id=1084717#c4 --- Comment #4 from Ancor Gonzalez Sosa <ancor@suse.com> --- (In reply to Jan Engelhardt from comment #3)
So why is the recommendation 256 MB? Is this a recommendation from a different vendor which SUSE chose to pick up, and if so, who was that vendor?
It's not like SUSE puts kernels onto the ESP, so that space seems wasted, at present.
First of all, you only have one shot to create a big-enough ESP (/boot/efi) partition to be shared by all the operating systems living in the same disk. So YaST prefer to "waste" a couple of hundreds of megabytes rather than annoying users with a bigger problem in the future when they want to install Ubuntu or Windows alongside the openSUSE system and it's already too late to fix the issue in an easy way. That being said, note that for Advanced Format 4K Native drives (4-KiB-per-sector) drives, the size must be at least 256 MiB because that's the minimum partition size of FAT32 drives (calculated as sector size (4KiB) x 65527 = 256 MiB), due to a limitation of the FAT32 file format. Those drives are common enough (more over time) to take them into consideration. https://en.wikipedia.org/wiki/Advanced_Format So if we have to choose between wasting 200 MiB (in 2018*) on one hand or causing problems to users with Advanced Format drives and/or to users wanting to install many operating systems on the other hand, he election is clear to YaST. [*] Really, 15 years ago in Europe it was already almost impossible to buy a disk smaller than 10GiB. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 http://bugzilla.opensuse.org/show_bug.cgi?id=1084717#c5 --- Comment #5 from Jan Engelhardt <jengelh@inai.de> ---
when they want to install Ubuntu or Windows alongside the openSUSE system
That does not answer the question - are we expecting Ubuntu or Windows to put molasses of data into the ESP? openSUSE certainly does not at present.
Advanced Format 4K Native drives (4-KiB-per-sector) drives, the size must be at least 256 MiB because that's the minimum partition size of FAT32 drives
So one could choose FAT16.
Really, 15 years ago in Europe it was already almost impossible to buy a disk smaller than 10GiB.
I am not arguing about the size choice of 256M, but I wish, in general, that everyone could get over the narrow-sightedness that everybody has, or has to have, high-density slow-access spinning hard disks. Flash was and is still one power-10 order of magnitude smaller, then (40 GB vs 4 GB CF card) and now (10 TB rust vs 1 TB SSDs). And that Optane looks like some more power-2 orders down in terms of size... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 http://bugzilla.opensuse.org/show_bug.cgi?id=1084717#c6 Joachim Wagner <jwagner@computing.dcu.ie> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwagner@computing.dcu.ie --- Comment #6 from Joachim Wagner <jwagner@computing.dcu.ie> --- According to https://bugzilla.redhat.com/show_bug.cgi?id=1046577 * Some EFIs systems have trouble with FAT32 filesystems with less than 512 MiB. * The specs can be interpreted to mean that FAT16 and FAT12 only need to be supported for removable media, not the system drive, and that only one of the two filesystem versions needs to be supported in addition to mandatory FAT32 support. * Partition size is set slightly bigger than 512 MiB to avoid having to supply detailed command line options to mkdosfs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 http://bugzilla.opensuse.org/show_bug.cgi?id=1084717#c7 Terje J. Hanssen <terje@nordland-teknikk.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |terje@nordland-teknikk.no --- Comment #7 from Terje J. Hanssen <terje@nordland-teknikk.no> --- I installed Leap 15 on one workstation in dualboot setup with existing Leap 42.3 which had a pre-partioned disk with /boot/efi of 156 MB size. When mounting this /boot/efi partition for Leap 15 warnings told: The system might not be able to boot. Missing device for /boot/efi with size >= 256 MiB and file system vfat. On the other hand, on my dualboot setup ultrabook Dell XPS 13 pre-installed with Ubuntu 16.04 pre-installed, the /boot/efi partitions was sized 600 MiB. I've currently used 66 MB here. I've found it useful to directly be able to Flash new BIOS versions saved on /boot/efi. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 http://bugzilla.opensuse.org/show_bug.cgi?id=1084717#c8 --- Comment #8 from Joachim Wagner <jwagner@computing.dcu.ie> --- Depending on the mount umask for /boot/efi, the wasted space could be used for a swap file. (Swap files should never be readable to users.) According to comments on https://askubuntu.com/questions/96522/using-a-fat32-partition-for-a-swapfile there is no filesystem overhead as swapon loads the blocklist of the swapfile into the kernel once and then the kernel accesses the blocks directly. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084717 http://bugzilla.opensuse.org/show_bug.cgi?id=1084717#c9 Donald Curtis <bugrprt21882@online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #9 from Donald Curtis <bugrprt21882@online.de> --- This issue is no longer actual. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com