Squid

Delete /config/network.cfg on the flash drive, reboot and reset things back up (this will revert you back to DHCP if you were using a static IP)

Are you sure that safe mode didn't fix it? Those files look suspiciously like what FCP writes to check the hard drives.

Jul 18 21:22:35 Tower sshd[19990]: Connection from 192.168.1.41 port 52386 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:35 Tower sshd[19990]: Received disconnect from 192.168.1.41 port 52386:11: [preauth] Jul 18 21:22:35 Tower sshd[19990]: Disconnected from 192.168.1.41 port 52386 [preauth] Jul 18 21:22:42 Tower sshd[20321]: Connection from 192.168.1.41 port 52441 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:42 Tower sshd[20321]: Invalid user from 192.168.1.41 port 52441 Jul 18 21:22:42 Tower sshd[20321]: Failed none for invalid user from 192.168.1.41 port 52441 ssh2 Jul 18 21:22:42 Tower sshd[20321]: Received disconnect from 192.168.1.41 port 52441:11: [preauth] Jul 18 21:22:42 Tower sshd[20321]: Disconnected from invalid user 192.168.1.41 port 52441 [preauth] Jul 18 21:22:42 Tower sshd[20325]: Connection from 192.168.1.41 port 52442 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:42 Tower sshd[20325]: Invalid user admin from 192.168.1.41 port 52442 Jul 18 21:22:42 Tower sshd[20325]: pam_unix(sshd:auth): check pass; user unknown Jul 18 21:22:42 Tower sshd[20325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 Jul 18 21:22:45 Tower sshd[20325]: Failed password for invalid user admin from 192.168.1.41 port 52442 ssh2 Jul 18 21:22:46 Tower sshd[20325]: Received disconnect from 192.168.1.41 port 52442:11: [preauth] Jul 18 21:22:46 Tower sshd[20325]: Disconnected from invalid user admin 192.168.1.41 port 52442 [preauth] Jul 18 21:22:46 Tower sshd[20567]: Connection from 192.168.1.41 port 52474 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:46 Tower sshd[20567]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 user=root Jul 18 21:22:48 Tower sshd[20567]: Failed password for root from 192.168.1.41 port 52474 ssh2 Jul 18 21:22:48 Tower sshd[20567]: Received disconnect from 192.168.1.41 port 52474:11: [preauth] Jul 18 21:22:48 Tower sshd[20567]: Disconnected from authenticating user root 192.168.1.41 port 52474 [preauth] Jul 18 21:22:48 Tower sshd[20612]: Connection from 192.168.1.41 port 52518 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:48 Tower sshd[20612]: Invalid user user from 192.168.1.41 port 52518 Jul 18 21:22:48 Tower sshd[20612]: pam_unix(sshd:auth): check pass; user unknown Jul 18 21:22:48 Tower sshd[20612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 Jul 18 21:22:51 Tower sshd[20612]: Failed password for invalid user user from 192.168.1.41 port 52518 ssh2 Jul 18 21:22:51 Tower sshd[20612]: Received disconnect from 192.168.1.41 port 52518:11: [preauth] Jul 18 21:22:51 Tower sshd[20612]: Disconnected from invalid user user 192.168.1.41 port 52518 [preauth] Jul 18 21:22:51 Tower sshd[20838]: Connection from 192.168.1.41 port 52567 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:51 Tower sshd[20838]: Invalid user admin from 192.168.1.41 port 52567 Jul 18 21:22:51 Tower sshd[20838]: Failed none for invalid user admin from 192.168.1.41 port 52567 ssh2 Jul 18 21:22:51 Tower sshd[20838]: Received disconnect from 192.168.1.41 port 52567:11: [preauth] Jul 18 21:22:51 Tower sshd[20838]: Disconnected from invalid user admin 192.168.1.41 port 52567 [preauth] Jul 18 21:22:51 Tower sshd[20843]: Connection from 192.168.1.41 port 52570 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:51 Tower sshd[20843]: Invalid user sysadm from 192.168.1.41 port 52570 Was this you? All from 192.168.1.41 What is that on your network?

Today's release adds in the translations for all of the search terms. When the GUI is running in a non English language, the autocomplete works against either English or the language you're in.

Turn off PHP errors in Tools - PHP Settings (CA is not designed around having them turned on and if anything ever happens, then it will effectively crash. But, FWIW that is already fixed for next release (was also pointed out to me by the resident PHP cop this morning)

You should post your diagnostics

Dismissing the banner is handled by a cookie. After dismissing it shouldn't appear again for IIRC 30 days. If when closing your browser it automatically clears cookies then you will see what you are seeing. You can also have the OS not check for OS updates in Settings - Notification Settings

There is no other server software that is comparable to Unraid

Probably best to post in the applicable support thread

Works for me no problem. I'd suggest closing all browser tabs open to the server. But, after a couple of minutes even sitting on that Scanning popup, the scan would still continue in the background and the next time you load up FCP it should be populated.

Jul 28 04:05:30 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1938859, gen 0 Quite possibly the root of your problems "Corrupt" is usually caused by bad memory. Run a couple of passes of Memtest from the boot menu. (If you boot via UEFI, then either switch temporarily to legacy boot or download onto a new flash drive from https://www.memtest86.com/ After handling the memory issues then other users can help you in recovering from the corruption present

Docker Folders has now been deprecated when running Unraid 6.12.3+ It should be uninstalled and replaced with Folder.View

And also hopefully publish to Apps so we can finally get rid of the original, and the barely functional fork

No idea. /tv doesn't show up in System in Sonarr?

First thing to look at would be the connections. SATA isn't particularly known as a robust connector and in many cases the non-locking variety actually work better than the locking ones. Reseat all cabling (sata & power) at both ends. Don't try any cable management (random cabling is better for EFI than nice neat wires) and also minimize (or better yet don't use) any power splitters at all.

Does the docker run command list an error?

reboot will fix it. Alternatively, rm /tmp/plugins/pluginPending/* This should never be an issue though on 6.12

Have you paid for a key, or is this a new trial. If the latter, then your flash drive is not returning a unique GUID and cannot be used. If you contact support with a copy & paste (no screenshots) of what shows within Tools - Registration they can tell you whats going on.

It's not capped, but rather a trade-off of how the system works. With Unraid set to use Read/Modify/Write in Disk Settings, write speeds take a hit but your power savings are better as only the drive involved in the write and parity drive are involved. With Reconstruct Write enabled, there is no degradation in speed at the expense that every drive in the array has to spin up to write anything to any drive. Cache Pools and Use Pool settings for the share are the usual method for combining the best of both worlds. The best user for advice on this and any tips / tweaks is currently on vacation.

I think that you're missing my point. LibreNMS' primary support venue is via themselves. They are the ones who actually are maintaining the container. The template is simply a way to install it, and I don't see any particular reason to remove it etc. Clicking the Project link takes you their website, and full documentation regarding installation, what the environment variables do etc are there via the link they have to https://www.librenms.org/#downloads If (as an example), the Apps tab only contained applications that are directly supported by whomever has created the template (ie: they created the template and the application within the container itself), the selection would be nothing but Plex (from PlexInc themselves) and plugins. Nothing else. If there is an issue where the container / app itself is abandoned / permanently broken, that is a different story and things would get removed. But there is no real issue with the template in these cases. While I would absolutely love for Apps to be the exact same as Google Play, where its a one click install with nothing else needed to be done by the end user, that is an unrealistic dream. Unraid is far better (far far better) than on competing platforms where you are forced to go and come up with the actual docker commands needed to execute things. The one thing where Unraid / containers is at a disadvantage on the base system is multi-container installations. This is where docker compose shines. However, I never stop pressuring the powers that be that we need to incorporate this to make this systems easier to use on the end-user but in an Unraid friendly way where we do not force the users to manually edit the .yaml files to install something suitable for their own environment.

Didn't know T&T did that. I always thought it was the Dynamix Stop Shell plugin...

FWIW, as a parity drive there would have been no file system / files / anything on it at all. Parity is simply a collection of bits used to reconstruct other drives in conjunction with the remaining drives. There is no filesystem associated with it. Adding it directly to the array would have had the OS automatically "clear" it in the background (if a parity disk was present) and then offer up to format it as XFS etc or as you noticed Preclear also does the "clearing" job.

The USB creator has always had some issues on certain systems with various drives. There are some workarounds online. However, the manual method 99.9% of the time works with every drive so long as its 32G or less. https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#manual-method Realistically, the manual method takes pretty much about 1 minute to accomplish and the only real advantage of the USB creator program is that you don't need to right click and select "Run As Administrator"

This might help In my particular case though, I found it far easier to remotely access a barebones VM via WG (or Connect) and then connect to the containers.

To restore your backup, you'd simply copy it onto the flash drive. But, it's not really clear. Is your backup via Connect or have you manually created one (by copying the contents of the flash drive somewhere else)