Aleksandar Todorov

Thank you Jorge. I`ve made the changes you suggested. Also disabled precision boost overdrive and activated power on after power cut. I hope that will help to make the system more stable.

Yeah I`m pretty sure hardware is causing the server to crash. I`m testing Unraid on new setup with x570 motherboard and better CPU. The RAM is nonECC too. Probably the motherboard B450M-K is too crappy to handle Unraid without crashes.

This time admin panel is not responding. I can access smb share and work with it but admin panel is not loading at all...

Jun 8 21:08:27 Tower wsdd2[2798]: starting. Jun 8 21:08:27 Tower root: /usr/sbin/winbindd -D Jun 8 21:08:28 Tower winbindd[2799]: [2022/06/08 21:08:28.013515, 0] ../../source3/winbindd/winbindd.c:1722(main) Jun 8 21:08:28 Tower winbindd[2799]: winbindd version 4.15.7 started. Jun 8 21:08:28 Tower winbindd[2799]: Copyright Andrew Tridgell and the Samba Team 1992-2021 Jun 8 21:08:28 Tower winbindd[2801]: [2022/06/08 21:08:28.016788, 0] ../../source3/winbindd/winbindd_cache.c:3085(initialize_winbindd_cache) Jun 8 21:08:28 Tower winbindd[2801]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jun 8 21:08:28 Tower emhttpd: shcmd (43): /etc/rc.d/rc.avahidaemon restart Jun 8 21:08:28 Tower root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Jun 8 21:08:28 Tower avahi-dnsconfd[1963]: read(): EOF Jun 8 21:08:28 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jun 8 21:08:28 Tower avahi-daemon[2818]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jun 8 21:08:28 Tower avahi-daemon[2818]: Successfully dropped root privileges. Jun 8 21:08:28 Tower avahi-daemon[2818]: avahi-daemon 0.8 starting up. Jun 8 21:08:28 Tower avahi-daemon[2818]: Successfully called chroot(). Jun 8 21:08:28 Tower avahi-daemon[2818]: Successfully dropped remaining capabilities. Jun 8 21:08:28 Tower avahi-daemon[2818]: Loading service file /services/sftp-ssh.service. Jun 8 21:08:28 Tower avahi-daemon[2818]: Loading service file /services/smb.service. Jun 8 21:08:28 Tower avahi-daemon[2818]: Loading service file /services/ssh.service. Jun 8 21:08:28 Tower avahi-daemon[2818]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.60. Jun 8 21:08:28 Tower avahi-daemon[2818]: New relevant interface br0.IPv4 for mDNS. Jun 8 21:08:28 Tower avahi-daemon[2818]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Jun 8 21:08:28 Tower avahi-daemon[2818]: New relevant interface lo.IPv6 for mDNS. Jun 8 21:08:28 Tower avahi-daemon[2818]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jun 8 21:08:28 Tower avahi-daemon[2818]: New relevant interface lo.IPv4 for mDNS. Jun 8 21:08:28 Tower avahi-daemon[2818]: Network interface enumeration completed. Jun 8 21:08:28 Tower avahi-daemon[2818]: Registering new address record for 192.168.1.60 on br0.IPv4. Jun 8 21:08:28 Tower avahi-daemon[2818]: Registering new address record for ::1 on lo.*. Jun 8 21:08:28 Tower avahi-daemon[2818]: Registering new address record for 127.0.0.1 on lo.IPv4. Jun 8 21:08:28 Tower emhttpd: shcmd (44): /etc/rc.d/rc.avahidnsconfd restart Jun 8 21:08:28 Tower root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Jun 8 21:08:28 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jun 8 21:08:28 Tower avahi-dnsconfd[2827]: Successfully connected to Avahi daemon. Jun 8 21:08:28 Tower emhttpd: shcmd (54): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 Jun 8 21:08:28 Tower kernel: loop2: detected capacity change from 0 to 41943040 Jun 8 21:08:28 Tower kernel: BTRFS: device fsid 66323b1c-6ee2-461f-9cdd-56c33e9363a9 devid 1 transid 85 /dev/loop2 scanned by udevd (2861) Jun 8 21:08:28 Tower kernel: BTRFS info (device loop2): flagging fs with big metadata feature Jun 8 21:08:28 Tower kernel: BTRFS info (device loop2): using free space tree Jun 8 21:08:28 Tower kernel: BTRFS info (device loop2): has skinny extents Jun 8 21:08:28 Tower root: Resize device id 1 (/dev/loop2) from 20.00GiB to max Jun 8 21:08:28 Tower emhttpd: shcmd (56): /etc/rc.d/rc.docker start Jun 8 21:08:28 Tower root: starting dockerd ... Jun 8 21:08:29 Tower avahi-daemon[2818]: Server startup complete. Host name is Tower.local. Local service cookie is 1204252576. Jun 8 21:08:29 Tower kernel: Bridge firewalling registered Jun 8 21:08:29 Tower avahi-daemon[2818]: Joining mDNS multicast group on interface br-64f387a028bf.IPv4 with address 172.31.200.1. Jun 8 21:08:29 Tower avahi-daemon[2818]: New relevant interface br-64f387a028bf.IPv4 for mDNS. Jun 8 21:08:29 Tower avahi-daemon[2818]: Registering new address record for 172.31.200.1 on br-64f387a028bf.IPv4. Jun 8 21:08:29 Tower avahi-daemon[2818]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jun 8 21:08:29 Tower avahi-daemon[2818]: New relevant interface docker0.IPv4 for mDNS. Jun 8 21:08:29 Tower avahi-daemon[2818]: Registering new address record for 172.17.0.1 on docker0.IPv4. Jun 8 21:08:30 Tower avahi-daemon[2818]: Service "Tower" (/services/sftp-ssh.service) successfully established. Jun 8 21:08:30 Tower avahi-daemon[2818]: Service "Tower" (/services/smb.service) successfully established. Jun 8 21:08:30 Tower avahi-daemon[2818]: Service "Tower" (/services/ssh.service) successfully established. Jun 8 21:08:32 Tower rc.docker: created network br0 with subnets: 192.168.1.0/24; Jun 8 21:08:32 Tower emhttpd: shcmd (70): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Jun 8 21:08:32 Tower kernel: loop3: detected capacity change from 0 to 2097152 Jun 8 21:08:32 Tower kernel: BTRFS: device fsid 716368d9-a89f-4047-83de-e3ce44cd562f devid 1 transid 16 /dev/loop3 scanned by udevd (2867) Jun 8 21:08:32 Tower kernel: BTRFS info (device loop3): flagging fs with big metadata feature Jun 8 21:08:32 Tower kernel: BTRFS info (device loop3): using free space tree Jun 8 21:08:32 Tower kernel: BTRFS info (device loop3): has skinny extents Jun 8 21:08:32 Tower root: Resize device id 1 (/dev/loop3) from 1.00GiB to max Jun 8 21:08:32 Tower emhttpd: shcmd (72): /etc/rc.d/rc.libvirt start Jun 8 21:08:32 Tower root: Starting virtlockd... Jun 8 21:08:32 Tower root: Starting virtlogd... Jun 8 21:08:32 Tower root: Starting libvirtd... Jun 8 21:08:32 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Jun 8 21:08:32 Tower emhttpd: nothing to sync Jun 8 21:08:32 Tower avahi-daemon[2818]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jun 8 21:08:32 Tower avahi-daemon[2818]: New relevant interface virbr0.IPv4 for mDNS. Jun 8 21:08:32 Tower avahi-daemon[2818]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Jun 8 21:08:32 Tower dnsmasq[3515]: started, version 2.86 cachesize 150 Jun 8 21:08:32 Tower dnsmasq[3515]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile Jun 8 21:08:32 Tower dnsmasq-dhcp[3515]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Jun 8 21:08:32 Tower dnsmasq-dhcp[3515]: DHCP, sockets bound exclusively to interface virbr0 Jun 8 21:08:32 Tower dnsmasq[3515]: reading /etc/resolv.conf Jun 8 21:08:32 Tower dnsmasq[3515]: using nameserver 192.168.1.8#53 Jun 8 21:08:32 Tower dnsmasq[3515]: read /etc/hosts - 2 addresses Jun 8 21:08:32 Tower dnsmasq[3515]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Jun 8 21:08:32 Tower dnsmasq-dhcp[3515]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jun 8 21:09:14 Tower webGUI: Successful login user root from 192.168.1.123 This is after rebooting anything unusual ?

At system boot the OS is printing "CPU is not supported" is this even possible??

Hello guys! I`m in great need of your help. 1. During copying or deleting files on my shares via smb in Windows suddenly all shares (under Shares tab in Admin panel) disappeared. Admin panel is active and I can establish a connection to Unraid except to my shares. The issue resolves after a system reboot until it happens again, it always does at some point. Had this issue many times already, every single day. I tried everything reinstalling Unraid, changing RAM dims but the same issue occurs again and again. I`m very frustrated because I spend so much time and I`m not able to resolve this by my self. I need to know what`s wrong... is it my hardware or it`s something else that I have done the wrong way. 2. On top of that I have WireGuard installed and set up. Suddenly wireguard went off and when I try to start it again it fails "Execution error Server error" System specs: AMD Ryzen 5 3600X 6-Core @ 3.8 GHz ASUSTeK COMPUTER INC. PRIME B450M-K 16GB DDR4 Crucial Balistix nonECC 2 x WDC_WD5000AAKX-07U6AA0_WD-WCC2EL928191 - 500 GB (1 parity) I ran diagnostics. Thank you in advance. tower-diagnostics-20220608-1900 anony.zip