None of my Win10 installations need one, but I have yet to find a reason to put Win10 on a GPT/UEFI PC.
Hi
It’s 16 MB not 16 GB and it’s type 0c01 MS reserved…
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 260M 0 part /boot/efi
├─sda2 8:2 0 16M 0 part
├─sda3 8:3 0 40G 0 part /
├─sda4 8:4 0 35G 0 part /data
├─sda5 8:5 0 4G 0 part [SWAP]
├─sda6 8:6 0 31.8G 0 part
└─sda7 8:7 0 789M 0 part
0 789M 0 part
big-bird:~ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 5675 sectors (2.8 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 534527 260.0 MiB EF00 EFI System
2 534528 567295 16.0 MiB 0C01 Microsoft reserved
3 567296 84453375 40.0 GiB 8300 Linux filesystem
4 84453376 157853695 35.0 GiB 8300 Linux filesystem
5 157853696 166242303 4.0 GiB 8200 Linux swap
6 166242304 232822081 31.7 GiB 0700 Microsoft basic data
OK, so instead of comment 20, this with MSR included:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 465.8G 0 disk
|-sdb1 8:17 0 320M 0 part /boot/efi
|-sdb2 8:18 0 16M 0 part
|-sdb3 8:19 0 4.1G 0 part [SWAP]
|-sdb4 8:20 0 41G 0 part /
|-sdb5 8:21 0 41G 0 part alt /
|-sdb6 8:22 0 43.2G 0 part WinSYS
|-sdb7 8:23 0 43.2G 0 part WinSYS alt
|-sdb8 8:24 0 146.5G 0 part /home
`-sdb9 8:25 0 146.5G 0 part Win Data
DFSee Linux 14.12: Executing: part -d:2
|ux|Dr|Type, description|Format|Related |OS2-LVM/BM / GPT / Crypt / add'l | Size MiB |
+--</dev/sdb GPT disk 2>--+--------<ST3500414CS>---------------------+-----------+
| 1| |EFI System (ESP)|FAT32 |GPT/EFI |sdX1 EFI System (ESP) | 320.0|
| 2| |MS Reserved (MSR)| |Windows |sdX2 Microsoft Reserved | 16.0|
| 3| |Linux Swap | SWAP |LinuxT1 |sdX3 Linux Swap | 4203.0|
| 4| |Linux Data | EXT4 |Linux |sdX4 openSUSE 15.0 | 42000.0|
| 5| |Linux Data | EXT4 |Linux |sdX5 openSUSE 15.1 | 42000.0|
| 6| |Windows BasicData| NTFS |Windows |sdX6 WinSYS 10 Release | 44200.0|
| 7| |Windows BasicData| NTFS |Windows |sdX7 WinSYS Insider Preview | 44200.0|
| 8| |Linux Data | XFS |Linux |sdX8 Linux /home | 150000.0|
| 9| |Windows BasicData| NTFS |Windows |sdX9 Windows User Data | 150000.0|
DFSee Linux 14.12: Executing: part -d:2 -n
|ux|Dr|Type, description|Begin Sect|End sector| Cylinder range | Sectors | Size MiB |
+--</dev/sdb GPT disk 2>------+----------+-------------------<ST3500414CS>----------+
| | |Fsp + GPT hdr/pta| 22| 7ff| 0 - 0| 7de| 1.0|
| 1| |EFI System (ESP)| 800| a07ff| 1 - 320| a0000| 320.0|
| 2| |MS Reserved (MSR)| a0800| a87ff| 321 - 336| 8000| 16.0|
| 3| |Linux Swap | a8800| 8ddfff| 337 - 4539| 835800| 4203.0|
| 4| |Linux Data | 8de000| 5ae5fff| 4540 - 46539| 5208000| 42000.0|
| 5| |Linux Data | 5ae6000| acedfff| 46540 - 88539| 5208000| 42000.0|
| 6| |Windows BasicData| acee000| 10341fff| 88540 - 132739| 5654000| 44200.0|
| 7| |Windows BasicData| 10342000| 15995fff| 132740 - 176939| 5654000| 44200.0|
| 8| |Linux Data | 15996000| 27e8dfff| 176940 - 326939| 124f8000| 150000.0|
| 9| |Windows BasicData| 27e8e000| 3a385fff| 326940 - 476939| 124f8000| 150000.0
I can buy into most of that mrmazda, but I don’t really want both of the Windows 10 on the machine. I don’t use the RTM version as it is on the laptop.
The image I posted (and failed to recognize the 16MB vs 16GB) is an accurate reflection of what is on the laptops HDD currently.
<1- also, this may be moot by tomorrow, my wife’s laptop looks to be failing, and she may have to use mine until we get her another. she is not sure about Linux.>
<2- but I am buying a used HP All-in-One from a friend, and it also has a 500GB HDD and that may be where Leap 15 (along with Win 10) ends up. Another toy{sigh}>
BTW what is ‘DFSee’? It is command-not-found in my Leap 15
It wasn’t entirely clear to me you were no longer interested in having two Windows installations.
BTW what is ‘DFSee’? It is command-not-found in my Leap 15
DFSee is scriptable non-free software I use to the exclusion of all other for writing partition tables. It uses identical UI on all supported (Intel) platforms: DOS, Linux, Mac, OS/2, Windows. Its logging facilitates tracking what is occupied by hundreds of partitions spread across many computers and disks. Its copy, clone and resize are components of my backup/restore routine.
I have a dumb question. The current efi partition is 100MB. (my image is gone from susepaste, see image in post #8 by malcomlewis).
If the installer wants to increase that to 200 or 300MB for the /boot/efi partition where does it take it from?
>>> probably /grub2/efi instead of /boot/efi
That image is for a 2TiB HD. I thought you were planning on installing to a 500GiB HD?
If the installer wants to increase that to 200 or 300MB for the /boot/efi partition where does it take it from?
Without knowing the current starting point, I won’t venture to speculate. Are you going to repartition? Go entirely with a wipe disk first proposal from YaST2?
Another proposal:
|ux|Dr|Type, description|Format |Related |VolumeLabel|GPT/Crypt/ add'l| Size MiB |
</dev/sdb GPT disk 2>-------+--------<ST3500414CS>----------------+----------+
| | |Fsp + GPT hdr/pta|-- -- --|-- -- --| | 1.0|
| 1| |EFI System (ESP)|FAT32 |GPT/EFI |sdX1 EFI System (ESP) | 320.0|
| 2| |MS Reserved (MSR)| |Windows |sdX2 Microsoft Reserved | 16.0|
| 3| |Linux Swap |SWAP |LinuxT1 |sdX3 Linux Swap | 4203.0|
| 4| |Linux Data |EXT4 |Linux |sdX4 openSUSE 15.0 | 42000.0|
| 5| |Linux Data |EXT4 |Linux |sdX5 openSUSE 15.1 | 42000.0|
| 6| |Windows BasicData|NTFS |Windows |sdX6 Windows 10 System | 48400.0|
| 7| |Linux Data |XFS |Linux |sdX7 Linux /home | 170000.0|
| 8| |Windows BasicData|NTFS |Windows |sdX8 Windows User Data | 170000.0|
|ux|Dr|Type, description|Begin Sect|End sector| Cylinder range | Sectors | Size MiB |
+--</dev/sdb GPT disk 2>------+----------+-------------------<ST3500414CS>--------+
| | |Fsp + GPT hdr/pta| 22| 7ff| 0 - 0| 7de| 1.0|
| 1| |EFI System (ESP)| 800| a07ff| 1 - 320| a0000| 320.0|
| 2| |MS Reserved (MSR)| a0800| a87ff| 321 - 336| 8000| 16.0|
| 3| |Linux Swap | a8800| 8ddfff| 337 - 4539| 835800| 4203.0|
| 4| |Linux Data | 8de000| 5ae5fff| 4540 - 46539| 5208000| 42000.0|
| 5| |Linux Data | 5ae6000| acedfff| 46540 - 88539| 5208000| 42000.0|
| 6| |Windows BasicData| acee000| 10b75fff| 88540 - 136939| 5e88000| 48400.0|
| 7| |Linux Data | 10b76000| 2577dfff| 136940 - 306939| 14c08000| 170000.0|
| 8| |Windows BasicData| 2577e000| 3a385fff| 306940 - 476939| 14c08000| 170000.0|
The image displayed in post #8 and again in post #10 are from an image I posted to susepaste. I don’t know how to make images stay in these forums.
I did a diskpart list (I believe) in windows, and copied the the information and pasted it in an image format.
It is my 500GB HDD, and I am looking at diskpart as I type to make sure I am not leading anyone astray.
I plan on making ONE windows partition unallocated(along with its small recovery partition) for the Leap 15 install, and will use the unallocated space to set up Leap 15 partitions.
So it will be Leap 15 and Windows 10. I will concern myself with Leap 15.1 when it is released.
I don’t know how to be more clear as to my intentions for the way I plan to install.
UNORGANIZED PARTITION SCHEME FOR MY UEFI LAPTOP
The EFI system partition
The 16MB MSR partition
a Linux / partition
a Linux /home partition
a Linux swap partition
The Windows 10 OS partition(the size shown in referred images)
The Windows 10 WRE(recovery) partition (the size shown in the referred images)
Please make future proposals around that. I know you are trying to help but I am confused enough as it is.
Outside of the 2 windows 10 partitions I don’t know sizes I will use YET. To be determined at install time.
When you create your image post on susepaste, watch for the “Expires” line and change the expiry date appropriately. Usually, if it is something that might be worth someone seeing farther down the road when they read this thread, you would set it to “never expire”.
In my mind, there is no such thing as a “dumb question” on these forums, only sometimes “dumb answers”.
100 meg is normally fine unless you plan to install a ton of different OS. The installer recommends 250+ but you can simply ignore that and go with the existing 100 meg just be sure it is mounted at /boot/efi in the partitioning scheme proposal.
Unless you are doing something unusual, 100M should be fine.
Yes, the installer thinks it should be at least 256M. In my opinion, that’s a poor installer decision that I wish they would change.
I just go to the expert partitioner, and set the existing EFI partition to be mounted at “/boot/efi”. And I ignore warnings about it being too small.
And I should be clear. My actual UEFI computers have 500M for their EFI partitions. Some of my test installs (in virtual machines) have used smaller EFI partitions and ignored the warnings from the installer. And they have all been fine.
Maybe some day I will learn to actually read the page and see what is there.
I still don’t understand how to make an image visible(IE; you girl friend in the screenshot section…lol)
@nrickert, @gogalthorp, If something happens to linux(like I mess it up somehow), will grub2 still boot windows?
If both OS boot in the same boot mode ie MBR or EFI then there should be no problem. Problem only occur when the OS use different booting.
OK, thanks!
Following is why I have a personal convention to create and recommend 320MiB as EFI partition size:
1-Hardware conditions exist where a 100MiB partition could be inadequate. (Microsoft explains)](https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions)
2-260,000 from #1’s explanation is a decimal similitude of 2^18 (262,144), so it’s not entirely clear what the actual magic number is.
3-Partition tables are always constructed using hex.
4-A reported FOSS bug exists, from where I can’t remember, involving ~250MiB somehow being inadequate.
5-500MB and 500MiB, compared to 100MiB, is gross oversize.
So, to make a size larger than 250MiB and also larger than 260MB but less than 500M, I round to a multiple of 4K blocksize 2^16 (65,536, a common I/O block or cluster size) added to the problematic minimum 2^18 (262,144) which results in 320MiB (327,680). It’s not necessary, just a convention that might someday avoid stumbling on the condition that less than “260M” would in fact be inadequate.