March 30, 20197 yr Author The check is still running, but the problem is already there. root@KartoffelHQ:~# df -h Filesystem Size Used Avail Use% Mounted on rootfs 5.8G 5.8G 0 100% / tmpfs 32M 236K 32M 1% /run devtmpfs 5.8G 0 5.8G 0% /dev tmpfs 5.9G 0 5.9G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 396K 128M 1% /var/log /dev/sda1 30G 404M 29G 2% /boot /dev/loop0 8.2M 8.2M 0 100% /lib/modules /dev/loop1 4.9M 4.9M 0 100% /lib/firmware /dev/md1 3.7T 3.1T 563G 85% /mnt/disk1 /dev/md2 3.7T 3.1T 604G 84% /mnt/disk2 /dev/md3 4.6T 4.0T 620G 87% /mnt/disk3 /dev/md4 4.6T 4.1T 552G 89% /mnt/disk4 /dev/md5 4.6T 2.3T 2.3T 50% /mnt/disk5 /dev/md6 3.7T 529G 3.2T 15% /mnt/disk6 /dev/md7 5.5T 11G 5.5T 1% /mnt/disk7 /dev/sdf1 239G 199G 40G 84% /mnt/cache shfs 31T 17T 14T 57% /mnt/user0 shfs 31T 18T 14T 57% /mnt/user /dev/loop2 30G 19G 11G 64% /var/lib/docker /dev/loop3 1.0G 17M 905M 2% /etc/libvirt
March 30, 20197 yr Community Expert Unlikely that faulty memory would be the cause, but can't hurt to check. Reboot and select memtest from the boot menu and let it run for at least one full pass. Then reboot in SAFE mode, disable Docker and VM Services, and try parity check again.
March 30, 20197 yr 23 hours ago, smeeee.again said: The Docker Containers are configured correctly. *IF* you happen to have say duplicati backing up to an unassigned device and that device isn't present, then everything will wind up going to RAM instead and you will see what you're seeing.
March 30, 20197 yr Author 5 hours ago, Squid said: *IF* you happen to have say duplicati backing up to an unassigned device and that device isn't present, then everything will wind up going to RAM instead and you will see what you're seeing. Duplicati is currently without entries. I suspected it after some research in the forum, but I had already removed the links to paths that no longer exist. 7 hours ago, trurl said: Unlikely that faulty memory would be the cause, but can't hurt to check. Reboot and select memtest from the boot menu and let it run for at least one full pass. Then reboot in SAFE mode, disable Docker and VM Services, and try parity check again. I will do that. Hopefully, it won't take too long, I already miss my server. Thanks also in between for the extensive help.
March 31, 20197 yr Author I've probably found the culprit. It was a userscript from the User Scripts plugin, which I forgot to disable. Because I wasn't at home I set the Fix common problems plugin to check every hour. When I noticed the message at home I checked the /tmp folder via the console and figured the script out. The script was supposed to synchronize the images of one folder with another every day, but couldn't do that anymore because the target was switched off and so it came as you already suspected and it just filled the /tmp to the limit. I'm now doing another check to see if it was the only problem. Hopefully this will be so. Thank you so much for your help!
July 2, 20215 yr Sorry to bring up an old one but I'm having this issue. As soon as I start parity check, the web ui becomes faulty and the array becomes undefined. I was able to get it to stop (it only ran for about a minute and this started) and I will attach the diagnostics file. Any help would be appreciated. Again this only happens when parity check starts. As soon as I stop it everything is normal again. Edit for grammar plexserver-diagnostics-20210702-0918.zip Edited July 2, 20215 yr by Jurak
Archived
This topic is now archived and is closed to further replies.