30 posts in this topic Last Reply May 16

Recommended Posts

I have recently moved my unRaid system from dual Xeon hardware to an AMD Ryzen 1700 setup. I have sleep states disabled as well as zen states initialised on boot.

The motherboard is an Asus X370-pro and it is on the most recent bios.

The only docker i am running is Plex server and I have disabled or updated the plugins.

I am able to pass through a GTX1070 to a Win10 VM and everything works as it should.

The problem is that within 24-30 hours or a reboot the system becomes unstable and apps or VMs become partially unusable. When the system partially crashes the unRaid GUI is still accessible except that it shows that the array is offline. I am however able to ssh into the system. I can access the array disks as well as the fuse mounts that I have to google drive and I can access files and folder structure. In this state I cannot play anything from the Plex Server but it can be used to browse content. The Win10 VM generally continues to function even after the unRaid GUI partially crashes. No other VM's or dockers can be started as it sees the array as offline. Although this sometimes flickers back and fourth from online and offline.

I am attaching the diagnostics file from after the most recent crash and manual reboot.

Downloading the diagnostics after parts of the system have crashed gives files with no data. I left the GUI log window open and here are the results that I can see now from the most recent crash

Share this post

Link to post

The csrf errors have been discussed a lot on the forum. Try searching for that, sorting that out and see if it resolves your problem.

I did do some searching on card tokens prior to posting but I couldn't find anything that helpful.

I just did another search and found the following post with this section.

unitialized csrf_token - Thus far the community has never onceseen any report of this being logged. Presumably it is an error generated by unRaid itself during Limetech's debugging period (ie: not plugin related), and should you see this you should post your diagnostics in the release thread for the version of unRaid you are running. EDIT: There is a possibility that if your rootfs is completely full due to misconfiguration of an application that you may see this particular token error.

Share this post

Link to post

I did do some searching on card tokens prior to posting but I couldn't find anything that helpful.

I just did another search and found the following post with this section.

unitialized csrf_token - Thus far the community has never onceseen any report of this being logged. Presumably it is an error generated by unRaid itself during Limetech's debugging period (ie: not plugin related), and should you see this you should post your diagnostics in the release thread for the version of unRaid you are running. EDIT: There is a possibility that if your rootfs is completely full due to misconfiguration of an application that you may see this particular token error. Edited August 20, 2017 by Squid

Should I repost my problem in the current release thread?

Run am there scan of fix common problems and see what it says. Also post diagnostics

Share this post

Link to post

I did do some searching on card tokens prior to posting but I couldn't find anything that helpful.

I just did another search and found the following post with this section.

unitialized csrf_token - Thus far the community has never onceseen any report of this being logged. Presumably it is an error generated by unRaid itself during Limetech's debugging period (ie: not plugin related), and should you see this you should post your diagnostics in the release thread for the version of unRaid you are running. EDIT: There is a possibility that if your rootfs is completely full due to misconfiguration of an application that you may see this particular token error.
Edited August 20, 2017 by Squid

Should I repost my problem in the current release thread?

Run am there scan of fix common problems and see what it says. Also post diagnostics

Fix common problems recommend changing my Plex docker from needo to another version as well as two other Dockers that I don't start anymore. The diagnostics that I get after rebooting should be attached to the original post. Please let me know if I should post them again. Thanks

Share this post

Link to post

The write error occurs when no space is left in the RAM file system. Do you have any docker containers running which may inadvertably write to memory instead of disk (check disk mappings)?

Once no space left, all kinds of unexpected things may happen (including the uninitialized csrf token error).

OK that makes sense. I do have PlexServer setup to use ram for transcoding but I do not use transcoding on this machine or share it with anyone at another location that would require transcoding. The current transcode location is /tmp

I'll change it to a location on the SSD cache drive and see if that makes things work better. I had been watching the RAM usage and although buff/cache usage was high, there always seemed to be enough free or accessible.

Share this post

Link to post

The server has been up for 22 hours and I am getting warnings from Fix Common Problems that Rootfs is getting full (97%). I shutdown the Plex Server docker and my Windows 10 VM and its still sitting at 97%.

Share this post

Link to post

The server has been up for 22 hours and I am getting warnings from Fix Common Problems that Rootfs is getting full (97%). I shutdown the Plex Server docker and my Windows 10 VM and its still sitting at 97%.

Share this post

Link to post

The server has been up for 22 hours and I am getting warnings from Fix Common Problems that Rootfs is getting full (97%). I shutdown the Plex Server docker and my Windows 10 VM and its still sitting at 97%.