Symptoms
When you try to login to the GUI of OMV you are not being logged in, but the login page shows up again
Check, if a full root filesystem is the problem
ssh into your server (check the new user guide on how to ssh into your server) and run following command
df df will show you the usage of each filesystem
the output of df will look like this:
15:01:03 root@server:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 8033820 0 8033820 0% /dev
tmpfs 1610128 27588 1582540 2% /run
dev/sda1 39108608 39108608 0 100% /
tmpfs 8050632 0 8050632 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 8050632 0 8050632 0% /sys/fs/cgroup
tmpfs 8050632 0 8050632 0% /tmp
folder2ram 8050632 75248 7975384 1% /var/log
folder2ram 8050632 4 8050628 1% /var/tmp
folder2ram 8050632 624 8050008 1% /var/lib/openmediavault/rrd
folder2ram 8050632 996 8049636 1% /var/spool
/dev/sda2 76360744 9428044 63010780 14% /srv/dev-disk-by-label-dataos
folder2ram 8050632 11648 8038984 1% /var/lib/rrdcached
/dev/md127 2884009464 1680001056 1203992024 59% /srv/dev-disk-by-label-pool
folder2ram 8050632 4 8050628 1% /var/lib/monit
folder2ram 8050632 1604 8049028 1% /var/cache/samba
/dev/sdb1 2930265540 1627081640 1300996536 56% /srv/dev-disk-by-label-internalbackupThe filesystem dev/sda1 which is mounted on "/" is the OS filesystem. The use of that filesystem is 100% --> the OS filesystem is full.
Find which folder is filling the filesystem
in the CLI run
cd / to change to the root of the OS file system
du -xhd1 du will show you the size of each folder on the root (x: do not descend into other filesystem; h: display output in human readable format; d1: show only first level of directories)
the output will look like this:
15:08:05 root@hawk:/# du -xhd1
9.8M ./etc
0 ./media
2.2G ./var
2.3G ./usr
1.4G ./boot
20K ./home
5.7M ./root
0 ./mnt
20.2G ./srv
0 ./opt
0 ./export
4.0M ./tmp_urbackup
16K ./.config
0 ./sharedfolders
25.8G .(To get only the 10 largest folders/files in order, use du -ahxd1 | sort -hr | head -n 10)
Identify the largest folder and change into that folder with
cd foldername replace foldername by the name of the largest folder
Repeat these steps until you identified the "deepest" folder which is filling your root filesystem.
Change into that folder and check with ls -al what is inside. ls lists the directory content (a: shows you also hidden entries, l: shows in a long list format)
Further steps depend on the reason:
Common Reasons for full OS filesystem
- Docker (e.g. large media library of plex)
- move docker from the OS filesystem to another one - RE: Installation and Setup Videos - Beginning, Intermediate and Advanced
- remove old images and volumes that are not needed anymore - Cleaning up Dockers
- a rsync job was running, when the target filesystem was not mounted --> the files were copied to a folder, which was created instead of mount point (usually in /srv/) (see also post #4)
- a symptom of this is, that the results for du and df do not match
(i.e disk capacity minus reported usage with du is not similar to the result of df) - Unmount all drives in /srv from CLI and force the unmount if needed; as an alternative shutdown, unplug all data drives, boot
- look in each mountpoint directory in /srv and see if anything is in there
- delete the wrongly created folder (
if you are in doubt physically disconnect the related hard drive to not delete the content on that drive)
- a symptom of this is, that the results for du and df do not match
- log files are spammed --> check the content of the log file and fix the root cause why the log file is spammed; after you fixed the problem you can reduce the size of the log file to 0 with truncate -s 0 logfile.log replace logfile.log
If you have any improvements that should be implemented, please let me know.
