I can set all this up during the install, and all seems to go OK, but when I click apply, I just get a blank partitioning screen (see attached screenshot), and the following in the logs:
Loading module partdisks.front…
Unable to get a correct object/changes from /dev/vg.
Committing changes in /dev/sda
Committing changes in /dev/sda-1
Committing changes in /dev/sda1
Committing changes in /dev/sda2
Committing changes in /dev/sdb
Committing changes in /dev/sdb-1
Committing changes in /dev/sdb1
I have confirmed via the console that I can manually partition the disk in this way, just cant get the installer to accept this setup.
Did you try apllying changes after creating each of the VGs/volumes/mount points?
—> /dev/sda2 - encrypted physical partition ----- Apply
—> /dev/mapper/sda2_crypt - volume group inside encrypted partition (vg00) ----- Apply
That would help us to know where exactly does it “stops”…
I can’t test it on a real machine right now, however it works as expected in a VM:
Anyway, before digging further, if you didn’t allready, create a encrypted partition, apply and reboot.
It may be that for some reason LVM doesn’t record changes properly, or installer is not able to read them ( Unable to get a correct object/changes from /dev/vg. )…
Then, ofc, after rebooting, proceed with setting up the rest, and let us know how it went.
Actually it doesn’t… I was to quick to reply ( took a screenshot and replied, without proceeding with installation )…
Anyway, there will be a ( hopefully ) fixed version landing in the repos soon, hang on
File descriptor 12 (/tmp/keeptalking.log) leaked on vgcreate invocation. Parent PID 5393: /bin/sh
Volume group “vg00” successfully created
File descriptor 12 (/tmp/keeptalking.log) leaked on vgchange invocation. Parent PID 5407: /bin/sh
0 logical volume(s) in volume group “vg00” now active
File descriptor 12 (/tmp/keeptalking.log) leaked on lvchange invocation. Parent PID 5413: /bin/sh
One or more specified logical volume(s) not found.
Unable to enable vg00. Ensure it’s not contained in a locked device.
Committing LVM changes to /dev/vg00/vg00-1…
File descriptor 12 (/tmp/keeptalking.log) leaked on lvcreate invocation. Parent PID 5482: /bin/sh
Rounding up size to full physical extent 1.83 GiB
Logical volume “vg00” created
Marking vg00 as inexistent because it appears empty
However, blank installer window resolved with refresh button
It was a small issue/fix allready fixed upstream ( we missed it somehow )…
Packages are rebuilt and added to the repo.
Boot the live, and update the installer:
sudo apt-get update
sudo apt-get install linstaller linstaller-config-trios linstaller-frontend-cli linstaller-frontend-glade linstaller-modules-base linstaller-session live-config-linstaller
Then fire it up, it should partition like a charm
There is a slight possibility that GRUB install will fail if/when installing to MBR. Also, lvm2 gets autoremoved… :mad:
Will fix everything tomorow.
OK, so for anyone else hitting this issue, here is what I had to do to get this working.
Boot into the live environment
apt-get update && apt-get upgrade -y
run the installer, and install your system, but do not reboot at the end
open a root console, chroot into /linstaller/target
apt-get install lvm2 (this seems to be missing from the install, and results in an un-bootable system - @Filip while you’re fixing some gear up tomorrow, you might want to add this…)
reinstall grub (update-grub then grub-install)
exit the chroot, and then reboot
After this, you should have a system with encrypted filesystem with lvm that boots successfully.
Great! You’re welcome & thank you for sharing the how-to!
It actually exists in a live system, but for some reason apt marks it for auto removal, which happens near the end of the install process ( even if you chose to install on lvm volume )…
Anyway, I’m working on it, shouldn’t take too long…
When you install on premade volumes ( formating them without removing/readding ), everything goes as usual ( on the surface ), however installer doesn’t fill up the crypttab at all ( resulting in “volume group xyz not found/Unable to find LVM” & no pass prompt @boot.
If you remove the physical volume, then recreate everything & install = there are no issues ( I’m still getting the ^“not found” error, but password promt shows, allowing me to unlock/boot. Also, crypttab is properly filled. ).
Now for the “wierd” bits ( to me at least ):
Both Thunar and Installer fail to mount ( or unlock ) encrypted partitions. They both prompt for pass, accept it and then: “Failed… Operation was cancelled” says Thunar/Installer logs this:
0 logical volume(s) in volume group "main" now active
Marking root as inexistent because it appears empty ## in reallity it's not empty, there's a previous installation on it.
Marking swap as inexistent because it appears empty
If, after that^, you start the lvm2 service manually ( sudo service lvm2 start ) = everything’s fine, you can now mount the encrypted partition in Thunar and installer does it’s job = system boots…
2 logical volume(s) in volume group "main" now active
lvm2 service is not started, even after you start it manually, it stays disabled on the next boot ( which doesn’t cause any trouble on the installed system, however given the above, it’s obviously needed in live )
Summing it up, I say wierd, since I guess that all of the above should be automatic. However, since I haven’t really used LVM before I might be ( terribly ) wrong.
Any info would be greatly appreciated.
In the mean time and in case somebody else, like me, doesn’t know about that and plans to install on existing volume(s):
– After unlocking PV in installer, fire up a terminal and run:
OK, looks like this was a bad package in the debian mirror i was using.
Have tested against another mirror, and all is working ok.
So, just to recap, I’ve done a fresh install, updated the required packages in the live environment, on a new disk, rebooted, and all works well.
@Filip Ill test the install on to existing partitions shortly and let you know how I get on.
FYI, still have issues with the number of updates required in the live environment and the size of aufs, but as long as your system has 4GB+ memory, or you setup a partition on your real disk and mount as /var/cache/apt before doing the update, all seems to be working.