I have had Unraid go unresponsive several times now after the server is not in use for while usually during the night. I can't access from Webgui or ssh or telnet or anything. I have a keyboard hooked up and this morning I went to type diagnostics to try to get the logs before powering down and even the keyboard was unresponsive. I had to hard reset again which I hate doing but had no choice. I'm running troubleshooting mode now on fix common problems to hopefully get those logs too. Not sure what is going on.

-I have plex docker running and home assistant docker as I'm trying that out.

-In the last month, I upgraded my system to a X79 board with a E5-2670 and now 16GB of memory.

-I attached 3-26-17 diagnostic logs from 10:12AM and then the logs this morning after hard reset to see if that helps.

 

Let me know what else to do to help figure this out? I tried to research other unresponsive posts to figure it out but couldn't make sense of it.

 

Thanks

snowtower-diagnostics-20170326-1011.zip

snowtower-diagnostics-20170327-0840.zip

Reiserfs disks seem to be the #1 reason for this issue, convert one of your disks to XFS, limit all writes to that disk for a few days/weeks by changing your shares(s) included disks and see if crashing stops, if yes convert remaining disks.

 

PS: IMO you should convert even if this isn't the source of the problem, there have been multiple issues with reiser lately and they have terrible performance in certain situations.

I have 2 disks that I can convert easily to XFS since I added them recently with my system upgrade and they have no data on them so I will try that out for sure. I saw lots going around about ReiserFS but was not sure what the deal was.

Ok my system was frozen again this morning. I was moving info to another disk to convert my last disk to XFS and woke up this morning to a frozen unraid again. I have logs since I have it in troubleshooting mode.

 

Any help would be appreciated.

snowtower-diagnostics-20170328-0718.zip

this won't really solve it, but i rolled back to 6.2.4 and system no longer crashes.  obviously the issue still exists, but i couldn't face a hard reset every couple days

Ok, in order for us to better diagnose what is going on, you will need to attach a monitor to your system and boot into console mode (not GUI mode).  From there, login to your server and type the following:

 

tail /var/log/syslog -f

This will print all log messages directly out to the console.  Let the system crash again and when it does, take a pic of the log on the monitor and post that back here.  That's the only way we can learn more about what's happening when the system crashes.

Ok I got the console showing logs. We will see what happens. My system in now on XFS on all the array drives except cache. We will see what happens in the morning.

Well of course it didn't crash last night but I checked out the system stats and almost all my system memory is cached. Is that normal? See attached screenshot. Plex docker and home assistant running but no one is watching anything on Plex and Hom assistant hardly has anything running in it.

9 minutes ago, Snowman said:

Is that normal?

 

Yes, Linux uses all free memory for cache, it will free it up as required by other processes.

Well maybe switching to XFS has solved it but not sure yet. I will have to run my VM and other things to see if it crashes.

Ok, please keep us posted.

Well, it has not crashed since moving everything to XFS so I guess the 6.3.2 does not like Resierfs but we seem stable now.