board update error

giuliomoro

Remork /dev/root 3.4G 3.4G 0 100% /

good catch, that's a full disk. The update procedure via IDE is quite space consuming in that it makes a full copy of the Bela folder . See if you have a folder in /root/_BelaUpdateBackup and how much space it takes:

du -sh /root/_BelaUpdateBackup

then you can then remove it with rm -rf /root/_BelaUpdateBackup. The less space-consuming way of updating is to download and uncompress the zip archive on the host and run scripts/update_board from within it.

Remork but i don't understand what is taking up that space.

it may be projects, project files, build files and any big wave audio files you may have in there.

Remork In file folder_list.c: 'm_pd.h' file not found column: 10, line: 26

where is that file from??

Remork

giuliomoro See if you have a folder in /root/_BelaUpdateBackup and how much space it takes:

will check.

giuliomoro it may be projects, project files, build files and any big wave audio files you may have in there.

well, that's why i checked the size of /root/Bela/projects/*...
that does not at all account for 3.4G of space..
and i shouldn't have any audio files on the EMMC, as i supposedly read everything from the sd card..

if i find the cause of the disk being full (and can remove what is taking up the space), i might even be able to run the Oled example without upgrading, as i think that is what went wrong trying to install that project as well.

thing is, upgrading is not the problem, it's the installed externals, going through the process of automounting the sd etc.. all that is working now, so i'm a bit reluctant to mess with it.

giuliomoro where is that file from??

that would be in the pd-externals project, i believe. will double check.

folder_list is an external that's part of the HCS library. i installed that library (had to remove some elements of it that caused the install to fail), some things show up as .pd files, others don't. this one doesn't. it's the only thing in the lib i'm actually using..

Remork

so i double checked..
i have my pd-externalsproject.
there's the hcsand zexy libraries under directories.
in directories/hcsi have folder_list-help.pdand folder_list.pd_linux.

but there's also folder_list.c in sources, which is the one giving me the error.
first line of code there is #include <m_pd.h>.

i did delete some of the other externals in the hcslibrary in a blind effort to free up some space, since i'm not using them. maybe i deleted some stuff that i shouldn't have.
(which makes my argument for wanting to hold off the upgrade because of reinstalling externals a bit weak.)

as for the backup taking up space:
cannot access '/root/_BelaUpdateBackup': No such file or directory

giuliomoro

Remork 1) the next gen image, as in: the one that came after 0.3.7, or one that's yet to come out?

the one that will come out in the future. This week I will make a v0.3.8h to support Bela Cape RevC, but it won't have this feature yet (I think, will let you know if otherwise).

Remork that would be rm -rf /var/cache/ /var/log/?

yes

Remork 3) to run 020 and actually get work started on the real issue 🙂, i would have to be running an image later than 0.3.8f?

no, just have your Bela core relatively up-to-date (because of a change in the OscReceiver API back in March this year).

Remork i have my pd-externalsproject.
there's the hcsand zexy libraries under directories.
in directories/hcsi have folder_list-help.pdand folder_list.pd_linux.

but there's also folder_list.c in sources, which is the one giving me the error.
first line of code there is #include <m_pd.h>.

Wondering how the sources folder got there: it shouldn't be there. But also, it shouldn't hurt: you are not supposed to build the pd-extended project; at most you will be shown some warnings when you open it but you can ignore them.

Remork

so i ran the following..

root@bela ~/Bela# du -sh /root/Bela/*

hoping that'd give me an idea of what is taking up all the space.
result:

12M	/root/Bela/Documentation
104K	/root/Bela/Doxyfile
72M	/root/Bela/IDE
8.0K	/root/Bela/LICENSE
36K	/root/Bela/Makefile
4.0K	/root/Bela/Makefile.libraries
4.0K	/root/Bela/Makefile.linkbela
4.0K	/root/Bela/README.md
18M	/root/Bela/build
300K	/root/Bela/core
18M	/root/Bela/examples
4.0K	/root/Bela/gitcommithash
276K	/root/Bela/include
844K	/root/Bela/lib
600K	/root/Bela/libraries
2.6M	/root/Bela/projects
136K	/root/Bela/pru
108K	/root/Bela/pru_rtaudio.txt
160K	/root/Bela/pru_rtaudio_irq.txt
11M	/root/Bela/resources
144K	/root/Bela/scripts
4.0K	/root/Bela/tmp
1.5M	/root/Bela/updates
4.0K	/root/Bela/uploads

