BoKKeR

What is the problem you are facing @RedReddington ? I got the CA one running, I could update the container with some help if something is broken

Thanks for the tip, I deleted this thread earlier as I figured out the problem. It was because I accidentally renamed the partition in UD (by clicking on its name). I will look at moving everything to cache

Weird thing happened, one of my disks filled up to where only 20kb was left. This made the docker service stuck. I couldnt open the tab. I did a restart, Docker service wouldnt load (docker image is on a separate disk) I used unBalancer to balance out the drive space. Did a couple of restarts but it still wont start. If I start docker with `dockerd` it gives no error unraid-diagnostics-20220111-1654.zip

I dont think anything is out of ordinary here

One more thing to note. I managed to write some data (partial download using deluge) to the array when it was in this state. Upon restarting when I got back all my data the partial downloads were still present. Meaning that the data I wrote to the ghost array persisted to the real array after restart. I cant restart in safe mode as I am abroad

Sorry that diagnostics was posted before I made this thread and resolved those problems I added a new diagnostics where all the data paths should be back unraid-diagnostics-20211201-1809.zip

I opened the user folder from the unraid console and tried looking for data, only the default shares were there. All empty. Also all docker containers reported that the data was missing. (Appdata worked as it was on a separate SSD)

Well something weird just happened. I logged into my unraid remotely as I noticed that my container was not running. The array was down. No biggie I thought to myself. I will just start it again. upon doing that I noticed that the array had no data on it at all. The base folders were there but the data was gone. The size of used drives still showed up but there was no data to be found. I did a restart and entered my encryption password again. Now the array started properly with all the data on it. Scary stuff unraid-diagnostics-20211201-1625.zip

I have read through several similar threads but I cant really solve it by myself. My docker image keeps filling up. The way I can mitigate this is removing dangling images. I understand that this should be caused because an image is leaking data into the docker image instead of a mounted volume. But I cant find which one and where Any help is appreciated. My docker image is at 60gb and slowly filling up unraid-diagnostics-20211201-1625.zip

I have a setup where I rsync my camera files from the sony camera SD card to a backup folder automatically upon attaching it to the server. But my sony camera choses to name the video files as 0001, 0002 etc, If I wipe the card and record new footage rsync would just overwrite existing backup as the new files would have the same names as the old ones. Is there a docker container for importing video files that would solve this? How do big studios deal with this?

Does your current setup support renaming files? I have a setup where I rsync my camera files from the sony camera SD card to a backup folder, but the sony camera choses to name the video files as 0001-0002 etc, If I wipe the card and record new footage rsync would just overwrite existing backup. Have you faced this problem?

thanks for commenting!

Could we get TLDR? Its really useful to get some quick tips about commands in a unix environment https://github.com/tldr-pages/tldr

I managed to fix it, the problem was that I skipped the initial clear command, after clearing the controller. it showed up on p20 sas2flash.efi.

having hard time getting my LSI 9220-i8 card detected on my GIGABYTE z370m d3h with sas2flash.efi p20 p15 p14,. sas2flsh.exe just gives me the PAL error. I tried both PCIE ports on my mobo, It shows up in unraid

<Data> <Volume> <HostDir>/mnt/user/appdata/RSSTT</HostDir> <ContainerDir>/config</ContainerDir> <Mode>rw</Mode> </Volume> </Data> I have this bit in my template but it does not appear when I try to add the app. (has been there for 4 months).

thanks I will do that, if you have a chance can you star the docker hub repo.

can you try adding a mounted config folder and reproduce the problem? -v /path/to/host/config:/config

I can look into this, can you share your docker run command that you get after adding the container?

I cant find this option, but to make sure I made a new container with a new config location and adjusted the config in swag, restarted swagger. I get the https login page on the subdomain, upon login I end up with the same error page.

Removing the block rebooting SWAG, I get even less access. I get to the login page. After login I am greeted with

thanks I tried that also. Same result I can resolve home assistant over nginx, but all the service calls fail.

I have multiple services running behind a reverse nginx proxy. But I am having issues with home assistant. The UI loads but the calls don't get forwarded and error out Failed to call service homeassistant/turn_off. Unable to find service light/turn_off I am running https://hub.docker.com/r/homeassistant/home-assistant on Unraid. This is the nginx config. The site loads but gives errors when I try to turn on lights. # make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name ha.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app homeassistant; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /api/websocket { resolver 127.0.0.11 valid=30s; set $upstream_app homeassistant; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } This is the command used to run the container: usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='HomeAssistant' --net='proxynet' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -p '8123:8123/tcp' --device='/dev/ttyUSB0' 'homeassistant/home-assistant' I am not sure if its more suited for home assistant?

+1 I would love to have this. Otherwise I might have to run a virtualisation OS and use that to run unraid

if you preset new like https://www.reddit.com/r/funny/new/.rss it should give you the newest submissions without the stickies. By default it uses top afaik. Does this work for you? @m0ngr31