Failure to upgrade from 2.2.1.18 to 3.0.0.8

Question

1

Failure to upgrade from 2.2.1.18 to 3.0.0.8

asked 2018-11-21 11:44:30 +0300

TimoR
11 ●1 ●1 ●2

Hi all,

I'm trying to upgrade to Sailfish 3.0.0.8 on my Jolla 1 phone. I've got 6.8GB free on my disk but I still get in my /var/log/systemupdate.log

upgrade-system transaction /4522_ebaeeaab from uid 0 finished with failed after 9760ms

Distribution upgrade error: Installation aborted by user

Upgrade completed with code 2

Later on in the logs I also see

sailfish-upgrade-ui-la-system_update_failed_disk_full: en_GB (444 x 204 @ 1320)

which I don't think is the actual error message

I think the first attempt to upgrade may have really had too little disk space but it shouldn't be the case anymore.

What makes this annoying is that I can't enable developer mode anymore. It asks for my security code, asks to accept terms, then it waits a while and returns to the Developer tools page without enabling Developer mode. So I'm stuck using just Shell-Ex for debugging.

Also now using the phone is a bit difficult because the events view seems to be broken and all installs from Jolla store just hang.

Any thoughts on how to proceed or how to get the developer mode working again would be greatly appreciated

edit retag flag offensive close delete

Comments

Have you balanced BTRFS (after resolving the "disk full" situation by deleting files)?

You may do that at the command line (needs root though, IIRC) or per BTRFS balance checker 2 (which is a bit tricky to use).

olf ( 2018-11-21 18:17:13 +0300 )edit

Hello TimoR, I seem to have a very similar issue with my Jolla 1, being unable to enable developer mode included. Should you discover a method to clear the problem, without having to go through a factory set back, I would be happy to hear about it, thx -spectorr

spectorr ( 2018-11-23 22:47:46 +0300 )edit

Glad to know I'm not the only one. I think resetting the factory settings is the only approach now. Has anyone done that recently with Jolla 1? Can someone confirm if the upgrade path from a very old Sailfish version to 3 still works?

TimoR ( 2018-11-26 10:51:58 +0300 )edit

@spectorr, you can sure fix a broken tile in the bathroom by tearing down and rebuilding the whole house. And if the hammer is the only tool you know, then that might appear to be the only feasible approach.

BTW, you could also perform a BTRFS-balancer run at the command line of the recovery console.

@TimoR, yes.

olf ( 2018-11-26 20:13:50 +0300 )edit

thx @olf, for my part I am absolutely certain never to have seen less free space than 6.5GB, so I had not expected a file system problem. Having had a closer look, apart from the issues described by TimoR, I find that the email app and its settings wont open, additionally seems Storeman having issues not being able to access its repositories. No patches have been installed previosly, so none have had to be deactivated or removed at any prior os-updates either. I am willing to have a closer look as per your suggestion for a file system fix, altho, to me, it seemed unrelated at first.

spectorr ( 2018-12-02 16:44:12 +0300 )edit

Have you balanced BTRFS (after resolving the "disk full" situation by deleting files)?
You may do that at the command line (needs root though, IIRC) or per BTRFS balance checker 2 (which is a bit tricky to use).
olf ( 2018-11-21 18:17:13 +0300 )edit
Hello TimoR, I seem to have a very similar issue with my Jolla 1, being unable to enable developer mode included. Should you discover a method to clear the problem, without having to go through a factory set back, I would be happy to hear about it, thx -spectorr
spectorr ( 2018-11-23 22:47:46 +0300 )edit
Glad to know I'm not the only one. I think resetting the factory settings is the only approach now. Has anyone done that recently with Jolla 1? Can someone confirm if the upgrade path from a very old Sailfish version to 3 still works?
TimoR ( 2018-11-26 10:51:58 +0300 )edit
@spectorr, you can sure fix a broken tile in the bathroom by tearing down and rebuilding the whole house. And if the hammer is the only tool you know, then that might appear to be the only feasible approach.
BTW, you could also perform a BTRFS-balancer run at the command line of the recovery console.
@TimoR, yes.
olf ( 2018-11-26 20:13:50 +0300 )edit
thx @olf, for my part I am absolutely certain never to have seen less free space than 6.5GB, so I had not expected a file system problem. Having had a closer look, apart from the issues described by TimoR, I find that the email app and its settings wont open, additionally seems Storeman having issues not being able to access its repositories. No patches have been installed previosly, so none have had to be deactivated or removed at any prior os-updates either. I am willing to have a closer look as per your suggestion for a file system fix, altho, to me, it seemed unrelated at first.
spectorr ( 2018-12-02 16:44:12 +0300 )edit

