emilgil

According to the wiki the RefreshRate is in seconds and 20 s is the default value? If I omit it, I get a 30 s refresh rate. 😕 Edit: even if I set the RefreshRate variable to 20 or 20000, I get a 30 s poll time.

NVM, found it in the wiki. ENV it is. https://github.com/ElectricBrainUK/UnraidAPI/wiki/Docker-installation

As an environment variable when launching the container or in the GUI?

Is there no way to slow down the polling frequency of the disks? Every 30 s is way too fast for me, my server rarely changes over a day or two. Also, is there really no way to prevent unneccessary entities from the MQTT queue? I have 4 disks + a cache drive but the API seems to think I have 23 or so...

Ok, new attempt. I ran a new session of Memtest with all four RAM sticks in place and had a truckload of errors. I then removed the smaller pair of RAM and restarted Memtest. This time it passed the test so I'll let it sit idle for a few days now before I re-enable Docker and my VMs.

Still no cigar. Sometimes it works for a couple of hours, other times just a few minutes. Sometimes Docker is activated, sometimes not. Sometimes it crashes when I start the array, sometimes not. I'm going crazy over this!

I ran 4 passes of Memtest86 yesterday without errors. I guess I just have to reinstall Unraid again and let it sit for a week or two without installing any addons or Dockers.

I just replaced all the bz* files from the original zip file and it only took a few minutes for my server to panic, I didn't even try to start the array.

Ok, that changes things a bit. I just don't understand why my server crashes more frequently now than a few days ago. After reinstalling a few weeks ago it crashed after a week or so, then when I began installing my docker containers it became more and more common. The last week it has crashed daily or more. Last night it wouldn't even start the array without panicking. I have ordered a new USB memory stick and once it arrives I'll run Memtest from it for a week or so.

My server crashed again as I was writing m previous post and after a reboot it crashes immediately when I try to start the array. I'm guessing that some file(s) have been corrupted by all these crashes.

Thanks, I'll give it a try.

Not really. This is from the last crash (earlier today): Then it seems something happened while I was trying to log in:

Another panic tonight. C-states are disabled, PSIC set to Typical Current Idle, RAM speed 2666 MHz.

Right, so even before these last two panics I had memory speed locked to 2400 MHz and power supply control set to Typical Idle. As far as I can remember, C-states were disabled but I'll double check.

Ok, so I had two more panics a few days ago. I didn't manage to catch any details on the first one but after that I enabled the syslog server. Unfortunately it doesn't give much information. I have attached a screenshot of the second panic as well as a diagnostics dump taken between the two panics. tower-diagnostics-20220531-2041.zip

I might have missed something here but whenever I use the Compose Pull-button, updated images for that stack is downloaded as expected. I then press Compose Up and all affected containers are restarted. However, the Update Ready flag is not removed from the running containers and I'm left with a number of dangling containers. Is this normal or am I doing something wrong? It doesn't matter if I shut the containers off (Compose Down) before pulling updates, I get the same behavior. Currently running Unraid 6.10.1 with Compose manager plugin 2022-05-27.

Yeah, I realized that there was a separate key file for the paid license. I've managed to start the array, time to run a parity check before I move on restoring other settings and disks.

Alright, after messing about with BIOS settings I finally managed to boot into Unraid. Super.dat seems to be working so let's see if we can spin up the drives now.

Ok, so no luck today. Tried removing all my USB devices but ended up in kernel panic anyway. Tried removing all my HDDs too but ended up in kernel panic. There are still two m.2 SSDs connected but only because they're such a pain to remove. I can't even add the key file to the USB memory without it panicking. I can't help thinking about HW issues, could my USB memory be corrupt even if I can write the Unraid image to it? A new one is only €12 so I might give that a try. Or should I ditch my AMD gear and spend another €300 on an Intel CPU and motherboard?

Alright, I did what you suggested and installed 6.10 stable on my USB. It booted fine the first time but once I copy my config folder on to the USB, it throws a series of error messages in quick succession before panicking again. It's far too fast for me to register any details, even if I knew what to look for. I'll try removing all USB devices and then all disks to see if it helps.

I wish I could, I can't even boot into safe mode...

I've had quite a few problems with my install of Unraid 6.9 and 6.10 RC1-4 but lately it has been running quite smoothly. Until yesterday morning that is, when I realized my server had crashed again. Kernel panic at approx 5 AM, what a lovely way to start the day. I restarted the server and waited to see it come back up but no, there was a new kernel panic during boot (even during Safe boot). Can somebody please help me sort this out? I can't really make anything out of the information from the first KP, the second one seems to stem from udev and some kind of disk failure (?) during boot? Needless to say, I can't access the server now. AMD Ryzen 3600X, Asus ROG Strix B450-F Gaming (BIOS updated in February 2022), 48 GB RAM and a LSI 9240-8i HBA in IT mode. I've had my fair share of panics due to power management issues but it has been running for a month or so now. Can anyone please shed some light on this?