MindRazorblade

Restarted my Unraid Server after a power outage and found both my drives in my RAID 1, btrfs cache pool were listed as unmountable. There seems to be some hesitancy with running checks/repairs with btrfs so I wanted to post my diagnostics and get some advice before doing something irreparable. I'm unsure of the value what's in my cache. I believe I have a backup of what could be in there but I'd rather not have to rely on it. If there's a way to view the file listing before anything invasive happens that would be idea. tower-diagnostics-20230726-2129.zip

Sorry, I'm mistaken. Mine is an HX only. I wasn't aware of the i model. I'll add that to the FOMO wishlist. Thanks!

Did you have to do anything special to get this working? I have the same HX series and mine is blank.

Thanks @Squid for pointing that out. Your description was just what was needed! In summary to those following this, your downloader (SabNZB/Get) communicates a file path of the download to Radarr. This file path only works from Radarr's side if it's path to the download is configured the same as your downloader. What I did earlier by making a symlink was a ductape solution where making a custom path in the Docker container was the real solution. An underlying cause of this, which is probably the same for many others, is that I am using binhex's Sab container and LinuxServer's Radarr container. Probably the file convention of one changed and caused the sudden disharmony.

I think I'm having the same issue. What I've seen from Radarr's logs is that the mover is looking for the file in the `/data` directory instead of the `/downloads`. I haven't changed my config over this time so my only guess is that it is due to a new way the container is configured. I tested this by creating a symlink from within the container with the command "ln -sfv /downloads /data". Double check your log to see the path before trying this. This may be separate a separate issue but I noticed that the container was set to use the "nightly" branch instead of "stable/latest".

Where are you connecting from?: From a laptop 192.168.7.13 What is the internal ip of your home assistant instance and what is the ip of your ha control panel instance?: 192.168.7.8:8123 is the ip address I access my HA instance from the laptop may I have a cencored out section of your home assistant's http config? http: api_password: !secret http_password login_attempts_threshold: 5 cors_allowed_origins: - http://192.168.8.8 Thanks for your help!

Hi @Siwat2545, I'm trying to get an instance of your Home Assistant Control Panel (HACP) to talk to my Home Assistant (HA) instance but it's giving me a pop up error saying "Unable to connect to Home Assistant. Please check the Server URL is accessible from this device or change the URL below:". I've followed the HACP troubleshooting, confirmed my API Password works and added a "cors_allowed_origins" section to the http part of my HA's configuration.yaml but still no luck. Do you have any idea what mistake I could be making?

I'm having this same issue. Just starting to explore the SAB logs (/config/logs/) but haven't seen anything that points to an issue with SAB so I suspect its an issue with the VPN. By chance, did you follow SpaceInvaderOne's tutorial for getting Let'sEncrypt/NGINX working with this? If so I wonder if having SAB, etc. on another network causes some issues with the VPN.

I see that that's where the container puts it but rclone is looking for it in ~/.config/rclone by default. Sent from my SM-G965U using Tapatalk

Is this docker functional for anyone still? It's not looking for the config file where the template assigns (in appdata). I've played around with a workaround but nothing worthwhile.

I might not be the first to ask but can you include rclone? I know there's a docker and a plugin for it but the plugin needs to be installed every reboot and the container is more than I need.

With a little bit of studying and experimentation I got this to work but I'm sure someone more experienced with udev would get this better I used the "User Scripts" app to setup a startup script that copies and refreshes the rules for the device so that the rules you setup in "99-usb-rules.rules" are loaded properly. Here it is: #!/bin/bash # copy persistent script from usb drive to drive at startup cp /boot/config/userFiles/99-usb-serial.rules /etc/udev/rules.d/ chmod 644 /etc/udev/rules.d/99-usb-serial.rules # udav has likely run before the copy completes so udev needs its rules refreshed udevadm control --reload-rules # a reset of the device is needed so the rules just copied can take hold udevadm trigger --attr-match=subsystem=tty I'm a little nervous about the last line resetting all tty subsystems since I wasn't able to get something like : udevadm trigger --attr-match=serial=0000:00:11.0 to work for some reason after confirming the serial with: udevadm info -a -n /dev/ttyUSB1 | grep '{serial}' | head -n1 Here are some links for education: http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/ https://www.thegeekdiary.com/beginners-guide-to-udev-in-linux/ http://reactivated.net/writing_udev_rules.html https://unix.stackexchange.com/questions/39370/how-to-reload-udev-rules-without-reboot http://www.reactivated.net/writing_udev_rules.html#example-printer https://askubuntu.com/questions/445735/why-do-my-udev-rules-run-if-i-use-udevadm-trigger-but-not-at-boot-time/635477 https://www.linux.com/news/udev-introduction-device-management-modern-linux-system If you run into any commands that look like they're aren't installed be conscious that udev changed a bit since some of these were written and there are new commands for these (e.g. udevadm info instead of udevinfo).

No luck for me either. I've just tried this too using User Scripts to execute the copy of these rules from my boot USB at disk startup just like you've done with go. I can confirm that the right file is in the right place according to the tutorial linked in aeleos. I wonder if the copy doesn't happen early enough in startup and the rules have already been run by the time they get copied. If anyone else has had luck doing this, please let us know.

Awesome, I appreciate that!

This worked, thanks! I swear I forced updated right before I posted, crazy.