Partitioning for a UEFI boot loader, can LVM be used?
I just bought a gently used laptop and I am trying to figure out why this is. It has a single SSD that when running fdisk -l shows as Disk: /dev/sda. Under it though are 5 "devices" under that disk, each can only be partitioned to the imposed limits on the "device" Eg: /dev/sda1 /dev/sda2 etc...
It used to be a Windows 8 machine before I tried it and despised everything it stood for, so I am trying to load Arch Linux on it at the moment. Some of these devices range from 150MB to 267GB. The MOBO is UEFI which is new to me, the Arch boot loader wants me to create the boot partition with something other than fdisk, FAT32. They recommend at least 500MB for the boot partition which seems absurdly expensive for a boot partition, but I digress. I wanted to make one of these 200MB devices the boot partition as FAT32, the 20GB device as my root partition in ext4, and the 265GB device as a single partition with a number of logical volumes each ext4 for /var /tmp and /home.
There isn't a single device on this disk that I want to use for boot that is quite 500MB and I don't want to share the 20GB device by splitting it into separate partitions for boot and root. If I use the whole 20GB device for just /boot however it would seem an unfortunate waste.
Is it possible to create the /boot partition as a logical volume on the larger device? Is there anything I would have to worry about with regards to UEFI and Gummiboot on Arch Linux? I apologize if this is a very beginner question.
boot partition lvm uefi
edited 1 hour ago
sourcejedi
22.7k435100
asked Dec 15 '14 at 12:27
maple_shaft
1891113
|
show 2 more comments
I just bought a gently used laptop and I am trying to figure out why this is. It has a single SSD that when running fdisk -l shows as Disk: /dev/sda. Under it though are 5 "devices" under that disk, each can only be partitioned to the imposed limits on the "device" Eg: /dev/sda1 /dev/sda2 etc...
It used to be a Windows 8 machine before I tried it and despised everything it stood for, so I am trying to load Arch Linux on it at the moment. Some of these devices range from 150MB to 267GB. The MOBO is UEFI which is new to me, the Arch boot loader wants me to create the boot partition with something other than fdisk, FAT32. They recommend at least 500MB for the boot partition which seems absurdly expensive for a boot partition, but I digress. I wanted to make one of these 200MB devices the boot partition as FAT32, the 20GB device as my root partition in ext4, and the 265GB device as a single partition with a number of logical volumes each ext4 for /var /tmp and /home.
There isn't a single device on this disk that I want to use for boot that is quite 500MB and I don't want to share the 20GB device by splitting it into separate partitions for boot and root. If I use the whole 20GB device for just /boot however it would seem an unfortunate waste.
Is it possible to create the /boot partition as a logical volume on the larger device? Is there anything I would have to worry about with regards to UEFI and Gummiboot on Arch Linux? I apologize if this is a very beginner question.
boot partition lvm uefi
edited 1 hour ago
sourcejedi
22.7k435100
asked Dec 15 '14 at 12:27
maple_shaft
1891113
1
no. not possible. also, lvm is a pretty nasty tech anyway.
– mikeserv
Dec 16 '14 at 0:03
why would you be opposed to shar[ing] the 20GB device by splitting it... anyway? I don't understand that at all. It sounds like you're not very clear on what partitioning means, and maybe a little in the dark about UEFI as well. Look here and follow the links to rodsbooks.com
– mikeserv
Dec 16 '14 at 0:24
@mikeserv Well I wanted the 20GB device as a single partition for root. That leaves the larger device unadulterated for /home and media making upgrades or OS changes easier. What I ultimately did last night was set the 400MB device to be the /boot partition anyway. I did find in Arch Wiki documentation where they explicitly stated LVM cannot be used for the /boot partition.
– maple_shaft
Dec 16 '14 at 12:19
@mikeserv I am very much in the dark about UEFI, I have only installed Linux before on a BIOS firmware and MBR partitions. UEFI and GUID partitions are very new to me.
– maple_shaft
Dec 16 '14 at 12:20
I just meant - what have you got against partitioning the 20gb disk? And what I said aboutlvm- ok, it isn't in-and-of-itself nasty, but when it swallows whole disk arrays and becomes a single point of failure, well.... Yeah, that's why I pointed you to those links - did you follow them?
– mikeserv
Dec 17 '14 at 0:48
|
show 2 more comments
I just bought a gently used laptop and I am trying to figure out why this is. It has a single SSD that when running fdisk -l shows as Disk: /dev/sda. Under it though are 5 "devices" under that disk, each can only be partitioned to the imposed limits on the "device" Eg: /dev/sda1 /dev/sda2 etc...
It used to be a Windows 8 machine before I tried it and despised everything it stood for, so I am trying to load Arch Linux on it at the moment. Some of these devices range from 150MB to 267GB. The MOBO is UEFI which is new to me, the Arch boot loader wants me to create the boot partition with something other than fdisk, FAT32. They recommend at least 500MB for the boot partition which seems absurdly expensive for a boot partition, but I digress. I wanted to make one of these 200MB devices the boot partition as FAT32, the 20GB device as my root partition in ext4, and the 265GB device as a single partition with a number of logical volumes each ext4 for /var /tmp and /home.
There isn't a single device on this disk that I want to use for boot that is quite 500MB and I don't want to share the 20GB device by splitting it into separate partitions for boot and root. If I use the whole 20GB device for just /boot however it would seem an unfortunate waste.
Is it possible to create the /boot partition as a logical volume on the larger device? Is there anything I would have to worry about with regards to UEFI and Gummiboot on Arch Linux? I apologize if this is a very beginner question.
boot partition lvm uefi
edited 1 hour ago
sourcejedi
22.7k435100
asked Dec 15 '14 at 12:27
maple_shaft
1891113
I just bought a gently used laptop and I am trying to figure out why this is. It has a single SSD that when running fdisk -l shows as Disk: /dev/sda. Under it though are 5 "devices" under that disk, each can only be partitioned to the imposed limits on the "device" Eg: /dev/sda1 /dev/sda2 etc...
It used to be a Windows 8 machine before I tried it and despised everything it stood for, so I am trying to load Arch Linux on it at the moment. Some of these devices range from 150MB to 267GB. The MOBO is UEFI which is new to me, the Arch boot loader wants me to create the boot partition with something other than fdisk, FAT32. They recommend at least 500MB for the boot partition which seems absurdly expensive for a boot partition, but I digress. I wanted to make one of these 200MB devices the boot partition as FAT32, the 20GB device as my root partition in ext4, and the 265GB device as a single partition with a number of logical volumes each ext4 for /var /tmp and /home.
There isn't a single device on this disk that I want to use for boot that is quite 500MB and I don't want to share the 20GB device by splitting it into separate partitions for boot and root. If I use the whole 20GB device for just /boot however it would seem an unfortunate waste.
Is it possible to create the /boot partition as a logical volume on the larger device? Is there anything I would have to worry about with regards to UEFI and Gummiboot on Arch Linux? I apologize if this is a very beginner question.
boot partition lvm uefi
boot partition lvm uefi
edited 1 hour ago
sourcejedi
22.7k435100
asked Dec 15 '14 at 12:27
maple_shaft
1891113
edited 1 hour ago
sourcejedi
22.7k435100
asked Dec 15 '14 at 12:27
maple_shaft
1891113
edited 1 hour ago
sourcejedi
22.7k435100
edited 1 hour ago
sourcejedi
22.7k435100
edited 1 hour ago
sourcejedi
22.7k435100
22.7k435100
asked Dec 15 '14 at 12:27
maple_shaft
1891113
asked Dec 15 '14 at 12:27
maple_shaft
1891113
asked Dec 15 '14 at 12:27
maple_shaft
1891113
1891113
1
no. not possible. also, lvm is a pretty nasty tech anyway.
– mikeserv
Dec 16 '14 at 0:03
why would you be opposed to shar[ing] the 20GB device by splitting it... anyway? I don't understand that at all. It sounds like you're not very clear on what partitioning means, and maybe a little in the dark about UEFI as well. Look here and follow the links to rodsbooks.com
– mikeserv
Dec 16 '14 at 0:24
@mikeserv Well I wanted the 20GB device as a single partition for root. That leaves the larger device unadulterated for /home and media making upgrades or OS changes easier. What I ultimately did last night was set the 400MB device to be the /boot partition anyway. I did find in Arch Wiki documentation where they explicitly stated LVM cannot be used for the /boot partition.
– maple_shaft
Dec 16 '14 at 12:19
@mikeserv I am very much in the dark about UEFI, I have only installed Linux before on a BIOS firmware and MBR partitions. UEFI and GUID partitions are very new to me.
– maple_shaft
Dec 16 '14 at 12:20
I just meant - what have you got against partitioning the 20gb disk? And what I said aboutlvm- ok, it isn't in-and-of-itself nasty, but when it swallows whole disk arrays and becomes a single point of failure, well.... Yeah, that's why I pointed you to those links - did you follow them?
– mikeserv
Dec 17 '14 at 0:48
|
show 2 more comments
1
no. not possible. also, lvm is a pretty nasty tech anyway.
– mikeserv
Dec 16 '14 at 0:03
why would you be opposed to shar[ing] the 20GB device by splitting it... anyway? I don't understand that at all. It sounds like you're not very clear on what partitioning means, and maybe a little in the dark about UEFI as well. Look here and follow the links to rodsbooks.com
– mikeserv
Dec 16 '14 at 0:24
@mikeserv Well I wanted the 20GB device as a single partition for root. That leaves the larger device unadulterated for /home and media making upgrades or OS changes easier. What I ultimately did last night was set the 400MB device to be the /boot partition anyway. I did find in Arch Wiki documentation where they explicitly stated LVM cannot be used for the /boot partition.
– maple_shaft
Dec 16 '14 at 12:19
@mikeserv I am very much in the dark about UEFI, I have only installed Linux before on a BIOS firmware and MBR partitions. UEFI and GUID partitions are very new to me.
– maple_shaft
Dec 16 '14 at 12:20
I just meant - what have you got against partitioning the 20gb disk? And what I said aboutlvm- ok, it isn't in-and-of-itself nasty, but when it swallows whole disk arrays and becomes a single point of failure, well.... Yeah, that's why I pointed you to those links - did you follow them?
– mikeserv
Dec 17 '14 at 0:48
1
1
no. not possible. also, lvm is a pretty nasty tech anyway.
– mikeserv
Dec 16 '14 at 0:03
no. not possible. also, lvm is a pretty nasty tech anyway.
– mikeserv
Dec 16 '14 at 0:03
why would you be opposed to shar[ing] the 20GB device by splitting it... anyway? I don't understand that at all. It sounds like you're not very clear on what partitioning means, and maybe a little in the dark about UEFI as well. Look here and follow the links to rodsbooks.com
– mikeserv
Dec 16 '14 at 0:24
why would you be opposed to shar[ing] the 20GB device by splitting it... anyway? I don't understand that at all. It sounds like you're not very clear on what partitioning means, and maybe a little in the dark about UEFI as well. Look here and follow the links to rodsbooks.com
– mikeserv
Dec 16 '14 at 0:24
@mikeserv Well I wanted the 20GB device as a single partition for root. That leaves the larger device unadulterated for /home and media making upgrades or OS changes easier. What I ultimately did last night was set the 400MB device to be the /boot partition anyway. I did find in Arch Wiki documentation where they explicitly stated LVM cannot be used for the /boot partition.
– maple_shaft
Dec 16 '14 at 12:19
@mikeserv Well I wanted the 20GB device as a single partition for root. That leaves the larger device unadulterated for /home and media making upgrades or OS changes easier. What I ultimately did last night was set the 400MB device to be the /boot partition anyway. I did find in Arch Wiki documentation where they explicitly stated LVM cannot be used for the /boot partition.
– maple_shaft
Dec 16 '14 at 12:19
@mikeserv I am very much in the dark about UEFI, I have only installed Linux before on a BIOS firmware and MBR partitions. UEFI and GUID partitions are very new to me.
– maple_shaft
Dec 16 '14 at 12:20
@mikeserv I am very much in the dark about UEFI, I have only installed Linux before on a BIOS firmware and MBR partitions. UEFI and GUID partitions are very new to me.
– maple_shaft
Dec 16 '14 at 12:20
I just meant - what have you got against partitioning the 20gb disk? And what I said about
lvm - ok, it isn't in-and-of-itself nasty, but when it swallows whole disk arrays and becomes a single point of failure, well.... Yeah, that's why I pointed you to those links - did you follow them?– mikeserv
Dec 17 '14 at 0:48
I just meant - what have you got against partitioning the 20gb disk? And what I said about
lvm - ok, it isn't in-and-of-itself nasty, but when it swallows whole disk arrays and becomes a single point of failure, well.... Yeah, that's why I pointed you to those links - did you follow them?– mikeserv
Dec 17 '14 at 0:48
|
show 2 more comments
1 Answer
1
active
oldest
votes
No.
UEFI Bios tries to find a partition in a GPT-partitioned boot device.
This partition needs to be tagged with "EFI System" (see fdisk's "t" command for all options) and also needs to be formatted with FAT filesystem.
You'll find a good explanation here...
Command (m for help): p
Disk /dev/sda: 167.7 GiB, 180045766656 bytes, 351651888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sda1 2048 534527 532480 260M EFI System
/dev/sda2 534528 351651839 351117312 167.4G Linux LVM
answered Jan 17 at 8:15
Josef Hopfgartner
212
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2funix.stackexchange.com%2fquestions%2f174337%2fpartitioning-for-a-uefi-boot-loader-can-lvm-be-used%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No.
UEFI Bios tries to find a partition in a GPT-partitioned boot device.
This partition needs to be tagged with "EFI System" (see fdisk's "t" command for all options) and also needs to be formatted with FAT filesystem.
You'll find a good explanation here...
Command (m for help): p
Disk /dev/sda: 167.7 GiB, 180045766656 bytes, 351651888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sda1 2048 534527 532480 260M EFI System
/dev/sda2 534528 351651839 351117312 167.4G Linux LVM
answered Jan 17 at 8:15
Josef Hopfgartner
212
add a comment |
No.
UEFI Bios tries to find a partition in a GPT-partitioned boot device.
This partition needs to be tagged with "EFI System" (see fdisk's "t" command for all options) and also needs to be formatted with FAT filesystem.
You'll find a good explanation here...
Command (m for help): p
Disk /dev/sda: 167.7 GiB, 180045766656 bytes, 351651888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sda1 2048 534527 532480 260M EFI System
/dev/sda2 534528 351651839 351117312 167.4G Linux LVM
answered Jan 17 at 8:15
Josef Hopfgartner
212
add a comment |
No.
UEFI Bios tries to find a partition in a GPT-partitioned boot device.
This partition needs to be tagged with "EFI System" (see fdisk's "t" command for all options) and also needs to be formatted with FAT filesystem.
You'll find a good explanation here...
Command (m for help): p
Disk /dev/sda: 167.7 GiB, 180045766656 bytes, 351651888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sda1 2048 534527 532480 260M EFI System
/dev/sda2 534528 351651839 351117312 167.4G Linux LVM
answered Jan 17 at 8:15
Josef Hopfgartner
212
No.
UEFI Bios tries to find a partition in a GPT-partitioned boot device.
This partition needs to be tagged with "EFI System" (see fdisk's "t" command for all options) and also needs to be formatted with FAT filesystem.
You'll find a good explanation here...
Command (m for help): p
Disk /dev/sda: 167.7 GiB, 180045766656 bytes, 351651888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sda1 2048 534527 532480 260M EFI System
/dev/sda2 534528 351651839 351117312 167.4G Linux LVM
answered Jan 17 at 8:15
Josef Hopfgartner
212
answered Jan 17 at 8:15
Josef Hopfgartner
212
answered Jan 17 at 8:15
Josef Hopfgartner
212
answered Jan 17 at 8:15
Josef Hopfgartner
212
212
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f174337%2fpartitioning-for-a-uefi-boot-loader-can-lvm-be-used%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
no. not possible. also, lvm is a pretty nasty tech anyway.
– mikeserv
Dec 16 '14 at 0:03
why would you be opposed to shar[ing] the 20GB device by splitting it... anyway? I don't understand that at all. It sounds like you're not very clear on what partitioning means, and maybe a little in the dark about UEFI as well. Look here and follow the links to rodsbooks.com
– mikeserv
Dec 16 '14 at 0:24
@mikeserv Well I wanted the 20GB device as a single partition for root. That leaves the larger device unadulterated for /home and media making upgrades or OS changes easier. What I ultimately did last night was set the 400MB device to be the /boot partition anyway. I did find in Arch Wiki documentation where they explicitly stated LVM cannot be used for the /boot partition.
– maple_shaft
Dec 16 '14 at 12:19
@mikeserv I am very much in the dark about UEFI, I have only installed Linux before on a BIOS firmware and MBR partitions. UEFI and GUID partitions are very new to me.
– maple_shaft
Dec 16 '14 at 12:20
I just meant - what have you got against partitioning the 20gb disk? And what I said about
lvm- ok, it isn't in-and-of-itself nasty, but when it swallows whole disk arrays and becomes a single point of failure, well.... Yeah, that's why I pointed you to those links - did you follow them?– mikeserv
Dec 17 '14 at 0:48