UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    No boot after update dev-chanel version 999

    Scheduled Pinned Locked Moved Fairphone 3
    5 Posts 2 Posters 278 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • K Offline
        Kutzi
        last edited by

        First thank you @Luksus for your great work to get Ubuntu Touch running on Fairphone 3(+). I use Ubuntu Touch daily on my Fairphone 3+ since it is available.

        Hi everyone,

        today i did an update from version 996 to version 999. After reboot the system didn't start anymore.

        Extract from log file /cache/ubuntu_updater.log:

        System Image Upgrader for Ubuntu Touch
        Preparing command file
        Starting image upgrader
        Loading keyring: archive-master.tar.xz
        Processing command file
        Loading keyring: image-master.tar.xz
        Loading keyring: image-signing.tar.xz
        unmount: /dev/block/mmcblk0p31: Invalid argument
        unmount: /cache/system: Invalid argument
        unmount: /system_root: Invalid argument
        e2fsck 1.43.3 (04-Sep-2016)
        /dev/block/bootdevice/by-name/system_b: recovering journal
        Pass 1: Checking inodes, blocks, and sizes
        Pass 2: Checking directory structure
        Pass 3: Checking directory connectivity
        Pass 4: Checking reference counts
        Pass 5: Checking group summary information
        Free blocks count wrong (137280, counted=137074).
        Fix? yes

        Free inodes count wrong (138269, counted=138219).
        Fix? yes

        /dev/block/bootdevice/by-name/system_b: ***** FILE SYSTEM WA
        S MODIFIED *****
        /dev/block/bootdevice/by-name/system_b: 58389/196608 files (
        0.0% non-contiguous), 649358/786432 blocks
        Keyring doesn't exist: device-signing
        Applying update: ubports-446b0c0babaff55a355fd3a17b20592aa2d
        68d19b4bc3c73203f87ba17660887.delta-ubports-0a2dc8c926909db0
        a49b675327b9c46df6b535c8affdf3146e746029df2361aa.tar.xz
        mv: bad 'data/': No such file or directory
        Keyring doesn't exist: device-signing
        Applying update: boot-66ae3c2e3bb0da6f5fed7791c8400b579583b4
        bc78d4719386229010d1349c4a.tar.xz
        mv: bad 'data/
        ': No such file or directory
        Keyring doesn't exist: device-signing
        Applying update: keyring-400895c98ce498ca2d89a7ff0266361b427
        057d52e4be69b10118fbcbf2eef34.tar.xz
        mv: bad 'data/': No such file or directory
        Keyring doesn't exist: device-signing
        Applying update: version-997.tar.xz
        mv: bad 'data/
        ': No such file or directory
        Keyring doesn't exist: device-signing
        Applying update: device-f80585d308a2fef0fd3fb75dc0a8bf1485ab
        9ad0d825c1d7869d51b85d3166bd.delta-device-09c58b19441bdc9423
        211b920922daa1d79095be8ca92a012750442248a5eebe.tar.xz
        mv: bad 'data/': No such file or directory
        Skipping missing file: boot-66ae3c2e3bb0da6f5fed7791c8400b57
        9583b4bc78d4719386229010d1349c4a.tar.xz
        Skipping missing file: keyring-400895c98ce498ca2d89a7ff02663
        61b427057d52e4be69b10118fbcbf2eef34.tar.xz
        Keyring doesn't exist: device-signing
        Applying update: version-998.tar.xz
        Keyring doesn't exist: device-signing
        Applying update: ubports-efafc0997df83d2170cb9b2854f60175bf3
        4dd8d9e77eb16e44aaafa982f46fb.delta-ubports446b0c0babaff55a
        355fd3a17b20592aa2d68d19b4bc3c73203f87ba17660887.tar.xz
        mv: bad 'data/
        ': No such file or directory
        Skipping missing file: boot-66ae3c2e3bb0da6f5fed7791c8400b57
        9583b4bc78d4719386229010d1349c4a.tar.xz
        Skipping missing file: keyring-400895c98ce498ca2d89a7ff02663
        61b427057d52e4be69b10118fbcbf2eef34.tar.xz
        Keyring doesn't exist: device-signing
        Applying update: version-999.tar.xz
        mv: bad 'data/*': No such file or directory
        Done upgrading...
        tune2fs 1.43.3 (04-Sep-2016)
        Setting reserved blocks percentage to 5% (638860 blocks)

        What happend?
        Is there any chance to get the system running again?

        mfG Kutzi

        LuksusL 2 Replies Last reply Reply Quote 0
        • LuksusL Offline
          Luksus @Kutzi
          last edited by

          @Kutzi Hm, there is a hotfix in the pipeline, which will be released as OTA-26. Maybe it broke something... I assume, you are using the devel-channel?

          Please try to reinstall with the ubports-installer (without wipe of course!).

          Devices: BQ e4.5, Fairphone 2, Fairphone 3, Lenovo X605F, Pinephone, Moto Z2 Force, OnePlus5T

          1 Reply Last reply Reply Quote 0
          • LuksusL Offline
            Luksus @Kutzi
            last edited by

            @Kutzi You can use the stable channel btw., since for xenial there won't come more new features and there is no benefit of using devel anymore.

            Devices: BQ e4.5, Fairphone 2, Fairphone 3, Lenovo X605F, Pinephone, Moto Z2 Force, OnePlus5T

            1 Reply Last reply Reply Quote 0
            • K Offline
              Kutzi
              last edited by

              @Luksus: Thank you for your quick response.

              All the time i use devel-channel. That's why I haven't changed it yet.
              Are there any efforts to port 20.04 for Fairphone 3(+)?

              LuksusL 1 Reply Last reply Reply Quote 0
              • LuksusL Offline
                Luksus @Kutzi
                last edited by

                @Kutzi there is already a focal-port. I am Using it for months now.
                Just needs an update-channel to make it available to all users.

                Devices: BQ e4.5, Fairphone 2, Fairphone 3, Lenovo X605F, Pinephone, Moto Z2 Force, OnePlus5T

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post