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

Unable to install Anbox on BQ Aquaris M10 FHD

Scheduled Pinned Locked Moved Support
4 Posts 3 Posters 766 Views 3 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.
    • D Offline
      droid001
      last edited by 20 Oct 2020, 20:33

      I've attempted to install Anbox following the steps at dailyuse/anbox but ran into an error 28: No space left on device:

      phablet@ubuntu-phablet:~$ sudo apt update 
      Ign:1 http://repo.ubports.com xenial InRelease           
      Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
      Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease     
      Hit:4 http://repo.ubports.com xenial Release                            
      Hit:5 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease    
      Reading package lists... Error!                   
      W: No sandbox user '_apt' on the system, can not drop privileges
      E: Write error - write (28: No space left on device)
      E: IO Error saving source cache
      E: The package lists or status file could not be parsed or opened.
      

      I also tested the troubleshooting instructions at the end of the page with the same results. I've got 3.5G left on the device so one would think there is sufficient space.
      I checked the amount of inodes which are being used with
      sudo df -i / and there were 45% used.
      How can I run apt update without getting the "No space left on device" error?
      Running 16.04 (OTA-13) on a BQ Aquaris M10 FHD.

      Aquarius m10 FHD

      1 Reply Last reply Reply Quote 0
      • L Offline
        lalu
        last edited by 21 Nov 2020, 23:16

        I can confirm this issue.
        output of df -h:

        Filesystem                       Size  Used Avail Use% Mounted on
        udev                             978M  4.0K  978M   1% /dev
        tmpfs                            196M  760K  196M   1% /run
        /dev/disk/by-partlabel/userdata   13G  2.5G  9.8G  20% /userdata
        /dev/loop0                       2.0G  2.0G     0 100% /
        /dev/loop1                       243M  231M  6.5M  98% /android/system
        none                             4.0K     0  4.0K   0% /android
        tmpfs                            980M  4.0K  980M   1% /etc/fstab
        tmpfs                            980M  2.0M  978M   1% /var/lib/lxc/android/rootfs
        /dev/disk/by-partlabel/system    1.5G  2.4M  1.5G   1% /android/cache
        /dev/disk/by-partlabel/protect1  5.9M   44K  5.6M   1% /android/protect_f
        /dev/disk/by-partlabel/protect2  5.9M   44K  5.6M   1% /android/protect_s
        none                             4.0K     0  4.0K   0% /sys/fs/cgroup
        tmpfs                            980M   16K  980M   1% /tmp
        none                             5.0M     0  5.0M   0% /run/lock
        none                             980M   83M  898M   9% /run/shm
        none                             100M     0  100M   0% /run/user
        cgmfs                            100K     0  100K   0% /run/cgmanager/fs
        tmpfs                            980M     0  980M   0% /media
        tmpfs                            980M     0  980M   0% /var/lib/openvpn/chroot/tmp
        tmpfs                            980M     0  980M   0% /var/lib/sudo
        tmpfs                            196M   40K  196M   1% /run/user/32011
        tmpfs                            196M     0  196M   0% /run/user/0
        

        The problem seems to have to do with / and /dev/loop0 but I don't know how to advance from here. Any hint is appreciated.
        And thanks for all the time and effort you put into this!

        D 1 Reply Last reply 28 Nov 2020, 08:54 Reply Quote 0
        • D Offline
          droid001
          last edited by 26 Nov 2020, 19:25

          This might be a solution in regards to increasing the partition for Android.

          Aquarius m10 FHD

          1 Reply Last reply Reply Quote 0
          • D Offline
            doniks @lalu
            last edited by 28 Nov 2020, 08:54

            @lalu said in Unable to install Anbox on BQ Aquaris M10 FHD:

            The problem seems to have to do with / and /dev/loop0 but I don't know how to advance from here. Any hint is appreciated.

            I've never touched a M10, but from what you show (loop0) your root filesystem is mounted from a .img file and not from the system partition. The Nexus 7, which I have, is also like this. It is very easy to resize the .img file and get a larger root filesystem. I don't have it around right now to double check, but as far as I remember, I do this: boot to recovery, adb shell, to get into it and then resize2fs /data/ubuntu.img 4G to increase the size to 4 gigabyte . Of course, if you break it you get to keep the pieces, so make your own decisions wrt backups, and worst case fall back to reinstalling with the installer, which should always work

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