I messed up those images, so some new ones apologies if you downloaded them already.
You'll need an SD card/USB memory stick with a partition containing:You may omit NEW_LV_SIZE from the config to allow the new volume to take the remaining space after the home partition is reduced in size. Though having both smaller and then online growing whichever happens to need extra space first might be a nice way to use the system.
You may also omit LV_TO_REDUCE_NAME from the config if you already have enough space available in your volume group.
You'll need to flash/dd a new boot image:This time I have test it, granted on a slightly different setup, I put an SD card in, created a LVM VG of planetlinux (the scripts prefer this to sailfishos though should boot/install to whichever is available), I then inserted a USB memory stick with the config & img files (FAT32 commented out the TO_REDUCE lines as with a fresh VG there is nothing to reduce), flashed the boot image to my choice of bootX and rebooted into that with the appropriate key combination. It took just under an hour for the actual install to happen, uncertain if that is due to the XZ compression applied to the image or the slowness of my SD/USB cards. This does of course mean that you could create the LVM setup on a desktop with a SD card reader and just do the flash/dd of the boot image on the device. I could write either of these up in more detail if needed. Its also occurred to me that you don't need to name the new LV in the config file as that is set from the cmdline inside the boot image which was one of the issues I had before where the config was making a different LV to the one the boot image was going to try to boot.
gabs5807 - given your current selection of boots (your using all of them) you'll have to sacrifice one, I'd probably drop TWRP to start with myself... but whatever you use the least.
Something I've noticed with this fresh image is that the QTerminal console fonts seem to be lacking a bunch of characters, fn+y|u, shift+fn+y|u etc gave you arrow pictures in different directions, now they give nothing. Must be a package missing from the minimal desktop install.
I did a test and put the gemian-config.txt and gemian-stretch.img.xz into filesystem root of my sdcard. dd linux-boot-lvm-gemian.img to boot2. On first boot it said: Panic cannot resize home.
I restartet sailfishos and did the resize manualy: lvm <enter>; lvresize --size 16G /dev/sailfish/home. commented LV_TO_REDUCE_* out and did a restart. It installed debian and booted it.
Next I will restore my old debian (have a tar) into the lvm gemian partition and hope it will boot too.
Very nice start, only resize does not work. Happy to have a lvm gemian.
I had tested 2 other varaints:
1. build an image file of lvm sailfishos and did a loop mount at initramfs. Worked, but on update it writes a nwe boot image to boot and did not find original lvm. I had to build a new boot image myself.
2. moved all from lvm to .stowaways (like before). sailfishos did not show the system storege under settings storage and disabled backup before update. But updates still works. The boot partition was not updated, I had to build the image with stowaways support manualy and dd it.
I think with gemian lvm sailfishos updates will work like they should.
But we still have the update dilemma for this multiboot environment: Every automatic updated operation system tries to write to boot (1st boot partiton).
edit: how it looks atm:
lvscan
ACTIVE '/dev/sailfish/root' [5.86 GiB] inherit
ACTIVE '/dev/sailfish/home' [16.00 GiB] inherit
ACTIVE '/dev/sailfish/gemian' [16.00 GiB] inherit
Show Posts
