Thread: Sailfish OS on Sony Xperia X (community build)
View Single Post
Kabouik is offline Kabouik
2018-12-05 , 01:14
Posts: 1,335 | Thanked: 3,931 times | Joined on Jul 2010 @ Brittany, France
#356
I tried to revert it to what it was with this:

Code:
lvm> lvreduce -L -4g /dev/sailfish/root
  WARNING: Reducing active and open logical volume to 2.44 GiB.
  THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce sailfish/root? [y/n]: y
  Size of logical volume sailfish/root changed from 6.44 GiB (1649 extents) to 2.44 GiB (625 extents).
  Logical volume sailfish/root successfully resized.
lvm> pvdisplay
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
  --- Physical volume ---
  PV Name               /dev/mmcblk0p51
  VG Name               sailfish
  PV Size               22.25 GiB / not usable 3.00 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              5696
  Free PE               1024
  Allocated PE          4672
  PV UUID               kCP1du-tUEV-1u0I-733O-g3bG-z0d1-VZXIAw
   
lvm> lvextend -L +4g /dev/sailfish/home
  Size of logical volume sailfish/home changed from <15.81 GiB (4047 extents) to <19.81 GiB (5071 extents).
  Logical volume sailfish/home successfully resized.
lvm> exit
  Exiting.
/ # resize2fs /dev/sailfish/home
resize2fs 1.43.1 (08-Jun-2016)
The filesystem is already 5192704 (4k) blocks long.  Nothing to do!

/ # resize2fs /dev/sailfish/root
resize2fs 1.43.1 (08-Jun-2016)
resize2fs: New size smaller than minimum (829066)

/ # lvm
lvm> lvscan
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  ACTIVE            '/dev/sailfish/root' [2.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [<19.81 GiB] inherit
lvm> exit
But now I am in a boot loop, of course.

Back to recovery mode, it now says my root partition cannot be mounted:

Code:
-----------------------------
     Jolla Recovery v2.0
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset device to factory state
2) Reboot device
3) Shell
4) Perform file system check
5) Run sshd
6) Exit
Type the number of the desired action and press [Enter]: 
3

If you continue, this may void your warranty. Are you really SURE? [y/N] y

  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
  2 logical volume(s) in volume group "sailfish" now active
mount: mounting /dev/sailfish/root on /rootfs failed: Invalid argument
[WARNING] Root file system unaccessible, bypassing device lock check.
/ #
I am kind of hopeless, I would really want to avoid a factory reset. I know I should have made a backup, but I was probably too confident after doing the same procedure with no issues on my Jolla C several times. Even if a factory reset or even a Sailfish X reflash are the only way, I would want to backup my $HOME from the recovery shell first, but I have no idea how to do that since my rootfs does not mount anymore.
Last edited by Kabouik; 2018-12-05 at 01:40.
 

The Following 2 Users Say Thank You to Kabouik For This Useful Post: