LVM why are new Logical Volumes inactive on boot?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I have two separate drives. one is for booting and one is for storage. I created a new logical volume called "lv_storage" in the volume group "ultrabay".
However, when I boot /dev/ultrabay/lv_storage is labeled inactive and therefore cannot be mounted by fstab. So I have to run "vgchange -ay" each time I boot and manually mount the drive.
How can I make LVM activate /dev/ultrabay/lv_storage on boot?
arch-linux lvm
asked Jan 4 at 15:43
MinceUtopia
212
add a comment |Â
up vote
1
down vote
favorite
I have two separate drives. one is for booting and one is for storage. I created a new logical volume called "lv_storage" in the volume group "ultrabay".
However, when I boot /dev/ultrabay/lv_storage is labeled inactive and therefore cannot be mounted by fstab. So I have to run "vgchange -ay" each time I boot and manually mount the drive.
How can I make LVM activate /dev/ultrabay/lv_storage on boot?
arch-linux lvm
asked Jan 4 at 15:43
MinceUtopia
212
3
Is there an uncommented "volume_list" entry in yourlvm.conffile (usually/etc/lvm/lvm.conf)?
– John
Jan 4 at 15:54
No, the volume_list line is commented. The device is encrypted but is decrypted on boot by dmcrypt after the LVM hook. Could this be the source of the issue?
– MinceUtopia
Jan 4 at 16:12
what does /etc/sysconfig/lvm or /etc/lvm/*conf (depending on distribution) say ? you can check vgs/lvs for details about you current config about this particular LV & dmesg to try to find a warning or error message that explain origin of the issue
– francois P
Jan 4 at 16:49
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have two separate drives. one is for booting and one is for storage. I created a new logical volume called "lv_storage" in the volume group "ultrabay".
However, when I boot /dev/ultrabay/lv_storage is labeled inactive and therefore cannot be mounted by fstab. So I have to run "vgchange -ay" each time I boot and manually mount the drive.
How can I make LVM activate /dev/ultrabay/lv_storage on boot?
arch-linux lvm
asked Jan 4 at 15:43
MinceUtopia
212
I have two separate drives. one is for booting and one is for storage. I created a new logical volume called "lv_storage" in the volume group "ultrabay".
However, when I boot /dev/ultrabay/lv_storage is labeled inactive and therefore cannot be mounted by fstab. So I have to run "vgchange -ay" each time I boot and manually mount the drive.
How can I make LVM activate /dev/ultrabay/lv_storage on boot?
arch-linux lvm
asked Jan 4 at 15:43
MinceUtopia
212
asked Jan 4 at 15:43
MinceUtopia
212
asked Jan 4 at 15:43
MinceUtopia
212
asked Jan 4 at 15:43
MinceUtopia
212
212
3
Is there an uncommented "volume_list" entry in yourlvm.conffile (usually/etc/lvm/lvm.conf)?
– John
Jan 4 at 15:54
No, the volume_list line is commented. The device is encrypted but is decrypted on boot by dmcrypt after the LVM hook. Could this be the source of the issue?
– MinceUtopia
Jan 4 at 16:12
what does /etc/sysconfig/lvm or /etc/lvm/*conf (depending on distribution) say ? you can check vgs/lvs for details about you current config about this particular LV & dmesg to try to find a warning or error message that explain origin of the issue
– francois P
Jan 4 at 16:49
add a comment |Â
3
Is there an uncommented "volume_list" entry in yourlvm.conffile (usually/etc/lvm/lvm.conf)?
– John
Jan 4 at 15:54
No, the volume_list line is commented. The device is encrypted but is decrypted on boot by dmcrypt after the LVM hook. Could this be the source of the issue?
– MinceUtopia
Jan 4 at 16:12
what does /etc/sysconfig/lvm or /etc/lvm/*conf (depending on distribution) say ? you can check vgs/lvs for details about you current config about this particular LV & dmesg to try to find a warning or error message that explain origin of the issue
– francois P
Jan 4 at 16:49
3
3
Is there an uncommented "volume_list" entry in your
lvm.conf file (usually /etc/lvm/lvm.conf)?– John
Jan 4 at 15:54
Is there an uncommented "volume_list" entry in your
lvm.conf file (usually /etc/lvm/lvm.conf)?– John
Jan 4 at 15:54
No, the volume_list line is commented. The device is encrypted but is decrypted on boot by dmcrypt after the LVM hook. Could this be the source of the issue?
– MinceUtopia
Jan 4 at 16:12
No, the volume_list line is commented. The device is encrypted but is decrypted on boot by dmcrypt after the LVM hook. Could this be the source of the issue?
– MinceUtopia
Jan 4 at 16:12
what does /etc/sysconfig/lvm or /etc/lvm/*conf (depending on distribution) say ? you can check vgs/lvs for details about you current config about this particular LV & dmesg to try to find a warning or error message that explain origin of the issue
– francois P
Jan 4 at 16:49
what does /etc/sysconfig/lvm or /etc/lvm/*conf (depending on distribution) say ? you can check vgs/lvs for details about you current config about this particular LV & dmesg to try to find a warning or error message that explain origin of the issue
– francois P
Jan 4 at 16:49
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
You mention in a comment that the underlying device is only decrypted after LVM is set up at boot time. This is the problem. Because the PV is encrypted, the LVM startup can't find it to activate the VG on it. You need to change the order of the decryption / LVM activation, or add a decryption routine to the LVM activation for that PV, or add a vgchange to the decryrption routine.
answered Jan 4 at 18:04
John
11.3k11630
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
You mention in a comment that the underlying device is only decrypted after LVM is set up at boot time. This is the problem. Because the PV is encrypted, the LVM startup can't find it to activate the VG on it. You need to change the order of the decryption / LVM activation, or add a decryption routine to the LVM activation for that PV, or add a vgchange to the decryrption routine.
answered Jan 4 at 18:04
John
11.3k11630
add a comment |Â
up vote
1
down vote
You mention in a comment that the underlying device is only decrypted after LVM is set up at boot time. This is the problem. Because the PV is encrypted, the LVM startup can't find it to activate the VG on it. You need to change the order of the decryption / LVM activation, or add a decryption routine to the LVM activation for that PV, or add a vgchange to the decryrption routine.
answered Jan 4 at 18:04
John
11.3k11630
add a comment |Â
up vote
1
down vote
up vote
1
down vote
You mention in a comment that the underlying device is only decrypted after LVM is set up at boot time. This is the problem. Because the PV is encrypted, the LVM startup can't find it to activate the VG on it. You need to change the order of the decryption / LVM activation, or add a decryption routine to the LVM activation for that PV, or add a vgchange to the decryrption routine.
answered Jan 4 at 18:04
John
11.3k11630
You mention in a comment that the underlying device is only decrypted after LVM is set up at boot time. This is the problem. Because the PV is encrypted, the LVM startup can't find it to activate the VG on it. You need to change the order of the decryption / LVM activation, or add a decryption routine to the LVM activation for that PV, or add a vgchange to the decryrption routine.
answered Jan 4 at 18:04
John
11.3k11630
answered Jan 4 at 18:04
John
11.3k11630
answered Jan 4 at 18:04
John
11.3k11630
answered Jan 4 at 18:04
John
11.3k11630
11.3k11630
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414795%2flvm-why-are-new-logical-volumes-inactive-on-boot%23new-answer', 'question_page');
);
Post as a guest
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
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
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
3
Is there an uncommented "volume_list" entry in your
lvm.conffile (usually/etc/lvm/lvm.conf)?– John
Jan 4 at 15:54
No, the volume_list line is commented. The device is encrypted but is decrypted on boot by dmcrypt after the LVM hook. Could this be the source of the issue?
– MinceUtopia
Jan 4 at 16:12
what does /etc/sysconfig/lvm or /etc/lvm/*conf (depending on distribution) say ? you can check vgs/lvs for details about you current config about this particular LV & dmesg to try to find a warning or error message that explain origin of the issue
– francois P
Jan 4 at 16:49