Update requires 500MB Warning. [answered]

Which device only has 2GB total memory?

indeed 2gb sounds suspiciously low.

@juiceme@tortoisedoc i updated the post to show my other storage. I have a lot more actually 256GB (1/2 on ext SD) total so not sure why SFOS limits to 2.1GB.

Ah, I did not realize you have da Turing device! :)

I am not very familiar with that so cannot say offhand but it is possible that your storage device (which usually is /dev/mmcblk0) is partitioned so that some partitions run out of space even though there's plenty of space left on the device as whole.

Could you please post the output of command "df -h" ?

funny is that there is a system data and user data. and user data is really huge comparing to system data. normally it is not the contrary on any linux distribution?
in jp1 there is just one...

@DarkTuring wow please add some crlf < br > on your df -h feedback

your pics are quite good, but i'm not sure that is efficient to let the full size on in. they are quite big on a screen....

sorry about that let me try post it again:

Filesystem Size Used Avail Use% Mounted on

rootfs
2.5G 2.1G 398M 84% / /dev/sailfish/root
2.5G 2.1G 398M 84% / /dev/sailfish/home
112G 41G 70G 37% /home devtmpfs
1.3G 184K 1.3G 1% /dev tmpfs
1.4G 440K 1.4G 1% /dev/shm tmpfs
1.4G 58M 1.4G 5% /run tmpfs
1.4G 0 1.4G 0% /sys/fs/cgroup tmpfs
1.4G 4.0K 1.4G 1% /tmp /dev/mmcblk0p16
4.9M 4.1M 808K 84% /persist tmpfs
1.4G 0 1.4G 0% /mnt/obb /dev/mmcblk0p1
64M 57M 7.6M 89% /firmware tmpfs
1.4G 0 1.4G 0% /mnt/asec /dev/mmcblk0p19
807M 801M 0 100% /fimage /dev/mmcblk0p20
228M 11M 206M 5% /mnt/vendor_data /dev/sailfish/home
112G 41G 70G 37% /opt/alien/data /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/bin /dev/sailfish/root
2.5G 2.1G 398M 84% /data/media /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/sbin /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/lib /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/usr /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/var /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/etc tmpfs
1.4G 4.0K 1.4G 1% /opt/alien/tmp /dev/sailfish/home
112G 41G 70G 37% /opt/alien/home devtmpfs
1.3G 184K 1.3G 1% /opt/alien/dev tmpfs
1.4G 440K 1.4G 1% /opt/alien/dev/shm tmpfs
1.4G 0 1.4G 0% /opt/alien/sys/fs/c group tmpfs
1.4G 58M 1.4G 5% /opt/alien/run /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/media /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/vendor /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/system_j olla /dev/sailfish/root
2.5G 2.1G 398M 84% /opt/alien/data_jol la /dev/mmcblk1
120G 31G 83G 28% /media/sdcard/02acc a7a-3b1f-41d4-99b5-e05be52fc9ca /dev/mmcblk1
120G 31G 83G 28% /opt/alien/media/sd card/02acca7a-3b1f-41d4-99b5-e05be52fc9ca /dev/mmcblk1
120G 31G 83G 28% /data/media/02acca7 a-3b1f-41d4-99b5-e05be52fc9ca /dev/fuse
112G 41G 70G 37% /opt/alien/storage/ sdcard0 [nemo@

@cemoi71 what does your storage profile look like?

@DarkTuring, thanks for sharing your filesystem info, it sure looks pretty strange to me!

Now, the interesting lines here are the 2 first ones;

rootfs                  2.5G  2.1G  398M  84%  /
/dev/sailfish/root  2.5G  2.1G  398M  84%  /

From that you can see that your root partition indeed is just 2.5GB, but the strange thing here is that there is no physical device mounted there, just some odd "/dev/sailfish/root/" whatever that might be?

Is it a symlink? Or maybe some encrypted partition? I have no idea yet... :)

Could you do few further commands please? What's the output og commands "mount", "cat /proc/mounts" and "ls -la /dev/sailfish/" ?

From the filesystem info it is evident that the problem is indeed root space related, as you see you have plenty of space available for user files on your home;

/dev/sailfish/home  112G   41G   70G  37%  /home

@cemoi71 the partition layout is pretty norma-looking to me except for the root partition location.

Typically android-derived devices have quite a few special partitions housing the firmaware, SoC and calibration files.

@juiceme yes yo're right i checked by me too. that's why i delete my comment.
Yes the root is too small, should be same size than the home.
but an other thing should be checked. not?

