Here is the output of mount -a:
:~$ adb shell
root@FP3:/ # mount -a
mount: '/dev/block/platform/soc/7824900.sdhci/by-name/vendor_a'->'/vendor': No such file or directory
mount: '/dev/block/mmcblk1p1'->'/sdcard': No such file or directory
mount: '/dev/block/bootdevice/by-name/boot'->'/boot': No such file or directory
mount: '/dev/block/bootdevice/by-name/misc'->'/misc': No such file or directory
Is the filesystem corrupt?
How can I check this using adb?
Hi everyone,
a few days ago, I updated my UT 20.04, which is installed on slot b, using ubports-installer. Previously, slot b also had UT 20.04 installed, which I used daily. The update process went smoothly and the operating system ran flawlessly, just as it did before the update.
In the Ubports installer, I saw that two channels with UT 24.04 were already available. A few hours after updating UT 20.04, I decided to switch the slot from b to a and install UT 24.04 there. Previously, slot a had UT 16.04 installed, which was still running, but I was no longer using it. The installation of UT 24.04 in slot a ran without errors and I was able to start the system without any problems. However, after using it for a short time, I noticed that Waydroid would not start. Since I absolutely need Waydroid for a few programs, I switched the slot back from a to b and started UT 20.04 as usual without any errors.
After a while, a message appeared saying that there was insufficient storage space. However, as I did not see this message immediately, it disappeared before I could read the source. UT 20.04 then stopped responding to commands. I could still perform sideways swipe gestures, but I could no longer open apps or press buttons. After a while, a message appeared saying that there was insufficient storage space. However, as I did not see this message immediately, it disappeared before I could read the source. UT 20.04 then stopped responding to commands. I could perform side swipe gestures, but I could no longer open apps or press buttons. Then I had to restart the device, which failed. UT 20.04 would no longer start. After changing the slot from b to a again, UT 24.04 started, but extremely slowly and stopped at the welcome screen. It no longer responded to user input. Reinstallation via ubports-installer is no longer possible for either UT 20.04 or UT 24.04, as the installer aborts shortly before the end of the installation.
I found out the following information using adb-shell:
root@FP3:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1825940 18616 1807324 2% /
tmpfs 1825940 804 1825136 1% /dev
tmpfs 1825940 0 1825940 0% /mnt
tmpfs 1825940 116 1825824 1% /tmp
tmpfs 1825940 0 1825940 0% /storage
/dev/block/mmcblk0p62 50044592 50028208 16384 100% /cache
The cache partition appears to be completely full. Could this be the problem?
Can I delete it without losing user data such as contacts, calendar, app settings, etc.?
What do I need to do to delete the cache data?
Thank you very much for your help...
Work with Peltor WS5 Workstyle Headset.
@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(+)?
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