My unraid Server crashes every 3-4 days. At the moment i want to make a Parity-Sync with a new 16TB disk.

Every 3-4 days the web UI crashes. Than i can not connect with Telnet or something else. I startet a syslog and see, when the web UI crashes, the whole Server crashes and does not make anything. At the first try i wait 30 days and hope that the parity sync complete, but nothing happened. The same always happen the years before with parity check. My Unraid Version is 6.11.5. The parity sync need 16 days.

 

This are the last line of the syslog before a crash (the whole log at the attachement):

 

Mar 25 08:12:52 Tower  avahi-daemon[3992]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214).
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Successfully dropped root privileges.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: avahi-daemon 0.8 starting up.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Successfully called chroot().
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Successfully dropped remaining capabilities.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Loading service file /services/sftp-ssh.service.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Loading service file /services/smb.service.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Loading service file /services/ssh.service.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.3.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: New relevant interface eth0.IPv4 for mDNS.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: New relevant interface lo.IPv6 for mDNS.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: New relevant interface lo.IPv4 for mDNS.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Network interface enumeration completed.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Registering new address record for 192.168.0.3 on eth0.IPv4.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Registering new address record for ::1 on lo.*.
Mar 25 08:12:52 Tower  avahi-daemon[3992]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mar 25 08:12:52 Tower  emhttpd: shcmd (190): /etc/rc.d/rc.avahidnsconfd restart
Mar 25 08:12:52 Tower root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped
Mar 25 08:12:52 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon:  /usr/sbin/avahi-dnsconfd -D
Mar 25 08:12:52 Tower  avahi-dnsconfd[4001]: Successfully connected to Avahi daemon.
Mar 25 08:12:52 Tower kernel: mdcmd (36): check 
Mar 25 08:12:52 Tower kernel: md: recovery thread: recon P ...
Mar 25 08:12:53 Tower  avahi-daemon[3992]: Server startup complete. Host name is Tower.local. Local service cookie is 1625600723.
Mar 25 08:12:54 Tower  avahi-daemon[3992]: Service "Tower" (/services/ssh.service) successfully established.
Mar 25 08:12:54 Tower  avahi-daemon[3992]: Service "Tower" (/services/smb.service) successfully established.
Mar 25 08:12:54 Tower  avahi-daemon[3992]: Service "Tower" (/services/sftp-ssh.service) successfully established.
Mar 25 08:12:54 Tower Parity Check Tuning: restart to be attempted
Mar 25 08:12:54 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 25 08:12:55 Tower kernel: mdcmd (37): nocheck 
Mar 25 08:12:55 Tower kernel: md: recovery thread: exit status: -4
Mar 25 08:13:01 Tower kernel: mdcmd (38): check CORRECT 3889747528
Mar 25 08:13:01 Tower kernel: 
Mar 25 08:13:01 Tower kernel: md: recovery thread: recon P ...
Mar 25 08:13:04 Tower Parity Check Tuning: Send notification: Array operation restarted: Parity Sync/Data Rebuild (12.4% completed)  (12.4% completed)
Mar 25 08:13:04 Tower Parity Check Tuning: ... but suppressed as system notifications do not appear to be enabled
Mar 25 08:13:04 Tower Parity Check Tuning: Paused: Parity Sync/Data Rebuild
Mar 25 08:13:04 Tower kernel: mdcmd (39): nocheck pause
Mar 25 08:13:04 Tower kernel: 
Mar 25 08:13:04 Tower kernel: md: recovery thread: exit status: -4
Mar 25 08:13:09 Tower Parity Check Tuning: Send notification: Paused: Parity Sync/Data Rebuild (12.4% completed)  (12.4% completed)
Mar 25 08:13:09 Tower Parity Check Tuning: ... but suppressed as system notifications do not appear to be enabled
Mar 25 08:13:15 Tower  nmbd[3961]: [2023/03/25 08:13:15.282300,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Mar 25 08:13:15 Tower  nmbd[3961]:   *****
Mar 25 08:13:15 Tower  nmbd[3961]:   
Mar 25 08:13:15 Tower  nmbd[3961]:   Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.3
Mar 25 08:13:15 Tower  nmbd[3961]:   
Mar 25 08:13:15 Tower  nmbd[3961]:   *****
Mar 25 08:13:47 Tower kernel: mdcmd (40): check resume
Mar 25 08:13:47 Tower kernel: md: recovery thread: recon P ...
Mar 25 08:13:54 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update

 

Now restart:

Mar 26 14:48:07 Tower kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Mar 26 14:48:07 Tower kernel: Linux version 5.19.17-Unraid (root@Develop) (gcc (GCC) 12.2.0, GNU ld version 2.39-slack151) #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022
Mar 26 14:48:07 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot

 

Can somebody help? I have an old Server from 2013. My Ram are only 4 GB. My next try is to change it to 16 GB.

 

Thank you!

Log.txt

Edited March 27, 20233 yr by Slayer_Cheffe

There's nothing relevant logged before the crash, this usually suggests a hardware problem, one thing you can try is to boot the server in safe mode with all docker/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.

Thanks, I try it, but I have no docker and I think no VMs.

I start the server in safe mode and start the parity sync.

In Safe mode everything is good. The parity-sync has worked. No crash in safe mode.

It was faster than before. Instead of 16 days the sync "only" need 9 days.

 

How can I find the Software problem in normal mode?

Basically you'll need to to this:

 

On 3/27/2023 at 10:30 AM, JorgeB said:

if it doesn't start turning on the other services one by one.

 

ok. The problem is only after 3-4 days so it will take a long time to find out

 

Yeah, it can be kind of a pain, but it's still the best suggestion I have.