TRusselo

/mnt/cache/ for /mnt/cache/appdata/netalertx and /mnt/cache/appdata/logs will have better performance than /mnt/user/ I learned this the hard way couple years ago. ESPhome would take 5 minutes to compile tiny sketches. changing to /mnt/cache, 20 seconds.

there was an update overnight. not much changed except my daemon now shows 2 interfaces, neither are the host network that the daemon exists on 192.168.1.0/24 .

and... I tried to install daemon on my linux-PC (im new to linux as a daily driver) what does this mean "your parameters"

ok so I have server and daemon working. but... daemon cannot see normal host network... even though daemon is on HOST network. Unraid HOST is showing the 192.168.1.12 interface, the subnet br0 192.168.1.0/24 no errors in logs for server, nor daemon daemon in server shows "no" interfaces this time. previously with other settings had something here. but still no network devices discovered then either. just WARN (seems irrelevant) 2025-12-24T00:20:33.114083Z INFO scanopy::daemon::discovery::manager: Discovery completed successfully 2025-12-24T00:20:33.114462Z WARN scanopy::daemon::discovery::service::network: Skipping 172.31.200.0/24 with CIDR 172.31.200.0/24, docker bridge subnets are scanning in docker discovery 2025-12-24T00:20:33.114474Z WARN scanopy::daemon::discovery::service::network: Skipping 172.21.0.0/16 with CIDR 172.21.0.0/16, docker bridge subnets are scanning in docker discovery 2025-12-24T00:20:33.114480Z WARN scanopy::daemon::discovery::service::network: Skipping 172.17.0.0/16 with CIDR 172.17.0.0/16, docker bridge subnets are scanning in docker discovery 2025-12-24T00:20:33.114484Z WARN scanopy::daemon::discovery::service::network: Skipping 172.20.0.0/16 with CIDR 172.20.0.0/16, docker bridge subnets are scanning in docker discovery 2025-12-24T00:20:33.114489Z WARN scanopy::daemon::discovery::service::network: Skipping 172.19.0.0/16 with CIDR 172.19.0.0/16, docker bridge subnets are scanning in docker discovery 2025-12-24T00:20:33.114494Z WARN scanopy::daemon::discovery::service::network: Skipping 172.18.0.0/16 with CIDR 172.18.0.0/16, docker bridge subnets are scanning in docker discovery 2025-12-24T00:20:33.119982Z INFO scanopy::daemon::discovery::service::base: Starting Network Discovery discovery session aacb2573-22c0-42bf-b444-44086326803c Then when Netowork scan starts: bf-b444-44086326803c discovery_type=Network { subnet_ids: None, host_naming_fallback: BestService } 2025-12-24T00:20:33.160259Z INFO scanopy::daemon::discovery::service::network: Phase 1: Checking host responsiveness total_ips=768 interfaced_ips=512 non_interfaced_ips=256 2025-12-24T00:20:33.163347Z INFO scanopy::daemon::discovery::service::network: Phase 1a: ARP scanning interfaced subnets count=512 concurrency=50 2025-12-24T00:20:44.150887Z INFO scanopy::daemon::runtime::service: Heartbeat sent daemon_id=e4383ce9-08c5-46ab-8597-d4e3450644a3 2025-12-24T00:21:03.140851Z INFO scanopy::daemon::shared::handlers: Received healthcheck request 2025-12-24T00:21:14.146151Z INFO scanopy::daemon::runtime::service: Heartbeat sent daemon_id=e4383ce9-08c5-46ab-8597-d4e3450644a3 2025-12-24T00:21:33.206850Z INFO scanopy::daemon::shared::handlers: Received healthcheck request 2025-12-24T00:21:44.145211Z INFO scanopy::daemon::runtime::service: Heartbeat sent daemon_id=e4383ce9-08c5-46ab-8597-d4e3450644a3 2025-12-24T00:22:03.279161Z INFO scanopy::daemon::shared::handlers: Received healthcheck request 5 min later no error in log

In the windows official app there is a setting to "serve all devices (including from clients)" This option is not available in the docker... Can this be added? It would be much easer to run a single OpenRGB server for all my PCs rather than run a server on each one, for connection to Home Assistant.

you can always re-open the logs after the container has shut down for the info you missed before the log window closed on you. But as previous user mentioned

the webhook variable in the template ended up making me bang my head against the desk for about 24 hours until I realized my production webhook url was not my server IP. I had set a base URL to expose the docker to receive google authentication, it changed my test URL to my domain name, but kept the production URL as an IP. but WRONG IP !!! I was trying to add other docker URL variables to fix the "issue" when I saw your existing variable set to 192.168.1.161 Im not sure if I overlooked this variable during setup, or if I assumed it was set to this IP for a reason... without remembering I have this IP reserved for something in my house. It is bad practice to hardcode IP addresses in the unraid docker templates. best practice is to leave blank for user to fill in, or use localhost, as it is usually the most likely choice. Thanks for setting up the template regardless!

