Ademar

There is absolutely no need for a template or to install this from "apps", Unraid is perfectly capable to run any docker container. Just go to docker, select "new container", use this repository: ghcr.io/borgbase/vorta-docker Map TCP port 5800 for the web UI, and map some folders.

I'm working on building a new pool with 4x 8TB drives in raidz1. As 2 of the drives are part of my current array, I need to be a bit creative in how I'll move the data over without having to buy any temporary drives. I'm making some changes to my existing array, this will need to stay alive while I build my ZFS pool and transfer the data. It will consist of 5x 4TB drives, one of them will be used as parity. 2 of these 4TB drives is 5 years old, and running perfectly fine. 2 of them are 10 years old, and haven't been used in 18 months. Am i crazy for using 10 year old drives? As long as I don't loose more than 1 drive during this whole process, I will be fine. I'll take some precautions, do preclear with verify, don't store anything precious on them, etc.

If you want to monitor a system with Wazuh, you either need to install the agent, or use the agentless monitoring capability. I really don't anything about that capability.

To make it easy for myself, I set up a dedicated Debian VM where I follow the official "Docker install" procedure. https://support.sandflysecurity.com/support/solutions/articles/72000078453-docker-image-install https://documentation.wazuh.com/current/deployment-options/docker/wazuh-container.html Wazuh AGENT as a docker container sounds like a terrible idea.

@InfInIty I've tried Sandfly, and that is able to scan Unraid over SSH. Some of the checks it's trying to do can't be completed, possibly due to Docker being used. But it does pass a lot of checks, and fail some. I also see there is an agentless mode to Wazuh, I haven't tried that yet.

Known issue https://info.linuxserver.io/issues/2023-11-22-qbittorrent/ To roll back, just press "Edit" on the docker container and add ":4.6.0" to the end of "Repository". https://hub.docker.com/r/linuxserver/qbittorrent/tags

Try opening it in incognito mode. If that works, you need to clear cookies/cache in your browser.

Can't find it under apps, maybe the template isn't being maintained anymore? The docker image is available on the repository ghcr.io/borgbase/vorta-docker

I'm in the habit of creating separate users for every device connecting to SMB on my server, and only giving the permissions that are necessary. I have an old user, "phone" that hasn't been used in over 6 months. After I upgraded 6.12.2 -> 6.12.3 I happened to run the "top" command to see which processes were running. To my surprise this "phone" user is running processes like mysqld, ruby, bundle and supervisord. This username has solely been used to give SMB access to the server, I really don't understand why that user is running any process on the server. Any ideas what's going on?

Why is the version hardcoded to "2021.8.2"?

Yes, I have that problem with multiple containers, not just this one. It comes and goes.

Thanks. "Required Port" 67 could also be named something else to make it clear it is only needed for DHCP?

The "Support Forum" link for this image leads to "https://lime-technology.com/forum/index.php?topic=50453.0", It would be nice to update it to this thread. And why does the container run with "--cap-add=NET_ADMIN"? It seems to work fine without it.

There is vibration on all disks when doing extended SMART test. The clicking sound is only on this disk. And it sounds like it's clicking when writing data, not when reading (in addition to periodically clicking during SMART test, as mentioned).

I put my phone on the disk, and used an app to measure vibrations. When doing "SMART extended self-test" there is actually a vibration spike every 5 seconds or so (same for all disks, so that seems normal), the clicking sound matches those vibration spikes (clicking on some vibrations, not all), so I'm pretty sure I've identified the disk making the sound. I still haven't been able to prove that anything is wrong, so I'm not sure if I should try to return it now, or wait.

For the past two days, a disk has been sporadically making clicking sounds. I typically hear a few clicks, then it can be quiet for a full day. I believe it's a 10 month old Seagate 8TB ST8000VN004 drive (parity). I've run parity sync, done speed tests, SMART test etc. and not found any fault with any of the drives. What should I do next? If a drive is failing I want to document it and get a new on the warranty.

Updated from 6.11.1 to 6.11.2 without issue.

You can add a SOCKS5 proxy under settings in qBittorrent. If you can reach their IP/hostname from your local network (VPN running on your router for example). https://helpdesk.privateinternetaccess.com/kb/articles/do-you-offer-a-socks5-proxy

Correct. (I use a local domain name, set in Pi-hole. So i set something like http://some.name)

I had an issue like this recently. I just needed to set the "APP_URL" container variable. See if your log says anything about an IP address, that's what tipped me off.

For the record, I've had the same issue with the same device on 6.9.2.

It was in /mnt/user/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Plug-in Support/Databases But in my situation I couldn't even load the webui, so it might be a different issue.

I also had a couple of broken containers. I would use WinSCP to go into the folders for those containers in appdata, and see if there are any files that have stricter permissions than other. For example some which are owned by "root" while the others is owned by other users. I don't know why upgrading would break this though.

After upgrading from 6.9.2 to 6.10.0 the official Plex image no longer works. The container is giving the same sqlite error message over and over 16:38:38[s6-init] making user provided files available at /var/run/s6/etc...exited 0. 16:38:38[s6-init] ensuring user provided files have correct perms...exited 0. 16:38:38[fix-attrs.d] applying ownership & permissions fixes... 16:38:38[fix-attrs.d] done. 16:38:38[cont-init.d] executing container initialization scripts... 16:38:38[cont-init.d] 40-plex-first-run: executing... 16:38:38[cont-init.d] 40-plex-first-run: exited 0. 16:38:38[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... 16:38:38[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. 16:38:38[cont-init.d] 50-plex-update: executing... 16:38:38[cont-init.d] 50-plex-update: exited 0. 16:38:38[cont-init.d] done. 16:38:38[services.d] starting services 16:38:38Starting Plex Media Server. 16:38:38[services.d] done. 16:38:39Error: Unable to set up server: sqlite3_statement_backend::loadOne: attempt to write a readonly database (N4soci10soci_errorE) 16:38:39Stopping Plex Media Server. 16:38:39kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] 16:38:44Starting Plex Media Server. 16:38:44Error: Unable to set up server: sqlite3_statement_backend::loadOne: attempt to write a readonly database (N4soci10soci_errorE) 16:38:44Stopping Plex Media Server. 16:38:44kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] 16:38:49[cont-finish.d] executing container finish scripts... 16:38:49[cont-finish.d] done. 16:38:49[s6-finish] waiting for services. 16:38:49[s6-finish] sending all processes the TERM signal. 16:38:52[s6-finish] sending all processes the KILL signal and exiting. 16:39:19Container stopped "plex-first--run" is mentioned, maybe the container mistakenly believes this is the first time running? I do not see anything wrong in the syslog, or wrong file permissions. Have anyone else run into this problem? Edit: working again after giving everyone write access to db file.