bclinton

You are correct. I copied my changes below that instead of replacing it. All is fine now, thanks!

FYI - I just upgrade from 1.4 which was fine and am now getting the error that enabler reported and the script aborts. Script Starting Nov 01, 2022 17:57.30 Full logs for this script are available at /tmp/user.scripts/tmpScripts/backup/log.txt # ##################################### created directory /dst/link_dest >f+++++++++ empty.file --link-dest arg does not exist: /dst/link_dest removed '/tmp/_tmp_user.scripts_tmpScripts_backup_script/empty.file' Error: Your destination /dst does not support hardlinks! Script Finished Nov 01, 2022 17:57.33 Full logs for this script are available at /tmp/user.scripts/tmpScripts/backup/log.txt

Hi friends. Trying to get grafana running on unraid 6.11.1 by following the instructions at Unraid | Unraid Data Monitoring with Prometheus and Grafana. I am stuck at step 10. Grafana container starts but when I try to launch the webui I get this error This page isn’t working right now 192.168.1.24 redirected you too many times. To fix this issue, try clearing your cookies. ERR_TOO_MANY_REDIRECTS The log repeats this.... logger=context userId=0 orgId=0 uname= t=2022-10-20T18:37:34.404787385-05:00 level=info msg="Request Completed" method=GET path=/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/192.168.1.24/login status=302 remote_addr=192.168.1.118 time_ms=0 duration=407.592µs size=783 referer= handler=notfound logger=cleanup t=2022-10-20T18:41:45.061524809-05:00 level=info msg="Completed cleanup jobs" duration=7.659615ms Just looking for a suggestion. Thanks.

I considered that but I wanted to see if I could reduce the power used by the server. I started with 16 TB data and 1 8TB parity but realized that I would be at least a couple of years from needing more that 8 TB of data. After I removed the 8TB drive my power usage went down almost 20 watts at idle.

Hi friends! I have been using unraid for about 18 months now. I have 2 8 TB drives with 1 being parity along with 2 1tb cache SSD's. It's been humming right along. I am up to about 5 TB on the data drive. With the prices of big drives coming down I am going to be swapping my 8TB parity and data drive soon. What would be the suggested process in doing this? I was thinking I should swap the parity drive first, let it rebuild with a new 12 TB drive. Once all is good, swap the data drive with the new 12 TB drive. Would that be the best way to accomplish this? At the rate I add data I figure this would be good for at least 3-4 years for me.

Do you terminate the docker containers before backing up the folders?

Yep....but mine are only about 5 gigs and I have room to spare on my backup drive.

The way I backup the appdata folder is using the backup/restore appdata plugin and store it in a backup share along with the plex backup and various other backup files. I then backup the backup share instead of the appdata folder with the rsync script.

The way I handle my appdata folder along with plex is back it up to a backup share with appdata backup folders once a week. I do this with other folders that are not really live backup friendly.....that way the script backups a nice clean tar file.

That worked! Thanks.

Greetings. I see that Unmanic has a new version so I decided to give it a look. Pretty slick! I have a quick question. I have added "--device=/dev/dri" to use my intel CPU in the extra parameter option. I would also like to limit CPU usage with "--cpus='.5" can I add both and if so how do I separate them? Thanks!

Awesome news! Can't wait!

Update. This morning I did a shutdown on the server rather than a reboot. Figured I would try the VM setup again. This time it started normal. Not sure what or why I was having problems before, but my guess is the shutdown seems to have resolved it. Before I would simply restart the server. Thanks again for helping with this. It is much appreciated.

unraid-diagnostics-20220119-1656.zip

Thanks for helping me. Here is the log. unraid-syslog-20220119-2246.zip