3.2.0.12 update fails on Accione P

Question

1

3.2.0.12 update fails on Accione P

asked 2019-11-28 21:46:55 +0200

jsommer
3324 ●97 ●142 ●154

The update for my productive Accione P device fails. It just shows the message after reboot and starting the installation process, that the update failed. I just have the option to press a button to reboot the device.

Maybe the system partition is too small again as described in this thread: https://together.jolla.com/question/204797/will-an-update-for-accione-and-accione-p-devices-be-available/

What is the minimal disc space? I have 620 MB free on system data and 1,4 GB free on user data.

Has someone any idea?

edit retag flag offensive close delete

Comments

3

make sure you did not installed or removed any package during download process and before update reboot

also please tell where to buy accione.

coderus ( 2019-11-29 00:33:30 +0200 )edit

1

I use the regular way to update the device: I checked system updates in the settings app ant trigger the download as well the installation.

Because, Accione P comes with an official Sailfish OS release including Alien Dalvik, the update should work. But I’m afraid, there is a disk space issue. I’m not sure.

I bought the Accione P and Accione device directly from Jala. Unfortunately I don’t get any updates for the Accione device, only for my Accione P devices.

jsommer ( 2019-11-29 10:22:59 +0200 )edit

Check if this article helped you:
https://jolla.zendesk.com/hc/en-us/articles/360005795474

jovirkku ( 2019-11-29 18:12:57 +0200 )edit

Thanks for your suggestion. As I assumed there seem to be a disc space error:

version --dup
REFRESHING CACHE AND DOWNLOADING PACKAGES
Finished transaction (status=1, runtime=90028ms)
UPGRADING SYSTEM
[0 %] [Install] droid-system-hy005 0.0.10-1.7.3.jolla: [50 %]
Error: Subprocess failed. Error: RPM failed:    installing package droid-system-hy005-0.0.10-1.7.3.jolla.armv7hl needs 123MB on the / filesystem

Finished transaction (status=2, runtime=13585ms)
UPGRADE NOT COMPLETE - Retry 1 of 9

I’m wondering which partition the download is using? Is it system data? I have 620 MG free disc space on that partition. I realize, that system protocols have 29.5 MB. Maybe I can remove them.

jsommer ( 2019-11-29 23:11:04 +0200 )edit

make sure you did not installed or removed any package during download process and before update reboot
also please tell where to buy accione.
coderus ( 2019-11-29 00:33:30 +0200 )edit
I use the regular way to update the device: I checked system updates in the settings app ant trigger the download as well the installation.
Because, Accione P comes with an official Sailfish OS release including Alien Dalvik, the update should work. But I’m afraid, there is a disk space issue. I’m not sure.
I bought the Accione P and Accione device directly from Jala. Unfortunately I don’t get any updates for the Accione device, only for my Accione P devices.
jsommer ( 2019-11-29 10:22:59 +0200 )edit
Check if this article helped you:
https://jolla.zendesk.com/hc/en-us/articles/360005795474
jovirkku ( 2019-11-29 18:12:57 +0200 )edit
Thanks for your suggestion. As I assumed there seem to be a disc space error:
version --dup REFRESHING CACHE AND DOWNLOADING PACKAGES Finished transaction (status=1, runtime=90028ms) UPGRADING SYSTEM [0 %] [Install] droid-system-hy005 0.0.10-1.7.3.jolla: [50 %] Error: Subprocess failed. Error: RPM failed: installing package droid-system-hy005-0.0.10-1.7.3.jolla.armv7hl needs 123MB on the / filesystem Finished transaction (status=2, runtime=13585ms) UPGRADE NOT COMPLETE - Retry 1 of 9
I’m wondering which partition the download is using? Is it system data? I have 620 MG free disc space on that partition. I realize, that system protocols have 29.5 MB. Maybe I can remove them.
jsommer ( 2019-11-29 23:11:04 +0200 )edit

Accepted Answer

3

answered 2020-01-06 16:52:01 +0200

jsommer
3324 ●97 ●142 ●154

Here is the solution. Thanks to Eugenio and others of the Sailfish OS Fan Club Telegram Group. The Sailfish Community is awesome.

