The Following 3 Users Say Thank You to olf For This Useful Post: | ||
|
2021-09-26
, 08:04
|
Posts: 177 |
Thanked: 427 times |
Joined on Sep 2017
|
#12
|
The Following User Says Thank You to suicidal_orange For This Useful Post: | ||
|
2021-09-26
, 16:44
|
|
Posts: 304 |
Thanked: 1,246 times |
Joined on Aug 2015
|
#13
|
Guess that means I have to uninstall stuff until I have 1GB free so sfos-upgrade doesn't complain, update, then lie to Jolla to get the latest recovery and resize so it works next time.
The Following 2 Users Say Thank You to olf For This Useful Post: | ||
|
2021-09-27
, 21:10
|
Posts: 177 |
Thanked: 427 times |
Joined on Sep 2017
|
#14
|
/ # e2fsck -f /dev/mapper/sailfish-root /dev/mapper/sailfish-root is mounted. e2fsck: Cannot continue, aborting.
The Following User Says Thank You to suicidal_orange For This Useful Post: | ||
But you really shall not use an older or vastly different (i.e., far newer) version.
(IIRC, I phrased this carefully in my guide to extend the root volume size.)
Side note: This is the same for all Linux computers, be it a PC, Notebook, Phone, whatever! Please refrain from using "anything that boots". While the on disk format of LVM and classical file systems should stay the same and changes always shall be upward compatible, nobody tests with vastly different versions of the tools to modify them (LVM and FS resize), so subtle incompatibilities may occur. And mind that you modify with newer tools (externally booted) and then boot the installed OS with the old versions, so upward compatibility is not sufficient.