The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Rootfs over encrypted lvm"
(40 intermediate revisions by the same user not shown) | |||
Line 10: | Line 10: | ||
<console> | <console> | ||
## | # ##i##dd if=/dev/zero of=/dev/sda3 bs=100M | ||
# ##i##dd if=/dev/urandom of=/dev/sda3 bs=100M | |||
</console> | </console> | ||
The <code>dd</code> part is optional, only for security | The <code>dd</code> part is optional, and the command only needs to be run for security reasons (i.e only if you had top secret files on your drive). The command overwrites the lingering data on the device with random data. It takes around 6 hours to complete for a 200GB drive. | ||
Note | {{Note}} You will get a message about reaching the end of the device when the <code>dd</code> command has finished. This behavior is intended. | ||
= Encrypting the drive = | = Encrypting the drive = | ||
<console> | <console> | ||
## | # ##i##cryptsetup --cipher aes-xts-plain64 luksFormat /dev/sda3 | ||
# ##i##cryptsetup luksOpen /dev/sda3 dmcrypt_root | |||
</console> | </console> | ||
Line 28: | Line 27: | ||
= Create logical volumes = | = Create logical volumes = | ||
<console> | <console> | ||
## | # ##i##pvcreate /dev/mapper/dmcrypt_root | ||
# ##i##vgcreate vg /dev/mapper/dmcrypt_root | |||
# ##i##lvcreate -L10G --name root vg | |||
# ##i##lvcreate -L2G --name swap vg | |||
# ##i##lvcreate -L5G --name portage vg | |||
# ##i##lvcreate -l 100%FREE -nhome vg | |||
</console> | </console> | ||
Feel free to specify your desired size by altering the numbers after the -L flag. For example, to make your portage dataset 20GB's, use the flag -L20G instead of -L5G. | Feel free to specify your desired size by altering the numbers after the -L flag. For example, to make your portage dataset 20GB's, use the flag -L20G instead of -L5G. | ||
Line 39: | Line 38: | ||
= Create a filesystem on volumes = | = Create a filesystem on volumes = | ||
<console> | <console> | ||
## | # ##i##mkfs.ext2 /dev/sda1 | ||
# ##i##mkswap /dev/mapper/vg-swap | |||
# ##i##mkfs.ext4 /dev/mapper/vg-root | |||
# ##i##mkfs.ext4 /dev/mapper/vg-portage | |||
# ##i##mkfs.ext4 /dev/mapper/vg-home | |||
</console> | </console> | ||
= Basic system setup = | = Basic system setup = | ||
<console> | <console> | ||
## | # ##i##swapon /dev/mapper/vg-swap | ||
# ##i##mkdir /mnt/funtoo | |||
# ##i##mount /dev/mapper/vg-root /mnt/funtoo | |||
# ##i##mkdir -p /mnt/funtoo/{boot,usr/portage,home} | |||
# ##i##mount /dev/sda1 /mnt/funtoo/boot | |||
# ##i##mount /dev/mapper/vg-portage /mnt/funtoo/usr/portage | |||
# ##i##mount /dev/mapper/vg-home /mnt/funtoo/home | |||
## | |||
</console> | </console> | ||
Now perform all the steps required for basic system install, please follow [http://docs.funtoo.org/wiki/Funtoo_Linux_Installation] | Now perform all the steps required for basic system install, please follow [http://docs.funtoo.org/wiki/Funtoo_Linux_Installation] | ||
don't forget to emerge | don't forget to emerge the following before your install is finished: | ||
* '''cryptsetup''' | |||
* '''lvm2''' | |||
* '''a bootloader (grub recommended)''' | |||
* '''kernel sources (gentoo-sources recommended)''' | |||
= Editing the fstab = | |||
Fire up your favorite text editor to edit <code>/etc/fstab</code>. You want to put the following in the file: | |||
<pre> | |||
# <fs> <mountpoint> <type> <opts> <dump/pass> | |||
/dev/sda1 /boot ext2 noauto,noatime 1 2 | |||
/dev/mapper/vg-swap none swap sw 0 0 | |||
/dev/mapper/vg-root / ext4 noatime,nodiratime,defaults 0 1 | |||
/dev/sr0 /mnt/cdrom auto noauto,ro 0 0 | |||
/dev/mapper/vg-portage /usr/portage ext4 noatime,nodiratime 0 0 | |||
/dev/mapper/vg-home /home ext4 noatime,nodiratime 0 0 | |||
</pre> | |||
= Kernel options = | = Kernel options = | ||
{{Note}}This part is particularly important: pay close attention. | |||
{{kernelop | |||
|'''General setup --->''' | |||
|'''[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support''' | |||
}} | |||
{{kernelop | |||
< | |'''Device Drivers --->''' <br> '''Generic Driver Options --->''' | ||
|'''[*] Maintain a devtmpfs filesystem to mount at /dev''' <br> | |||
}} | |||
{{kernelop | |||
< | |'''Device Drivers --->''' <br> '''[*] Multiple devices driver support --->''' | ||
|'''<*>Device Mapper Support''' <br> '''<*> Crypt target support''' | |||
}} | |||
<*> XTS support | {{kernelop | ||
|'''Cryptographic API --->''' | |||
|'''-*-AES cipher algorithms''' <br> '''<*> XTS support''' | |||
}} | |||
= Initramfs setup and configuration = | |||
== Better-initramfs == | |||
'''Build your initramfs with [https://bitbucket.org/piotrkarbowski/better-initramfs better-initramfs] project.''' | |||
{{note}}better-initramfs supports neither dynamic modules nor udev, so you should compile your kernel with built-in support for your block devices. | |||
<console> | |||
# ##i##cd /opt | |||
# ##i##git clone git://github.com/slashbeast/better-initramfs.git | |||
# ##i##cd better-initramfs | |||
# ##i##less README.rst | |||
# ##i##bootstrap/bootstrap-all | |||
# ##i##make prepare | |||
# ##i##make image | |||
</console> | |||
< | Copy resulting <code>initramfs.cpio.gz</code> to <code>/boot</code>: | ||
# | <console># ##i##cp output/initramfs.cpio.gz /boot</console> | ||
# | |||
# | |||
# | |||
# | |||
</ | |||
Alternatively, a pre-compiled binary initramfs is available at https://bitbucket.org/piotrkarbowski/better-initramfs/downloads | |||
<console> | |||
# ##i##wget https://bitbucket.org/piotrkarbowski/better-initramfs/downloads/release-x86_64-v0.7.2.tar.bz2 | |||
Alternatively pre-compiled binary initramfs available at https://bitbucket.org/piotrkarbowski/better-initramfs/downloads | # ##i##tar xf release-x86_64-v0.5.tar.bz2 | ||
< | # ##i##cd release* | ||
# tar xf release-x86_64-v0.5.tar.bz2 | # ##i##gzip initramfs.cpio | ||
# cd release* | # ##i##cp initramfs.cpio.gz /boot | ||
# gzip initramfs.cpio | </console> | ||
# cp initramfs.cpio.gz /boot</ | |||
Remember, better-initramfs project is a work in progress, so you need to update from time to time. It can be done easily with <code>git</code>. Go to the better-initramfs source dir and follow: | Remember, better-initramfs project is a work in progress, so you need to update from time to time. It can be done easily with <code>git</code>. Go to the better-initramfs source dir and follow: | ||
< | <console> | ||
# less ChangeLog | # ##i##cd /opt/better-initramfs | ||
</ | # ##i##git pull | ||
Please | # ##i##less ChangeLog | ||
</console> | |||
{{Note}}Please read the ChangeLog carefuly and perform necessary updates to <code>/etc/boot.conf</code>. Also, please backup the working <code>/boot/initramfs.cpio.gz</code> and <code>/etc/boot.conf</code> before updating better-initramfs. | |||
= Genkernel | == Genkernel == | ||
Funtoo's genkernel capable to create initramfs for encrypted drive. Compile and install kernel and initramfs of your favorite kernel sources: | Funtoo's genkernel capable to create initramfs for encrypted drive. Compile and install kernel and initramfs of your favorite kernel sources: | ||
< | <console> | ||
# ##i##genkernel --kernel-config=/path/to/your/custom-kernel-config --no-mrproper --makeopts=-j5 --install --lvm --luks all </console> | |||
Configure the bootloader as described above, with correct kernel and initramfs images names. An example for genkernel and grub2: | Configure the bootloader as described above, with correct kernel and initramfs images names. An example for genkernel and grub2: | ||
Line 127: | Line 148: | ||
kernel kernel-genkernel-x86_64-2.6.39 | kernel kernel-genkernel-x86_64-2.6.39 | ||
initrd initramfs-genkernel-x86_64-2.6.39 | initrd initramfs-genkernel-x86_64-2.6.39 | ||
params += crypt_root=/dev/ | params += crypt_root=/dev/sda3 dolvm real_root=/dev/mapper/vg-root rootfstype=ext4 resume=swap:/dev/mapper/vg-swap quiet | ||
}</pre>}} | }</pre>}} | ||
= Grub2 configuration = | |||
= Bootloader Configuration = | |||
== Grub2 configuration == | |||
An example of <code>/etc/boot.conf</code> for better-initramfs | An example of <code>/etc/boot.conf</code> for better-initramfs | ||
{{code|/etc/boot.conf|<pre> | {{code|/etc/boot.conf|<pre> | ||
Line 141: | Line 164: | ||
kernel bzImage[-v] | kernel bzImage[-v] | ||
initrd /initramfs.cpio.gz | initrd /initramfs.cpio.gz | ||
params += enc_root=/dev/ | params += enc_root=/dev/sda3 lvm luks root=/dev/mapper/vg-root rootfstype=ext4 resume=swap:/dev/mapper/vg-swap quiet | ||
}</pre>}} | }</pre>}} | ||
Now, run <code>boot-update</code> to write the configuration files to <code>/boot/grub/grub.cfg</code> | |||
/ | |||
= Lilo configuration = | == Lilo configuration == | ||
For oldschool geeks, an example for lilo bootloader. Emerge lilo with device-mapper support | For oldschool geeks, an example for lilo bootloader. Emerge lilo with device-mapper support | ||
< | <console> | ||
# echo 'sys-boot/lilo device-mapper' >> /etc/portage/package.use/lilo | # ##i##echo 'sys-boot/lilo device-mapper' >> /etc/portage/package.use/lilo | ||
# emerge lilo</ | # ##i##emerge lilo | ||
</console> | |||
{{code|/etc/lilo.conf|<pre>append="init=/linuxrc dolvm crypt_root=/dev/sda2 real_root=/dev/mapper/vg-root" | {{code|/etc/lilo.conf|<pre>append="init=/linuxrc dolvm crypt_root=/dev/sda2 real_root=/dev/mapper/vg-root" | ||
Line 172: | Line 188: | ||
label=funtoo | label=funtoo | ||
</pre>}} | </pre>}} | ||
= Syslinux bootloader setup = | |||
Syslinux is another advanced bootloader which you can find on all live CD's. | == Syslinux bootloader setup == | ||
Syslinux is another advanced bootloader which you can find on all live CD's. Syslinux bootloader does not require additional BIOS boot partition. /dev/sda2 is the root partition. | |||
<pre> | <pre> | ||
# emerge syslinux | # emerge syslinux | ||
Line 191: | Line 208: | ||
= Final steps = | = Final steps = | ||
Umount everything, close encrypted drive and reboot | Umount everything, close encrypted drive and reboot | ||
< | <console> | ||
vgchange -a n | # ##i##umount -l -v /mnt/funtoo/{dev, proc, home, usr/portage, boot} | ||
cryptsetup luksClose /dev/sda2 dmcrypt_root</ | # ##i##vgchange -a n | ||
# ##i##cryptsetup luksClose /dev/sda2 dmcrypt_root | |||
</console> | |||
After reboot you will get the following: | After reboot you will get the following: | ||
<pre>>>> better-initramfs started. Kernel version 2.6.35-gentoo-r10 | <pre>>>> better-initramfs started. Kernel version 2.6.35-gentoo-r10 | ||
Line 226: | Line 245: | ||
* [[gentoo-wiki:Root filesystem over LVM2, DM-Crypt and RAID|Root filesystem over LVM2, DM-Crypt, and RAID]] | * [[gentoo-wiki:Root filesystem over LVM2, DM-Crypt and RAID|Root filesystem over LVM2, DM-Crypt, and RAID]] | ||
* [http://wiki.archlinux.org/index.php/System_Encryption_with_LUKS_for_dm-crypt System Encryption with LUKS for dm-crypt] | * [http://wiki.archlinux.org/index.php/System_Encryption_with_LUKS_for_dm-crypt System Encryption with LUKS for dm-crypt] | ||
* [http://en.wikipedia.org/wiki/Logical_volume_management Wikipedia article on LVM] | |||
* [https://wiki.archlinux.org/index.php/Dm-crypt_with_LUKS Arch Wiki article] | |||
[[Category:HOWTO]] | [[Category:HOWTO]] |
Revision as of 15:55, December 10, 2013
This howto describes how to setup LVM and rootfs with cryptoLUKS-encrypted drive
Prepare the hard drive and partitions
This is an example partition scheme, you may want to choose differently.
/dev/sda1
used as /boot
. /dev/sda2
will be encrypted drive with LVM.
/dev/sda1
--/boot
partition./dev/sda2
-- BIOS boot partition (not needed for MBR - only needed if you are using GPT) This step required for GRUB2. For more info, see: [1] for more information on GPT and MBR./dev/sda3
--/
partition, will be the drive with LUKS and LVM.
root # dd if=/dev/zero of=/dev/sda3 bs=100M root # dd if=/dev/urandom of=/dev/sda3 bs=100M
The dd
part is optional, and the command only needs to be run for security reasons (i.e only if you had top secret files on your drive). The command overwrites the lingering data on the device with random data. It takes around 6 hours to complete for a 200GB drive.
{{{1}}}
You will get a message about reaching the end of the device when the dd
command has finished. This behavior is intended.
Encrypting the drive
root # cryptsetup --cipher aes-xts-plain64 luksFormat /dev/sda3 root # cryptsetup luksOpen /dev/sda3 dmcrypt_root
There you'll be prompted to enter your password phrase for encrypted drive, type your paranoid password there.
Create logical volumes
root # pvcreate /dev/mapper/dmcrypt_root root # vgcreate vg /dev/mapper/dmcrypt_root root # lvcreate -L10G --name root vg root # lvcreate -L2G --name swap vg root # lvcreate -L5G --name portage vg root # lvcreate -l 100%FREE -nhome vg
Feel free to specify your desired size by altering the numbers after the -L flag. For example, to make your portage dataset 20GB's, use the flag -L20G instead of -L5G.
Create a filesystem on volumes
root # mkfs.ext2 /dev/sda1 root # mkswap /dev/mapper/vg-swap root # mkfs.ext4 /dev/mapper/vg-root root # mkfs.ext4 /dev/mapper/vg-portage root # mkfs.ext4 /dev/mapper/vg-home
Basic system setup
root # swapon /dev/mapper/vg-swap root # mkdir /mnt/funtoo root # mount /dev/mapper/vg-root /mnt/funtoo root # mkdir -p /mnt/funtoo/{boot,usr/portage,home} root # mount /dev/sda1 /mnt/funtoo/boot root # mount /dev/mapper/vg-portage /mnt/funtoo/usr/portage root # mount /dev/mapper/vg-home /mnt/funtoo/home
Now perform all the steps required for basic system install, please follow [2] don't forget to emerge the following before your install is finished:
- cryptsetup
- lvm2
- a bootloader (grub recommended)
- kernel sources (gentoo-sources recommended)
Editing the fstab
Fire up your favorite text editor to edit /etc/fstab
. You want to put the following in the file:
# <fs> <mountpoint> <type> <opts> <dump/pass> /dev/sda1 /boot ext2 noauto,noatime 1 2 /dev/mapper/vg-swap none swap sw 0 0 /dev/mapper/vg-root / ext4 noatime,nodiratime,defaults 0 1 /dev/sr0 /mnt/cdrom auto noauto,ro 0 0 /dev/mapper/vg-portage /usr/portage ext4 noatime,nodiratime 0 0 /dev/mapper/vg-home /home ext4 noatime,nodiratime 0 0
Kernel options
{{{1}}}
This part is particularly important: pay close attention.
Initramfs setup and configuration
Better-initramfs
Build your initramfs with better-initramfs project.
{{{1}}}
better-initramfs supports neither dynamic modules nor udev, so you should compile your kernel with built-in support for your block devices.
root # cd /opt root # git clone git://github.com/slashbeast/better-initramfs.git root # cd better-initramfs root # less README.rst root # bootstrap/bootstrap-all root # make prepare root # make image
Copy resulting initramfs.cpio.gz
to /boot
:
root # cp output/initramfs.cpio.gz /boot
Alternatively, a pre-compiled binary initramfs is available at https://bitbucket.org/piotrkarbowski/better-initramfs/downloads
root # wget https://bitbucket.org/piotrkarbowski/better-initramfs/downloads/release-x86_64-v0.7.2.tar.bz2 root # tar xf release-x86_64-v0.5.tar.bz2 root # cd release* root # gzip initramfs.cpio root # cp initramfs.cpio.gz /boot
Remember, better-initramfs project is a work in progress, so you need to update from time to time. It can be done easily with git
. Go to the better-initramfs source dir and follow:
root # cd /opt/better-initramfs root # git pull root # less ChangeLog
{{{1}}}
Please read the ChangeLog carefuly and perform necessary updates to /etc/boot.conf
. Also, please backup the working /boot/initramfs.cpio.gz
and /etc/boot.conf
before updating better-initramfs.
Genkernel
Funtoo's genkernel capable to create initramfs for encrypted drive. Compile and install kernel and initramfs of your favorite kernel sources:
root # genkernel --kernel-config=/path/to/your/custom-kernel-config --no-mrproper --makeopts=-j5 --install --lvm --luks all
Configure the bootloader as described above, with correct kernel and initramfs images names. An example for genkernel and grub2:
Bootloader Configuration
Grub2 configuration
An example of /etc/boot.conf
for better-initramfs
Template:Code
Now, run boot-update
to write the configuration files to /boot/grub/grub.cfg
Lilo configuration
For oldschool geeks, an example for lilo bootloader. Emerge lilo with device-mapper support
root # echo 'sys-boot/lilo device-mapper' >> /etc/portage/package.use/lilo root # emerge lilo
Syslinux bootloader setup
Syslinux is another advanced bootloader which you can find on all live CD's. Syslinux bootloader does not require additional BIOS boot partition. /dev/sda2 is the root partition.
# emerge syslinux # mkdir /boot/extlinux # extlinux --install /boot/extlinux # dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda - or - # sgdisk /dev/sda --attributes=1:set:2 # dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda, for GPT partition
Final steps
Umount everything, close encrypted drive and reboot
root # umount -l -v /mnt/funtoo/{dev, proc, home, usr/portage, boot} root # vgchange -a n root # cryptsetup luksClose /dev/sda2 dmcrypt_root
After reboot you will get the following:
>>> better-initramfs started. Kernel version 2.6.35-gentoo-r10 >>> Create all the symlinks to /bin/busybox. >>> Initiating /dev/dir >>> Getting LVM volumes up (if any) Reding all physical volumes. This make take awhile... No volume group found No volume group found >>> Opening encrypted partition and mapping to /dev/mapper/dmcrypt_root Enter passphrase fore /dev/sda2:
Type your password
>>> Again, getting LVM volumes up (if any, after map dmcrypt). Reading all physical volumes. This may take a while... Found volume group "vg" using metadata type lvm2 4 logical volume(s) in volume group "vg" now active >>> Mounting rootfs to /newroot >>> Umounting /sys and /proc. >>> Switching root to /newroot and executing /sbin/init. INIT: version 2.88 booting Loading /libexec/rc/console/keymap OpenRC 0.6.1 is starting up Funtoo Linux (x86_64) ...boot messages omitted for clarity orion login: oleg Password: Last login: Thu Oct 14 20:49:21 EEST 2010 on tty1 oleg@orion ~ %