I got a new server and upgraded to 7.0 at basically the same time (pretty dumb I know), and have since been having random crashes every 24-48 hours. The logs saved to my cache drive don't point to anything, there's nothing written for about 4 hours prior to the crash which occurred at 6:40 AM. See here:

Jan 14 17:26:01 Wyse unassigned.devices: Share settings updated.
Jan 14 17:26:01 Wyse plugin-manager: unassigned.devices.plg updated
Jan 14 17:39:46 Wyse flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Jan 14 23:00:01 Wyse Plugin Auto Update: Checking for available plugin updates
Jan 14 23:00:04 Wyse Plugin Auto Update: Community Applications Plugin Auto Update finished
Jan 15 02:00:01 Wyse shfs: /usr/sbin/zfs unmount 'cache/media' 2>&1
Jan 15 02:00:01 Wyse shfs: /usr/sbin/zfs destroy 'cache/media' 2>&1
Jan 15 02:00:01 Wyse shfs: /usr/sbin/zfs mount 'cache/media' 2>&1
Jan 15 02:15:47 Wyse monitor_nchan: Stop running nchan processes

Looking at the monitor after the crash - it's basically a black screen with every few seconds a flicker of text that's really hard to make out. It says something about VGA and DRM? Not sure if there's any relevance to that.

 

What else can I do to troubleshoot this? If I mirror the logs to my flash instead of my cache drive will it catch anything extra? I'm currently running an extended memtest. I ran it for 3 successful passes after I assembled the system, but I'm going to run it for longer this time. If that doesn't show anything I guess the next step is to downgrade to 6.12.14 and see if the problem goes away.

 

Any advice?

 

Thanks.

 

 

wyse-diagnostics-20250113-2102.zip

If 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. 

1 hour ago, JorgeB said:

If 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. 

Ok thanks I'll try that. If it is hardware then I'm not sure really what else to do. RAM is brand new and tests fine. PSU is also brand new, I'm not sure how to test that. The only other thing I can think of is the USB boot drive - is there a way to test that?

You can try a different one, also, and 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.

On 1/15/2025 at 10:31 AM, JorgeB said:

If 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. 

Update: server is crashing more frequently now. Last night after about 3 hours with only plugins + plex running. Then again today after 2 hours while in safe mode with only Scrypted running. 

 

Local syslog captured this:

Jan 17 13:30:01 Green crond[1701]: exit status 127 from user root /usr/sbin/nutstats > /dev/null 2>&1
Jan 17 14:00:01 Green crond[1701]: exit status 127 from user root /usr/sbin/nutstats > /dev/null 2>&1

I assume this is just a byproduct of my NUT plugin not being loaded but a configured script still running? Does this mean anything or nothing?

 

My next step will be to boot into a UGreen OS and see if it still crashes, and if so, proceed down the route of warranty replacement.

Did you try loading up a trial USB?  When those things start to fail it can cause all sorts of inexplicable problems.

2 minutes ago, Veah said:

Did you try loading up a trial USB?  When those things start to fail it can cause all sorts of inexplicable problems.

Oh like restore from backup onto a new USB? I haven't tried that. I did a chkdsk on my usb drive and it all came back ok. The reason I don't think it's the USB is that this all started when I updated to Unraid 7.0 and moved to a new server simultaneously. Dumb to do both at once I know.

10 minutes ago, mattalat said:

Oh like restore from backup onto a new USB?

I would just load fresh and use trial.  Assign your drives the same way you have in your current array.  Load up a few docker containers and just test fresh.  If that works out, then run a restore on that new USB.  

Occurred to me now with v7 you don't even need to assign array anymore to start.  Try that might be even better.

7 minutes ago, Veah said:

Occurred to me now with v7 you don't even need to assign array anymore to start.  Try that might be even better.

Thanks I'll give that a shot now

4 hours ago, Veah said:

I would just load fresh and use trial.  Assign your drives the same way you have in your current array.  Load up a few docker containers and just test fresh.  If that works out, then run a restore on that new USB.  

Well it had gone from crashing every 24-48 hours to 3-4 hours and then to less than an hour when I finally read your message. Now it's been up for 4 hours with the new flash drive, fingers crossed. I thought for sure it had something to do with switching to a new server but maybe my damn drive decided to fail at the same time. Thanks for your advice, I'll update again tomorrow if server stays up.

 

