Rysz

No special reason, it's just what I use personally and I wanted to show how to set something different than the default. 😉 But you're right, of course, 5% should be just fine for the random bit flip that people will want to guard against ("bit rot")...

This is baked into Unraid NUT, so you'd just chose the appropriate apc_modbus driver: https://networkupstools.org/docs/man/apc_modbus.html

There's a screenshot of you spamming another user via DM, so you should change all your passwords as it seems your account was compromised?

You can activate scrolling here: Any other scrolling, in terms of arrow keys or page up/down, is dependent on the program being executed.

It's not an issue if you orchestrate startup/stop correctly using the provided hook scripts. In general you'd want the mergerFS mounts to mount at array start and unmount at array stop. Intermittent failures I've not seen, it seems to work extremely reliably for most people from what I've heard.

That's your browser closing the connection (going away), so either the browser or connection drop-outs.

The idea is quite the opposite actually, it's for files which do not change often and just sit there. Think your family photos, recordings of your super rare favourite TV series, anything irreplaceable. These are the files where you won't notice corruption until you open them again in one or two years. The program checks these files continuously so you can rest at ease that they are still in tip top shape. Files which you regularly update or interact with, you'll likely notice problems, and for those ZFS is better. Recursive mode is added in the latest update, the quick guide and documentation have been updated with how to use it.

I'm not an expert on the "File Integrity" plugin, but from what I know it only does checksumming. This means it calculates checksums for all your data, and you can see if something changed (but not repair). On the other hand, par2cron doesn't protect all your data, but lets you create protection sets for important data. Those sets it verifies the integrity, so you can see if something changed, and lets you repair in case of corruption (unless severe).

Recursive creation will be possible within the next 1-2 updates, I'm currently working on this (as well as some other features).

You can try taking out one stick, and then test each stick separately, see if that changes anything.

Since you're having such problems, I wouldn't completely rule out the memory being the issue after all. I'm not sure how the tests of Memtest86+ and LMT differ under the hood, it's possible they test different paths. I haven't seen any false positives from LMT yet... so I'd not rule RAM out until you really find another "smoking gun".

par2cron for UNRAID https://github.com/desertwitch/par2cron https://github.com/desertwitch/par2cron-unRAID PAR2 Integrity & Self-Repair Engine Selective automated protection for directory trees par2cron is a tool that wraps par2cmdline (a parity-based file recovery tool) to achieve automated periodic integrity creation, verification and repair within any given directory tree. It is designed for use with non-changing WORM-type of files, perfect for adding a degree of protection to media libraries or backups. The driving idea is that you do not need to invest in a filesystem (like ZFS) that protects all your data, at the disadvantage of additional complexities, when you really only care that important subsets of your data remain protected. The array is scanned for marker files, and a PAR2 set created for every directory containing such a _par2cron file. For verification, the program loads the PAR2 sets and verifies that the data which they are protecting is healthy, otherwise flagging the PAR2 set for repair. Once repair runs, corrupted or missing files are recovered. Many command-line tunables, as well as configuration directives, are offered for more granular adjustment of how to create, when to verify and in what situation to repair. It being set up, you can simply protect any valuable folder by just placing a _par2cron file in it; the tool will create a PAR2 set and pick it up into the periodic verification and repair cycle - now protected from corruption/bitrot (with e.g. 15% redundancy, consuming less disk space than a full-redundancy solution). Installable via Community Applications

Run memtest86 for at least 3 full passes, if nothing comes up I'd treat it as false positive unless you're having problems.

Yes, you can use PeaNUT - also you should set "Enable Manual Configuration" to "for UPS Driver", so you can set other settings still.

The configuration part is still needed, but you don't need to change the backend anymore.

Sorry I didn't mean to come across as abrasive, any removals are eventually up to the CA maintainer @Squid too. I can see where you're coming from, and I know (being a developer myself) that supporting things can take a toll time/motivation-wise. And, thinking about it some more, I agree that "official" may be a bit misguiding in this light, although I'm unsure of a better wording... Of course you can petition the CA maintainer to remove the software, but I think it will just pop up somewhere else instead. Maybe it's best to put a few lines in your GitHub/Discord instead, that you only support the installation methods you've provided. Thanks for developing this piece of software, FOSS development is unforgiving and brutal at times, especially on the support side. P.S. As for harm, I don't think a template can really do much, if it pointed to another malicious container it'd loose the "official" tag. Anything else should be immediately obvious to the installing user, who always is presented the permissions/fields before install. Even the container it uses is made visible to the user before install, so a user consciously has to make the decision to install that.

It's just a template that points to the Docker container you listed on your GitHub, hence showing as "official". It's a marker that it's using the Docker container provided by the official repository of the software. I don't know what this being available on Unraid changes for you. You released that Docker container into the wild and your software under GPL, specifically chose that permissive license. Asking for it to be removed from specific places now is like trying to stop wind with a paper bag - are you going to do this for every single place that distributes your software? This is just my opinion and, for what it's worth, I have nothing to do with CA, but releasing free software and then asking for such removals seems backwards to me - especially when the template is in fact pointing to the very container you released (the "official" one). I'd be happy for the publicity and that people are willing to re-publish and support the software you've written, the template is not much more than a link and that should be well within their rights under the license you chose. Rather than removing the template entirely, maybe tell the template maintainer how to fix it up... changing a path can't be that hard, be glad it uses your Docker container. It's not like they made a new container (which would've been well within their rights under the license you chose). Just tell people on your Discord that you're not supporting it, if if bothers you that much, but I don't see the issue for Unraid.

Yes, check out the autonuke non-interactive invocations - see nwipe -h for details. Using that your invocation with the && followed by the notification agent should work. 😉

I‘m afraid there‘s no such video, but all documentation can be found here: GitHubGitHub - desertwitch/mirrorshuttle: MirrorShuttle helps o...MirrorShuttle helps organize and move files into read-only network shares - without ever granting write access. Ideal for media servers; adios, ransomware. - desertwitch/mirrorshuttle

This looks like a memory (RAM) issue, I'd run a memory test.

Usually you'd just open a command line and run python3 my_script.py The autostart script is just for stuff that needs to be installed on system boot, most users won't need this.

Please try to set it up exactly as in the screenshot (except for IPs): https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/page/82/#findComment-1589967 You need to disable "login credential" as both screenshots show, this is likely the issue here. Then for the username and password in Unraid NUT just use "slaveuser" and "12345" or something (some bogus values, but not same as UPS name).

Post a screenshot of the UniFi UPS Settings (in UniFi web interface) and the NUT debug package (can be found in NUT Settings in Unraid web interface).

Aufzeichnung 2025-12-14 101633.mp4

It already does that, if you select text it should copy it to the clipboard on releasing the mouse button.