Pjrezai

For the past week every couple of days I have been experiencing random crashes recently and am unsure if it's hardware or software causing it. The entire system will crash, stays powered on but can't be accessed via the web GUI + all services go down. Seems to mostly happen while playing content on Plex both direct play and transcoding but it has also happened while doing nothing. I've attached syslog. Any help is appreciated. syslog (1)

Hi guys! I am not doing much right now (except moving some large files), and not running much besides plex and file sharing, and my i9-13900k is jumping onto high loads like this. I don't know why. Hitting some times 90celcius just moving files. Idling at 50-55

Hi, I read through that link and I couldn't find an actual solution. I keeps on losing access to the shares every few hours and so my server is unusable

Hi guys! Just so frustrating, I just fixed another issue that had been plaguing me for a month just for another issue to pop up. I am getting so frustrated with UNRAID. I have attached my Diag below. ANY help would be greatly appreciated!! tower-diagnostics-20230512-0024.zip

Well yea it definitely is a hardware problem because I am running a whole new instance of unraid. Yeah I replaced the RAM with the same make and model. I do have another new-in-box of the same motherboard. The only thing I don't have a spare of is the CPU. I really hope it isn't that because it is the most difficult to deal with, but I assume it would be with my luck. Do you think it is just that the particular make and model of the motherboard and RAM don't play well with Unraid? I doubt it but I have the ASUS PRIME Z-690A and G.Skill Ripjaw DDR5 5200 RAM.

I installed a fresh trial version of unraid on the new hardware and it crashed again. I have done a memtest in the past (via the built-in one on my motherboard; the one on the unraid USB doesn't work - but I even bought new memory just in case). It still crashes. I have attached the syslog. It happened on Aug18. I don't know if there is something in the BIOS that is the issue? The motherboard? The CPU? I'm really lost. ANY help would be very appreciative! syslog test-diagnostics-20230422-1932.zip

Based on the syslog could it be a CPU issue? Maybe something I could change in the BIOS?

Thanks for that option! That would be very convenient. So Just an update, I went and purchased new ram (same make and model) thinking maybe the previous ram was defective and still got a crash. I have attached it below. I am lost for words on why now, but maybe you can see something in the logs! Thanks for all your help guys! syslog-192.168.1.146 (1).log tower-diagnostics-20230412-0217.zip

Ah sorry, thanks! Thought it might be more than one problem. So I basically moved back to my old hardware and it seems like everything is running smoothly so far. I will wait a few days to see, but this could basically point to it being a hardware problem - which is unfortunate because the new hardware is brand new - an i9-13900k and asus prime Z-690a and 32gb ddr5 5200 G.Skill. I did a memtest and didn't come up with any errors but still I feel as though odds are it is the memory since I bought them used (the cpu and motherboard are new)

Hi guys, I have been trying everything the past two weeks to resolve this issue, but every day or two my server completely crashes. I have attached the diag and syslog. ANY help would be greatly appreciated!!! tower-diagnostics-20230407-1649.zip syslog-192.168.1.146-2.log

Nope, doesn't seem to be the c-states. Crashed again in record time (within an hour or so).

Hi! So it completely crashed again without having the torrent client open. So I decided to look into the hardware. Thanks for pointing that out to me. I ran a memtest and didn't get any errors though. Then I read somewhere about c-states. I decided to disable them and run the server again and see if in the next few days it crashes again. Do you think it may be the c-states? Also, I have attached the newest syslog for the newest crash. Hopefully you can see something in there. In they syslog it seems to have occurred around 2:11am this morning, if you can take a look around that time in the syslogs. syslog-192.168.1.146.log

Dang. Would there be a list of possible problems I could look into based on the call traces or your intuition?

I downgraded to librtorrentv1 but still complete failure of unraid (docker, etc.). I cannot even SSH into it to download the diagnostic. I had to hard reboot. All I could pull after theh reboot is the syslog. I am lost for words on what the problem is :( :( syslog-192.168.1.146-2.log

Hi! Did you figure this out? Where did you find the public folder in the first place? I am using the binhex overseerr container and the public folder doesn't exist in the appdata folder. Also where is /app/src/components? Sorry if this is a newbie question