@cemoi71 well, it looks that the root is a bit tight but by no means should it be as large as the home partiton. Most user-interested files reside in /home anyway :)

Now what I suspect is that root has been mounted as a loop filesystem through crypto, but let's see what @DarkTuring answers to my questions, maybe that illuminates it a bit.

on my device the root points to the same partition than home...

rootfs 14G 9.7G 3.7G 73% /
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /
devtmpfs 404M 64K 404M 1% /dev
tmpfs 405M 828K 404M 1% /dev/shm
tmpfs 405M 49M 357M 12% /run
tmpfs 405M 0 405M 0% /sys/fs/cgroup
tmpfs 405M 4.0K 405M 1% /tmp
/dev/mmcblk0p19 7.9M 4.1M 3.9M 52% /drm
/dev/mmcblk0p18 64M 45M 20M 70% /firmware
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /home
/dev/mmcblk0p25 7.9M 4.2M 3.8M 53% /persist
/dev/mmcblk0p9 48M 11M 37M 22% /var/systemlog
tmpfs 405M 0 405M 0% /mnt/asec
tmpfs 405M 0 405M 0% /mnt/obb
/dev/mmcblk1p1 59G 25G 31G 45% /media/sdcard/d0198a7f-9702-40a3-b2d5-890d66b77754
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/data
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/bin
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/sbin
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/lib
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/usr
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/var
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/etc
tmpfs 405M 4.0K 405M 1% /opt/alien/tmp
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/home
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/vendor
devtmpfs 404M 64K 404M 1% /opt/alien/dev
tmpfs 405M 828K 404M 1% /opt/alien/dev/shm
tmpfs 405M 0 405M 0% /opt/alien/sys/fs/cgroup
tmpfs 405M 49M 357M 12% /opt/alien/run
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/media
/dev/mmcblk1p1 59G 25G 31G 45% /opt/alien/media/sdcard/d0198a7f-9702-40a3-b2d5-890d66b77754
/dev/mmcblk0p28 14G 9.7G 3.7G 73% /opt/alien/system_jolla
/dev/fuse 14G 9.7G 3.7G 73% /opt/alien/home/nemo/android_storage
/dev/fuse 14G 9.7G 3.7G 73% /home/nemo/android_storage

@cemoi71, that's a typical filesystem layout for Jolla sbj-1 device. Pretty much what I have.

On my other devices (Jolla-C, Jolla Tablet, ported Nexus5/SFOS, Nexus7/SFOS) all have different filesystem layouts so don't be surprised that the Turing device has yet another layout :)

Besides of those all only sbj-1 has btrfs, fhich again makes things a bit different.

what should the crypto do? encrypt the whole system? or just the user data?
seems that here they are separatly (the home and the root).
would interest me how it looks like under /dev/disk/by-id/ and especially under /dev/disk/by-uuid/...

a bit different yes. that don't wonder me at last. firstly i thought that by jolla would be simple. small device => small os => small complexity comparing with bigger devices (please don't laugh). After a little bit documenting and be more awake. then ... right... ok.

anyway.
first it seems that home and root are separate right? the ll feedback for /dev/disk/by-uuid/ may reveal some info. Is that wrong?
Then a question where i have no idea... for an os, just 2,5gb size is not a little bit tight?

what is the /fimage? seems to be full...

So, @DarkTuring, what's the output of "mount", "cat /proc/mounts" and "ls -la /dev/sailfish/" ?

This is a bit lengthy but here is the mount:

