Hi Everyone,

Just moved to Unraid from my old QNAP NAS.

I've tried to di things in proper way by using server hardware:

OS: UNRAID UNLEASHED 7.3.2

MB: E3C246D4U2-2T

LAN: 2x Intel 10Gbit

CPU: Xeon E-2176G

RAM: 64GB (16x4GB) DDR4 SK Hynix 2400 ECC UDIMM

POOL: 6x Ironwolf Pro 4TB Raid-Z2

PSU: Corsair SF750 80+ Platinum

BOOT: Patriot P320 128GB

APP: 2x1TB Samsung 970 EVO NVME

CASE: Jonsbo N6

HS: Thermalright SI100

FAN: 2x BeQuiet! 140, 4xBeQuiet! 120

Everything was working properly, just after 8 hrs of uptime, the web server start to been unaccessible.

The shares were mounted still and working good, as well as the main terminal.

Attached the diagnostics and the syslog previous I've downloaded after reboot (somewhere in the middle of this syslog the issue happened).

Thanks a lot to anyone that could help me!

custos-unraid-syslog-previous-20260731-0715.zip custos-unraid-diagnostics-20260731-0925.zip

Edited 15 hours ago15 hr by HariSeldon

Syslog previously covered over 48H of uptime, but there's nothing relevant logged I can see there that would explain a crash, one 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, including the individual docker containers.

thanks Jorge for the reply!

Sorry 8 hours was meant from last reboot, but yes is 48hrs of uptime.

no docker ot whatsoever, just ZFS shares, that's it.

hardware was working properly, as I could access via IPMI interface, and shares was accessibile though both ethernet interface, also from console I was able to check with dmesg and so on and everything working for hw point of view.

was just the webui not working.

Edited 12 hours ago12 hr by HariSeldon

If you have console access, get the diagnostics right after it happens (before rebooting).

33 minutes ago, JorgeB said:

If you have console access, get the diagnostics right after it happens (before rebooting).

I did it! Before reboot! I have in the usb drive, as soon as I come back home I’ll share it! Thanks !

here it is

custos-unraid-diagnostics-20260731-0008.zip

I'm still not seeing a reason for the issue, when it happens again, grab the following outputs from the Unraid console before rebooting:

date

curl -sv --connect-timeout 3 --max-time 15 http://127.0.0.1/ -o /dev/null

curl -sv --connect-timeout 3 --max-time 15 http://127.0.0.1/webGui/images/UN-logotype-gradient.svg -o /dev/null

curl -sv --connect-timeout 3 --max-time 15 http://<UNRAID-IP>/ -o /dev/null

ss -lntp

ss -lxnp

ps -eo pid,ppid,stat,wchan:32,etime,cmd | grep -E 'nginx|php-fpm|emhttp|unraid-api|nchan'

ls -la /var/log/nginx

tail -n 300 /var/log/nginx/error.log

tail -n 300 /var/log/phplog

tail -n 300 /var/log/syslog

ls -ld /usr/local/emhttp /usr/local/emhttp/state /var/local/emhttp

readlink /usr/local/emhttp/state

stat /usr/local/emhttp/auth-request.php

ls -l /var/run/php-fpm.sock /var/run/unraid-api.sock /var/run/emhttpd.socket

ip -br addr

ip -s link

ip neigh show

From another LAN machine, test both URLs:

curl -v --connect-timeout 3 --max-time 15 http://<UNRAID-IP>/

curl -v --connect-timeout 3 --max-time 15 http://<server-name>.local/

arp -an

The results should help rule out the main possibilities.

5 hours ago, JorgeB said:

I'm still not seeing a reason for the issue, when it happens again, grab the following outputs from the Unraid console before rebooting:

date

curl -sv --connect-timeout 3 --max-time 15 http://127.0.0.1/ -o /dev/null

curl -sv --connect-timeout 3 --max-time 15 http://127.0.0.1/webGui/images/UN-logotype-gradient.svg -o /dev/null

curl -sv --connect-timeout 3 --max-time 15 http://<UNRAID-IP>/ -o /dev/null

ss -lntp

ss -lxnp

ps -eo pid,ppid,stat,wchan:32,etime,cmd | grep -E 'nginx|php-fpm|emhttp|unraid-api|nchan'

ls -la /var/log/nginx

tail -n 300 /var/log/nginx/error.log

tail -n 300 /var/log/phplog

tail -n 300 /var/log/syslog

ls -ld /usr/local/emhttp /usr/local/emhttp/state /var/local/emhttp

readlink /usr/local/emhttp/state

stat /usr/local/emhttp/auth-request.php

ls -l /var/run/php-fpm.sock /var/run/unraid-api.sock /var/run/emhttpd.socket

ip -br addr

ip -s link

ip neigh show

From another LAN machine, test both URLs:

curl -v --connect-timeout 3 --max-time 15 http://<UNRAID-IP>/

curl -v --connect-timeout 3 --max-time 15 http://<server-name>.local/

arp -an

The results should help rule out the main possibilities.

Thanks ! I’ll do that !