I was just looking into this too

Did you get this figured out?

Reading through the forums over the past 7 years I know I'm not the only one that this happens to

1. I have been running unrade for 7 years and I'm on my 8th USB flash drive. I have tried different brands and types with and without LEDs... I lose one flash drive per year using unraid. I have had zero other hardware failures in the same amount of time. So no, it's not the same. 2. A system can have more than one hot spare

I have 2 issues that worry me if I were to pass away... 1. USB flash is likely to die within a year. My USB dies every year. 2. No "hot-spare" feature to auto rebuild a failed drive. With these 2 unaddressed issues, my server, my legacy, would not survive without intervention for long after my death. This worries me.

My cache was bad. purchased a new drive at store started array with VM OFF / DOCKER OFF terminal mkdir /mnt/disk7/CACHE-BACKUP/ cp -Rfvp /mnt/cache/* /mnt/disk7/CACHE-BACKUP/ wait stop array. remove old cache drive. start array. stop array. add new cache drive. start array. cp -Rfvp /mnt/disk7/CACHE-BACKUP/* /mnt/cache/ start array. enable docker, enable VM

I have been having issues with docker lately. Upon reboot it does not auto start. docker file at 75% full Manually starting has worked once per boot. shutting down docker and re-starting does not work. failed to start error. Last night docker service shut down. Reboot machine. Docker wont start, even manually. I just got a message from "fix common problems" it says my cache is mounted read only?!? Unraid 6.12.4 diags below from dmesg: [ 147.302393] BTRFS error (device sdc1): unable to find ref byte nr 4726796288 parent 0 root 5 owner 110749390 offset 20393984 ... [ 147.302598] BTRFS: error (device sdc1: state A) in __btrfs_free_extent:3067: errno=-2 No such entry [ 147.302944] BTRFS info (device sdc1: state EA): forced readonly [ 147.302948] BTRFS error (device sdc1: state EA): failed to run delayed ref for logical 4726796288 num_bytes 4096 type 178 action 2 ref_mod 1: -2 [ 147.302952] BTRFS: error (device sdc1: state EA) in btrfs_run_delayed_refs:2144: errno=-2 No such entry [ 147.303304] BTRFS info (device sdc1: state EMA): turning on async discard [ 147.303307] BTRFS error (device sdc1: state EMA): Remounting read-write after error is not allowed [ 154.069448] BTRFS: device fsid 340edf27-5c02-45de-a544-66414f31295d devid 1 transid 1041182 /dev/loop2 scanned by mount (18956) [ 154.069842] BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm [ 154.069852] BTRFS info (device loop2): using free space tree [ 154.076436] BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 158, gen 0 [ 154.116183] BTRFS info (device loop2): enabling ssd optimizations [ 154.116189] BTRFS info (device loop2): start tree-log replay [ 154.116192] BTRFS warning (device loop2): log replay required on RO media [ 154.116854] BTRFS error (device loop2): open_ctree failed [ 154.209514] loop2: detected capacity change from 0 to 2097152 [ 154.214563] BTRFS: device fsid 19370b97-4ce9-472f-b454-3cd5fb59f6af devid 1 transid 16168 /dev/loop2 scanned by mount (19003) [ 154.214950] BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm [ 154.214960] BTRFS info (device loop2): using free space tree [ 154.220240] BTRFS info (device loop2): enabling ssd optimizations ... [ 174.250968] sd 11:0:0:0: device_block, handle(0x0011) [ 175.498424] sd 11:0:0:0: device_unblock and setting to running, handle(0x0011) [ 175.505760] sd 11:0:0:0: Power-on or device reset occurred [ 199.437504] loop3: detected capacity change from 0 to 157286400 [ 199.439748] BTRFS: device fsid 340edf27-5c02-45de-a544-66414f31295d devid 1 transid 1041182 /dev/loop3 scanned by mount (25474) [ 199.440171] BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm [ 199.440180] BTRFS info (device loop3): using free space tree [ 199.441469] BTRFS info (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 158, gen 0 [ 199.446427] BTRFS info (device loop3): enabling ssd optimizations [ 199.446432] BTRFS info (device loop3): start tree-log replay [ 199.446435] BTRFS warning (device loop3): log replay required on RO media [ 199.447325] BTRFS error (device loop3): open_ctree failed is my cache drive failiing? I found a similar issue with another user, his drive was dying. EDIT: i just got back from the store and installed a new 2tb nvme. not sure how to do a cache swap though. spaceinvaderone video on the subject requires docker working and using krusader. EDIT: 6 hours later I get a failed disk error on my parity 0 drive rebooted, cant start array in maintenance mode. more diags attached. EDIT: purchased an NVME its mounted as unassigned. currently cp -Rfvp /mnt/cache/* /mnt/disk7/CACHE-BACKUP/ big-z-diagnostics-20240204-0906.zip big-z-diagnostics-20240204-1617.zip