[Solved] Enlarge logical Volume (LVM on Luks)

I moved my whole system to a new SSD which is bigger than the old one, now I need to enlarge the root partition.
sda3 is my LUKS encrypted partition.
lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 74,5G 0 disk
├─sda1 8:1 0 2M 0 part
├─sda2 8:2 0 200M 0 part /boot
└─sda3 8:3 0 29,6G 0 part
└─MyStorage 254:0 0 29,6G 0 crypt
├─MyStorage-swapvol 254:1 0 1G 0 lvm [SWAP]
└─MyStorage-rootvol 254:2 0 28,6G 0 lvm /
How can I resize sda3, MyStorage and Mystorage-rootvol without loosing data?
I found a post in the ubuntu-Wiki, but didn't quite understand Step 3.
Thanks in advance
Last edited by hasdf (2014-11-23 17:17:38)

frostschutz wrote:Is there free space on the disk to make that partition larger?
If I got you right, there is free space after the partition:
Modell: ATA INTEL SSDSA2M080 (scsi)
Festplatte /dev/sda: 156301488s
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Name Flags
34s 2047s 2014s Freier Platz
1 2048s 6143s 4096s
2 6144s 415743s 409600s ext2
3 415744s 62533262s 62117519s
62533263s 156301454s 93768192s Freier Platz
Thank you for your help! I'll try it and post the result here.
EDIT: I coudn't enlarge the partition like frostschulz said. And since I had to delete the partition in question, I just deleted everything and reinstalled archlinux with a full system backup.
Last edited by hasdf (2014-11-23 17:15:07)

Similar Messages

2 question concerning LVM over LUKS

I succesfully configured LVM over LUKS, but have 2 parts that are not 100% clear to me
My setup is now
/dev/vda1 /boot
/dev/vda2 LVM2 with volumegroup name lvm holding three logical volumes: lvm-root, lvm-home, lvm-swap
The following I am wondering if someone would like to clarify to me
1. For booting I added cryptdevice to my kernel with the following parameter settings
kernel /vmlinuz-linux cryptdevice=/dev/vda2:encrypted root=/dev/mapper/lvm-root ro
It doesn't seems to matter what name I use in the red part of cryptdevice.
So why do I need to put a name in this red part ?? Does it matter at all what name I use here ??
2. I did not fill in anyhting in /etc/crypttab and all seems to be working without issues.
I could have entered something like "encrypted /dev/vda2 none luks" in it....
What good would it do me to enter anything in crypttab ?? When would I really need this to be filled in ??
Hoping someone would mind to explains this to me .... thx

I just started playing with encryption so take what I say with a block of salt.
The name you give is what will show up in /dev/mapper, ie /dev/mapper/encrypted in this case. Since you're using lvm I think you could change the name every boot if you wanted. OTOH, if you formatted the partition directly, you could use the /dev/mapper/encrypted in fstab for example.
On the subject of crypttab I can't help you, except to say that in my experiments with encryption I've never touched it.

[solved] Filesystem check fail - Cannot access LVM Logical Volumes

I am getting a "File System Check Failed"on startup, I recently did a full system upgrade but I'm not entirely sure that the cause of the issue as I don't reboot very often.
I get the error right before this line is echo'ed out:
/dev/mapper/Arch_LVM-Root:
The super block could not be read or does not describe a correct ext2 filesystem...
this is odd because the only ext2 filesystem I have is on an non-LVM boot partition...
I can log-in and mount / as read/write and I can activate LVM with
modprobe dm-mod
and
vgchange -ay Arch_LVM
and they show up in lvdisplay but their status is "NOT available"
I just need to mount these logical volumes so I can retrieve some personal data in my home directory, I am also hesitant to use LVM again if I can't retrieve my data.
any suggestions?
Last edited by action_owl (2010-08-15 02:15:58)

I just popped in the install disk and was able to mount and access the LVM groups as expected, something must have been wonky with my filesystem

RAID on LVM logical volumes

Hey,
i've got a 1T and a 500G hard drive in my workstation. The 500G drive is my media disk. I initialized a software RAID-1 with one missing drive on a 500G logical volume on the 1T disk. After formatting and copying all the data from the media disk over to the new raid partition, I added the old 500G partition to the RAID.
After rebooting my machine, the RAID was in inactive state and hence the filesystem could not be mounted.
I found out, that in /etc/rc.sysinit the search for software RAID arrays is performed before the search for LVM volume groups. I started switching the RAID and LVM sections but after reboot nothing changed. I presume it's caused by the lv devices missing in /proc/partitions, which is used by md to scan for raid members by default.
I decided to add some lines to /etc/rc.local (also my RAID device is /dev/md127 Oo):
mdadm --stop /dev/md127
mdadm --assemble /dev/md127 /dev/vg00/raid-data /dev/sdb1
mount /mnt/raid
It works now, but it is not a clean solution.
How is it supposed to do RAID on top of LVM logical volumes in Arch Linux? Are there any alternative ideas of solutions to this problem (sure there are)?
Thanks in advance.

