Hi everyone,

I’m having a recurring issue with my Unraid server. Lately, it has been crashing almost daily. Sometimes it happens after just an hour, but other times it can run without any problems for up to a week. I really have no idea what could be causing this anymore.

I’ve attached the full diagnostics file in case it helps someone identify the issue. After every crash, a parity check automatically starts when the server comes back up.

For troubleshooting, I already replaced the RAM and also ran a 48-hour stress test without any errors. Unfortunately, the crashes are still happening.

Any advice or help would be greatly appreciated.

Thanks in advance everyone!

tower-diagnostics-20250904-1254.zip

Enable the syslog server and post that after a crash.

11 minutes ago, JorgeB said:

Enable the syslog server and post that after a crash.

Thank you for the quick response. I’ve started the syslog server and will share the logs after the next crash occurs. :)

1 hour ago, JorgeB said:

Enable the syslog server and post that after a crash.

Hi,
My Unraid server has crashed again. Here is the log file from the syslog server.

Thank you in advance.
I hope you can spot something that explains why the server keeps crashing.syslog.logsyslog.log

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Sep 4 05:45:26 Tower rc.rsyslogd: Syslog server daemon... Started.

There was a GPU problem just before the crash, try retesting after temporarily removing the GPU or just the Nvidia driver.

Hi, Thank you for that information.

19 hours ago, JorgeB said:

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)

Sep 4 05:30:24 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Sep 4 05:45:26 Tower rc.rsyslogd: Syslog server daemon... Started.

There was a GPU problem just before the crash, try retesting after temporarily removing the GPU or just the Nvidia driver.

I let it run over night again and the crashes happened again. Maybe you find something again in that nee log.

Thank you in advanced again.

syslog-192.168.178.5.log

I assume it crashed here:

Sep 5 00:48:09 Tower kernel: docker0: port 3(vethee312b1) entered disabled state

Sep 5 01:25:04 Tower rc.rsyslogd: Syslog server daemon... Started.

If yes, I'm afraid there's nothing relevant logged, this can also be a hardware issue, 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.

Additionally, look in the BIOS for a "Global C-States" or similar setting and disable that to retest, it's been known to be a problem with some boards, with both Intel and AMD CPUs.

Hi am having exactly the same problem and its driving me insane. I used to have it before occasionaly when i put a certain level of demand on it now it happens daily even when the server doesn't appear to be doing anything (more so over night),I'm running out of things to try.The problem seems to have got worse since i added an additional drive. In term of hardware setup ive got : -

Intel 13600K

Strix B760 i motherboard

64gb Corsair Vengeance 6200mts RAM

WD 850 SNx 1tb cache drive

Samsung SSD 500gb drive

LSI 9300 8i HBA

4x seagate x18 16tb exos drives

Ive tried all sorts to see if it resolves the problem: -

• Updated the bios to the latest version.

• Ran memtest and that passed with flying colors

• Added a HBA, previously i was using a Chinese nvme SATA expansion card , i thought it might be the nvme getting overwhelmed as its usually designed to manage the IO of 1 drive not 4.

• Switched Splitlocking detection off

• Set docker containers to ipvlan for Macvlan

• Ran a smart test against the new drive and no issues have been found.

I also switched off docker service for a bit and woke up in the morning to find the server had locked up again. so i don't think its the containers.

I'm lost as to what else i could be . I'll try and upload what has been requested above.

12 minutes ago, PhantomICEMAN said:

Hi am having exactly the same problem and its driving me insane.

Since this thread is still active, please start a new one and add the diagnostics, or it can get confusing.

Hi everyone,

I’ve let the server run for several days, and it still crashes—even with all plugins and Docker containers disabled and the array stopped. That leads me to believe it’s a hardware issue. Has anyone had a similar problem? If so, which component turned out to be faulty? Because the crashes happen at very different intervals, I’m leaning toward a failing power supply. What do you think?

Thanks in advance :)

If you have multiple RAM sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

You can also run a 24 hour minimum memtest from the boot menu to see if you have bad ram if you want to try and test all of it at once.