March 19, 20179 yr First time I have ever seen this, so just asking for some help because I got no idea... Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums hades-diagnostics-20170319-0918.zip would this type of error occur because of the issue with Disk 1 I see in the log? Edited March 19, 20179 yr by wickedathletes
March 20, 20179 yr Author not sure if related but this is in my logs now: error: webGui/include/ProcessStatus.php: wrong csrf_token `
March 21, 20179 yr 10 hours ago, wickedathletes said: not sure if related but this is in my logs now: error: webGui/include/ProcessStatus.php: wrong csrf_token ` Not related....
March 21, 20179 yr Author 12 hours ago, Squid said: Not related.... ya i saw that note but it appeared when I tried to spin up a drive to run a smart scan, so maybe a bug in the unraid UI itself?
March 21, 20179 yr 3 minutes ago, wickedathletes said: ya i saw that note but it appeared when I tried to spin up a drive to run a smart scan, so maybe a bug in the unraid UI itself? Same principal applies. If the browser / device you tried to spin up the drive was stale (existed before a reboot of the server, and hadn't navigated around any pages), then the wrong csrf value would be used -> hence the error. All wrong_csrf errors generated by a browser can be fixed by simply hitting another tab in unRaid's UI (or refreshing the page). Wrong csrf's generated by some mobile app (controlR et al) may need a restart of the app. Edited March 21, 20179 yr by Squid
Archived
This topic is now archived and is closed to further replies.