WizADSL

Have you tried a different power supply? I had an issue like this (although in my case the system freeze was every few days IIRC). Same as you capturing the syslog didn't help because the server would just silently freeze. I don't recall if I had the same symptom where holding down the power button didn't work.

To add to what @JorgeB said, I've also had unexpected reboots when my power supply was dying and I've also had it happen because the battery in my UPS needed to be replaced.

I'm aware of that. My current UPS uses that cable and it is carrying a USB signal. However, the documentation for the UPS mentioned here clearly states it's a serial interface with a separate port for USB. If the UPS doesn't match that Port layout then that's another story. But the documentation is very clear.

If this is accurate to what the back of your unit looks like: then @Vr2Io is right and what you want is the USB port, hopefully the cable is included because they are doing a VERY non-standard thing by putting a USB-A plug at both ends. The RJ45 connector is clearly labeled as serial so you don't want to use that (if, as you describe the cable is RJ45 at one end and USB on the other, it most likely contains a serial-to-USB converter and is not what you want to use).

If it helps at all, this is what my settings page looks like: Yours should look very similar, would you mind posting a screenshot?

Do you mean that the settings in unraid, after you save them, aren't overwriting the previous settings? Also, you're using a USB cable I assume, if the new UPS came with one use that one rather the the old one (it shouldn't matter but I've had issues with cables)

Not sure I understand your issue, but I'm going to assume you are connecting the USB cable like you had before with the 1000 and it's not reading anything from the UPS? If that is the case, go into the menu on the APC UPS and go to the configuration menu, there you will find an option called "Menu Type", if that is set to "Standard", change it to "Advanced". Now you will have additional options in the configuration menu. One of the new options on the configuration menu will be an item to enable ModBus, this is a protocol that is used over the USB connection from the UPS. Once that is enabled, in UnRaid, go to the UPS settings and set the "UPS cable" to "USB" and the "UPS type" to "ModBus". See if that helps. You may notice that among other things, once the menu is set to advanced you can also modify the voltages that the UPS will switch at, in case you need it.

On the parity topic, I personally run dual parity (I added a second parity drive as soon as the feature was available). I like that if I have a drive failure, the extra parity protects my data while I replace the failed disk. All if the data on my array is also "replaceable", but my time has value and if paying for an extra drive keeps me from having to spend the time to rebuild everything, then it's very cheap insurance. If you lose data (especially 10s of terrabytes), just figuring out what you lost can be a tall order. A few hundred bucks for an extra drive will seem very cheap at that point. Speaking of failure, another array feature that I don't think was mentioned is that because unraid uses dedicated parity and the individual drives just contain standard filesystems, if you lose a data drive (and don't have parity to rebuild it) then you lose ONLY what was on that one drive since the data isn't stripped. On a conventional stripped array you would lose everything.

Version 7.1.2 (and maybe 7.1.0+, I didn't install those and I upgraded directly to 7.1.2) of UnRaid add the "nchan_max_reserved_memory" directive the the nginx configuration file. If (like me) you were adding that in the go file for previous versions, nginx will not start after the update to 7.1.2 and you will not be able to get to the web interface. If this happens to you it's because the "nchan_max_reserved_memory" is in the nginx config file twice and that will cause nginx to not start.

There have been a few requests for the ability to disable the Docker update check (Jan 25, 2025, Oct 6, 2024, Oct 15, 2024). I'm also interested in being able to disable this. Maybe a broader feature request would be for the ability to see a list of all of the checks that are available in Fix Common Problems with the ability to disable/ignore them. This would be especially useful because the way it works now, you have to wait for a problem to occur before you can ignore it. Also, it SEEMS that the ignore mechanism uses the exact wording of the notification which for something like Docker updates would be a real game of Whack-a-Mole as the message would vary depending on the name of the container.

I would hold off on adding any more RAM for now. As you may know RAM isn't just consumed by processes that need it, but is also used for caching (which will be released when needed), from the OS's point of view, "unused RAM is useless RAM" it's just a matter of how it's allocated. Here is a graph from my 64 GB system: As you can see about 40 of 64 GB of the RAM is in use but the vast majority is cache. If you want to see a graph like this on your system, install the "Dynamix System Statistics" plugin.

@Jazer, you may want to post the URL you have open and what browser and version you are using. Also, whether that's the only tab you have open that's pointed at your unraid server.

This is probably not the issue but do you have your server connected to a UPS? If so can you verify that the UPS is working and able to keep the connected load powered if the utility power fails?

There is a "Legacy License" section in the FAQ on the unraid.net site where the upgrade pricing for legacy licenses is spelled out. Upgrading a legacy license to another legacy license does not sound like it affects upgrade rights.

There is the unlikely possibility that a plugin in your browser could be interfering. Could you try to make a trivial change from the browser on your phone and see if that works?