delcypher wrote:
Hi I've been looking into backing up one of my LVM logical volumes and I came across this (http://www.novell.com/coolsolutions/appnote/19386.html) article.
I'm a little confused by it as it states that "Nice work, your logical volume is now fault tolerant!".
Are you sure that's the article? I can't find anything on that page about "nice work" or "fault tolerant"...?
delcypher wrote:My concern is that because my volumegroup spans across two drives if anyone of them fails I will loose all may data.
Correct.
delcypher wrote:Is there any setup I can do by which I can have a perfect mirror of my volumegroup so that if one of my drives fail I still have a perfectly function volumegroup.
Use 2 disks to create a RAID-1 array, then use that as your PV.
sda1 + sdb1 = md0 => pv
delcypher wrote:I understand linux supports software raid but would I need two drives identically sized (1TB) or can I just have one drive (i.e. 2TB) that is a mirror of my volumegroup?
You can use 2 partitions on the same disk to create a RAID array, but that defeats the whole purpose of RAID.
It sounds like you're merging the meanings of 'redundant' and 'backup' -- they are distinct things, so you need to decide if you want redundancy or backup. Or both ideally.

LVM2 - installer "see" already existing logical volumes [SOLVED]

I've been messing about with LVM for about a week now and ran into a snag with the installer.
Essentially if, for whatever reason, I make my logical volumes, then reboot and start the installer it won't "see" my L.Vols at all. I did the
modprobe dm_mod
before starting and after starting the installer. The result is still the same either way. I ended up removing the L.Vols and re-creating them, then running the installer again. It seems to be the only way I can get the setup scripts to "find" the Logical Volumes properly if the Physical Extent/Volume Group/Logical Volumes pre-existed before invoking /arch/setup.
I searched the installation forum but the closest thing I found was this from a year ago: http://bbs.archlinux.org/viewtopic.php?id=48483. I'm a bit baffled as to how I can get the installation routine to recognise the volumes exist so I don't need re-create things every time I want to do another install. Any advice is appreciated.
*goes to search elsewhere*
MS
Last edited by MoonSwan (2009-04-06 23:11:26)

I think once you've modprobe dm_mod, u should be able to do a bunch of commands to activate existing volume groups and logical volumes. I'm running an lvm setup and it took me ages to suss it all out and get up and running.
You can definitely do an lvscan command which should look for logical volumes and list them for you. I think you can activate them through there too. Does doing any of the following give you anything once you've done the modprobe?
pvdisplay
vgdisplay
lvdisplay
Also
ls -al /dev/mapper (I think) should lisy the devices for lvm tht already exist. Sorry can't be more accurate for you at the mo, am not in front of my linux box. :-(

Extending an LVM Logical Volume to Another Disk

I have read the article in the wiki and also this guide since my drives are encrypted. I have already set up arch on one drive with LVM on top of an encrypted volume (following the linked guide strictly with exceptions on the cipher and the partitioning). So far everything works very well but I'm only halfway where I want to end up. Additional to the one HDD I want to use two more, all of them encrypted (no problem here) and one logical volume spread across all three drives (problem be here).
So, to clarify, on /dev/sda I have two partitions, /boot (unencrypted, 130 MB) and /dev/sda2 (encrypted, ~2TB) on which the LVM volumes are.
/dev/sda2 is added to vgroup and has several logical volumes of which /home is the largest.
On the other hand I have /dev/sdb and /dev/sdc. Both should only contain one encrypted partition and extend /home. That is why I chose LVM in the first place.
I started with /dev/sdc since all the data on it has been backed up already. The entire drive is now one big encrypted partition called /dev/sdc1. I mounted it with sudo cryptsetup luksOpen /dev/sdc1 lvm. And here I am stuck.
1) First of all I'm not entirely clear on the last part "lvm" of that command, I initially thought it would be the name this partition would be mounted under but in the guide I took this from it is not explained and I want to be extra careful here because I have a lot of data on /dev/sda2 that is not backed up and I don't want to accidentally erase the logical volumes I already have.
2) I guess the next part would be creating a physical volume on the mounted partition via lvm pvcreate /dev/mapper/lvm but again I want to be extra clear on this, I really do not want to temper with the volumes I already have unless I know exactly what effects it will have. If I would mount the encrypted partition with sudo cryptsetup luksOpen /dev/sdc1 aaa would I then have to create the physical volume with lvm pvcreate /dev/mapper/aaa? Because I already used lvm when I created all the volumes on the first drive (sda) and I don't know if they are still mounted under the same name (after many reboots and setting up the arch which I am currently using) in which case I might be in danger of overwriting something?
3) From what I have read so far I could extend /home now with lvextend -l +100%FREE vgroup/home, is that correct? After that I would only have to extend the file system (ext4) on /home and it would be done?
I hope it is clear what I am trying to do, if not please do ask. Thanks in advance for reading all of this.