Answer 1

0

answered 2018-12-14 18:27:28 +0300

TimoR
11 ●1 ●1 ●2

I finally found time to figure out the recovery mode and ran the btrfs balance

btrfs balance start -dusage=5 /mnt

Which relocated 1 chunk. Now I get a different error when upgrading

sailfish-upgrade-ui[628]: Enabled repository: adaptation0, adaptation0
sailfish-upgrade-ui[628]: Enabled repository: aliendalvik, aliendalvik
sailfish-upgrade-ui[628]: Enabled repository: apps, apps
sailfish-upgrade-ui[628]: Enabled repository: customer-jolla, customer-jolla
sailfish-upgrade-ui[628]: Enabled repository: eas, eas
sailfish-upgrade-ui[628]: Enabled repository: hotfixes, hotfixes
sailfish-upgrade-ui[628]: Enabled repository: jolla, jolla
sailfish-upgrade-ui[628]: Enabled repository: store, store
sailfish-upgrade-ui[628]: Enabled repository: xt9, xt9
PackageKit[660]: get-repo-list transaction /4558_edbedbbb from uid 0 finished with success after 388ms
sailfish-upgrade-ui[628]: Setting the enabled state of store to false
PackageKit[660]: uid 0 is trying to obtain org.freedesktop.packagekit.system-sources-configure auth (only_trusted:0)
PackageKit[660]: uid 0 obtained auth for org.freedesktop.packagekit.system-sources-configure
PackageKit[660]: repo-enable transaction /4559_cddbbeee from uid 0 finished with success after 34ms
sailfish-upgrade-ui[628]: Upgrading distribution jolla-configuration-sbj
PackageKit[660]: uid 0 is trying to obtain org.freedesktop.packagekit.upgrade-system auth (only_trusted:0)
sailfish-upgrade-ui[628]: Progress: 101
PackageKit[660]: uid 0 obtained auth for org.freedesktop.packagekit.upgrade-system
sailfish-upgrade-ui[628]: Progress: 101
sailfish-upgrade-ui[628]: Progress: 0
sailfish-upgrade-ui[628]: Progress: 100
packagekitd[660]: adaptation0 is not cached! Do a refresh
packagekitd[660]: aliendalvik is not cached! Do a refresh
packagekitd[660]: apps is not cached! Do a refresh
packagekitd[660]: customer-jolla is not cached! Do a refresh
packagekitd[660]: eas is not cached! Do a refresh
packagekitd[660]: hotfixes is not cached! Do a refresh
packagekitd[660]: jolla is not cached! Do a refresh
packagekitd[660]: xt9 is not cached! Do a refresh
packagekitd[660]: Pattern not found: pattern:jolla-configuration-sbj
sailfish-upgrade-ui[628]: Progress: 0
sailfish-upgrade-ui[628]: Progress: 100
mce[578]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
sailfish-upgrade-ui[628]: Progress: 0
packagekitd[660]: Before commit: 0 downloads, 0 installs, 0 removals
packagekitd[660]: Byte sizes: 0 download, 0 install, 0 remove, 0 cached
packagekitd[660]: Download space required 0 bytes, available 7301263360 bytes
packagekitd[660]: Installation space required 0 bytes, available 7301263360 bytes
mce[578]: modules/proximity.c: report_proximity(): state: CLOSED -> OPEN
sailfish-upgrade-ui[628]: Progress: 100
PackageKit[660]: upgrade-system transaction /4560_dbbcaabd from uid 0 finished with success after 2786ms
sailfish-upgrade-ui[628]: Upgrade completed with code 1
sailfish-upgrade-ui[628]: Reverting the enabled state of store to true
PackageKit[660]: uid 0 is trying to obtain org.freedesktop.packagekit.system-sources-configure auth (only_trusted:0)
PackageKit[660]: uid 0 obtained auth for org.freedesktop.packagekit.system-sources-configure
PackageKit[660]: repo-enable transaction /4561_eaaedcad from uid 0 finished with success after 23ms
DSME[600]: reboot request received over D-Bus from pid 628: /usr/libexec/sailfish-upgrade-ui
DSME[600]: dummy reply to com.nokia.dsme.request.req_reboot

