harris

Okay good to know. Would this issue be better with a newer generation Ryzen CPU or an Intel one? I'm thinking of swapping out this CPU to use for something else anyway so if it would be better on a different CPU then I could do that. I worry with this one because I know I've had issues in the past that caused major downtime, and I'm a bit uncomfortable with playing with setting and risking it (particularly since the issue is intermittent, so I won't know if I've broken something until I'm potentially away from home or something and can't be there to rip the plug)

I'm running Unraid on a Ryzen 3900X. A while back I was having all kinds of issues with the OS locking up randomly and requiring me to fully unplug the machine to reboot it. After some research, I found threads like this and this that suggested it was due to bugs in the linux kernel with Ryzen and power-management and C-states. I followed some guides and disabled all of that stuff in my BIOS, and it worked! No more lockups! However, now my CPU is running at 80W idle which is... not good. Power is super expensive where I live and I want to get this down. All of my sleep state troubles were a while back and since then Unraid (and the Linux Kernel) has had multiple updates. So my question is: Is the original issue with Ryzen sleep states still a thing? Have others had success reverting back to more efficient power management in newer versions of Unraid?

I can't seem to get this running, as it seems to not like that I have a password for redis. I get this error: [Nest] 282 - 08/21/2023, 11:49:34 AM ERROR [RedisCacheService] ReplyError: WRONGPASS invalid username-password pair or user is disabled. [Nest] 282 - 08/21/2023, 11:49:34 AM ERROR [RedisCacheService] ReplyError: Ready check failed: NOAUTH Authentication required. [Nest] 282 - 08/21/2023, 11:49:34 AM ERROR [RedisCacheService] ReplyError: WRONGPASS invalid username-password pair or user is disabled. [Nest] 282 - 08/21/2023, 11:49:34 AM ERROR [RedisCacheService] ReplyError: Ready check failed: NOAUTH Authentication required. /ghostfolio/apps/api/node_modules/redis-parser/lib/parser.js:179 return new ReplyError(string) ^ ReplyError: NOAUTH Authentication required. at parseError (/ghostfolio/apps/api/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/ghostfolio/apps/api/node_modules/redis-parser/lib/parser.js:302:14) { command: { name: 'client', args: [ 'setname', 'bull:REFUQV9HQVRIRVJJTkdfUVVFVUU=' ] } } Node.js v18.17.1 error Command failed with exit code 1. I use this same redis instance for another container (with the same config) and it works fine, so something is happening with ghostfolio. Anyone else have this issue?

I went into the bios and followed the instructions to disable C-States. Seems like that worked as things have been stable so far. I'm going to mark this as resolved, but if it restarts then I'll come back here. Thanks again!

Thanks, that looks promising. I thought maybe sleep states would be involved! I'll have to borrow a friends GPU to get into the bios because my spare kicked the bucket, but I'll do that and report back the results. Thanks for the help!

I recently updated my unraid server to 6.11.5 and found that it started going unresponsive. Every few days it would just go dark, to the point where I can't even ping the server. The lights and fans are still going, though. I've been trying to figure out what is going on but I haven't been able to pinpoint any patterns to when it fails, and nothing in the logs stands out to me. I've attached my syslog file which should have a couple of crashes in it at this point. The most recent one I discovered today (Jun 21) and rebooted, although it probably went unresponsive before then. I've also included diagnostics in case that helps. I'm desperate here as this happens every couple of days now and the downtime is really becoming an issue. If there is any other info I can provide please let me know and I'd be happy to provide it. syslog shoebox-diagnostics-20230621-0859.zip