emo@localhost ~]$ mount/dev/mapper/sailfish-root on / type ext4 (rw,noatime,data=ordered)/dev/mapper/sailfish-home on /home type ext4 (rw,relatime,data=ordered)devtmpfs on /dev type devtmpfs (rw,relatime,size=1277600k,nr_inodes=168272,mode=755)none on /proc type proc (rw,relatime)none on /sys type sysfs (rw,relatime)tmpfs on /dev/shm type tmpfs (rw,relatime,size=1461876k,nr_inodes=173371)devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)tmpfs on /run type tmpfs (rw,nosuid,nodev,size=1461876k,nr_inodes=173371,mode=755)tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,size=1461876k,nr_inodes=173371,mode=755)cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/debug type
cgroup (rw,nosuid,nodev,noexec,relatime,debug)
cgroup on /sys/fs/cgroup/cpu,cpuacct type
cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type
cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type
cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type
cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type
cgroup (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
cgroup on /sys/fs/cgroup/blkio type
cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type
cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)debugfs on /sys/kernel/debug type debugfs (rw,relatime)tmpfs on /tmp type tmpfs (rw,size=1461876k,nr_inodes=173371)/dev/mmcblk0p16 on /persist type ext4 (rw,nosuid,nodev,relatime,data=ordered)tmpfs on /mnt/obb type tmpfs (rw,relatime,size=1461876k,nr_inodes=173371,mode=755,gid=1000)/dev/mmcblk0p1 on /firmware type vfat (ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)tmpfs on /mnt/asec type tmpfs (rw,relatime,size=1461876k,nr_inodes=173371,mode=755,gid=1000)mtp on /dev/mtp type functionfs (rw,relatime)/dev/mmcblk0p19 on /fimage type ext4 (rw,noatime,data=ordered)fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)statefs on /run/state type fuse.statefs (rw,nosuid,nodev,relatime,userec,size=1461876k,nr_inodes=173371,mode=755)
cgroup on /opt/alien/sys/fs/cgroup/systemd type
cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /opt/alien/sys/fs/cgroup/debug type
cgroup (rw,nosuid,nodev,noexec,relatime,debug)
cgroup on /opt/alien/sys/fs/cgroup/cpu,cpuacct type
cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /opt/alien/sys/fs/cgroup/memory type
cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /opt/alien/sys/fs/cgroup/devices type
cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /opt/alien/sys/fs/cgroup/freezer type
cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /opt/alien/sys/fs/cgroup/net_cls,net_prio type
cgroup(rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
cgroup on /opt/alien/sys/fs/cgroup/blkio type
cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /opt/alien/sys/fs/
cgroup/perf_event type
cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)debugfs on /opt/alien/sys/kernel/debug type debugfs (rw,relatime)fusectl on /opt/alien/sys/fs/fuse/connections type fusectl (rw,relatime)tmpfs on /opt/alien/run type tmpfs (rw,nosuid,nodev,size=1461876k,nr_inodes=173371,mode=755)statefs on /opt/alien/run/state type fuse.statefs (rw,nosuid,nodev,relatime,user_id=0,group_id=998,default_permissions,allow_other)/dev/mapper/sailfish-root on /opt/alien/media type ext4 (rw,noa[nemo@localhost ~]$ qdf -h/dev/mapper/sailfish-root on /opt/alien/vendor type ext4 (rw,noatime,data=ordered)/dev/mapper/sailfish-root on /opt/alien/system_jolla type ext4(rw,noatime,data=ordered)/dev/mapper/sailfish-root on /opt/alien/data_jolla type ext4 (rw,noatime,data=ordered)proc on /opt/alien/proc type proc (rw,relatime)/dev/mmcblk1 on /media/sdcard/02acca7a-3b1f-41d4-99b5-e05be52fc9ca type ext4 (rw,nosuid,nodev,noexec,noatime,dirsync,data=ordered)/dev/mmcblk1 on /data/media/02acca7a-3b1f-41d4-99b5-e05be52fc9ca type ext4 (rw,nosuid,nodev,noexec,noatime,dirsync,data=ordered)/dev/mmcblk1 on /opt/alien/media/sdcard/02acca7a-3b1f-41d4-99b5-e05be52fc9ca type ext4 (rw,nosuid,nodev,noexec,noatime,dirsync,data=ordered)statefs on /run/user/100000/state type fuse.statefs (rw,nosuid,nodev,relatime,user_id=100000,group_id=100000,default_permissions,allow_other)statefs on /opt/alien/run/user/100000/state type fuse.statefs (rw,nosuid,nodev,relatime,user_id=100000,group_id=100000,default_permissions,allow_other)/dev/fuse on /opt/alien/storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=100000,group_id=100000,default_permissions,allow_other)[nemo@local

And here is the cat /proc command output:

mo@localhost ~]$ cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/sailfish/root / ext4 rw,noatime,data=ordered 0 0
/dev/sailfish/home /home ext4 rw,relatime,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=1277600k,nr_inodes=168272,mode=755 0 0
none /proc proc rw,relatime 0 0
none /sys sysfs rw,relatime 0 0
tmpfs /dev/shm tmpfs rw,relatime,size=1461876k,nr_inodes=1733710 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620 0 0
tmpfs /run tmpfs rw,nosuid,nodev,size=1461876k,nr_inodes=173371,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,size=1461876k,nr_inodes=173371,mode=755 0 0
~~~ Couple more lines that dont seem relevantdebugfs /opt/alien/sys/kernel/debug debugfs rw,relatime 0 0
fusectl /opt/alien/sys/fs/fuse/connections fusectl rw,relatime0 0
tmpfs /opt/alien/run tmpfs rw,nosuid,nodev,size=1461876k,nr_inodes=173371,mode=755 0 0
statefs /opt/alien/run/state fuse.statefs rw,nosuid,nodev,relatime,user_id=0,group_id=998,default_permissions,allow_other 0 0
/dev/sailfish/root /opt/alien/media ext4 rw,noatime,data=ordered 0 0
/dev/sailfish/root /opt/alien/vendor ext4 rw,noatime,data=ordered 0 0
/dev/sailfish/root /opt/alien/system_jolla ext4 rw,noatime,data=ordered 0 0
/dev/sailfish/root /opt/alien/data_jolla ext4 rw,noatime,data=ordered 0 0
proc /opt/alien/proc proc rw,relatime 0 0
/dev/mmcblk1 /media/sdcard/02acca7a-3b1f-41d4-99b5-e05be52fc9caext4 rw,dirsync,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/mmcblk1 /data/media/02acca7a-3b1f-41d4-99b5-e05be52fc9ca ext4 rw,dirsync,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/mmcblk1 /opt/alien/media/sdcard/02acca7a-3b1f-41d4-99b5-e05be52fc9ca ext4 rw,dirsync,nosuid,nodev,noexec,noatime,data=ordered 0 0
statefs /run/user/100000/state fuse.statefs rw,nosuid,nodev,relatime,user_id=100000,group_id=100000,default_permissions,allow_other 0 0
statefs /opt/alien/run/user/100000/state fuse.statefs rw,nosuid,nodev,relatime,user_id=100000,group_id=100000,default_permissions,allow_other 0 0
/dev/fuse /opt/alien/storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=100000,group_id=100000,default_permissions,allow_other 0 0
[ne

And finally here is the ls -la command output:

[nemo@localhost ~]$ ls -la /dev/sailfish
total 0
drwxr-xr-x 2 root root 80 1970-01-09 13:53 .
drwxr-xr-x 19 root root 17200 2016-12-14 06:10 ..
lrwxrwxrwx 1 root root 25 1970-01-09 13:53 home -> /dev/map
per/sailfish-home
lrwxrwxrwx 1 root root 25 1970-01-09 13:53 root -> /dev/map
per/sailfish-root

@juiceme thanks for weeding through it and clarifying my storage situation. So if i understand it correctly i have a linux partition of 2.5GB for my root (system) called /dev/sailfish , i dont know if it is encrypted or not. The home directory i can just copy paste to the external SD and browse through with a file explorer so i doubt home, is encrypted, SD external isnt since Android has access to it and again i formatted and partitioned it and can browse through it.

@cemoi71 the /fimage is the factory flashing image for the phone. i just deleted it but it didnt seem to change my available space since 700MB didnt free up.

Running sudo fdisk -l i am getting a nice summary:

disk /dev/mmcblk0: 116.5 GiB, 125069950976 bytes, 244277248 sec tors
Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: gpt

Disk identifier: 98101B32-BBE2-XXXXXXXXXCXXCCC

Device Start End Sectors Size Type

/dev/mmcblk0p1 131072 262143 131072 64M Microsoft ba

/dev/mmcblk0p2 262144 263167 1024 512K unknown

/dev/mmcblk0p3 263168 263231 64 32K unknown

/dev/mmcblk0p4 393216 393279 64 32K unknown

/dev/mmcblk0p5 524288 525311 1024 512K unknown

/dev/mmcblk0p6 525312 526311 1000 500K unknown

/dev/mmcblk0p7 655360 688127 32768 16M unknown

/dev/mmcblk0p8 786432 787431 1000 500K unknown

/dev/mmcblk0p9 787432 789479 2048 1M Microsoft ba

/dev/mmcblk0p10 789480 792551 3072 1.5M unknown

/dev/mmcblk0p11 792552 795623 3072 1.5M unknown

/dev/mmcblk0p12 795624 797671 2048 1M unknown

/dev/mmcblk0p13 917504 920575 3072 1.5M unknown

/dev/mmcblk0p14 1048576 1048577 2 1K unknown

/dev/mmcblk0p15 1048578 1048593 16 8K unknown

/dev/mmcblk0p16 1179648 1245183 65536 32M Microsoft ba

/dev/mmcblk0p17 1245184 1277951 32768 16M unknown

/dev/mmcblk0p18 1310720 1331199 20480 10M unknown

/dev/mmcblk0p19 1441792 3694591 2252800 1.1G Microsoft ba

/dev/mmcblk0p20 3694592 4218879 524288 256M Microsoft ba

/dev/mmcblk0p21 4325376 4345855 20480 10M unknown

/dev/mmcblk0p22 4456448 244277214 239820767 114.4G Microsoft ba

Disk /dev/mmcblk0rpmb: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/sailfish-root: 2.5 GiB, 2621440000 bytes, 5120000 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/sailfish-home: 111.9 GiB, 120162615296 bytes,

234692608 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk1: 119.2 GiB, 128026935296 bytes, 250052608 sec tors.....

OK, now I get it :)

