karateo Posted December 28, 2015 Share Posted December 28, 2015 A weird problem. New install with a few dockers and a few plugins (temperature, system stats which I uninstalled), community applications, dynamix active streams). See pictures of problem. Webgui becomes unstable and eventually nothing works. Tried diagnostics command from putty but got the following. Powerdown command didn't do anything. Also, it's the second time it happens. Ony thing I found is that the first time it got unstable, I uninstalled system stats and i got a minutes of stable webgui. But after a while the problem appeared again. https://www.dropbox.com/sh/fh87sin35j1t6nc/AADtqd5LzZVK_gDmNPEtS4jha?dl=0 # diagnostics Starting diagnostics collection... Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 12 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: syntax error, unexpected $end, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or '"' in /var/local/emhttp/disks.ini on line 628 in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 5429 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 4125 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 3269 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 14 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 3801 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 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 50 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 52 done. ZIP file '/boot/logs/tower-diagnostics-20151228-1032.zip' created. After I stopped array this is my disk space. root@TOWER:/boot/logs# df -h df: ‘/mnt/disk1’: No such file or directory df: ‘/mnt/disk2’: No such file or directory df: ‘/mnt/user’: No such file or directory Filesystem Size Used Avail Use% Mounted on tmpfs 128M 2.6M 126M 3% /var/log /dev/sda1 7.5G 107M 7.4G 2% /boot /dev/loop0 1.8G 1.8G 0 100% /var/lib/docker After a restart I found the diagnostics zip and I attached it. tower-diagnostics-20151228-1032.zip Link to comment
trurl Posted December 28, 2015 Share Posted December 28, 2015 Every file in your diagnostics zip is 0 bytes. Your df command is showing your docker img is full and so probably corrupt. You will have to delete and recreate it and then figure out what is filling it up. Link to comment
karateo Posted December 28, 2015 Author Share Posted December 28, 2015 Did a df again after a restart and while everything is working fine. root@TOWER:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 128M 3.1M 125M 3% /var/log /dev/sda1 7.5G 106M 7.4G 2% /boot /dev/md1 466G 438G 28G 94% /mnt/disk1 /dev/md2 466G 425G 41G 92% /mnt/disk2 shfs 932G 863G 69G 93% /mnt/user /dev/loop0 10G 2.2G 6.3G 26% /var/lib/docker Now /dev/loop0 is 10Gb and before it was 1.8Gb. My docker image is default size (10Gb) so what was the 1.8 ? Link to comment
karateo Posted December 29, 2015 Author Share Posted December 29, 2015 Today morning the same thing. Also df -h looks fine but cannot create diagnostics zip root@TOWER:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 128M 3.2M 125M 3% /var/log /dev/sda1 7.5G 107M 7.4G 2% /boot /dev/md1 466G 438G 28G 94% /mnt/disk1 /dev/md2 466G 425G 41G 92% /mnt/disk2 shfs 932G 863G 69G 93% /mnt/user /dev/loop0 10G 2.2G 6.3G 26% /var/lib/docker I stopped the only running docker (deluge brand new setup with no torrents to download) and got some functionality back. Still cannot created diagnostics zip. Also, after a few minutes webgui lost functionality again. Log file Dec 29 09:19:02 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:20:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:21:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:22:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:23:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:24:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:25:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:26:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:27:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:28:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:29:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:30:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:31:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:32:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:33:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:34:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:35:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:36:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:37:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:38:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:39:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:40:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:41:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:42:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:43:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:44:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:44:10 TOWER sshd[24242]: Accepted password for root from 192.168.1.20 port 1829 ssh2 Dec 29 09:44:58 TOWER shfs(null): fuse_main exit: 1 Dec 29 09:45:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:46:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:46:03 TOWER php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'stop' 'deluge' Dec 29 09:46:04 TOWER kernel: veth332bb47: renamed from eth0 Dec 29 09:46:04 TOWER kernel: docker0: port 1(veth9c9279f) entered disabled state Dec 29 09:46:04 TOWER kernel: docker0: port 1(veth9c9279f) entered disabled state Dec 29 09:46:04 TOWER avahi-daemon[8688]: Withdrawing workstation service for veth332bb47. Dec 29 09:46:04 TOWER avahi-daemon[8688]: Withdrawing workstation service for veth9c9279f. Dec 29 09:46:04 TOWER kernel: device veth9c9279f left promiscuous mode Dec 29 09:46:04 TOWER kernel: docker0: port 1(veth9c9279f) entered disabled state Dec 29 09:46:06 TOWER ntpd[1456]: Deleting interface #3 docker0, 172.17.42.1#123, interface stats: received=0, sent=0, dropped=0, active_time=82775 secs Dec 29 09:47:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:48:01 TOWER crond[1479]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Dec 29 09:48:02 TOWER emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Uninstalled plugin system stats and again functionality returned and I got to create a diagnostics zip. Anyone can help? tower-diagnostics-20151229-0949.zip Link to comment
trurl Posted December 29, 2015 Share Posted December 29, 2015 The syslog in your diagnostics are incomplete and don't even cover the complete boot up, nor does it contain any of the text from your most recent post. Also, the screenshots in you OP have blanks in the upper right where the webUI normally displays the version. Maybe something wrong with your flash. Put it in you PC and let it checkdisk. Then boot into memtest and let it run for a day. If that is OK, boot in safe mode and stop the docker service and see if it will run for a while that way. Link to comment
karateo Posted December 29, 2015 Author Share Posted December 29, 2015 Server Description Version UptimeTOWER • 192.168.1.2 Media server 6.1.6 5 hours, 37 minutes Flash drive is brand new and did a test before formating and copying files. I will make a memtest if it happens again and then boot in safe mode. I don't know if ECC memory means that if it had a problem I would be informed somehow. Can't I simply disable docker from Settings? Also, the only way to disable plugins is by uninstalling them? Is there any way to get complete syslog next time? Maybe it run out of memory and started deleting oldest data? Where is the log stored at and how can I check the memory there? Link to comment
karateo Posted December 30, 2015 Author Share Posted December 30, 2015 Disabled notifications and after 13 hours I didn't notice anything in webgui. But, preclear shows an error which I think is related to the above problem. Other than the error showing it is running normal. The bytes read at post-read are increasing normally. root@TOWER:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 128M 2.6M 126M 2% /var/log /dev/sda1 7.5G 107M 7.4G 2% /boot /dev/md1 466G 438G 28G 94% /mnt/disk1 /dev/md2 466G 425G 41G 92% /mnt/disk2 shfs 932G 863G 69G 93% /mnt/user /dev/loop0 10G 4.7G 4.1G 54% /var/lib/docker And again I can not run diagnostics root@TOWER:~# diagnostics Starting diagnostics collection... Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 179 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 3511 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 4223 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 3066 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 3802 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 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 50 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 52 Warning: file_put_contents(): Only 0 of 36 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 66 Warning: file_put_contents(): Only 0 of 36 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 66 Warning: file_put_contents(): Only 0 of 36 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 66 Warning: file_put_contents(): Only 0 of 36 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 66 done. ZIP file '/boot/logs/tower-diagnostics-20151230-0939.zip' created. Lastly, I bought Basic licence for now! Feedback unRAID Server Basic Which tool should I run to check usb device? It is the Sandisk Cruzer Edge This is the cause of the problem df -h /usr Filesystem Size Used Avail Use% Mounted on - 1.8G 1.8G 0 100% / Where is /usr located? How can I resize it? Found this http://lime-technology.com/forum/index.php?topic=27249.msg239383#msg239383 So did the below but it doesn't add up to 1.8Gb. root@TOWER:~# du -hs /usr/* 0 /usr/adm 63M /usr/bin 22M /usr/doc 4.4M /usr/include 184K /usr/info 0 /usr/lib 173M /usr/lib64 20M /usr/libexec 7.7M /usr/local 9.8M /usr/man 21M /usr/sbin 98M /usr/share 0 /usr/spool 2.7M /usr/src 0 /usr/tmp I am a linux newbie so I need your guidance! Link to comment
itimpi Posted December 30, 2015 Share Posted December 30, 2015 With unRAID, everything that is not under /boot (the flash drive) or /mnt (the hard disks) is in RAM. Link to comment
karateo Posted December 30, 2015 Author Share Posted December 30, 2015 With unRAID, everything that is not under /boot (the flash drive) or /mnt (the hard disks) is in RAM. root@TOWER:~# free -m total used free shared buffers cached Mem: 3774 2536 1237 0 144 2104 -/+ buffers/cache: 287 3487 Swap: 0 0 0 No problem with RAM! 1) Why is / only 1.8Gb and how can I resize if I need to? or the solution 2) How to determine what is taking so much space I run du -a / | sort -n -r | head -n 20 but I don't have any space in /tmp to calculate the output! Link to comment
bonienl Posted December 30, 2015 Share Posted December 30, 2015 With unRAID, everything that is not under /boot (the flash drive) or /mnt (the hard disks) is in RAM. root@TOWER:~# free -m total used free shared buffers cached Mem: 3774 2536 1237 0 144 2104 -/+ buffers/cache: 287 3487 Swap: 0 0 0 No problem with RAM! 1) Why is / only 1.8Gb and how can I resize if I need to? or the solution 2) How to determine what is taking so much space I run du -a / | sort -n -r | head -n 20 but I don't have any space in /tmp to calculate the output! Something is not set up properly on your system. The size of your root folder should be your RAM size. It looks like your root folder is mounted to something else (flash?) Is there anything in the file: /etc/fstab ? To eliminate issues, disable Docker and VMs (see settings page Docker/VMs) and next start your system in safe mode. Link to comment
karateo Posted December 30, 2015 Author Share Posted December 30, 2015 Something is not set up properly on your system. The size of your root folder should be your RAM size. It looks like your root folder is mounted to something else (flash?) Is there anything in the file: /etc/fstab ? To eliminate issues, disable Docker and VMs (see settings page Docker/VMs) and next start your system in safe mode. Only this /etc/fstab /dev/disk/by-label/UNRAID /boot vfat auto,rw,exec,noatime,nodiratime,umask=0,shortname=mixed 0 1 also /etc/mtab cat /etc/mtab tmpfs /var/log tmpfs rw,size=128m,mode=0755 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 /dev/sda1 /boot vfat rw,noatime,nodiratime,umask=0,shortname=mixed 0 0 /dev/md1 /mnt/disk1 btrfs rw,noatime,nodiratime 0 0 /dev/md2 /mnt/disk2 btrfs rw,noatime,nodiratime 0 0 shfs /mnt/user fuse.shfs rw,nosuid,nodev,noatime,allow_other 0 0 /dev/loop0 /var/lib/docker btrfs rw 0 0 /dev/md3 /mnt/disk3 btrfs rw,noatime,nodiratime 0 0 How is / mounted to all the ram? Also, after restart / was ~20% full and after 2hours its 41% again size is only 1.8G Is there any command to check what is increasing in size by time? Another diagnostics zip attached after I disabled docker (vm was already disabled) Also free space in / is still decreasing! 42% completed the command I tried before for top usage root@TOWER:~# sudo du -a --exclude=/proc/* / | sort -n -r | head -n 20 du: cannot access ‘/sys/kernel/slab/unraid/md’: No such file or directory 1805508308 / 1804897076 /mnt 902448512 /mnt/user 490021892 /mnt/user/Photos 457894256 /mnt/disk1 444554292 /mnt/disk2 401566172 /mnt/user/Synology/-=Videos=- 401566172 /mnt/user/Synology 277085912 /mnt/disk2/Photos 274198252 /mnt/user/Synology/-=Videos=-/Movies 234362764 /mnt/disk1/Synology/-=Videos=- 234362764 /mnt/disk1/Synology 228904468 /mnt/disk1/Synology/-=Videos=-/Movies 212935980 /mnt/disk1/Photos 167203408 /mnt/disk2/Synology/-=Videos=- 167203408 /mnt/disk2/Synology 165236012 /mnt/user/Photos/2003 - 2014 94522940 /mnt/user/Synology/-=Videos=-/temp 94522940 /mnt/disk2/Synology/-=Videos=-/temp 87323564 /mnt/disk1/Photos/2003 - 2014 w Anything wrong here? tower-diagnostics-20151230-1454.zip Link to comment
itimpi Posted December 30, 2015 Share Posted December 30, 2015 I must admit I did not think that / had all RAM. I thought it had enough to hold the unpacked bzimage and bzroot files, and that parts that grow in size (e.g. /var/log) were mounted separately? Link to comment
karateo Posted December 30, 2015 Author Share Posted December 30, 2015 screenshot from htop also used space is still increasing there should be a way to see what is writing and where root@TOWER:~# df -h / Filesystem Size Used Avail Use% Mounted on - 1.8G 819M 1011M 45% / Link to comment
trurl Posted December 30, 2015 Share Posted December 30, 2015 According to syslog in latest diagnostic you didn't boot in SAFE mode. Also, do you have anything in /boot/extra? Link to comment
karateo Posted December 30, 2015 Author Share Posted December 30, 2015 Now I booted to SAFE MODE. Before, I tried to stop array but it kept trying to unmount shares. I had to run powerdown -r Attached latest diagnostics in SAFE MODE. I have no folder /boot/extra root@TOWER:/boot# ls System\ Volume\ Information/ install.txt* make_bootable.bat* preclear_reports/ bzimage* ldlinux.c32* make_bootable_mac* syslinux/ bzroot* ldlinux.sys* memtest* changes.txt* license.txt* packages/ config/ logs/ preclear_disk.sh* Also, for the last 5 minutes df -h is stable at 235M / 13% which indicates that the problem does not exist in SAFE MODE. I really appreciate your help! tower-diagnostics-20151230-1634.zip Link to comment
bonienl Posted December 30, 2015 Share Posted December 30, 2015 I suggest one of the plugins to have foul play. Which plugins have you installed ? Make sure you use only verified ones. This information isn't visible in the diagnostics file you have uploaded, since it was taken AFTER you started in safe mode. Link to comment
karateo Posted December 30, 2015 Author Share Posted December 30, 2015 I think all of those are verified This is the list of installed plugins, right? root@TOWER:/boot/config/plugins# ls NerdPack/ checksum.plg* dynamix.kvm.manager/ powerdown/ NerdPack.plg* dockerMan/ dynamix.system.temp/ powerdown-x86_64.plg* checksum/ dynamix/ dynamix.system.temp.plg* I will uninstall all and start to install one per second day. Link to comment
bonienl Posted December 30, 2015 Share Posted December 30, 2015 I think all of those are verified This is the list of installed plugins, right? root@TOWER:/boot/config/plugins# ls NerdPack/ checksum.plg* dynamix.kvm.manager/ powerdown/ NerdPack.plg* dockerMan/ dynamix.system.temp/ powerdown-x86_64.plg* checksum/ dynamix/ dynamix.system.temp.plg* I will uninstall all and start to install one per second day. Suspicion is the "checksum" plugin. You might want to post your settings of this plugin in the related topic and ask for verification and advice. Link to comment
trurl Posted December 30, 2015 Share Posted December 30, 2015 I think all of those are verified This is the list of installed plugins, right? root@TOWER:/boot/config/plugins# ls NerdPack/ checksum.plg* dynamix.kvm.manager/ powerdown/ NerdPack.plg* dockerMan/ dynamix.system.temp/ powerdown-x86_64.plg* checksum/ dynamix/ dynamix.system.temp.plg* I will uninstall all and start to install one per second day. Note that only the .plg files (and their associated folders) are actually installable/uninstallable plugins. The others are builtin. If you uninstall them instead of deleting you should be OK. Also, I use all of those, including checksum, without issue. Link to comment
karateo Posted December 30, 2015 Author Share Posted December 30, 2015 All the plugins are "brand new" with no settings altered by me. I have only used the system temp to show cpu/motherboard temp at the bottom of webgui. Before "accusing" one plugin I will try to find exactly which one caused the problem. Thanks for your guidance on troubleshooting! I am happy this happened now, so I got the opportunity to troubleshoot before transferring all data to unraid. Next step is to boot in normal mode and uninstalling all plugins. I hope that it's that simple! Link to comment
bonienl Posted December 30, 2015 Share Posted December 30, 2015 All the Dynamix plugins come from me, I am certain these can not cause your problem. I don't use the checksum plugin myself, but I do know that it can take resources if configured wrongly, hence my suggestion to ask. This is not an accusation of any kind. Squid is a very well respected developer! Link to comment
karateo Posted December 31, 2015 Author Share Posted December 31, 2015 Marked as solved. Thanks everyone. I have booted to normal mode and after 13hours I still have 13% space used and for the first time really low cpu usage! I just installed system temp and I will wait for another 12 hours. One question. Is it better to run a VM (for example debian which I have some experience and I prefer) and run in there the deluge/sonarr/couchpotato/plex or using dockers? I read various problems with dockers and I don't have the time to waste playing around. Also, running VM debian, is it like proxmox containers? Do the system share core files so it uses much less memory? Link to comment
itimpi Posted December 31, 2015 Share Posted December 31, 2015 One question. Is it better to run a VM (for example debian which I have some experience and I prefer) and run in there the deluge/sonarr/couchpotato/plex or using dockers? I read various problems with dockers and I don't have the time to waste playing around. Dockers are much lighter weight and consume less resources than a VM based solution. Most of the time that problems are reported with dockers it tends to be because they have been misconfigured in some way. Another point that is not always obvious is that Dockers run 'headless' whereas with a VM you require a keyboard/monitor (which is not the one dedicated to unRAID) to manage them. Having said that since you are familiar with it as long as your hardware is up to it there is no reason not to run a VM. Also, running VM debian, is it like proxmox containers? Do the system share core files so it uses much less memory? No. A VM installs a complete copy of the OS and is completely isolated from the host. This means it tends to use more resources in terms of RAM and disk space than a docker. Link to comment
karateo Posted December 31, 2015 Author Share Posted December 31, 2015 The problem with misconfigured dockers comes from the lack of proper documentation I think. It would be much easier a wiki than everyone asking at the forum. For example, I am not sure which is better. /mnt/user/appdata/deluge or /mnt/disk1/appdata/deluge As I am installing one by one the plugins again. Can I delete some folder to reset any changes I had done before uninstalling or everything is reset already? Link to comment
trurl Posted December 31, 2015 Share Posted December 31, 2015 The problem with misconfigured dockers comes from the lack of proper documentation I think. It would be much easier a wiki than everyone asking at the forum. For example, I am not sure which is better. /mnt/user/appdata/deluge or /mnt/disk1/appdata/deluge As I am installing one by one the plugins again. Can I delete some folder to reset any changes I had done before uninstalling or everything is reset already? Actually, better is to use a cache drive for appdata. Any writes to the parity array will keep the parity disk going, and writes to cache don't. I have seen reports that /mnt/user/appdata can cause some issues with certain dockers that create hardlinks for their appdata. So /mnt/cache/appdata (or /mnt/disk1/appdata if you insist) could be better. I personally use /mnt/cache/appdata since my appdata share is a cache-only share. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.