LVM Ontop of LUKS using Grub Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionVery poor read performance compared to write performance on md(raid1) / crypt(luks) / lvmGrub-install: embedding is not possible in Bios/GPTGRUB doesn't find /boot in LVMGrub disable recovery not working on detected OSNixOS installation on multi-boot system with GRUB (from Arch installation)Macbook pro retina 2013 with full disk encryption boot issueChainloading in LUKS on LVM from ESPInstalling GRUB to encrypted partition doesn't work if (root) is F2FSRemoving the swap partition from a LUKS encrypted SSDDUbuntu 18.04 LUKS boot problems
What's the difference between (size_t)-1 and ~0?
Replacing HDD with SSD; what about non-APFS/APFS?
Is above average number of years spent on PhD considered a red flag in future academia or industry positions?
If A makes B more likely then B makes A more likely"
Complexity of many constant time steps with occasional logarithmic steps
Autumning in love
How to stop my camera from exagerrating differences in skin colour?
How do I keep my slimes from escaping their pens?
Estimated State payment too big --> money back; + 2018 Tax Reform
Can the prologue be the backstory of your main character?
Strange behaviour of Check
Can a zero nonce be safely used with AES-GCM if the key is random and never used again?
Need a suitable toxic chemical for a murder plot in my novel
Area of a 2D convex hull
Is there folklore associating late breastfeeding with low intelligence and/or gullibility?
Active filter with series inductor and resistor - do these exist?
I'm thinking of a number
Why is there no army of Iron-Mans in the MCU?
When is phishing education going too far?
Statistical model of ligand substitution
Single author papers against my advisor's will?
How should I respond to a player wanting to catch a sword between their hands?
Working around an AWS network ACL rule limit
Can I throw a longsword at someone?
LVM Ontop of LUKS using Grub
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionVery poor read performance compared to write performance on md(raid1) / crypt(luks) / lvmGrub-install: embedding is not possible in Bios/GPTGRUB doesn't find /boot in LVMGrub disable recovery not working on detected OSNixOS installation on multi-boot system with GRUB (from Arch installation)Macbook pro retina 2013 with full disk encryption boot issueChainloading in LUKS on LVM from ESPInstalling GRUB to encrypted partition doesn't work if (root) is F2FSRemoving the swap partition from a LUKS encrypted SSDDUbuntu 18.04 LUKS boot problems
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
What am I trying to do?
Install Arch with full system encryption (sans boot and media partition) using LVM on top of LUKS on an external hard drive (sdb)
using: http://suddenkernelpanic.blogspot.com/2013/03/arch-linux-lvm-on-top-of-luks-2013-style.html
What is my problem:
System boots grub and it appears there is some confusion on where to find root
Error: Device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d' not found. skipping fsck
Error: Unable to find root device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d'
Where I deviated from this tutorial
I used Grub Instead of Syslinux as the tutorial suggests (This seems to be the crux) and it's really hazy on the solution for Grub
My partition scheme consists of an extra FAT32 partition that is not involved in the encryption (seems irrelevant to the issue)
Issues on /etc/default/grub:
(I feel like this is where the issue is)
From what I've read I need to update a couple of places in this file specifically:
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
and I'm supposed to uncomment:
GRUB_DISABLE_LINUX_UUID=true
Issues on /etc/mkinitcpio.conf
I'm supposed to add the hooks as follows
HOOKS="... encrypt lvm2 ... filesystems ..."
Here's my fstab entry for root
<filesystem>
/dev/mapper/lvmpool-root
UUID=f7153c4b-e6ea-48a2-9ee1-bf38c037173d / ext4 rw,relatime,data=ordered 0 1
Current Work-Around
I can still use the system because after it errors out, it drops me into a recovery shell, at which type I can simply do a:
cryptsetup luksOpen /dev/sdb2 crypt
enter password
Then exit recovery shell and it drops me back into a normal arch login prompt.
This wouldn't be so bad, if it weren't so time consuming... (Takes forever to error out on boot, like 20 seconds)
Other Resources I tried
I have also used:
wiki.archlinux.org/index.php/Beginners%27_guide
wiki.archlinux.org/index.php/Gr … encryption
wiki.archlinux.org/index.php/Dm … oot_loader
wiki.archlinux.org/index.php/Dm … VM_on_LUKS
arch-linux grub luks lvm
add a comment |
What am I trying to do?
Install Arch with full system encryption (sans boot and media partition) using LVM on top of LUKS on an external hard drive (sdb)
using: http://suddenkernelpanic.blogspot.com/2013/03/arch-linux-lvm-on-top-of-luks-2013-style.html
What is my problem:
System boots grub and it appears there is some confusion on where to find root
Error: Device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d' not found. skipping fsck
Error: Unable to find root device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d'
Where I deviated from this tutorial
I used Grub Instead of Syslinux as the tutorial suggests (This seems to be the crux) and it's really hazy on the solution for Grub
My partition scheme consists of an extra FAT32 partition that is not involved in the encryption (seems irrelevant to the issue)
Issues on /etc/default/grub:
(I feel like this is where the issue is)
From what I've read I need to update a couple of places in this file specifically:
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
and I'm supposed to uncomment:
GRUB_DISABLE_LINUX_UUID=true
Issues on /etc/mkinitcpio.conf
I'm supposed to add the hooks as follows
HOOKS="... encrypt lvm2 ... filesystems ..."
Here's my fstab entry for root
<filesystem>
/dev/mapper/lvmpool-root
UUID=f7153c4b-e6ea-48a2-9ee1-bf38c037173d / ext4 rw,relatime,data=ordered 0 1
Current Work-Around
I can still use the system because after it errors out, it drops me into a recovery shell, at which type I can simply do a:
cryptsetup luksOpen /dev/sdb2 crypt
enter password
Then exit recovery shell and it drops me back into a normal arch login prompt.
This wouldn't be so bad, if it weren't so time consuming... (Takes forever to error out on boot, like 20 seconds)
Other Resources I tried
I have also used:
wiki.archlinux.org/index.php/Beginners%27_guide
wiki.archlinux.org/index.php/Gr … encryption
wiki.archlinux.org/index.php/Dm … oot_loader
wiki.archlinux.org/index.php/Dm … VM_on_LUKS
arch-linux grub luks lvm
add a comment |
What am I trying to do?
Install Arch with full system encryption (sans boot and media partition) using LVM on top of LUKS on an external hard drive (sdb)
using: http://suddenkernelpanic.blogspot.com/2013/03/arch-linux-lvm-on-top-of-luks-2013-style.html
What is my problem:
System boots grub and it appears there is some confusion on where to find root
Error: Device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d' not found. skipping fsck
Error: Unable to find root device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d'
Where I deviated from this tutorial
I used Grub Instead of Syslinux as the tutorial suggests (This seems to be the crux) and it's really hazy on the solution for Grub
My partition scheme consists of an extra FAT32 partition that is not involved in the encryption (seems irrelevant to the issue)
Issues on /etc/default/grub:
(I feel like this is where the issue is)
From what I've read I need to update a couple of places in this file specifically:
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
and I'm supposed to uncomment:
GRUB_DISABLE_LINUX_UUID=true
Issues on /etc/mkinitcpio.conf
I'm supposed to add the hooks as follows
HOOKS="... encrypt lvm2 ... filesystems ..."
Here's my fstab entry for root
<filesystem>
/dev/mapper/lvmpool-root
UUID=f7153c4b-e6ea-48a2-9ee1-bf38c037173d / ext4 rw,relatime,data=ordered 0 1
Current Work-Around
I can still use the system because after it errors out, it drops me into a recovery shell, at which type I can simply do a:
cryptsetup luksOpen /dev/sdb2 crypt
enter password
Then exit recovery shell and it drops me back into a normal arch login prompt.
This wouldn't be so bad, if it weren't so time consuming... (Takes forever to error out on boot, like 20 seconds)
Other Resources I tried
I have also used:
wiki.archlinux.org/index.php/Beginners%27_guide
wiki.archlinux.org/index.php/Gr … encryption
wiki.archlinux.org/index.php/Dm … oot_loader
wiki.archlinux.org/index.php/Dm … VM_on_LUKS
arch-linux grub luks lvm
What am I trying to do?
Install Arch with full system encryption (sans boot and media partition) using LVM on top of LUKS on an external hard drive (sdb)
using: http://suddenkernelpanic.blogspot.com/2013/03/arch-linux-lvm-on-top-of-luks-2013-style.html
What is my problem:
System boots grub and it appears there is some confusion on where to find root
Error: Device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d' not found. skipping fsck
Error: Unable to find root device 'uuid=f7153c4b-e6ea-48a2-9ee1-bf38c037173d'
Where I deviated from this tutorial
I used Grub Instead of Syslinux as the tutorial suggests (This seems to be the crux) and it's really hazy on the solution for Grub
My partition scheme consists of an extra FAT32 partition that is not involved in the encryption (seems irrelevant to the issue)
Issues on /etc/default/grub:
(I feel like this is where the issue is)
From what I've read I need to update a couple of places in this file specifically:
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
and I'm supposed to uncomment:
GRUB_DISABLE_LINUX_UUID=true
Issues on /etc/mkinitcpio.conf
I'm supposed to add the hooks as follows
HOOKS="... encrypt lvm2 ... filesystems ..."
Here's my fstab entry for root
<filesystem>
/dev/mapper/lvmpool-root
UUID=f7153c4b-e6ea-48a2-9ee1-bf38c037173d / ext4 rw,relatime,data=ordered 0 1
Current Work-Around
I can still use the system because after it errors out, it drops me into a recovery shell, at which type I can simply do a:
cryptsetup luksOpen /dev/sdb2 crypt
enter password
Then exit recovery shell and it drops me back into a normal arch login prompt.
This wouldn't be so bad, if it weren't so time consuming... (Takes forever to error out on boot, like 20 seconds)
Other Resources I tried
I have also used:
wiki.archlinux.org/index.php/Beginners%27_guide
wiki.archlinux.org/index.php/Gr … encryption
wiki.archlinux.org/index.php/Dm … oot_loader
wiki.archlinux.org/index.php/Dm … VM_on_LUKS
arch-linux grub luks lvm
arch-linux grub luks lvm
edited 17 hours ago
Rui F Ribeiro
42.1k1483142
42.1k1483142
asked Oct 11 '14 at 3:16
CyberpsychosisCyberpsychosis
6317
6317
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Your problem seems to be in the difference of :crypt
as volume group for /dev/sdb2
and using lvmpool-
as volumegroup name as parameter for root.
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
The example here:
cryptdevice=/dev/partition:MyStorage root=/dev/mapper/MyStorage-rootvol
has matching :MyStorage
and MyStorage-
. That page specifically targets grub
(and not Syslinux), with LVM on top of LUKS. So I would follow that set up.
That you have an extra, not encrypted partition, doesn't matter.
1
This is what keeps getting me. When they state things like "partition" do they mean SDB2 or SDB and does "Mystorage" mean LVMpool or Crypt or what? Those words are just so friggin' vague
– Cyberpsychosis
Oct 11 '14 at 16:14
In "Preparing the logical volumes" it says that MyStorage is the Volume Group and rootvol the Logical Volume
– Anthon
Oct 11 '14 at 16:42
add a comment |
Thank you Anthon for your answer above, it greatly contributed to solving my problem.
It seems the solution to my issue was two parts.
- The entry in /etc/default/grub, for me should read:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdb2:lvmpool root=/dev/mapper/lvmpool-root"
To break down each entry:
cryptdevice consists of the partition you applied the encryption too, in my case /dev/sdb2 and lvmpool (my volume group)
root is simply pointing to the location of my encrypted root lvmpool (which is located on sdb2)
- After that entry is made (and this was a key mistake for me) you must run:
grub-mkconfig -o /boot/grub/grub.cfg
This will update your /boot/grub/grub.cfg with the information you added to /etc/default/grub.
After I did that, the system booted straight into the prompt to unlock the root partition.
add a comment |
include in mkinitcpio.conf
MODULES="dm_mod dm_crypt ext4 aes_x86_64 sha256 sha512"
HOOKS="... encrypt lvm2 ..."
include in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="... quiet "
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdX:name"
GRUB_ENABLE_CRYPTODISK="y"
run command:
sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-install --recheck --target=i386-pc /dev/sda
sudo pacman -S linux linux-headers
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%2f160504%2flvm-ontop-of-luks-using-grub%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your problem seems to be in the difference of :crypt
as volume group for /dev/sdb2
and using lvmpool-
as volumegroup name as parameter for root.
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
The example here:
cryptdevice=/dev/partition:MyStorage root=/dev/mapper/MyStorage-rootvol
has matching :MyStorage
and MyStorage-
. That page specifically targets grub
(and not Syslinux), with LVM on top of LUKS. So I would follow that set up.
That you have an extra, not encrypted partition, doesn't matter.
1
This is what keeps getting me. When they state things like "partition" do they mean SDB2 or SDB and does "Mystorage" mean LVMpool or Crypt or what? Those words are just so friggin' vague
– Cyberpsychosis
Oct 11 '14 at 16:14
In "Preparing the logical volumes" it says that MyStorage is the Volume Group and rootvol the Logical Volume
– Anthon
Oct 11 '14 at 16:42
add a comment |
Your problem seems to be in the difference of :crypt
as volume group for /dev/sdb2
and using lvmpool-
as volumegroup name as parameter for root.
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
The example here:
cryptdevice=/dev/partition:MyStorage root=/dev/mapper/MyStorage-rootvol
has matching :MyStorage
and MyStorage-
. That page specifically targets grub
(and not Syslinux), with LVM on top of LUKS. So I would follow that set up.
That you have an extra, not encrypted partition, doesn't matter.
1
This is what keeps getting me. When they state things like "partition" do they mean SDB2 or SDB and does "Mystorage" mean LVMpool or Crypt or what? Those words are just so friggin' vague
– Cyberpsychosis
Oct 11 '14 at 16:14
In "Preparing the logical volumes" it says that MyStorage is the Volume Group and rootvol the Logical Volume
– Anthon
Oct 11 '14 at 16:42
add a comment |
Your problem seems to be in the difference of :crypt
as volume group for /dev/sdb2
and using lvmpool-
as volumegroup name as parameter for root.
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
The example here:
cryptdevice=/dev/partition:MyStorage root=/dev/mapper/MyStorage-rootvol
has matching :MyStorage
and MyStorage-
. That page specifically targets grub
(and not Syslinux), with LVM on top of LUKS. So I would follow that set up.
That you have an extra, not encrypted partition, doesn't matter.
Your problem seems to be in the difference of :crypt
as volume group for /dev/sdb2
and using lvmpool-
as volumegroup name as parameter for root.
GRUB_CMDLINE_LINUX="root=/dev/mapper/lvmpool-root cryptdevice=/dev/sdb2:crypt ro"
The example here:
cryptdevice=/dev/partition:MyStorage root=/dev/mapper/MyStorage-rootvol
has matching :MyStorage
and MyStorage-
. That page specifically targets grub
(and not Syslinux), with LVM on top of LUKS. So I would follow that set up.
That you have an extra, not encrypted partition, doesn't matter.
edited Oct 11 '14 at 6:57
answered Oct 11 '14 at 6:25
AnthonAnthon
61.7k17107171
61.7k17107171
1
This is what keeps getting me. When they state things like "partition" do they mean SDB2 or SDB and does "Mystorage" mean LVMpool or Crypt or what? Those words are just so friggin' vague
– Cyberpsychosis
Oct 11 '14 at 16:14
In "Preparing the logical volumes" it says that MyStorage is the Volume Group and rootvol the Logical Volume
– Anthon
Oct 11 '14 at 16:42
add a comment |
1
This is what keeps getting me. When they state things like "partition" do they mean SDB2 or SDB and does "Mystorage" mean LVMpool or Crypt or what? Those words are just so friggin' vague
– Cyberpsychosis
Oct 11 '14 at 16:14
In "Preparing the logical volumes" it says that MyStorage is the Volume Group and rootvol the Logical Volume
– Anthon
Oct 11 '14 at 16:42
1
1
This is what keeps getting me. When they state things like "partition" do they mean SDB2 or SDB and does "Mystorage" mean LVMpool or Crypt or what? Those words are just so friggin' vague
– Cyberpsychosis
Oct 11 '14 at 16:14
This is what keeps getting me. When they state things like "partition" do they mean SDB2 or SDB and does "Mystorage" mean LVMpool or Crypt or what? Those words are just so friggin' vague
– Cyberpsychosis
Oct 11 '14 at 16:14
In "Preparing the logical volumes" it says that MyStorage is the Volume Group and rootvol the Logical Volume
– Anthon
Oct 11 '14 at 16:42
In "Preparing the logical volumes" it says that MyStorage is the Volume Group and rootvol the Logical Volume
– Anthon
Oct 11 '14 at 16:42
add a comment |
Thank you Anthon for your answer above, it greatly contributed to solving my problem.
It seems the solution to my issue was two parts.
- The entry in /etc/default/grub, for me should read:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdb2:lvmpool root=/dev/mapper/lvmpool-root"
To break down each entry:
cryptdevice consists of the partition you applied the encryption too, in my case /dev/sdb2 and lvmpool (my volume group)
root is simply pointing to the location of my encrypted root lvmpool (which is located on sdb2)
- After that entry is made (and this was a key mistake for me) you must run:
grub-mkconfig -o /boot/grub/grub.cfg
This will update your /boot/grub/grub.cfg with the information you added to /etc/default/grub.
After I did that, the system booted straight into the prompt to unlock the root partition.
add a comment |
Thank you Anthon for your answer above, it greatly contributed to solving my problem.
It seems the solution to my issue was two parts.
- The entry in /etc/default/grub, for me should read:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdb2:lvmpool root=/dev/mapper/lvmpool-root"
To break down each entry:
cryptdevice consists of the partition you applied the encryption too, in my case /dev/sdb2 and lvmpool (my volume group)
root is simply pointing to the location of my encrypted root lvmpool (which is located on sdb2)
- After that entry is made (and this was a key mistake for me) you must run:
grub-mkconfig -o /boot/grub/grub.cfg
This will update your /boot/grub/grub.cfg with the information you added to /etc/default/grub.
After I did that, the system booted straight into the prompt to unlock the root partition.
add a comment |
Thank you Anthon for your answer above, it greatly contributed to solving my problem.
It seems the solution to my issue was two parts.
- The entry in /etc/default/grub, for me should read:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdb2:lvmpool root=/dev/mapper/lvmpool-root"
To break down each entry:
cryptdevice consists of the partition you applied the encryption too, in my case /dev/sdb2 and lvmpool (my volume group)
root is simply pointing to the location of my encrypted root lvmpool (which is located on sdb2)
- After that entry is made (and this was a key mistake for me) you must run:
grub-mkconfig -o /boot/grub/grub.cfg
This will update your /boot/grub/grub.cfg with the information you added to /etc/default/grub.
After I did that, the system booted straight into the prompt to unlock the root partition.
Thank you Anthon for your answer above, it greatly contributed to solving my problem.
It seems the solution to my issue was two parts.
- The entry in /etc/default/grub, for me should read:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdb2:lvmpool root=/dev/mapper/lvmpool-root"
To break down each entry:
cryptdevice consists of the partition you applied the encryption too, in my case /dev/sdb2 and lvmpool (my volume group)
root is simply pointing to the location of my encrypted root lvmpool (which is located on sdb2)
- After that entry is made (and this was a key mistake for me) you must run:
grub-mkconfig -o /boot/grub/grub.cfg
This will update your /boot/grub/grub.cfg with the information you added to /etc/default/grub.
After I did that, the system booted straight into the prompt to unlock the root partition.
answered Oct 11 '14 at 18:25
CyberpsychosisCyberpsychosis
6317
6317
add a comment |
add a comment |
include in mkinitcpio.conf
MODULES="dm_mod dm_crypt ext4 aes_x86_64 sha256 sha512"
HOOKS="... encrypt lvm2 ..."
include in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="... quiet "
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdX:name"
GRUB_ENABLE_CRYPTODISK="y"
run command:
sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-install --recheck --target=i386-pc /dev/sda
sudo pacman -S linux linux-headers
add a comment |
include in mkinitcpio.conf
MODULES="dm_mod dm_crypt ext4 aes_x86_64 sha256 sha512"
HOOKS="... encrypt lvm2 ..."
include in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="... quiet "
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdX:name"
GRUB_ENABLE_CRYPTODISK="y"
run command:
sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-install --recheck --target=i386-pc /dev/sda
sudo pacman -S linux linux-headers
add a comment |
include in mkinitcpio.conf
MODULES="dm_mod dm_crypt ext4 aes_x86_64 sha256 sha512"
HOOKS="... encrypt lvm2 ..."
include in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="... quiet "
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdX:name"
GRUB_ENABLE_CRYPTODISK="y"
run command:
sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-install --recheck --target=i386-pc /dev/sda
sudo pacman -S linux linux-headers
include in mkinitcpio.conf
MODULES="dm_mod dm_crypt ext4 aes_x86_64 sha256 sha512"
HOOKS="... encrypt lvm2 ..."
include in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="... quiet "
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sdX:name"
GRUB_ENABLE_CRYPTODISK="y"
run command:
sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo grub-install --recheck --target=i386-pc /dev/sda
sudo pacman -S linux linux-headers
edited Aug 9 '15 at 20:19
don_crissti
52k15141169
52k15141169
answered Aug 9 '15 at 20:15
user161348user161348
1
1
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.
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%2f160504%2flvm-ontop-of-luks-using-grub%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
-arch-linux, grub, luks, lvm