It's not encryption, you just have LVM volumes there;

lrwxrwxrwx 1 root root 25 1970-01-09 13:53 home -> /dev/mapper/sailfish-home
lrwxrwxrwx 1 root root 25 1970-01-09 13:53 root -> /dev/mapper/sailfish-root

Now, you should be able to resize LVM partitions on the fly so actually you can increase the root size by allocating bytes from /home/ there.

@juiceme ok thats fantastic, means at least i dont have to start from scratch. Is that something i need to do through an external terminal in order to unmount my volumes, or can it be done via mounted volume on the phone in terminal?

Trying these linux commamds for LVM expansion didnt seem to work:

[root@localhost nemo]# lvs
bash: lvs: command not found
[root@localhost nemo]# pvcreate
bash: pvcreate: command not found
[root@localhost nemo]# pvccreate
bash: pvccreate: command not found
[root@localhost nemo]# pvcreate bash: pvcreate: command not found
[root@localhost nemo]# vgcreate bash: vgcreate: command not found
[root@localhost nemo]# lvcreate bash: lvcreate: command not found
[root@localhost nemo]# vgextend bash: vgextend: command not found

When i create a new virtual volume what would i name it and will it matter later on? /dev/mapper/sailfish-root is already taken so i could name it /dev/root-expand?