Enable developer mode in the Sailfish settings app.
Enable remote login inside of the developer settings.
Connect to your device using ssh nemo@ip-address with the ip-address, that is shown in the developer settings.
Switch to root user with devel-su.
Add your public key to the file /home/nemo/.ssh/authorized_keys.
Copy the file to the root user with cp /home/nemo/.ssh/authorized_keys /root/.ssh/authorized_keys.
Quit the ssh connection with exit.
Connect to your device using ssh root@ip-address with the ip-address, that is shown in the developer settings.
Prepare unmounting the home partion:
1. mkdir -p /var/lib/tmp/connman
2. cp -Rav /home/.system/var/lib/connman/* /var/lib/tmp/connman
3. Edit /etc/connman/main.conf by setting StorageRoot = /var/lib/tmp
Restart connman or reboot the device.
If you restart reconnect with ssh root@ip-address
Stop the user session systemctl stop user@100000.service.
Check to which size you need to shrink the home partition, for example with lsblk. Let's assume the partition is 22GB large.
Shrink your /home to 21GB (for instance 1GB less than the current size) with lvresize -L 21G --resizefs --autobackup y sailfish/home (this step will include unmounting /home, for that to be possible we had to stop the user session.) 15.Check the file system with vgs, lvs and df -h
Expand the root partition with the above chosen size (1GB for instance) lvextend -L +1G --resizefs sailfish/root
Finally reboot your device with systemctl reboot.

edit flag offensive delete publish link

Answer 2

2

answered 2019-12-17 00:46:43 +0200

jsommer
3324 ●97 ●142 ●154

updated 2019-12-17 01:57:15 +0200

Unfortunately I couldn't find a solution to update my Accione P, because I couldn't access my device in recovery mode through telnet to resize the system partition. I use a MacBook Pro with USB-C, that could be the problem. However the linked solution in my initial post did work in the past. I tried the following:

It's not possible to install HoRNDIS on macOS Catalina any more.
I installed HoRNDIS and Telnet with Homebrew on a macOS Mojave partition. However I get a time out error, if I try to access the device with telnet.
I tried three different cables, with and without USB-A to USB-C adapter.
I tried KDE and Ubuntu Desktop as a VM with VMWare Fusion on the Mojave Partition.
I installed a Ubuntu Desktop VM with VMWare on the Mojave partition.
I tried Windows 10 as a VM with VMWare, but I couldn't find the driver, that is mentioned in the Zendesk documentation for accessing the device in recovery mode.
I also tried the system update with a terminal command via ssh over WLAN as linked in one of the comments. I just get the error of missing disk space.
I also tried an older MacBook Pro 15 with USB-A ports, but it has also Catalina installed.

Maybe I will try it on a more older Macbook Pro 17 with High Sierra, but in the past I only could access my device in recovery mode with a Linux VM.

The only solution that might work is, to delete unnecessary libraries on the system partition, that are reinstalled with an update of the system. My system partition has a size of 2.5 GB. 1.8 GB are used and 600 GB are free. 1.5 GB are used for "Sailfish OS and other files", 40.6 MB for Sailfish apps, 29 MB for system protocols, 4 KB for Sailfish SDK and 0 KB for the rest.

EDIT

I have tested the recovery mode of my Accione developer device. I can access this device. I is still using release 2 of Sailfish OS, because Jala doesn't provide any updates for this device. Only for Accione P.

So, the problem is my Accione P. Maybe a hardware problem, but USB-C works for charging. I assume some firmware or operating system issue. It's frustrating. Has someone any idea?

edit flag offensive delete publish link

Answer 3

2

answered 2019-12-17 11:43:07 +0200

jsommer
3324 ●97 ●142 ●154

I found this thread https://together.jolla.com/question/200683/sailfishx-gemini-the-rootfs-is-too-small/ with the following suggested solution without the recovery mode.

enable dev mode

enable remote login, noting the password for nemo

devel-su

drop your ssh pubkey in /root/.ssh/authorized_keys

ssh in directly as root (we will be killing the user session in a moment)

stop the user session [root@Sailfish ~]# systemctl stop user@100000.service

shrink your /home to 32GiB with [root@Sailfish ~]# lvresize -L 32G --resizefs --autobackup y sailfish/home (this step will include unmounting /home, for that to be possible we had to stop the user session.)

cleanly reboot your Sailfish X device with [root@Sailfish ~]# systemctl reboot

Afterwards I need to increase the size of the system partition. Unfortunately I'm missing some details:

How can I create the keys after I have removed them?
Do I need to reboot between step 4 and 5 or just re-establish an ssh session? With ssh root@ip-adress-of-my-device?
To which size should I shrink the home partition. It's usually not just the memory size of 32GB minus home partition size and system partition system size.

edit flag offensive delete publish link

Comments

1

Before doing all of this, have you tried to free at least 3 GB on your /home partition?

Giacomo Di Giacomo ( 2019-12-17 11:57:15 +0200 )edit

Thanks for your comment. Yes, I had removed all music files. I have 14.5 GB free on the home partition.

jsommer ( 2019-12-17 13:31:17 +0200 )edit

Answer 4

1

answered 2020-01-02 19:36:29 +0200

jsommer
3324 ●97 ●142 ●154

The Sailfish community suggests to use fdisk. I'm not familiar with this tool. So the next question is, how to use it.

The partitions seem to me confusing, because 22.3 GB home partition and 2.5 GB root partition seem to me little for 32 GB RAM of the device. Here is the listing of fdisk:

Disk /dev/zram0: 512 MiB, 536870912 bytes, 131072 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mmcblk0: 29.1 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98101B32-BBE2-4BF2-A06E-2BB33D000C20

Device            Start      End  Sectors  Size Type
/dev/mmcblk0p1   131072   303103   172032   84M Microsoft basic data
/dev/mmcblk0p2   393216   393217        2    1K unknown
/dev/mmcblk0p3   393218   393233       16    8K unknown
/dev/mmcblk0p4   393234   394257     1024  512K unknown
/dev/mmcblk0p5   394258   395281     1024  512K Microsoft basic data
/dev/mmcblk0p6   395282   396305     1024  512K unknown
/dev/mmcblk0p7   396306   397329     1024  512K Microsoft basic data
/dev/mmcblk0p8   397330   401425     4096    2M unknown
/dev/mmcblk0p9   401426   405521     4096    2M Microsoft basic data
/dev/mmcblk0p10  405522   406033      512  256K unknown
/dev/mmcblk0p11  406034   406545      512  256K unknown
/dev/mmcblk0p12  406546   439313    32768   16M Microsoft basic data
/dev/mmcblk0p13  439314   442385     3072  1.5M unknown
/dev/mmcblk0p14  442386   445457     3072  1.5M unknown
/dev/mmcblk0p15  524288   524351       64   32K unknown
/dev/mmcblk0p16  524352   527423     3072  1.5M unknown
/dev/mmcblk0p17  527424   527455       32   16K unknown
/dev/mmcblk0p18  655360   677887    22528   11M unknown
/dev/mmcblk0p19  786432   788479     2048    1M unknown
/dev/mmcblk0p20  788480   790527     2048    1M Microsoft basic data
/dev/mmcblk0p21  790528   921599   131072   64M unknown
/dev/mmcblk0p22  921600  1052671   131072   64M unknown
/dev/mmcblk0p23 1052672  1054719     2048    1M unknown
/dev/mmcblk0p24 1054720  7346175  6291456    3G unknown
/dev/mmcblk0p25 7471104  7995391   524288  256M unknown
/dev/mmcblk0p26 7995392  8060927    65536   32M unknown
/dev/mmcblk0p27 8060928  8062975     2048    1M unknown
/dev/mmcblk0p28 8062976  8063999     1024  512K unknown
/dev/mmcblk0p29 8064000  8064063       64   32K unknown
/dev/mmcblk0p30 8064064  8588351   524288  256M unknown
/dev/mmcblk0p31 8650752  8650815       64   32K unknown
/dev/mmcblk0p32 8781824  8782847     1024  512K Microsoft basic data
/dev/mmcblk0p33 8782848  8784895     2048    1M unknown
/dev/mmcblk0p34 8784896  8850431    65536   32M unknown
/dev/mmcblk0p35 8850432  8851455     1024  512K unknown
/dev/mmcblk0p36 8851456  8859647     8192    4M Microsoft basic data
/dev/mmcblk0p37 8912896  8913407      512  256K unknown
/dev/mmcblk0p38 8913408  8913919      512  256K unknown
/dev/mmcblk0p39 8913920  8914431      512  256K unknown
/dev/mmcblk0p40 8914432  8914943      512  256K unknown
/dev/mmcblk0p41 8914944  8915455      512  256K unknown
/dev/mmcblk0p42 8915456  8915967      512  256K unknown
/dev/mmcblk0p43 9043968  9044479      512  256K unknown
/dev/mmcblk0p44 9044480  9044991      512  256K unknown
/dev/mmcblk0p45 9044992  9045007       16    8K unknown
/dev/mmcblk0p46 9045008  9176079   131072   64M unknown
/dev/mmcblk0p47 9176080 61071326 51895247 24.8G unknown

Disk /dev/mapper/sailfish-root: 2.5 GiB, 2621440000 bytes, 5120000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/sailfish-home: 22.3 GiB, 23945281536 bytes, 46768128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I also checked the structure of the filesystem with df -h:

Filesystem            Size  Used Avail Use% Mounted on
rootfs                2.4G  1.8G  600M  75% /
/dev/sailfish/root    2.4G  1.8G  600M  75% /
devtmpfs              1.4G  680K  1.4G   1% /dev
tmpfs                 1.4G     0  1.4G   0% /dev/shm
tmpfs                 1.4G   20M  1.4G   2% /run
tmpfs                 1.4G     0  1.4G   0% /sys/fs/cgroup
tmpfs                 1.4G  8.0K  1.4G   1% /tmp
tmpfs                 1.4G     0  1.4G   0% /mnt
/dev/mmcblk0p24       794M  705M   68M  92% /fimage
/dev/mmcblk0p26        28M  408K   27M   2% /persist
/dev/mmcblk0p12        12M  5.0M  6.5M  44% /dsp
/dev/mmcblk0p1         84M   71M   14M  85% /firmware
/dev/mapper/sailfish-home
                       22G   11G   12G  49% /home
tmpfs                 284M  1.2M  283M   1% /run/user/100000
/dev/mapper/sailfish-home
                       22G   11G   12G  49% /opt/alien/data
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/bin
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/sbin
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/lib
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/usr
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/var
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/etc
tmpfs                 1.4G  8.0K  1.4G   1% /opt/alien/tmp
/dev/mapper/sailfish-home
                       22G   11G   12G  49% /opt/alien/home
devtmpfs              1.4G  680K  1.4G   1% /opt/alien/dev
tmpfs                 1.4G     0  1.4G   0% /opt/alien/dev/shm
tmpfs                 1.4G     0  1.4G   0% /opt/alien/sys/fs/cgroup
tmpfs                 1.4G   20M  1.4G   2% /opt/alien/run
tmpfs                 284M  1.2M  283M   1% /opt/alien/run/user/100000
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/media
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/vendor
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/system_jolla
/dev/sailfish/root    2.4G  1.8G  600M  75% /opt/alien/data_jolla

I couldn't find a command to resize a partition. I think I have to use resize2fs. I found this article, but the steps include a deletion of a partition. I want to avoid it: https://geekpeek.net/resize-filesystem-fdisk-resize2fs/

Does someone knows a good tutorial?

edit flag offensive delete publish link

Comments

Have you tried this one? https://together.jolla.com/question/156279/installing-system-updates-fails-when-there-is-not-enough-space-in-system-data-partition/?answer=156670#post-id-156670

avhakola ( 2020-01-03 18:18:04 +0200 )edit

Yes, the problem is, that I can't access the device via USB-C in recovery mode. The linked approach worked in the past. but something has changed, hopefully not a hardware defect. Anyway I have to find another solution.

jsommer ( 2020-01-03 19:13:15 +0200 )edit

Answer 5

1

answered 2020-01-05 18:07:37 +0200

jsommer
3324 ●97 ●142 ●154

updated 2020-01-05 18:08:29 +0200

The linked solution in answer 3 seem to be promising: https://together.jolla.com/question/200683/sailfishx-gemini-the-rootfs-is-too-small/

I was able to follow the steps, but I'm not sure about the parameters for resizing according the partition names:

lvresize -L 32G --resizefs --autobackup y sailfish/home
lvextend -L +1G --resizefs sailfish/root

Answer 4 lists the partition names:

/dev/mapper/sailfish-home
/dev/mapper/sailfish-root

edit flag offensive delete publish link

3.2.0.12 update fails on Accione P

Comments

5 Answers

Comments

Comments

Question tools

Stats

Related questions

3.2.0.12 update fails on Accione P

Comments

5 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions