GUI not available due to rootfs run out of space

[Fireball3]

Hi folks,

I ran into this issue after installing the MiniDLNA docker.

Probably didn't pay attention (took the presettings) with the settings of the docker.

Now the server is running out of space on the rootfs when booting.

The GUI is not available, SMB not running, array is not mounted.

Luckily I can ssh in and see what's going on.

When trying to grab a diagnostics I get this:

 

root@Tower:~# diagnostics
Starting diagnostics collection...
Warning: file_put_contents(): Only 0 of 5 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 80
Warning: file_put_contents(): Only 0 of 975 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85
Warning: file_put_contents(): Only 0 of 78 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 101
Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120
Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122
Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120
Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device
echo: write error: No space left on device

Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160
Warning: file_put_contents(): Only 0 of 65 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 166
Warning: file_put_contents(): Only 0 of 535 bytes written, possibly out of free disk space in 
/usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 210
done.
ZIP file '/boot/logs/tower-diagnostics-20210117-0922.zip' created.

The diagnostic file contains only empty files.

 

Checking for space:

root@Tower:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          684M  684M     0 100% /
tmpfs            32M  368K   32M   2% /run
devtmpfs        684M     0  684M   0% /dev
tmpfs           747M     0  747M   0% /dev/shm
cgroup_root     8.0M     0  8.0M   0% /sys/fs/cgroup
tmpfs           128M  140K  128M   1% /var/log
/dev/sda       1003M  246M  758M  25% /boot
/dev/loop0      9.2M  9.2M     0 100% /lib/modules
/dev/loop1      7.3M  7.3M     0 100% /lib/firmware

 

Is my assumption correct about the docker filling up the rootfs?

That was the last thing I set up before this problem arose.

How can I free up the space used by the docker?

 

I checked the stick on a Windows machine for filesystem issues, but all is fine.

I have teamviewer access only to the server. Safe boot and such things are not an option.

I can ask the remote user to plug the stick into a Windows machine and change/modify content on the stick or

do it via console.

I would prefer not to set up a new config but remove the docker to free up space.

 

[Fireball3]

I pulled the syslog.

Maybe this will encourage you to give me some advice. 😉

syslog_18.01.2021.txt

 

I wonder why the rootfs is 684M only.

Shouldn't that be of the size of installed RAM??? 🤔

Edited January 18, 2021 by Fireball3

[Fireball3]

OK, weekend is approaching and I have to get the media server up and running again... 😓

My plan is to setup a clean unRAID on the USB and copy the settings without the docker from the old install.

Maybe I should skip the plugins also since they are giving errors in the syslog?

 

So, what are the essential parts that I need to copy to the fresh install?

super.dat

license file

...

?