Installed LVM pkcon install LVM and e2fsprogs

and ran:

[root@localhost nemo]# lvextend -L+4G /dev/mapper/sailfish-root Insufficient free space: 1024 extents needed, but only 0 available [root@localhost nemo]#

But it can only extend to the size of the logic volume which is 2.5GB so i guess i have to figure out how to increase the logical volume first.

Nice just created a new partition using fdisk and after writing the partition table and reboot the phone is bricked lol:

What i did was follow: http://geekswing.com/geek/unix/extending-a-linux-disk-with-lvm-extending-root-partition/

Which seemed reasonable enough: fdisk /dev/mapper/sailfish-home select n, e, p, 4, sector 5120001 to 25000000, w, reboot fdisk -l I could see my new ~9.5GB partition before the reboot, but after the reboot phone doesnt start up.

oops! Sorry to hear it did not go through cleanly!

Basically your approach was correct and should have worked unless Turing has something funny about their partitioning.

Can you recover the device via similar methods that are used with bricked Jolla sbj-1's? There are so few Turing devices around I don't know about the procedure.

@juiceme was able to check and correct the file system through the recovery terminal phew! And good news my 9.5GB partition is still there but its not a physical device yet and i can't create and add it to the LVM sailfish-root, i am getting the error:

fdisk -l (here is my new partition, created from space in -home ) Device Boot Start End Sectors Size Id Type
/dev/mapper/sailfish-home-part4 5120001 25000000 19880000 9.5G 5 Extended

[root@localhost nemo]# pvcreate /dev/mapper/sailfish-home-part4

ERROR: Device /dev/mapper/sailfish-home-part4 not found (or ignored by filtering).

@DarkTuring seems that you need someone who is really experienced with LVM.
I add exactly the same issue with a desktop last year. 2 Partition with LVM, the one for the system was too tight after some months.
And at beginning i thought that would be simple to make wider afterwards. NADA! tried different things, other people tried to help me but none was experienced. At last i made the installation again in traditional way.

Did you contact the jolla support team in charge of it? And maybe you could make a specific thread for helping on LVM partitions...

@cemoi71 let me create a new thread thats a good idea, Jolla Support wasnt all too helpful since its not a Jolla device but a Turing device and that company doesnt have support hehe. You are my support actually.

Hi can you paste output of following command for me:

devel-su du -x -a / | sort -n -r | head -n 50