Yunohost 3.0 on raspberry 3 Problem of disc size and app install

Version française plus bas.

Firstly, try to make a research of your problem on this forum. Try with the text of the error if you have an error displayed.

My YunoHost configuration

Hardware: rpi 3
Internet access: ethernet at home
YunoHost version:
yunohost: 3.0
yunohost-admin: 3.0
moulinette: 3.0
ssowat: 3.0

After installing yunohost on a sd card I can see that the system don’t use the full size of the disc, only 2Go while there is 8Go. I mean the system doesn’t reconize the full disc. Even after the post install etc.

The when I want to install app such as nextcloud or Wallabag or Etherpad Mypads it doesn’t work. I give you some logs.

But I’m able to install app like Jirafeau. So I think the main probelm is the disk space.
For Nextcloud :

La configuration de SSOwat a été générée

Remove the user nextcloud

/etc/cron.d/nextcloud wasn't deleted because it doesn't exist.

Removing database nextcloud

!!

nextcloud's script has encountered an error. Its execution was cancelled.

!!

Unable to install Nextcloud

2018-06-28 14:10:56 URL:https://download.nextcloud.com/server/releases/nextcloud-13.0.2.tar.bz2 [44842305/44842305] -> "app.tar.bz2" [1]

dpkg-preconfigure: unable to re-open stdin:

debconf: falling back to frontend: Teletype

debconf: (This frontend requires a controlling tty.)

debconf: unable to initialize frontend: Readline

debconf: falling back to frontend: Readline

debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)

debconf: unable to initialize frontend: Dialog

dpkg-preconfigure: unable to re-open stdin:

debconf: falling back to frontend: Teletype

debconf: (This frontend requires a controlling tty.)

debconf: unable to initialize frontend: Readline

debconf: falling back to frontend: Readline

debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)

debconf: unable to initialize frontend: Dialog

For Etherpad Mypads :

 The user etherpad_mypads was not found

/etc/fail2ban/filter.d/etherpad_mypads.conf wasn't deleted because it doesn't exist.

/etc/fail2ban/jail.d/etherpad_mypads.conf wasn't deleted because it doesn't exist.

/etc/nginx/conf.d/mondomaine.net.d/etherpad_mypads.conf wasn't deleted because it doesn't exist.

/var/www/etherpad_mypads wasn't deleted because it doesn't exist.

ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 1

Removing database

/usr/local/n wasn't deleted because it doesn't exist.

Logged from file actionsmap.py, line 502

IOError: [Errno 28] No space left on device

self.stream.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 845, in flush

self.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 885, in emit

Traceback (most recent call last):

Logged from file app.py, line 1101

IOError: [Errno 28] No space left on device

self.stream.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 845, in flush

self.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 885, in emit

Traceback (most recent call last):

Logged from file actionsmap.py, line 489

IOError: [Errno 28] No space left on device

self.stream.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 845, in flush

self.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 885, in emit

Traceback (most recent call last):

Logged from file actionsmap.py, line 478

IOError: [Errno 28] No space left on device

self.stream.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 845, in flush

self.flush()

File "/usr/lib/python2.7/logging/__init__.py", line 885, in emit

Traceback (most recent call last):

Logged from file __init__.py, line 399

IOError: [Errno 28] No space left on device

self.stream.flush()

[…]

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/core-util-is: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/core-util-is/package.json: Cannot open: No such file or directory

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/core-util-is: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/core-util-is: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args/test.js: Cannot open: No such file or directory

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args/index.js: Cannot open: No such file or directory

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args/.travis.yml: Cannot open: No such file or directory

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args/package.json: Cannot open: No such file or directory

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args/readme.md: Cannot open: No such file or directory

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args/license.md: Cannot open: No such file or directory

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/process-nextick-args: Cannot mkdir: No space left on device

tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/string_decoder/.npmignore: Cannot write: No space left on device

1.1% ## 3.9% ##### 8.0% ############ 17.6% ################### 27.1% ########################## 36.7% ######################################## 55.6% ############################################### 65.3% ##################################################### 74.9% ############################################################ 84.5%tar: lib/node_modules/npm/node_modules/sha/node_modules/readable-stream/node_modules/string_decoder/index.js: Wrote only 4096 of 7680 bytes

2018-06-28 13:51:08 URL:https://codeload.github.com/tj/n/tar.gz/v2.1.7 [9592/9592] -> "n.tar.gz" [1]

Installation of N - Node.js version management

Hellow,

can you explain how you installed YunoHost ?

Also to confirm your issue with the disk space, you may look at the output of df -h which should list the partition for ‘/’ and the associated total and free space :wink:

I’ve installed Yunohost through the Raspberry Pi image and using Etcher 1.4.4 from a Debian 8 XFCE.

filesystem Size Used Avail Use% Mounted on
/dev/root 2.2G 1.9G 162M 93% /
devtmpfs 460M 0 460M 0% /dev
tmpfs 464M 92K 464 1% /dev/shm
tmpfs 464M 18M 446M 4% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblik0p1 43M 22M 21M 51% /boot
tmpfs 93M 0 93M 0% /run/user/0

Annex question : why can’t we use bittorent to download Yunohost images ?

If needed the diagnostic :