Remork

root@bela ~/Bela# du -sh /root/*
236M	/root/Bela
1.3M	/root/hcs-0.1
0	/root/without
2.5M	/root/zexy-v2.3.0
root@bela ~/Bela#

giuliomoro

Hmmm so the bulk of your disk usage is outside the home folder.. in normal conditions there should be over 1GB available. Could it be you installed a lot of packages with apt-get at some point?

Remork

giuliomoro Could it be you installed a lot of packages with apt-get at some point?

i have no idea what that means, so i doubt it. 🙂

anything i can do to check the contents outside of the home folder?

giuliomoro

Sure, du -sh /*. And also du -sh /var/log/* /var/cache/*

Remork

giuliomoro du -sh /*

duh. could've come up w that maself 🙂

results:

29M	/boot
0	/dev
3.1M	/etc
572K	/home
117M	/lib
16K	/lost+found
4.0K	/media
5.1M	/mnt
78M	/opt
du: 
cannot access '/proc/988/task/988/fd/3': No such file or directory
du: cannot access '/proc/988/task/988/fdinfo/3': No such file or directory
du: 
cannot access '/proc/988/fd/3': No such file or directory
du: cannot access '/proc/988/fdinfo/3': No such file or directory
0	/proc
240M	/root
9.4M	/run
4.9M	/sbin
4.0K	/srv
0	/sys
28K	/tmp
979M	/usr
2.0G	/var

and

root@bela ~/Bela# du -sh /var/log/* /var/cache/*
16K	/var/log/alternatives.log
32K	/var/log/apt
224K	/var/log/auth.log
88K	/var/log/bootstrap.log
0	/var/log/btmp
755M	/var/log/daemon.log
320K	/var/log/debug
0	/var/log/distccd.log
244K	/var/log/dpkg.log
4.0K	/var/log/faillog
7.1M	/var/log/kern.log
8.0K	/var/log/lastlog
6.2M	/var/log/messages
762M	/var/log/syslog
736K	/var/log/wtmp
309M	/var/cache/apt
2.1M	/var/cache/debconf
20K	/var/cache/ldconfig
4.0K	/var/cache/man

giuliomoro

Remork 755M /var/log/daemon.log

Have you got a program running on boot which prints a lot of stuff?

You can safely remove everything in /var/cache and /var/log. Don't touch /usr.

Remork

i would think that /usr at 979M and /var at 2G seem to stand out most..

if i run du -sh /var/*, it's indeed var/log that stands out at 1.5G.
mostly made up of var/log/daemon.log & var/log/syslog, apparently..

is this expected?

Remork

giuliomoro you mean with [print] objects?
i do track three slider values, and some button presses..
does it store all that data? ❓
because it has been on display as an interactive installation for several days.. so yeah, if it stores days worth of slider values.. that would explain a lot 🙂

Remork

probably 🙂
would make for easier updates, for starters.

some questions:

1) the next gen image, as in: the one that came after 0.3.7, or one that's yet to come out?

2) giuliomoro You can safely remove everything in /var/cache and /var/log.

that would be rm -rf /var/cache/* /var/log/*?

3) to run 020 and actually get work started on the real issue 🙂, i would have to be running an image later than 0.3.8f?

thanks for your time again!

giuliomoro

Yeah but I am actually confused as to why it doesn't actually delete older values when close to filling up the disk. There may be some settings to be tweaked ...
In the next gen image, none of this is actually written to disk ever, which is probably a wiser move.

Remork

giuliomoro no, just have your Bela core relatively up-to-date (because of a change in the OscReceiver API back in March this year).

hmm okay, not sure what that translates to in terms of Bela images, and whether i should upgrade from 0.3.7 to use my Oled easily? advice? after that i'm done bugging you, i promise 🙂
.

Remork

is it possible (really wild stab in the dark) that it either got created when installing the library, or it gets created when using the object?

giuliomoro

You can update your bela code without updating image: https://learn.bela.io/using-bela/bela-techniques/updating-bela/ ; or you can grab v0.3.8g and call it a day if you don't mind reflashing .

Remork

does updating imply reinstalling external libraries?
i'm supposing reflashing does..
would much prefer it if i can avoid it.

giuliomoro

reflashing does; updating the core code via IDE doesn't touch the projects or anything else you may have installed on the image.