Upgrade to 4.5.x fails due to not enough space in /opt

General
#1

In one phone upgrade from latest 4.4.x to 4.5 fails with this error:

[...] sailfish-upgrade-ui[4664]: Distribution upgrade error: Subprocess failed. Error: RPM failed:         installing package appsupport-system-privileged-11.0.0.60.28-1.11.1.jolla.armv7hl needs 14MB more space on the /opt filesystem

If I look into /opt then I see that files are only in alien subfolder with this content:

username@:/opt/alien$ ls -lh
total 416M   
-rw-r--r--    1 root     root        4.0K Jul  7  2022 build.prop
-rw-r--r--    1 root     root      339.5M Jul  7  2022 system.img
--w-------    1 root     root       76.9M Dec  1  2019 system.img;5de434f9

File system.img;5de434f9 seems like something strange - can anyone advise if it simply can be deleted?

And are the other ones needed? Since Android layer is used in that phone, then probably yes…

#2

Is /opt on your device something separate from /? Because if not you can make some space (15MB) on root and continue.

#3

In this case /opt is on separate partition - that’s the way installer did it.

#4

Maybe this discussion provides some useful background information (although no solution):

#5

Thanks, @olf
Before starting this thread, I read earlier ones and found that one as well. But I do not know if it does apply to my case - I the phone has degooglified Android layer as it comes from Jolla Store.

Maybe someone from Jolla team would know if this strange file (system.img;5de434f9) has to be in that folder. If not then I could delete it and problem would be solved.

At least this refers to the possibility that system.img;5de434f9 is not needed:

# rpm -ql aliendalvik-system
/etc/gbinder.d/alien.conf
/opt/alien/build.prop
/opt/alien/system.img
#6

Basically it does, because …

  • the phone has degooglified Android layer as it comes from Jolla Store.

… all phones with a licensed SailfishOS have Alien Dalvik (recently aka “Android App Support”) and this is what the feature request I mentioned was about. The specific use case is different though.

Maybe someone from Jolla team would know if this strange file (system.img;5de434f9) has to be in that folder.

Yeah, “maybe”. But if you do not ask and do not file a bug report (you filed these posts is in the category “general discussion”) no “someone from Jolla team” will reply.

If not then I could delete it and problem would be solved.

Yes, likely nobody knows for sure, so you may delete it right away. But I would never “advise” to do so, because you are the system administrator of your Linux phone, hence you decide and you have the full responsibility for your actions. But as the file-name is weird, it is definitely not a full system image (too small), it is not even readable (only writeable for root) this file is most definitely garbage.

The more interesting point is, why it was created there: Something went wrong, but what? Maybe this is just a consequence of an earlier error.

At least this refers to the possibility that system.img;5de434f9 is not needed:

Yes, it is usually not there.

You may post the output of devel-su df -h here to see, at which places you have a space issue and how grave it is.

P.S.: In any case, do backup your data before trying to fix this. No backup, no mercy!

#7

I copied system.img;5de434f9 to partition outside / and /opt and continued with upgrade. It ended with an error, but rebooted and called itself after that 4.5.0.21. Looked up the error (this time not enough space on /) and saw that some 200 packages were not upgraded.

As UI did not offer any upgrades, so finished the whole thing with:

ssu re 4.5.0.21
zypper ref
zypper dup

After boot thereafter there were no errors and Android subsystem did its migration. Everything that is needed works currently fine.

Thanks to everyone who responded.