K1ngJony

Thanks @JorgeB and @Michael_P! Both answers very helpful. I thought it was possible to tell which process was chewing up the RAM, however I'll closely monitor it and limit the memory to the container if needed.

Hi Unraid community, I require some assistance with my server and would much appreciate your help. My Fix Common Problems plugin is reporting that my server is running out of memory and killing off processes to free some up. I've only had my Plex docker killed off so far, so nothing major, just more of an annoyance. I figured I should post here before it gets worse though. I've attached my diagnostics for your perusal. When I had a look, I was unable to find the culprit, though I suppose I don't really know what I'm looking for, so some guidance for next time as to where I should be looking would also be greatly appreciated. TIA. schirmer-nas-diagnostics-20240220-2309.zip

Not sure. I set it up, as instructed, to (what I thought was) transcode on RAM. I've given up on xteve anyway so, if I delete the docker will that clear it?

The rootfs and /var/log errors both arose in Fix Common Problems on my server. I have been wondering why my VM keeps crashing lately and I now suspect it's because of this. I have attached my diagnostics and supplied the output for my folder on RAM below. Any help fixing these two issues would be greatly appreciated. Folders output: plugin: installing: https://raw.githubusercontent.com/Squidly271/misc-stuff/master/memorystorage.plg plugin: downloading https://raw.githubusercontent.com/Squidly271/misc-stuff/master/memorystorage.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/misc-stuff/master/memorystorage.plg ... done This script may take a few minutes to run, especially if you are manually mounting a remote share outside of /mnt/disks or /mnt/remotes /usr/bin/du --exclude=/mnt/user --exclude=/mnt/user0 --exclude=/mnt/disks --exclude=/proc --exclude=/sys --exclude=/var/lib/docker --exclude=/boot --exclude=/mnt -h -d2 / 2>/dev/null | grep -v 0$' ' 4.0K /tmp/ca_notices 3.0M /tmp/pkg 11G /tmp/xteve 736K /tmp/user.scripts 11M /tmp/fix.common.problems 28K /tmp/unassigned.devices 13M /tmp/community.applications 8.0K /tmp/ca.turbo 420K /tmp/notifications 632K /tmp/plugins 4.0K /tmp/emhttp 11G /tmp 928K /usr/man 20K /usr/info 824K /usr/doc 248K /usr/include 23M /usr/libexec 5.0M /usr/src 57M /usr/share 46M /usr/sbin 152M /usr/local 693M /usr/lib64 5.3M /usr/lib 333M /usr/bin 1.3G /usr 22M /sbin 68K /run/libvirt 1.1M /run/docker 4.0K /run/avahi-daemon 4.0K /run/elogind 4.0K /run/dbus 284K /run/udev 8.0K /run/blkid 1.6M /run 4.0K /lib64/xfsprogs 12K /lib64/pkgconfig 1.5M /lib64/elogind 4.0K /lib64/e2fsprogs 1.5M /lib64/security 28M /lib64 69M /lib/modules 4.0K /lib/systemd 88K /lib/modprobe.d 32K /lib/dhcpcd 8.1M /lib/udev 216M /lib/firmware 293M /lib 8.0K /etc/vulkan 4.0K /etc/OpenCL 4.0K /etc/nvidia-container-runtime 8.0K /etc/docker 4.0K /etc/rsyslog.d 4.0K /etc/netatalk 1.3M /etc/libvirt 332K /etc/libvirt- 4.0K /etc/pkcs11 144K /etc/lvm 8.0K /etc/libnl 8.0K /etc/ssmtp 16K /etc/samba 40K /etc/php-fpm.d 16K /etc/php-fpm 8.0K /etc/php 36K /etc/nginx 2.2M /etc/file 24K /etc/avahi 48K /etc/apcupsd 48K /etc/security 244K /etc/ssl 608K /etc/ssh 48K /etc/mcelog 88K /etc/mc 48K /etc/logrotate.d 4.0K /etc/sensors.d 36K /etc/iproute2 9.1M /etc/udev 24K /etc/modprobe.d 4.0K /etc/skel 108K /etc/pam.d 4.0K /etc/elogind 4.0K /etc/cron.monthly 4.0K /etc/cron.hourly 8.0K /etc/cron.daily 4.0K /etc/cron.d 8.0K /etc/cron.weekly 8.0K /etc/dbus-1 4.0K /etc/sasl2 72K /etc/default 332K /etc/rc.d 8.0K /etc/acpi 60K /etc/profile.d 16M /etc 12M /bin 306M /var/sa 85M /var/local 4.0K /var/kerberos 32K /var/state 2.2M /var/cache 16K /var/named 52K /var/tmp 16K /var/spool 8.0K /var/lock 73M /var/log 8.4M /var/lib 474M /var 4.0K /root/.local 4.0K /root/.cache 4.0K /root/.config 32K /root 13G / 0 /mnt/rootshare 0 /mnt Finished. NOTE: If there is any subdirectory from /mnt appearing in this list, then that means that you have (most likely) a docker app which is directly referencing a non-existant disk or cache pool script: memorystorage.plg executed schirmer-nas-diagnostics-20220927-0947.zip

Thanks for your advice @itimpi. I'll RMA the drive then, just to be safe. Definitely don't want a parity drive (or any drive for that matter) failing on me anytime soon if I can avoid it.

Hi all, This is my first time seeing issues arise with preclear. I've only precleared one disk prior and everything was successful. This time my first preclear failed during the pre-read stage, then I ran three more preclears just to be sure (1 cycle, then 2 more, hence separate logs) and they were all successful but had an increasing number of sectors re-allocated. Do I need to be concerned about the sector re-allocation or does it mean that preclear worked as it should and "fixed" the bad sectors? I currently have one 14TB parity drive and my intent was to swap it out for this 18TB one. It's still sitting unmounted because I'm not sure if I need to RMA the drive. I trust this forum can help me figure that out. I have attached the three preclear logs and the SMART report for your pursual. Thanks for your help! preclear_rpt_ZR52F3K9_2021-11-25.txt preclear_rpt_ZR52F3K9_2021-11-19.txt preclear_disk_ZR52F3K9_21780.txt ST18000NM000J_ZR52F3K9-20211125-0948.txt

I had this message ("Machine Check Events detected on your server" "Your server has detected hardware errors.") pop up in Common Problems and was told to post my diagnostics here to get some advice. Anything I need to worry about or look at fixing? schirmer-nas-diagnostics-20210725-1348.zip