Does the UEFI partition either “MUST” or “SHOULD” be first for some reason? If so why?
up vote
6
down vote
favorite
In a non-English Ubuntu-it.org wiki page it's stated that the UEFI partition MUST be always placed at the start of the disk.
This is not the case in the English Ubuntu Community Help Wiki page.
So does the UEFI partition either "MUST" or "SHOULD" (assuming a bad wording in the former page) be first for some reason? If so why? Or this is totally irrelevant?
partitioning uefi bootloader
add a comment |
up vote
6
down vote
favorite
In a non-English Ubuntu-it.org wiki page it's stated that the UEFI partition MUST be always placed at the start of the disk.
This is not the case in the English Ubuntu Community Help Wiki page.
So does the UEFI partition either "MUST" or "SHOULD" (assuming a bad wording in the former page) be first for some reason? If so why? Or this is totally irrelevant?
partitioning uefi bootloader
1
For my latest installation (Arch Linux + GRUB + GPT + UEFI), it is last.
– muru
May 4 '15 at 18:14
add a comment |
up vote
6
down vote
favorite
up vote
6
down vote
favorite
In a non-English Ubuntu-it.org wiki page it's stated that the UEFI partition MUST be always placed at the start of the disk.
This is not the case in the English Ubuntu Community Help Wiki page.
So does the UEFI partition either "MUST" or "SHOULD" (assuming a bad wording in the former page) be first for some reason? If so why? Or this is totally irrelevant?
partitioning uefi bootloader
In a non-English Ubuntu-it.org wiki page it's stated that the UEFI partition MUST be always placed at the start of the disk.
This is not the case in the English Ubuntu Community Help Wiki page.
So does the UEFI partition either "MUST" or "SHOULD" (assuming a bad wording in the former page) be first for some reason? If so why? Or this is totally irrelevant?
partitioning uefi bootloader
partitioning uefi bootloader
edited May 4 '15 at 21:28
Fabby
25.8k1359159
25.8k1359159
asked May 4 '15 at 17:57
kos
25.1k869117
25.1k869117
1
For my latest installation (Arch Linux + GRUB + GPT + UEFI), it is last.
– muru
May 4 '15 at 18:14
add a comment |
1
For my latest installation (Arch Linux + GRUB + GPT + UEFI), it is last.
– muru
May 4 '15 at 18:14
1
1
For my latest installation (Arch Linux + GRUB + GPT + UEFI), it is last.
– muru
May 4 '15 at 18:14
For my latest installation (Arch Linux + GRUB + GPT + UEFI), it is last.
– muru
May 4 '15 at 18:14
add a comment |
2 Answers
2
active
oldest
votes
up vote
7
down vote
accepted
The key words "SHOULD", "MUST" and "MAY" (capitalised) in this answer are to be interpreted as described in RFC 2119.
An (U)EFI System Partition (ESP from now on):
- MAY reside at the beginning of the disk
and** ** - SHOULD be FAT32 because of Windows compatibility.
The only official limit is:
- the ESP MUST reside in the first 2.2 Terabytes of the disk.
So, the ESP MUST reside anywhere in those first 2.2 TB of the disk, but there is absolutely no need for the ESP to be the first partition or reside on the beginning of the disk whatsoever.
(It's just that some large company in Redmond, WA advises system integrators differently)...
I would put it as the last partition on the disk (if < 2.2TB) as it's only used to load other OSes, but that's just a personal, totally subjective opinion!
do you mean "if < 2.2 TB" in that last sentance? otherwise I don't think your advice makes sense...
– KutuluMike
May 4 '15 at 23:07
@Fabby, In practice would a non-FAT32 UEFI work fine?
– Pacerier
May 4 '15 at 23:37
2
The document linked to by "official limit" in your post refers to BIOS and MBR limitations. The ESP is an EFI construct, so BIOS limits don't apply to it. I have placed ESPs well above the 2TiB mark and successfully booted computers from those ESPs. That said, an ESP on an MBR disk would necessarily reside below the 2^32 sector (usually 2TiB) mark, or at least begin there. MBR is seldom used for system disks on EFI-based systems, though, so this limit barely merits a footnote.
– Rod Smith
May 5 '15 at 1:07
Here is one good reason for not having EFI partition be first. I have a SanDisk Extreme USB Flash drive that is dual ended. One side has a standard USB connector and the other a USB-C connector for phones. The drive has multiple 5 partitions on it for various Linux installs and one data partition. By placing the data partition first, both Windows and Android can mount and read/write. Android and any pre-creator's update Windows systems will only mount the first partition of a removeable drive.
– BrianHVB
Jul 24 at 2:45
add a comment |
up vote
3
down vote
The EFI specification specifically states that there are no limits on this detail:
UEFI does not impose a restriction on the number or location of System Partitions that can exist on a system.
(Version 2.5, p. 540.)
As a practical matter, putting the ESP first is advisable because this location is unlikely to be impacted by partition moving and resizing operations. For instance, suppose the ESP exists between OS A and OS B partitions, and you decide to delete OS B and give its space to OS A. In this case, you'll need to move the ESP before you can expand the OS A partition. Also, some tools, such as efibootmgr
, use /dev/sda1
as the default location for the ESP. Thus, if you place the ESP elsewhere and then forget to override the defaults, you can create an unbootable entry.
Putting the ESP at the end of the disk can work almost as well in most cases, but there are some subtle problems with that approach. For one thing, if you change the number of partitions, the number of the ESP may no longer match its position on the disk, or some partitioning tools may renumber it. Either outcome can cause confusion or require reconfiguration. Also, if you use RAID and add disk space, an ESP at the end of the disk will suddenly become one in the middle, which may require you to move it.
Many pre-installed Windows systems put the ESP at position #2, with #1 being occupied by a small manufacturer-specific partition. Such a configuration works fine, and since the manufacturer's partition is also unlikely to be moved or deleted, this configuration isn't really any worse than putting the ESP at position #1. I wouldn't go out of my way to "fix" such a configuration, but I also wouldn't do it that way myself, if I were given a blank disk and told to start installing OSes.
Overall, if you have some compelling reason to create an ESP at other than the first position, feel free to do so; but if you're starting with a blank disk and have no compelling reason otherwise, I'd put the ESP first.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
accepted
The key words "SHOULD", "MUST" and "MAY" (capitalised) in this answer are to be interpreted as described in RFC 2119.
An (U)EFI System Partition (ESP from now on):
- MAY reside at the beginning of the disk
and** ** - SHOULD be FAT32 because of Windows compatibility.
The only official limit is:
- the ESP MUST reside in the first 2.2 Terabytes of the disk.
So, the ESP MUST reside anywhere in those first 2.2 TB of the disk, but there is absolutely no need for the ESP to be the first partition or reside on the beginning of the disk whatsoever.
(It's just that some large company in Redmond, WA advises system integrators differently)...
I would put it as the last partition on the disk (if < 2.2TB) as it's only used to load other OSes, but that's just a personal, totally subjective opinion!
do you mean "if < 2.2 TB" in that last sentance? otherwise I don't think your advice makes sense...
– KutuluMike
May 4 '15 at 23:07
@Fabby, In practice would a non-FAT32 UEFI work fine?
– Pacerier
May 4 '15 at 23:37
2
The document linked to by "official limit" in your post refers to BIOS and MBR limitations. The ESP is an EFI construct, so BIOS limits don't apply to it. I have placed ESPs well above the 2TiB mark and successfully booted computers from those ESPs. That said, an ESP on an MBR disk would necessarily reside below the 2^32 sector (usually 2TiB) mark, or at least begin there. MBR is seldom used for system disks on EFI-based systems, though, so this limit barely merits a footnote.
– Rod Smith
May 5 '15 at 1:07
Here is one good reason for not having EFI partition be first. I have a SanDisk Extreme USB Flash drive that is dual ended. One side has a standard USB connector and the other a USB-C connector for phones. The drive has multiple 5 partitions on it for various Linux installs and one data partition. By placing the data partition first, both Windows and Android can mount and read/write. Android and any pre-creator's update Windows systems will only mount the first partition of a removeable drive.
– BrianHVB
Jul 24 at 2:45
add a comment |
up vote
7
down vote
accepted
The key words "SHOULD", "MUST" and "MAY" (capitalised) in this answer are to be interpreted as described in RFC 2119.
An (U)EFI System Partition (ESP from now on):
- MAY reside at the beginning of the disk
and** ** - SHOULD be FAT32 because of Windows compatibility.
The only official limit is:
- the ESP MUST reside in the first 2.2 Terabytes of the disk.
So, the ESP MUST reside anywhere in those first 2.2 TB of the disk, but there is absolutely no need for the ESP to be the first partition or reside on the beginning of the disk whatsoever.
(It's just that some large company in Redmond, WA advises system integrators differently)...
I would put it as the last partition on the disk (if < 2.2TB) as it's only used to load other OSes, but that's just a personal, totally subjective opinion!
do you mean "if < 2.2 TB" in that last sentance? otherwise I don't think your advice makes sense...
– KutuluMike
May 4 '15 at 23:07
@Fabby, In practice would a non-FAT32 UEFI work fine?
– Pacerier
May 4 '15 at 23:37
2
The document linked to by "official limit" in your post refers to BIOS and MBR limitations. The ESP is an EFI construct, so BIOS limits don't apply to it. I have placed ESPs well above the 2TiB mark and successfully booted computers from those ESPs. That said, an ESP on an MBR disk would necessarily reside below the 2^32 sector (usually 2TiB) mark, or at least begin there. MBR is seldom used for system disks on EFI-based systems, though, so this limit barely merits a footnote.
– Rod Smith
May 5 '15 at 1:07
Here is one good reason for not having EFI partition be first. I have a SanDisk Extreme USB Flash drive that is dual ended. One side has a standard USB connector and the other a USB-C connector for phones. The drive has multiple 5 partitions on it for various Linux installs and one data partition. By placing the data partition first, both Windows and Android can mount and read/write. Android and any pre-creator's update Windows systems will only mount the first partition of a removeable drive.
– BrianHVB
Jul 24 at 2:45
add a comment |
up vote
7
down vote
accepted
up vote
7
down vote
accepted
The key words "SHOULD", "MUST" and "MAY" (capitalised) in this answer are to be interpreted as described in RFC 2119.
An (U)EFI System Partition (ESP from now on):
- MAY reside at the beginning of the disk
and** ** - SHOULD be FAT32 because of Windows compatibility.
The only official limit is:
- the ESP MUST reside in the first 2.2 Terabytes of the disk.
So, the ESP MUST reside anywhere in those first 2.2 TB of the disk, but there is absolutely no need for the ESP to be the first partition or reside on the beginning of the disk whatsoever.
(It's just that some large company in Redmond, WA advises system integrators differently)...
I would put it as the last partition on the disk (if < 2.2TB) as it's only used to load other OSes, but that's just a personal, totally subjective opinion!
The key words "SHOULD", "MUST" and "MAY" (capitalised) in this answer are to be interpreted as described in RFC 2119.
An (U)EFI System Partition (ESP from now on):
- MAY reside at the beginning of the disk
and** ** - SHOULD be FAT32 because of Windows compatibility.
The only official limit is:
- the ESP MUST reside in the first 2.2 Terabytes of the disk.
So, the ESP MUST reside anywhere in those first 2.2 TB of the disk, but there is absolutely no need for the ESP to be the first partition or reside on the beginning of the disk whatsoever.
(It's just that some large company in Redmond, WA advises system integrators differently)...
I would put it as the last partition on the disk (if < 2.2TB) as it's only used to load other OSes, but that's just a personal, totally subjective opinion!
edited Nov 26 at 15:56
answered May 4 '15 at 18:15
Fabby
25.8k1359159
25.8k1359159
do you mean "if < 2.2 TB" in that last sentance? otherwise I don't think your advice makes sense...
– KutuluMike
May 4 '15 at 23:07
@Fabby, In practice would a non-FAT32 UEFI work fine?
– Pacerier
May 4 '15 at 23:37
2
The document linked to by "official limit" in your post refers to BIOS and MBR limitations. The ESP is an EFI construct, so BIOS limits don't apply to it. I have placed ESPs well above the 2TiB mark and successfully booted computers from those ESPs. That said, an ESP on an MBR disk would necessarily reside below the 2^32 sector (usually 2TiB) mark, or at least begin there. MBR is seldom used for system disks on EFI-based systems, though, so this limit barely merits a footnote.
– Rod Smith
May 5 '15 at 1:07
Here is one good reason for not having EFI partition be first. I have a SanDisk Extreme USB Flash drive that is dual ended. One side has a standard USB connector and the other a USB-C connector for phones. The drive has multiple 5 partitions on it for various Linux installs and one data partition. By placing the data partition first, both Windows and Android can mount and read/write. Android and any pre-creator's update Windows systems will only mount the first partition of a removeable drive.
– BrianHVB
Jul 24 at 2:45
add a comment |
do you mean "if < 2.2 TB" in that last sentance? otherwise I don't think your advice makes sense...
– KutuluMike
May 4 '15 at 23:07
@Fabby, In practice would a non-FAT32 UEFI work fine?
– Pacerier
May 4 '15 at 23:37
2
The document linked to by "official limit" in your post refers to BIOS and MBR limitations. The ESP is an EFI construct, so BIOS limits don't apply to it. I have placed ESPs well above the 2TiB mark and successfully booted computers from those ESPs. That said, an ESP on an MBR disk would necessarily reside below the 2^32 sector (usually 2TiB) mark, or at least begin there. MBR is seldom used for system disks on EFI-based systems, though, so this limit barely merits a footnote.
– Rod Smith
May 5 '15 at 1:07
Here is one good reason for not having EFI partition be first. I have a SanDisk Extreme USB Flash drive that is dual ended. One side has a standard USB connector and the other a USB-C connector for phones. The drive has multiple 5 partitions on it for various Linux installs and one data partition. By placing the data partition first, both Windows and Android can mount and read/write. Android and any pre-creator's update Windows systems will only mount the first partition of a removeable drive.
– BrianHVB
Jul 24 at 2:45
do you mean "if < 2.2 TB" in that last sentance? otherwise I don't think your advice makes sense...
– KutuluMike
May 4 '15 at 23:07
do you mean "if < 2.2 TB" in that last sentance? otherwise I don't think your advice makes sense...
– KutuluMike
May 4 '15 at 23:07
@Fabby, In practice would a non-FAT32 UEFI work fine?
– Pacerier
May 4 '15 at 23:37
@Fabby, In practice would a non-FAT32 UEFI work fine?
– Pacerier
May 4 '15 at 23:37
2
2
The document linked to by "official limit" in your post refers to BIOS and MBR limitations. The ESP is an EFI construct, so BIOS limits don't apply to it. I have placed ESPs well above the 2TiB mark and successfully booted computers from those ESPs. That said, an ESP on an MBR disk would necessarily reside below the 2^32 sector (usually 2TiB) mark, or at least begin there. MBR is seldom used for system disks on EFI-based systems, though, so this limit barely merits a footnote.
– Rod Smith
May 5 '15 at 1:07
The document linked to by "official limit" in your post refers to BIOS and MBR limitations. The ESP is an EFI construct, so BIOS limits don't apply to it. I have placed ESPs well above the 2TiB mark and successfully booted computers from those ESPs. That said, an ESP on an MBR disk would necessarily reside below the 2^32 sector (usually 2TiB) mark, or at least begin there. MBR is seldom used for system disks on EFI-based systems, though, so this limit barely merits a footnote.
– Rod Smith
May 5 '15 at 1:07
Here is one good reason for not having EFI partition be first. I have a SanDisk Extreme USB Flash drive that is dual ended. One side has a standard USB connector and the other a USB-C connector for phones. The drive has multiple 5 partitions on it for various Linux installs and one data partition. By placing the data partition first, both Windows and Android can mount and read/write. Android and any pre-creator's update Windows systems will only mount the first partition of a removeable drive.
– BrianHVB
Jul 24 at 2:45
Here is one good reason for not having EFI partition be first. I have a SanDisk Extreme USB Flash drive that is dual ended. One side has a standard USB connector and the other a USB-C connector for phones. The drive has multiple 5 partitions on it for various Linux installs and one data partition. By placing the data partition first, both Windows and Android can mount and read/write. Android and any pre-creator's update Windows systems will only mount the first partition of a removeable drive.
– BrianHVB
Jul 24 at 2:45
add a comment |
up vote
3
down vote
The EFI specification specifically states that there are no limits on this detail:
UEFI does not impose a restriction on the number or location of System Partitions that can exist on a system.
(Version 2.5, p. 540.)
As a practical matter, putting the ESP first is advisable because this location is unlikely to be impacted by partition moving and resizing operations. For instance, suppose the ESP exists between OS A and OS B partitions, and you decide to delete OS B and give its space to OS A. In this case, you'll need to move the ESP before you can expand the OS A partition. Also, some tools, such as efibootmgr
, use /dev/sda1
as the default location for the ESP. Thus, if you place the ESP elsewhere and then forget to override the defaults, you can create an unbootable entry.
Putting the ESP at the end of the disk can work almost as well in most cases, but there are some subtle problems with that approach. For one thing, if you change the number of partitions, the number of the ESP may no longer match its position on the disk, or some partitioning tools may renumber it. Either outcome can cause confusion or require reconfiguration. Also, if you use RAID and add disk space, an ESP at the end of the disk will suddenly become one in the middle, which may require you to move it.
Many pre-installed Windows systems put the ESP at position #2, with #1 being occupied by a small manufacturer-specific partition. Such a configuration works fine, and since the manufacturer's partition is also unlikely to be moved or deleted, this configuration isn't really any worse than putting the ESP at position #1. I wouldn't go out of my way to "fix" such a configuration, but I also wouldn't do it that way myself, if I were given a blank disk and told to start installing OSes.
Overall, if you have some compelling reason to create an ESP at other than the first position, feel free to do so; but if you're starting with a blank disk and have no compelling reason otherwise, I'd put the ESP first.
add a comment |
up vote
3
down vote
The EFI specification specifically states that there are no limits on this detail:
UEFI does not impose a restriction on the number or location of System Partitions that can exist on a system.
(Version 2.5, p. 540.)
As a practical matter, putting the ESP first is advisable because this location is unlikely to be impacted by partition moving and resizing operations. For instance, suppose the ESP exists between OS A and OS B partitions, and you decide to delete OS B and give its space to OS A. In this case, you'll need to move the ESP before you can expand the OS A partition. Also, some tools, such as efibootmgr
, use /dev/sda1
as the default location for the ESP. Thus, if you place the ESP elsewhere and then forget to override the defaults, you can create an unbootable entry.
Putting the ESP at the end of the disk can work almost as well in most cases, but there are some subtle problems with that approach. For one thing, if you change the number of partitions, the number of the ESP may no longer match its position on the disk, or some partitioning tools may renumber it. Either outcome can cause confusion or require reconfiguration. Also, if you use RAID and add disk space, an ESP at the end of the disk will suddenly become one in the middle, which may require you to move it.
Many pre-installed Windows systems put the ESP at position #2, with #1 being occupied by a small manufacturer-specific partition. Such a configuration works fine, and since the manufacturer's partition is also unlikely to be moved or deleted, this configuration isn't really any worse than putting the ESP at position #1. I wouldn't go out of my way to "fix" such a configuration, but I also wouldn't do it that way myself, if I were given a blank disk and told to start installing OSes.
Overall, if you have some compelling reason to create an ESP at other than the first position, feel free to do so; but if you're starting with a blank disk and have no compelling reason otherwise, I'd put the ESP first.
add a comment |
up vote
3
down vote
up vote
3
down vote
The EFI specification specifically states that there are no limits on this detail:
UEFI does not impose a restriction on the number or location of System Partitions that can exist on a system.
(Version 2.5, p. 540.)
As a practical matter, putting the ESP first is advisable because this location is unlikely to be impacted by partition moving and resizing operations. For instance, suppose the ESP exists between OS A and OS B partitions, and you decide to delete OS B and give its space to OS A. In this case, you'll need to move the ESP before you can expand the OS A partition. Also, some tools, such as efibootmgr
, use /dev/sda1
as the default location for the ESP. Thus, if you place the ESP elsewhere and then forget to override the defaults, you can create an unbootable entry.
Putting the ESP at the end of the disk can work almost as well in most cases, but there are some subtle problems with that approach. For one thing, if you change the number of partitions, the number of the ESP may no longer match its position on the disk, or some partitioning tools may renumber it. Either outcome can cause confusion or require reconfiguration. Also, if you use RAID and add disk space, an ESP at the end of the disk will suddenly become one in the middle, which may require you to move it.
Many pre-installed Windows systems put the ESP at position #2, with #1 being occupied by a small manufacturer-specific partition. Such a configuration works fine, and since the manufacturer's partition is also unlikely to be moved or deleted, this configuration isn't really any worse than putting the ESP at position #1. I wouldn't go out of my way to "fix" such a configuration, but I also wouldn't do it that way myself, if I were given a blank disk and told to start installing OSes.
Overall, if you have some compelling reason to create an ESP at other than the first position, feel free to do so; but if you're starting with a blank disk and have no compelling reason otherwise, I'd put the ESP first.
The EFI specification specifically states that there are no limits on this detail:
UEFI does not impose a restriction on the number or location of System Partitions that can exist on a system.
(Version 2.5, p. 540.)
As a practical matter, putting the ESP first is advisable because this location is unlikely to be impacted by partition moving and resizing operations. For instance, suppose the ESP exists between OS A and OS B partitions, and you decide to delete OS B and give its space to OS A. In this case, you'll need to move the ESP before you can expand the OS A partition. Also, some tools, such as efibootmgr
, use /dev/sda1
as the default location for the ESP. Thus, if you place the ESP elsewhere and then forget to override the defaults, you can create an unbootable entry.
Putting the ESP at the end of the disk can work almost as well in most cases, but there are some subtle problems with that approach. For one thing, if you change the number of partitions, the number of the ESP may no longer match its position on the disk, or some partitioning tools may renumber it. Either outcome can cause confusion or require reconfiguration. Also, if you use RAID and add disk space, an ESP at the end of the disk will suddenly become one in the middle, which may require you to move it.
Many pre-installed Windows systems put the ESP at position #2, with #1 being occupied by a small manufacturer-specific partition. Such a configuration works fine, and since the manufacturer's partition is also unlikely to be moved or deleted, this configuration isn't really any worse than putting the ESP at position #1. I wouldn't go out of my way to "fix" such a configuration, but I also wouldn't do it that way myself, if I were given a blank disk and told to start installing OSes.
Overall, if you have some compelling reason to create an ESP at other than the first position, feel free to do so; but if you're starting with a blank disk and have no compelling reason otherwise, I'd put the ESP first.
answered May 5 '15 at 1:01
Rod Smith
34.9k43770
34.9k43770
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f618244%2fdoes-the-uefi-partition-either-must-or-should-be-first-for-some-reason-if-s%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
For my latest installation (Arch Linux + GRUB + GPT + UEFI), it is last.
– muru
May 4 '15 at 18:14