TallMan206

How do I reauth? It gives me this error: ERROR: You will need to issue a --reauth and re-authorise this client to obtain a fresh auth token.

But it reads from the zfs array, it write to the backupserver zfs pool, so that should, in this case, not count, right?

Hi, I have 2 Unraid servers. A mainserver, and a backupserver. They are connected with 10G. Mainserver: 1x 20TB HDD with the Movieshare and 4 other shares, 1x 20TB parity drive. All shares are ZFS Datasets. Backupserver: 2 ZFS RAIDZ1 pools, existing of 3x8TB SAS with 500GB SSD as cache and a pool of 4x4TB with 500GB cache. I am running a backup from different shares of this drive and the drive max out on 150MB/s, but as soon as it reaches the Movies share, and it copies some data, the speed goes down to around 15 to 25 MB/s. What could cause something like this? I saw this behavior with luckybackup, but also with Duplicacy. I first thought Duplicacy was the issue, because it makes chunks, and does compression. The Movies dataset is around 8.4TB. Thanks. unraid-diagnostics-20241113-1621.zip

Hi, I made 2 pools of ZFS in my backup server, running UnRAID 7 beta 4. I don't have the option to divide a share over multiple pools, as you have in an Array, to expand the share over another drive, if the first drive is getting full. Is there an option to do this with Pools? (CLI for example) I can select another pool, but that means that it is going to move from Pool-one to Pool-Two. I don't want that, I just need extra space in case the Pool-One gets full, that the Movies start filling up the other Pool (Pool-Two)

For me the Backup Button disappeared after deleting old backups.

Hi, My colors for the drives don't apply. I want to change the 2 lowest drives to another color. I select: Save, and the color is back to the orange one. It does not apply. What could cause this issue?

The S3 sleep plugin keeps shutting down my server backup while there is a backup running and the parity drive is active. What am I doing wrong? Settings:

No problem. I appreciate your help very much.

Yeah, I even removed the docker image already and restarted. All other dockers install fine except this one.

I changed it, but still the error: 6832a27680156c4dc412edc80c7c98278c14cf17bd959ab78d578f8d0ee8e4a3 docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/var/lib/docker/containers/6832a27680156c4dc412edc80c7c98278c14cf17bd959ab78d578f8d0ee8e4a3/resolv.conf" to rootfs at "/etc/resolv.conf": open /var/lib/docker/btrfs/subvolumes/c24ae8e7d723af04d2793928a65f9dde956713a9aab8de3e30807b1b64e1ed58/etc/resolv.conf: read-only file system: unknown.

Hi, When I install LMS on my UnRAID server I get an error. docker run -d --name='lms' --net='bridge' --pids-limit 2048 -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="UnRAID" -e HOST_CONTAINERNAME="lms" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5082]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/JPDVM2014/icons/main/lms.webp' -p '5082:5082/tcp' -v '/mnt/user/Music Complete/':'/music complete':'ro' -v '/mnt/ssd-pool/appdata/lms':'/var/lms':'rw' -v '/mnt/ssd-pool/appdata/lms/config/':'/etc/':'ro' --user 99:100 'epoupon/lms:latest' e13fcb56eefc8dccfb0a94554d27f4230f0ff41c326b66e48d12228bb1247aa1 docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/var/lib/docker/containers/e13fcb56eefc8dccfb0a94554d27f4230f0ff41c326b66e48d12228bb1247aa1/resolv.conf" to rootfs at "/etc/resolv.conf": open /var/lib/docker/btrfs/subvolumes/dcabebd7c50e5abbcccdc95ec42909f60533cd142f8332c8e9dded14230500c6/etc/resolv.conf: read-only file system: unknown. The command failed. What is the cause of this, and how to resolve?

Solved by renaming the docker again and restart the server (don't know why the reboot was necessary)

Hi, I'm on UnRAID 7.0.0 beta 3, and my user scripts don't work anymore. The script runs, logs says that the script ran well, but I don't see any changes in on the Spotweb site. I also had problems with other scripts, but I want to focus on Spotweb now. My scripts, which worked before: #!/bin/bash docker exec spotweb su -l www-data -s /usr/bin/php /var/www/spotweb/retrieve.php >/dev/null 2>&1 Script Finished Oct 15, 2024 15:45.02 (runs every 15 minutes) Full logs for this script are available at /tmp/user.scripts/tmpScripts/spotnet_retrieve/log.txt And here you see it's older than 15 minutes. Logs are attached. What could cause my scripts not to work anymore? I did rename the spotweb container a while ago, to Spotweb. I like to have everyting starting with a capital letter (OCD), could that cause something like this? Thanks for the help. unraid-diagnostics-20241015-1600.zip

How can the server shutdown while doing a parity check? (S3 Sleep plugin)

For now I solved it to run the shares to cache first, 2nd pool the ssd-pool, but I like to find a way to directly put it on the ssdpool without symlinks

Exclusive shares are on.

Hi, Some of my 'shares' are symlinks, and this gives problems when trying to access them from for example Krusader. Now I installed a Windows 11 VM, with spaceinvaderone's video with the VirtIO-FS service to access the Unraid server from explorer in WIn 11 to process 3D blurays with BD3D2MK3D, but i cannot reach the files on the downloads share. Situation: The accessable shares are on the array, but the symlink shares are all on my ssd-pool, which is a separate pool of ssd's to hold my appdata and downloads. How come those are symlinks, while the shares are created from the share menu in Unraid, and i just selected the ssdpool instead of the array? Also, the shares on the ssd pool say: exclusive access. I cannot change that. The shares on the array do NOT say that. What is the reason for this symlinks?

The logs says it's working, I can see the files on my backupserver, and everything is working fine. Thanks for all the help. The issue: My backupserver starts up on Tuesdays at 23:50. The LB cron is suppose to run at 00:00. This is already Wednesday ofcourse, not Tuesday. I had it on Tuesday. Stupid, stupid, stupid. My mistake. I'm happy it has been resolved. Thanks all for the help, especially @ich777

I was too early. It does not work yet. The cron does not run at the set time. I tried with a single folder backup, but it does not run. It is on console mode. When I type DATE in the docker terminal: Wed 18 Sep 2024 03:14:09 PM CEST When I setup the cron: Could it be that I should enter 03:20? Or is that automatically AM then?

It works now. Logs show also that it runs.

Yes, console mode is on. The script should have ran last night, but the log shows the last run was the 12th of september (manual run). Today I tested the cron with the day on Wednesday, and setting a time for 5 minutes later then the current time. Waiting for the script to start, but nothing happens. Privileged mode removed! Here a manual run:

Hi I just privileged mode to find that rsa-key within the luckybackup container, which was not visible before that. The jobs work perfectly manually, and the I tested a lot with the cron to see if they start, but it does not. The time seems to be good inside the docker.

Hi, Cron from luckybackup does not work. Timezone is Europe Paris, which matches with Lloret de Mar where I live. The docker runs with privileged mode. I checked the docker that it is also on the right timezone. Date also gives the right info. Do you have any suggestions?

Solved with the script from JorgeB! Thanks!!

Hi, I've removed that script. I am on Unraid 7 beta2. But the problem already existed on 6.12.13. Anyway, it seems to keep working now, even after some reboots (to try) my issue has been resolved. Thanks for the help