It still takes very short time and it just automatically reboots afterwards without doing anything. Any more suggestions on what to try?

edit flag offensive delete publish link

Comments

No, you do not get any error at all, anymore: Problem solved! ;)

More seriously, as you are still struggling to update at the command line:

There is no error message anymore, so BTRFS-balancing solved the original issue.
The update process you triggered did nothing, because "<repo xyz=""> is not cached! Do a refresh</repo>".

So why don't you try to issue a pkcon refresh (as root) as instructed?
One should also follow Jolla's guide how to upgrade SFOS at the command line (especially the steps after a successful upgrade, see section "Final clean up"). Guides provided here at TJC tend to omit crucial steps (i.e., commands).

If all that fails (including the sections "If it keeps failing" and "Troubleshooting" in Jolla's guide) come back here, I have a few more tricks in store.

olf ( 2018-12-14 21:28:46 +0300 )edit

I can run pkcon refresh from shell-ex and it will prompt for my security code. It seems to run successfully but doesn't really do anything. I also ran the cleanup bits from your link. Meaning, I removed the files.

Upgrading still fails and there's nothing new in the /var/log/systemupdate.log

It's a bit difficult to run things as root as I can't enable the developer mode.

TimoR ( 2018-12-17 11:47:00 +0300 )edit

@TimoR, without the ability to become root user, it does not make much sense to continue to try upgrading, as most failures will likely be caused by not being root. So lets try to address this issue first.

Why are you using ShellEx? As it is not a proper Shell, IMO it is only suitable to issue a single command every now and then, but not for any more intensive use or debugging.
Does ToeTerm not install / work for you?
What do you mean with "it will prompt for my security code"? Do you mean "it asks for the root password" (which is the "ssh password" set in the SFOS settings app) by that? Can you please Cut&Paste the exact message displayed.
How do you perform your manual upgrading exactly? All guides have a shell and being root user (per devel-su) as prerequisites, which you apparently cannot fulfill (currently). Can you please Cut&Paste which sequence of commands you use.

Side note: An inconvenient, but feasible way would be to become root at the recovery console, mount the system partitions and perform the SFOS upgrade manually there. While the commands to perform the upgrade are the same, the preparation is much more error prone.
So lets first try to analyse and solve your "not becoming root" issue when booted regularly.

olf ( 2018-12-18 17:30:32 +0300 )edit

Answer 2

0

answered 2019-01-15 10:58:46 +0300

TimoR
11 ●1 ●1 ●2

Couldn't get around to enable root access. I did the factory reset an now it's all fine

edit flag offensive delete publish link

Comments

thx for letting us know. I will then do the same, but needless to say really, I'm rather unhappy about this issue happening in the first place. Perhaps worth mentioning, with system upgrades possibly being this problematic, maybe it might be a good idea enabling developer mode BEFORE doing essential updating. regards

spectorr ( 2019-01-19 16:06:00 +0300 )edit

Failure to upgrade from 2.2.1.18 to 3.0.0.8

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Failure to upgrade from 2.2.1.18 to 3.0.0.8

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions