Re: [qubes-users] Re: Corrupted LVM Pool Metadata - no free space (recoverable?)

2018-08-14 Thread joeviocoe
I use a custom dracut module from the2nd, ykluks, so I don't know about how to modify it to unlock multiple volumes. Also, I may want to stick with LUKS instead of ecryptfs because yubikey support. Can you elaborate on the steps for using Btrfs during install of Qubes, the documentation is still

Re: [qubes-users] Re: Corrupted LVM Pool Metadata - no free space (recoverable?)

2018-08-13 Thread Chris Laprise
On 08/13/2018 05:32 PM, joevio...@gmail.com wrote: On Monday, 13 August 2018 17:13:06 UTC-4, Chris Laprise wrote: On 08/13/2018 04:47 PM, Related question. If I installed Qubes and used LUKS encryption (I have to run cryptsetup openLuks just to see the LVM inside)... then I add physical driv

Re: [qubes-users] Re: Corrupted LVM Pool Metadata - no free space (recoverable?)

2018-08-13 Thread joeviocoe
On Monday, 13 August 2018 17:13:06 UTC-4, Chris Laprise wrote: > On 08/13/2018 04:47 PM, > > Related question. > > > > If I installed Qubes and used LUKS encryption (I have to run cryptsetup > > openLuks just to see the LVM inside)... then I add physical drives to my > > Volume Group, and star

Re: [qubes-users] Re: Corrupted LVM Pool Metadata - no free space (recoverable?)

2018-08-13 Thread Chris Laprise
On 08/13/2018 04:47 PM, joevio...@gmail.com wrote: Related question. If I installed Qubes and used LUKS encryption (I have to run cryptsetup openLuks just to see the LVM inside)... then I add physical drives to my Volume Group, and start adding more AppVMs to the pool, that starts writing to t

[qubes-users] Re: Corrupted LVM Pool Metadata - no free space (recoverable?)

2018-08-13 Thread joeviocoe
Related question. If I installed Qubes and used LUKS encryption (I have to run cryptsetup openLuks just to see the LVM inside)... then I add physical drives to my Volume Group, and start adding more AppVMs to the pool, that starts writing to the PV... Is the data on the new drive, encrypted? Ca