Waodus

Solved by installing truenas scale. Unraid just keeps crashing on my hardware.

Also here the syslog. its pretty big. keeps spewing out: 01:34:12 Sausage nginx: 2024/05/09 01:34:12 [crit] 6555#6555: ngx_slab_alloc() failed: no memory May 9 01:34:12 Sausage nginx: 2024/05/09 01:34:12 [error] 6555#6555: shpool alloc failed May 9 01:34:12 Sausage nginx: 2024/05/09 01:34:12 [error] 6555#6555: nchan: Out of shared memory while allocating message of size 14179. Increase nchan_max_reserved_memory. May 9 01:34:12 Sausage nginx: 2024/05/09 01:34:12 [error] 6555#6555: *519731 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" May 9 01:34:12 Sausage nginx: 2024/05/09 01:34:12 [error] 6555#6555: MEMSTORE:01: can't create shared message for channel /disks also this happened that cought my eye that keeps happening. May 23 04:35:01 Sausage dhcpcd[1110]: br0: carrier lost May 23 04:35:03 Sausage network: reload service: ntpd May 23 04:35:03 Sausage ntpd[3412]: ntpd exiting on signal 1 (Hangup) May 23 04:35:03 Sausage ntpd[3412]: 127.127.1.0 local addr 127.0.0.1 -> <null> May 23 04:35:03 Sausage ntpd[6062]: ntpd [email protected] Tue Jun 6 17:07:37 UTC 2023 (1): Starting May 23 04:35:03 Sausage ntpd[6062]: Command line: /usr/sbin/ntpd -g -u ntp:ntp May 23 04:35:03 Sausage ntpd[6062]: ---------------------------------------------------- May 23 04:35:03 Sausage ntpd[6062]: ntp-4 is maintained by Network Time Foundation, May 23 04:35:03 Sausage ntpd[6062]: Inc. (NTF), a non-profit 501(c)(3) public-benefit May 23 04:35:03 Sausage ntpd[6062]: corporation. Support and training for ntp-4 are May 23 04:35:03 Sausage ntpd[6062]: available at https://www.nwtime.org/support May 23 04:35:03 Sausage ntpd[6062]: ---------------------------------------------------- May 23 04:35:03 Sausage ntpd[6062]: DEBUG behavior is enabled - a violation of any May 23 04:35:03 Sausage ntpd[6062]: diagnostic assertion will cause ntpd to abort May 23 04:35:03 Sausage ntpd[6064]: proto: precision = 0.068 usec (-24) May 23 04:35:03 Sausage ntpd[6064]: basedate set to 2023-05-25 May 23 04:35:03 Sausage ntpd[6064]: gps base set to 2023-05-28 (week 2264) May 23 04:35:03 Sausage ntpd[6064]: initial drift restored to 30.709000 May 23 04:35:03 Sausage ntpd[6064]: Listen normally on 0 lo 127.0.0.1:123 May 23 04:35:03 Sausage ntpd[6064]: Listen normally on 1 lo [::1]:123 May 23 04:35:03 Sausage ntpd[6064]: Listening on routing socket on fd #18 for interface updates May 23 04:35:03 Sausage ntpd[6064]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 23 04:35:03 Sausage network: reload service: avahidaemon May 23 04:35:03 Sausage avahi-daemon[3143]: Got SIGTERM, quitting. May 23 04:35:03 Sausage avahi-daemon[3143]: avahi-daemon 0.8 exiting. May 23 04:35:03 Sausage avahi-daemon[6169]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). May 23 04:35:03 Sausage avahi-daemon[6169]: Successfully dropped root privileges. May 23 04:35:03 Sausage avahi-daemon[6169]: avahi-daemon 0.8 starting up. May 23 04:35:03 Sausage avahi-daemon[6169]: Successfully called chroot(). May 23 04:35:03 Sausage avahi-daemon[6169]: Successfully dropped remaining capabilities. May 23 04:35:03 Sausage avahi-daemon[6169]: Loading service file /services/sftp-ssh.service. May 23 04:35:03 Sausage avahi-daemon[6169]: Loading service file /services/smb.service. May 23 04:35:03 Sausage avahi-daemon[6169]: Loading service file /services/ssh.service. May 23 04:35:03 Sausage avahi-daemon[6169]: Network interface enumeration completed. May 23 04:35:03 Sausage avahi-daemon[6169]: Server startup complete. Host name is Sausage.local. Local service cookie is 2798356656. May 23 04:35:03 Sausage avahi-daemon[6169]: Service "Sausage" (/services/ssh.service) successfully established. May 23 04:35:03 Sausage avahi-daemon[6169]: Service "Sausage" (/services/smb.service) successfully established. May 23 04:35:03 Sausage avahi-daemon[6169]: Service "Sausage" (/services/sftp-ssh.service) successfully established. May 23 04:35:03 Sausage network: reload service: samba May 23 04:35:03 Sausage wsdd2[3644]: 'Terminated' signal received. May 23 04:35:03 Sausage wsdd2[3644]: terminating. May 23 04:35:03 Sausage winbindd[3648]: [2024/05/23 04:35:03.755139, 0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler) May 23 04:35:03 Sausage winbindd[3647]: [2024/05/23 04:35:03.755142, 0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler) May 23 04:35:03 Sausage winbindd[3648]: Got sig[15] terminate (is_parent=0) May 23 04:35:03 Sausage winbindd[3647]: Got sig[15] terminate (is_parent=1) May 23 04:35:03 Sausage smbd[6226]: [2024/05/23 04:35:03.810113, 0] ../../source3/smbd/server.c:1741(main) May 23 04:35:03 Sausage smbd[6226]: smbd version 4.17.12 started. May 23 04:35:03 Sausage smbd[6226]: Copyright Andrew Tridgell and the Samba Team 1992-2022 May 23 04:35:03 Sausage kernel: igc 0000:06:00.0 eth3: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX May 23 04:35:03 Sausage wsdd2[6242]: starting. May 23 04:35:03 Sausage kernel: bond0: (slave eth3): link status definitely up, 1000 Mbps full duplex May 23 04:35:03 Sausage kernel: bond0: (slave eth3): making interface the new active one May 23 04:35:03 Sausage kernel: device eth3 entered promiscuous mode May 23 04:35:03 Sausage kernel: bond0: active interface up! May 23 04:35:03 Sausage kernel: br0: port 1(bond0) entered blocking state May 23 04:35:03 Sausage kernel: br0: port 1(bond0) entered forwarding state May 23 04:35:03 Sausage dhcpcd[1110]: br0: carrier acquired May 23 04:35:03 Sausage winbindd[6243]: [2024/05/23 04:35:03.939608, 0] ../../source3/winbindd/winbindd.c:1440(main) May 23 04:35:03 Sausage winbindd[6243]: winbindd version 4.17.12 started. May 23 04:35:03 Sausage winbindd[6243]: Copyright Andrew Tridgell and the Samba Team 1992-2022 May 23 04:35:03 Sausage winbindd[6246]: [2024/05/23 04:35:03.945127, 0] ../../source3/winbindd/winbindd_cache.c:3117(initialize_winbindd_cache) May 23 04:35:03 Sausage winbindd[6246]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 May 23 04:35:03 Sausage dhcpcd[1110]: br0: rebinding lease of 10.0.0.117 May 23 04:35:03 Sausage dhcpcd[1110]: br0: probing address 10.0.0.117/24 May 23 04:35:05 Sausage kernel: igc 0000:06:00.0 eth3: NIC Link is Down May 23 04:35:05 Sausage kernel: bond0: (slave eth3): link status definitely down, disabling slave May 23 04:35:05 Sausage kernel: device eth3 left promiscuous mode May 23 04:35:05 Sausage kernel: bond0: now running without any active interface! May 23 04:35:05 Sausage kernel: br0: port 1(bond0) entered disabled state May 23 04:35:06 Sausage dhcpcd[1110]: br0: carrier lost May 23 04:35:12 Sausage kernel: igc 0000:06:00.0 eth3: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX May 23 04:35:12 Sausage dhcpcd[1110]: br0: carrier acquired May 23 04:35:12 Sausage kernel: bond0: (slave eth3): link status definitely up, 1000 Mbps full duplex May 23 04:35:12 Sausage kernel: bond0: (slave eth3): making interface the new active one May 23 04:35:12 Sausage kernel: device eth3 entered promiscuous mode May 23 04:35:12 Sausage kernel: bond0: active interface up! syslog.1.txt syslog.txt

Ok, the server has been running for a while now. That is good! however when I look in the logs i see many errors. I will share it here sausage-diagnostics-20240523-2058.zip

Is there anyone that knows something?

Hello, I am dealing with a pretty annoying problem. about once in 4-6 days the unraid web gui becomes inaccessible, also the shares stop working. However the plugins keep working as if nothing has happened. i tried booting into safe mode and it would not crash for around 5 days, then i rebooted it into normal mode. i removed all the plugins i had and only ran the arr suite and plex. today i saw it crashed again, this has happened 4 or 5 times now. I dont know why this is happening and its driving me insane. I have set up the syslog server to clone the logs to the usb drive. however it shows me nothing usefull. I will attach the log here for you to see and hopefully find something. memtest came out as a pass. I have also tried putting the unraid usb into a usb2.0 port but this did not solve the issue. I will also attach a picture of the monitor that is hooked up to the server so you can see the error messages its having while its crashed. and another pricture of the screen when i was shutting it down by short pressing the power button. This is when i shut the server down syslog sausage-diagnostics-20240506-2100.zip