May 17, 20242 yr Hello, I'm experiencing recurring crashes with my Unraid server. Here are the details of my setup and the issues I'm facing: Hardware: Motherboard: ASUSTeK COMPUTER INC. - K31CD-K CPU: i5-7400 Memory: 31 GiB (2.7 GiB used, 19 GiB free) Drives: Samsung Flash Drive (sda): SMART data unavailable due to unknown USB bridge. ST2000DM001-1ER164 (sdd): 2 TB, no SMART errors. Samsung SSD 860 EVO 500GB (sdf): 500 GB, no SMART errors. ST4000VN008-2DR166 (sde): 4 TB, no SMART errors. ST12000NE0007-2GT116 (sdc): 12 TB, no SMART errors. ST12000VN0007-2GS116 (sdb): 12 TB, no SMART errors. Symptoms: The server was last operational until May 17th, 12:50:08. It seems to shut down or stop responding randomly, necessitating a full restart. No critical errors or anomalies are observed in the logs or SMART data from the drives. Logs and Observations: System logs up to the crash show normal activities with no critical errors. Memory usage is well within limits. All drives passed their SMART tests with no signs of reallocated sectors, uncorrectable errors, or other health issues. I've attached the relevant log files and SMART reports for further analysis. The picture is what pops up when my server crash. Any help in diagnosing and resolving this issue would be greatly appreciated. Thank you. unscinfinity-diagnostics-20240517-1301.zip syslog-192.168.1.175.log
May 17, 20242 yr Author 2 minutes ago, NinjkaPower14 said: Hello, I'm experiencing recurring crashes with my Unraid server. Here are the details of my setup and the issues I'm facing: Hardware: Motherboard: ASUSTeK COMPUTER INC. - K31CD-K CPU: i5-7400 Memory: 31 GiB (2.7 GiB used, 19 GiB free) Drives: Samsung Flash Drive (sda): SMART data unavailable due to unknown USB bridge. ST2000DM001-1ER164 (sdd): 2 TB, no SMART errors. Samsung SSD 860 EVO 500GB (sdf): 500 GB, no SMART errors. ST4000VN008-2DR166 (sde): 4 TB, no SMART errors. ST12000NE0007-2GT116 (sdc): 12 TB, no SMART errors. ST12000VN0007-2GS116 (sdb): 12 TB, no SMART errors. Symptoms: The server was last operational until May 17th, 12:50:08. It seems to shut down or stop responding randomly, necessitating a full restart. No critical errors or anomalies are observed in the logs or SMART data from the drives. Logs and Observations: System logs up to the crash show normal activities with no critical errors. Memory usage is well within limits. All drives passed their SMART tests with no signs of reallocated sectors, uncorrectable errors, or other health issues. I've attached the relevant log files and SMART reports for further analysis. The picture is what pops up when my server crash. I thought it was power or heat at first but it doesn't seam so. here's mor info about my server Any help in diagnosing and resolving this issue would be greatly appreciated. Thank you. unscinfinity-diagnostics-20240517-1301.zip 111.58 kB · 0 downloads syslog-192.168.1.175.log 216.92 kB · 0 downloads
May 18, 20242 yr Community Expert 11 hours ago, NinjkaPower14 said: It seems to shut down Do you mean sometimes it shuts down by itself?
May 18, 20242 yr Author 12 hours ago, JorgeB said: Do you mean sometimes it shuts down by itself? Well not really... the computer itself stays on, but I can't do anything like connecting to it and all my docker shutdown. So unraid crash idk why but not the computer itself at random times like 1 to 3 times per month and I have to restart the computer for it to work again.
May 19, 20242 yr Community Expert Unfortunately there's nothing relevant logged in the persistent syslog, this can be a hardware issue, because memtest is only definitive if it finds errors, try with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM, another thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
May 20, 20242 yr Author Its down again today and here whats on the screen directly after. There's à fatal error so I home it mean something this time... syslog-192.168.1.175.log Edited May 20, 20242 yr by NinjkaPower14 Adding the syslog
May 20, 20242 yr Community Expert Solution That could be macvlan related, do you have the persistent syslog? But in any case change docker network to ipvlan, reboot and retest.
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.