Turns out this is not quite over yet. After successfully dealing with LVM I was about to reboot when something occurred to me: The second HDD (sdc1) will not be decrypted at boot and I have no idea what would happen if LVM tries to mount a volume that is spread across two disks of which one is not available.
So I searched for some time and everything I could find was this thread. Well, he is talking about altering the encrypt hook and generate a new initramfs to be able to enter more than one cryptdevice in grub. I have never dealt with hooks before and never got my hands on bash script like this. Now my options are pretty weak: I could do what he describes although I have no idea how it works or I could revert all the changes to LVM. Naturally I chose option number one, parsed the hook, edited the menu.lst, rebooted and "Waiting 10 seconds for device /dev/sda2".
So yeah it's my fault for trying something I have no clue about.
I tried to access the volumes from the live cd, but even though I decrypted the drives and loaded up lvm with vgchange -a -y I can not access the logical volumes. I naively tried to access the files such as menu.lst but I can't get there. Probably because I just lack the knowledge how to do that. But even if I would be able to access the files, could I build the hooks of my system from within the live cd?
Last edited by venehan_snakes (2011-10-18 16:49:48)

Extending LVM logical volume

Hi I recently added a new hard drive to my computer which had an existing LVM on the first drive.
I created an LVM physical volume on my new hard drive and added it to my existing volume group (volgroup)
pvcreate /dev/sdb1
vgextend volgroup /dev/sdb1
I then proceeded to extend one of LVM logical volumes so that it used all the free space on my volume group (volgroup)
I tried
lvextend -l 100%FREE volgroup/home
but this didn't extend the volume (it stayed the same size)... but
lvextend -l +100%FREE volgroup/home
did. What I don't understand is why. The description of the -l option is as follows
-l, --extents [+]LogicalExtentsNumber[%{VG|LV|PVS|FREE|ORIGIN}]
Extend or set the logical volume size in units of logical extents. With the + sign the value is added to the actual size
of the logical volume and without it, the value is taken as an absolute one. The number can also be expressed as a per‐
centage of the total space in the Volume Group with the suffix %VG, relative to the existing size of the Logical Volume
with the suffix %LV, of the remaining free space for the specified PhysicalVolume(s) with the suffix %PVS, as a percent‐
age of the remaining free space in the Volume Group with the suffix %FREE, or (for a snapshot) as a percentage of the
total space in the Origin Logical Volume with the suffix %ORIGIN.
As far as I can see the "+" only makes sense when setting the logical volume size in units of logical extents. If you're using %FREE that should be the percentage of free space of the volume group.
Any ideas?

--- Logical volume ---
LV Name /dev/volgroup/home
VG Name volgroup
LV UUID PjPjuh-lPuN-j79Z-OIdI-ZniR-NOQT-NiRGbc
LV Write Access read/write
LV Status available
# open 1
LV Size 1.65 TiB
Current LE 433488
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:4
It was originally ~900GiB. Thanks for your explaination.

Linux LVM (Logical Volume Manager) for CentOS on Azure?

Hi. I am trying out Azure and installed a OpenLogic CentOS 6 virtual machine. I note that it is not running LVM (Logical Volume Manager) by default. I would like to ask if it is possible to:
1. have CentOS Linux installed with LVM by default when creating a Linux virtual machine on Azure
2. switch to LVM after adding a new disk
On the other hand, is it a good idea to use LVM at all? Will it affect performance, features on Azure?
Thanks.