{
    "host": "Debian 9.4",
    "kernel": "4.14.49-v7+",
    "packages": {
        "yunohost": {
            "repo": "stable",
            "version": "3.0.0.1"
        },
        "yunohost-admin": {
            "repo": "stable",
            "version": "3.0.0"
        },
        "moulinette": {
            "repo": "stable",
            "version": "3.0.0"
        },
        "ssowat": {
            "repo": "stable",
            "version": "3.0.0"
        }
    },
    "backports": [],
    "system": {
        "disks": {
            "root": "Mounted on /, 2.2GiB (289.6MiB free)",
            "mmcblk0p1": "Mounted on /boot, 42.5MiB (20.9MiB free)"
        },
        "memory": {
            "ram": "927.2MiB (647.2MiB free)",
            "swap": "100.0MiB (100.0MiB free)"
        }
    },
    "nginx": [
        "nginx: the configuration file /etc/nginx/nginx.conf syntax is ok",
        "nginx: configuration file /etc/nginx/nginx.conf test is successful"
    ],
    "services": {
        "glances": "running (enabled)",
        "nslcd": "running (enabled)",
        "metronome": "running (enabled)",
        "postfix": "exited (enabled)",
        "rspamd": "running (enabled)",
        "yunohost-firewall": "exited (enabled)",
        "nginx": "running (enabled)",
        "php7.0-fpm": "running (enabled)",
        "dnsmasq": "running (enabled)",
        "fail2ban": "running (enabled)",
        "yunohost-api": "running (enabled)",
        "mysql": "running (enabled)",
        "avahi-daemon": "running (enabled)",
        "dovecot": "running (enabled)",
        "redis-server": "running (enabled)",
        "slapd": "running (enabled)",
        "ssh": "running (enabled)"
    },
    "applications": {},
    "security": {
        "CVE-2017-5754": {
            "name": "meltdown",
            "vulnerable": false
        }
    }
}

Hmokay, that’s a bit weird because the image should have a script that expand the partition at first boot … maybe that did not work for some reason

According to this post you should be able to follow these instructions to do it “manually” :

There is a utility called raspi-config. This runs on first boot if you’re connected directly to the RPi. If you’re over SSH you can run it manually using $ sudo raspi-config. (I think you can re-run the tool manually at any time).

The second option on the blue dialog that follows is titled expand_rootfs, with the description “Expand root partition to fill SD card”.

Selecting this will cause your root partition to be resized to fill the card the next time you boot your RPi.

About your other question :

Essentially because nobody is maintaining this :wink: I don’t know how we could create a new torrent automatically for each build (probably doable technically but we are short on humanpower), and even then since we are likely to regularly rebuild with newer version I don’t know if that make so much sense …

I’ve gone to “Advanced Options” and then “Expand Filesystem” and then reboot but the problem still remain. :face_with_raised_eyebrow:

Finaly I installed a YunoHost_v251_rpi.img on the same sd card and it works ! It recognized the full disk. I’ve updated until 2.7.14 and I’ll see for the 3.0

But it still weird : why a direct insall of yunhost 3 doesn’t work well ?

I dunno, it should … :s Maybe that’s some weird thing that happened with the SD file system and ended unable to expand item ? idk … During my tests the automatic root partition extension worked :confused:

Hello,

To use all SD card space, you have to resize the root partition like this :

root@home00:~# df -h
Sys. fich. Taille Util. Dispo Uti% Monté sur
rootfs 2,9G 1,1G 1,7G 39% /
/dev/root 2,9G 1,1G 1,7G 39% /
devtmpfs 460M 0 460M 0% /dev
tmpfs 93M 236K 93M 1% /run
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 186M 0 186M 0% /run/shm
/dev/mmcblk0p1 56M 20M 37M 35% /boot
root@home00:~#
root@home00:~#
root@home00:~# resize2fs -p /dev/sda1
resize2fs 1.42.5 (29-Jul-2012)
Le système de fichiers de /dev/sda1 est monté sur / ; le changement de taille doit être effectué en ligne
old_desc_blocks = 1, new_desc_blocks = 4
Le système de fichiers /dev/sda1 a maintenant une taille de 13107200 blocs.

root@home00:~# df -h
Sys. fich. Taille Util. Dispo Uti% Monté sur
rootfs 50G 1,1G 47G 3% /

In this case, i move root partition from SD card to external USB hard disk. But, only with SD card, it’s the same process. It was raspbian iso and a resize is the best practice to use the full device.

Sorry for my English language…

I’ve had the exact same problem! Where did you get the old image?

Hier @Someone ,

It’s in french but you could try to install YunoHost on a Stretch Raspbian Lite based :
https://avignu.wiki.tuxfamily.org/doku.php?id=documentation:yunohost-stretch-v3.x.x.x-rpi

Old stuff in english :
https://avignu.wiki.tuxfamily.org/doku.php?id=documentation:yunohost-jessie-v2.7.x-rpi_en

ppr

I had the same issue. I solved it by installing rasbian lite (Debian stretch) from the website of raspberry pi and then installed yunohost in command line

Hi,

I had the same issue flashing the yunohost 3.0 image with Etcher, and raspi-config couldn’t expand the root partition.

It was solved using this command
resize2fs -p /dev/mmcblk0p2