March 22, 20233 yr Help please?! The flash and Cache drives disappear and appear immediately. on and off mainserver-diagnostics-20230322-0206.zip
March 22, 20233 yr Author this is with the dissapeared mainserver-diagnostics-20230322-0232.zip log : https://drive.google.com/file/d/1-5n9Ln81yT4V_sye7Voxdxk3aJVbio1n/view?usp=sharing Edited March 22, 20233 yr by MosteanuV
March 22, 20233 yr Author Help? anybody? I am not turning the server back so that I don't break something.
March 22, 20233 yr Community Expert There are some plugin related errors, boot in safe mode and post new diags.
March 22, 20233 yr Author Thanks you for the answer. This is the diag in safe mode: https://drive.google.com/file/d/1-5uA9un-bMtSrBVdZYhuNgRoucWVlqIe/view?usp=sharing
March 22, 20233 yr Community Expert Next time please attach here in the forum, everything looks OK so far, start the array and if any issues post new diags.
March 22, 20233 yr Author It happened again X) mainserver-diagnostics-20230322-2215.zip Edited March 22, 20233 yr by MosteanuV
March 23, 20233 yr Author I left it running and now this is what I get when I login: Warning: array_merge(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 169 Warning: session_start(): Cannot start session when headers already sent in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 8 Warning: session_start(): Cannot start session when headers already sent in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 214 Warning: session_regenerate_id(): Cannot regenerate session id - session is not active in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 217 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/emhttp/plugins/dynamix/include/Translations.php:169) in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 222
March 23, 20233 yr Community Expert Solution Filesystem Size Used Avail Use% Mounted on rootfs 16G 16G 22M 100% / Rootfs is full, this usually happens if you have some mappings to anything other than /mnt/user, since they will be mapped to RAM, check all.
March 23, 20233 yr Author I have 32gb, not 16 is there anyway to see what is filling the ram? "top" shows only a few % usage of memory I restarted and the array started crashing at 61% memory usage. Edited March 23, 20233 yr by MosteanuV
March 23, 20233 yr Community Expert 5 minutes ago, MosteanuV said: I have 32gb, not 16 That is the max size of the rootfs which is normally set to half the available RAM. If it ever gets full then Unraid will start crashing. 7 minutes ago, MosteanuV said: is there anyway to see what is filling the ram? Start by doing ls -l /mnt from a console session to see if there are any unexpected entries at that level. You can then use a command of the form du -sh /mnt/path-to-investigate to look at the size of any unexpected folders
March 23, 20233 yr Author I found out why: I have an rclone and it had a cache option on mount. thank you for the help! Edited March 23, 20233 yr by MosteanuV
March 23, 20233 yr Author I give up. It is still crashing all the time!!! This is another diagnostic mainserver-diagnostics-20230323-2015.zip @itimpi @JorgeB please help!!! Edited March 23, 20233 yr by MosteanuV
March 23, 20233 yr Community Expert Diags are incomplete but looks like the same problem, post output of df -h
March 23, 20233 yr Community Expert Those diagnostics are not much use as nearly all the files in them are 0 length suggesting something has gone seriously wrong.. I would suggest trying to get some diagnostics before the system crashes again to see if something can be spotted.
March 23, 20233 yr Author @JorgeB Filesystem Size Used Avail Use% Mounted on rootfs 16G 15G 765M 96% / tmpfs 32M 1.7M 31M 6% /run /dev/sda1 15G 776M 14G 6% /boot overlay 16G 15G 765M 96% /lib/firmware overlay 16G 15G 765M 96% /lib/modules devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 16G 0 16G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 488K 128M 1% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 0 1.0M 0% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/addons tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1 13T 13T 22G 100% /mnt/disk1 /dev/md2 13T 13T 27G 100% /mnt/disk2 /dev/md3 15T 15T 29G 100% /mnt/disk3 /dev/md4 9.1T 9.1T 24G 100% /mnt/disk4 /dev/md5 15T 6.2T 8.4T 43% /mnt/disk5 /dev/sdd1 932G 56G 876G 6% /mnt/cache /dev/nvme0n1p1 1.9T 137G 1.7T 8% /mnt/plex shfs 64T 56T 8.5T 87% /mnt/user0 shfs 64T 56T 8.5T 87% /mnt/user team1crypt: 1.0P 0 1.0P 0% /mnt/user/teamdrives/team1 /dev/loop2 20G 14G 5.6G 71% /var/lib/docker /dev/loop3 1.0G 5.7M 903M 1% /etc/libvirt team2crypt: 1.0P 0 1.0P 0% /mnt/user/teamdrives/team2 Edited March 23, 20233 yr by MosteanuV
March 24, 20233 yr Author I saw but how can i find out what is making it full? It was ok a few days ago
March 24, 20233 yr Community Expert On 3/23/2023 at 9:06 AM, JorgeB said: if you have some mappings to anything other than /mnt/user, since they will be mapped to RAM, check all.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.