So, I’ve been trying unsuccessfully to resize the root partition.
One of the issues that I have is the following:
Jolla Recovery v2.0
Welcome to the recovery tool!
The available options are:
- Reset device to factory state
- Reboot device
- Shell
- Perform file system check
- Run sshd
- 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
/dev/mmcblk1: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk1: read failed after 0 of 4096 at 62537007104: Input/output error
/dev/mmcblk1: read failed after 0 of 4096 at 62537064448: Input/output error
/dev/mmcblk1: read failed after 0 of 4096 at 4096: Input/output error
/dev/mmcblk1p1: read failed after 0 of 4096 at 62520229888: Input/output error
/dev/mmcblk1p1: read failed after 0 of 4096 at 62520287232: Input/output error
/dev/mmcblk1p1: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk1p1: read failed after 0 of 4096 at 4096: Input/output error
2 logical volume(s) in volume group “sailfish” now active
Thu Mar 3 12:53:01 UTC 2022
Type your devicelock code and press [ENTER] key:
(please note that the typed numbers won’t be shown for security reasons)
The second problem would be that the e2fsck -f /dev/sailfish/home reports a ton of issues:
Just one for reference:
/ # e2fsck -f /dev/sailfish/home
e2fsck 1.45.4 (23-Sep-2019)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks…
Superblock has an invalid journal (inode 8).
Clear? cancelled!
e2fsck: The journal superblock is corrupt while checking journal for home
e2fsck: Cannot proceed with file system check
and if I run this with a -y option, these would be fixed, or so it would seem, because after that, the device is locked, because the lock code is no longer valid (hash file messed up during these file system fixes?). I’ve seen this problem in one of other threads here, but there is no definite solution.
So, the following thing I did is to reset the device back to factory state, choosing the option #1 in the recovery menu. That cleared everything alright, but upon another try of e2fsck, the same issues arose. How is that possible, and more importantly, how can I get around this problem?
Thanks!
P.S. I can’t really get a hang of this formatting system in the thread…
What would be the markup for code/console?