Hi,
Based on my experience, you can add disk to an Azure VM. You can install the Logical Volume Manager to manage the disks attached to the VM. In addition, there is no Linux VM with LVM installed by default. If you want to have this, please submit your requirement
in Azure feedback:
http://feedback.azure.com/forums/34192--general-feedback
In addition, since you can have only one OS system disk for an Azure VM, this limitation may make multi-disk logical volume manager setups unworkable.
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Mounting an LVM on Luks Partition [SOLVED]

Hello Arch Linux Community:
This likely sounds like a very stupid question, but I have honestly hit a wall and need some advice. To make a long story short I was messing around in some configuration files and forgot to undo a change that I made before rebooting, which has rendered my system mostly inoperable. (I mistakenly changed the address for Bash in /etc/shells, so I can't log in as either my user or root). Now ordinarily this would be a very simple fix, but for whatever reason it is proving to be far more difficult that I anticipated. My root partition is stored as Logical Volume on a Physical Volume on /dev/sda3 and the entire Volume Group (containing my root, home, swap and var partitions) is locked up with Luks.
I booted my computer to an Arch live CD and attempted to mount the root filesystem, though wasn't exactly sure how to go about doing it (I tried several methods). First I tried just opening the root logical volume and mounting that.
# cryptsetup luksOpen /dev/sda3 rootvol
# mount /dev/mapper/rootvol /mnt
This resulted in the system alerting me that the device I was trying to mount was an LVM2 member and that the system could not do it. So next I tried opening the entire Volume Group.
# cryptsetup luksOpen /dev/sda3 VolGroup00
# mount /dev/mapper/VolGroup00 /mnt
Which, as I expected did not work. However, when I tried to mount the root volume again (having opened the entire Volume Group)
# mount /dev/mapper/VolGroup00-rootvol /mnt
and
# mount /dev/VolGroup00/rootvol /mnt
the system alerted me that the device I was trying to mount did not exist, which is odd considering that running
# lvdisplay /dev/VolGroup00
showed all of my logical volumes to exist at the locations /dev/VolGroup00/foo.
I could really use some guidance here. I know that I'm probably missing something very stupid and obvious, but I cannot for the life of me see it. Thank you for your time.
Douglas Bahr Rumbaugh, Jr.
Last edited by douglasr (2013-06-23 23:14:56)

After the luksOpen I believe you need
vgchange -a y

[SOLVED]using dd to make image backup of logical volume?

I recently got my Ocz Revodrive working under Archlinux by creating logical volumes on it which worked out great, i also got openbox configured to my liking but i want to make an image back up of my Revodrives logical volumes into image files to restore for later use. I was reading the disk cloning wiki about the dd command and just wanted to double check that the dd command below would work ok?
Once i boot into the Arch live usb, and run the following commands it should create an image file on the hard drive mounted under /mnt/backupdata ? Sorry for the straight forward question, i just want to make sure i have the right command before i back up data i dont have a copy of.
dd if=/dev/mapper/VolGroupArray-lvroot of=/mnt/backupdata/test.img bs=16m
dd if=/dev/mapper/VolGroupArray-lvhome of=/mnt/backupdata/test.img bs=16m
Also anyone have any feedback on what blocksize to use for backing up to a standard hard drive, is 16m okay?
Last edited by itzmeluigi (2013-08-05 06:01:54)

Oops heh, i would usually rename it to test1.img and test2.img, i was using it as an example. Once i create the images, would the commands below be the proper way to restore them?
dd if=/mnt/backupdata/test1.img of=/dev/mapper/VolGroupArray-lvroot bs=16m
dd if=/mnt/backupdata/test2.img of=/dev/mapper/VolGroupArray-lvhome bs=16m
Thanks
Edit: All the commands ended up working perfectly i had to change the lower case m to bs=16M. Once i did that the image files were created and worked just fine
Last edited by itzmeluigi (2013-08-05 06:01:30)

[SOLVED] Initramfs fails to properly mount luks partition

Hello All,
As I foreshadowed in my intro, I'm having trouble getting encrypted Archlinux to work on my Acer Aspire 5750. I've previously had encrypted Debian Netinst and encrypted Aptosid working on this device. The arch iso I'm using is 2011.08.19-core-i686.
https://bbs.archlinux.org/viewtopic.php?id=124415 appears similar and Tallahassee offers a workaround, but it doesn't work for me (unless I'm doing something wrong?)
I suspect there is a bug in the init scripts used by the initramfs. I would like to first of all determine whether I really should file a bug report (and if so where), and secondly whether we can find a workaround to get things up and running in the meantime.
Now for the meaty bits.
Old grub doesn't appear to support lvm or luks, so I first of all prepare for grub 2 by installing the gptfdisk package into the iso environment. I use gdisk to set up a 1 or 2 mb bios boot partition at the start of /dev/sda, followed by a 256mb partition (/dev/sda2) for /boot, with the rest of the drive given to the partition intended for the encrypted root partition (/dev/sda3).
I use cfdisk to toggle the partition type for /dev/sda3 to 8e (Linux LVM).
Run the following commands, with credits to Aptosid: Installing to a Cryptroot:
pvcreate /dev/sda3
vgcreate vg /dev/sda3
lvcreate -n crypt --extents 100%FREE vg
cryptsetup --verify-passphrase -c aes-xts-plain:sha512 luksFormat /dev/mapper/vg-crypt
cryptsetup luksOpen /dev/mapper/vg-crypt cryptroot
pvcreate /dev/mapper/cryptroot
vgcreate cryptvg /dev/mapper/cryptroot
lvcreate -n swap --size 2g cryptvg
lvcreate -n root --extents 25%FREE cryptvg
lvcreate -n home --extents 100%FREE cryptvg
/arch/setup
Go through the arch setup as normal. At the bit where you configure hard-drives, you'll find all your encrypted partitions ready waiting to be labelled and formatted. Stop after installing packages.
After installing packages, press CTL-ALT-F2 and log in. Edit /mnt/etc/rc.conf and /mnt/etc/mkinitcpio.conf. CTL-ALT-F1 and reinstall packages. Proceed with the configure step.
Don't install a boot loader; just quit after configuring everything.
Follow the steps here: Grub 2 During Archlinux Installation.
The automatically generated grub.cfg doesn't include things necessary to lvm and luks. Before running grub_bios-install, I edit the grub.cfg to insmod lvm and flag the kernel with cryptdevice=/dev/mapper/vg-crypt:cryptvg-root and rootfstype=ext4 (because that is the encrypted root's filesystem).
At this point, I would expect the system to be bootable, so reboot.
Grub2 loads up. I can verify the changes I made to grub.cfg by pressing `e'. So boot and see the messages,
Loading Linux linux ...
Loading initial ramdisk ...
A password is required to access the cryptvg-root volume:
Enter passphrase for /dev/mapper/vg-crypt:
So far so good. I enter my passphrase. The following messages ensue:
vgscan: unrecognized option '--sysinit'
Error during parsing of command line.
device-mapper: create ioctl failed: Device or resource busy
mount: mounting /dev/mapper/cryptvg-root on /new_root failed: Device or resource busy
ERROR: Failed to mount he real root device.
Bailing out, you are on your own. Good luck.
So I get dumped into the ramfs. That ain't much fun.
Does anyone have some ideas on things to try next? Should I file a bug report?
Last edited by /dev/zero (2011-10-22 00:28:52)

Not sure what you mean by difficult and buggy to work with... at this low level, if a VM is having issues replicating this sort if thing, it's not a very useful VM. Find one that doesn't suck. I tend to use KVM because it's terminal friendly via emulation of a serial console.
Anyways, I can reproduce your issue and fix it. There's 2 things you'll need to change:
1) You're naming your unlocked cryptdevice the same thing as your root. That's creating a clash with the name you've given your root logical volume. Since the name isn't really important, just change your cryptdevice declare to "cryptdevice=/dev/mapper/vg-crypt:root"
2) Since you're doing the xzibit thing and nesting lvm inside of the crypt device (i still think its really bizzare to do this, but it looks like mkinitcpio supports it anyways), you'll need to add the lvm2 hook a second time to HOOKS in /etc/mkinitcpio.conf after the encrypt hook.
Last edited by falconindy (2011-10-22 00:19:10)

LVM on LUKS on LVM

Does anyone know if, on a system with LVM on LUKS on LVM, a logical volume created inside a LUKS container can be added to the same volume group that the LUKS container is in? Even if this is possible, is it this just a bad idea from a security perspective? Should the outer LVM and inner LVM each have their own physical devices, volume groups, and logical volumes?

sda
└─sda1
└─Storage 254:0 0 XG 0 lvm
├─Storage-lrootvol 254:1 0 XG 0 lvm /
└─luks 254:0 0 XG 0 crypt
├─Storage-lvarvol 254:2 0 XG 0 lvm /var
├─Storage-lhomevol 254:3 0 XG 0 lvm /home
├─Storage-ltmpvol 254:4 0 XG 0 lvm /tmp
└─Storage-lswapvol 254:5 0 XG 0 lvm swap
Yes, that's what I was thinking, except that it's all on sda2 because sda1 is my EFI System partion.
Why don't you just encrypt the root partition as well? Any reason why that wouldn't work for you?
This is on a laptop, so I was trying to avoid the performance/battery life penalty of encrypting the root partition.

[SOLVED] Encrypt-Hook with LVM-on-Crypt fails to encrypt root part...

Hi,
I think that since the mkinitcpio (0.14.0-1) update (and the regeneration of the initramfs for my kernel) the encrypt hook doesn't work anymore. (At least for me)
I have my root filesystem in a LVM, which physical volume is encrypted with luks.
Here are my hooks from /etc/mkinitcpio.conf:
HOOKS="base udev autodetect modconf block keyboard keymap encrypt lvm2 resume filesystems fsck shutdown"
Output when I let it generate the initramfs:
% mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.9.7-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [lvm2]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
-> Running build hook: [shutdown]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.7-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [lvm2]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
-> Running build hook: [shutdown]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
But I am able to mount in manually within the emergency shell by executing:
$ cryptsetup luksOpen /dev/sda3 system
Enter passphrase for /dev/sda3:
$ lvm vgscan
Reading all physical volumes. This may take a while...
Found volume group "vg_system" using metadata type lvm2
$ lvm vgchange -ay
3 logical volume(s) in volume group "vg_system" now active
$ exit
Last edited by PyroDevil (2013-06-29 11:14:35)

Thanks for the link.
mdias wrote:
ok, I found a temporary workaround that seems to work for me,
I edited the file /usr/lib/initcpio/hooks/lvm2 to add this:
run_hook() {
lvm pvscan --cache --activate ay
Now, this will activate all lvm volumes regardless of lvm.conf, but it suits my needs for now.
This solution didn't work for me.
On boot time I was not asked to enter a password for the encrypted partition.
That's the reason I thought it was the encryption hook.

LVM on LUKS split across drives

I'm installing LVM on LUKS, as follows:
/dev/sda1: boot
/dev/sda2: first LUKS device
/dev/sdb1: second LUKS device
/dev/sda2 and /dev/sdb1 are in a volume group, which is then split into logical volumes.
/dev/sda2 and /dev/sdb1 have the same password.
How can I only be prompted once for this password at boot?

Strike0 has told me in the past that this is actually supported. Just use the LVM2 hook twice, once before and once after the encrypt hook. There is also the cryptsetup-multi package, but it is partially broken. In these forums somewhere there are instructions from falconindy on using the hook (maybe the install) file from the multi package in the current cryptsetup package. but you are going to have to seach for that yourself.

Finding whole mapping from database file - filesystems - logical volume manager - logical partitions

Hello,
Trying to make reverse engeneering of database files and their physical carriers on logical partitions ( fdisk ).
And not able to make whole path from filesystem down to partitions with intermediate logical volumes.
1. select from dba_data_files ...
2. df -k
to get the listing of filesystems
3. vgdisplay
4. lvdisplay
5. cat /proc/partitions
6. fdisk /dev/sda -l
   fdisk /dev/sdb -l
Problem I have is that not able to determine which partitions are consisten in logical volumes. And then which logical volumens are consisted in filesystem.
Thank you for hint or direction.

Hello Wadhah,
Before start the discussion let me explain I am newcommer to Oracle Linux. My genetic with dba experience of Oracle is from IBM UNIX ( AIX 6.1 ) and Oracle 11gr2.
First task is to get the complete picture of one database on Oracle Linux for future maintenance tasks and make database more flexible and
preparing for more intense work:
-adding datafiles,
-optimize/replace archive redolog files on separated filesystem from ORACLE_BASE
- separating auditing log files from $ORACLE_BASE to own filesystem
- separating diag directory on separated file system ( logging, tracing )
- adding/enlarging TEMP ts
- adding/enlarging undo
- enlarging redo for higher transaction rate ( to reduce number of switched per time perceived in alert_SID.log )
- adding online redo and control files mirrors
So in this context try to inspect content of the disk space from the highest logical level in V$, DBA views down to fdisk partitions.
The idea was to go in these steps:
1. select paths of present online redo groups, datafiles, controlfiles, temp, undo
   from V$, dba views
2. For the paths got from the step 1
   locate filesystems and for those filesystems inspect which are on logical volumens and which are directly on partitions.
3. For all used logical volumes locate the logical partitions and their disks /dev/sda, /dev/sdb, ...

[Solved] Enlarge logical Volume (LVM on Luks)

Similar Messages

Maybe you are looking for