23 hours ago, Veah said:

I would just load fresh and use trial.  Assign your drives the same way you have in your current array.  Load up a few docker containers and just test fresh.  If that works out, then run a restore on that new USB.  

UGHH. Ok so this is weird. It ran for 24 hours with no crashing on the new flash drive. Then I restored from backup my regular server build and it crashed within an hour. Nothing is recorded in the logs. Does this mean it's some sort of setting in my saved build that is causing the crash?

5 minutes ago, mattalat said:

Does this mean it's some sort of setting in my saved build that is causing the crash?

Yep.  I would not be able to dissect logs well enough to isolate where the problem is.  Have a look at the Dynamix Factory Reset plugin.  You should be able to keep your array and pool and default the rest.  See if it runs stable after that.

1 hour ago, Veah said:

Yep.  I would not be able to dissect logs well enough to isolate where the problem is.  Have a look at the Dynamix Factory Reset plugin.  You should be able to keep your array and pool and default the rest.  See if it runs stable after that.

Ok I just reset everything and now running only scrypted as a test. I wonder if somehow my docker img file was corrupted and was causing the crash. We’ll see how it goes. 

When your unraid crashes, are the dockers you're running still accessible?

 

I've been having similar problems since upgrading to 7.0 - the WebUI will stop responding, and trying to reboot via SSH won't work either (even though it gives me a message saying it will).

 

My docker containers still work though, so I can still access things like my Homepage and Plex, etc. But I've had to hard reset it each time to be able to get the WebUI back again.

5 hours ago, cglatot said:

When your unraid crashes, are the dockers you're running still accessible?

 

I've been having similar problems since upgrading to 7.0 - the WebUI will stop responding, and trying to reboot via SSH won't work either (even though it gives me a message saying it will).

 

My docker containers still work though, so I can still access things like my Homepage and Plex, etc. But I've had to hard reset it each time to be able to get the WebUI back again.

Nope, it's a full on crash with all containers no longer functioning. Requires pulling the power plug to reboot. There's a thread on the "bug reports" forum that sounds like what you're experiencing though.

Ahhhh, I found the post you were talking about, thanks!

 

Hope you can get your problem solved!

I just did a new install with brand new cpu mobo and ram, drives etc. Was getting crashes anytime I ran parity or tried to copy data, for over a week.

 

Turns out my LSI raid controller and HP Expander dont do well in the PCIe slots on CPU lanes. Moved them to chipset PCIE and stable on all tasks.

This has been happening to me too since updating to 7.0

I have tried:

New boot USB

Removed and/or checked all Plugins

Booting in safe mode doesn't even work

downgraded and reupgraded to 7.0

Logs show nothing useful other than 

"monitor_nchan: Stop running nchan processes"

Docker containers are usually still up but just recently even dockers go down too. 

 

I don't know what to do and it is driving me crazy.

5 hours ago, thewagdy said:

Booting in safe mode doesn't even work

Can you expand on this, safe mode just doesn't load plugins, no reason for that mode not to work if the normal one does.

This is happening to me even more frequently than it was (used to randomly happen once per week) now every couple days, no warnings I didn't even realize it was down for the last 2 days until I went to use something. Last thing in log was "Stop running nchan processes"

On 2/26/2025 at 8:52 PM, Evilpig said:

This is happening to me even more frequently than it was (used to randomly happen once per week) now every couple days, no warnings I didn't even realize it was down for the last 2 days until I went to use something. Last thing in log was "Stop running nchan processes"

Yes! its so frustrating. I had rolled back but I needed to upgrade again because I am getting an intel gpu for plex. and only 3 hours after upgrading same issue. even on 7.0.1. 

On 2/19/2025 at 1:57 AM, JorgeB said:

Can you expand on this, safe mode just doesn't load plugins, no reason for that mode not to work if the normal one does.

When I rebooted in safe mode I could not navigate to the gui via network. Never came back up 

3 hours ago, thewagdy said:

When I rebooted in safe mode I could not navigate to the gui via network. Never came back up 

That means there are other issues, safe mode is just normal boot without plugins.

3 hours ago, JorgeB said:

That means there are other issues, safe mode is just normal boot without plugins.

Here is my latest diagnostics I was able to get during the latest crash. I cant last more than a few hours before gui becomes unresponsive. 

wagdyserver-diagnostics-20250301-0533.zip