-
Docker containers startup extremely slow
Dear lord. I assumed that all containers started at the same time, and that the timers ran consecutively. Does that mean that the order in which they appear from top to bottom on the Docker page is also the order in which they start?
-
Docker containers startup extremely slow
Ok so if I understand you correctly, if I set one container to 120s wait, all the containers below it also wait 120s?
-
Docker containers startup extremely slow
Here you go bignas-diagnostics-20261021-0911.zip
-
Docker containers startup extremely slow
I hadn't rebooted in 5 months, so without changing any settings I did today. Ever since then Docker has been really slow to start up. I have about 40 containers and it takes 20 minutes to load them all. This is new behaviour. Previously everything was started in 3-5 minutes. After having watched it load all the containers, it looks like Docker starts every container one by one, instead of all at the same time. Is this new? Can I change this back to it's previous setting somehow? I can speed it up by manually starting the containers, but that's tedious work. Things I've tried: Updating from 7.3.0 to 7.3.3 Updating all the plugins Booting with Docker off, and manually starting it.
-
[Support] kilrah/searxng
Recently my instance of SearXNG stopped working. Every time it does a search, it changes the user to 977:977, which makes it impossible for SearXNG to access the files in the appdata folder. When I change it back to 99:100 I can do exactly one succesful search before it changes itself back to 977:977 again and it's unable to search. Someone suggested adding --user 977:977 to extra parameters of the docker container. I did, and now my docker container has disappeared. I can't even find it with Portainer. What is going on? How do I get my container back? And how can I make it function again without constantly switching users to 977?
-
Errors after updating to 7.3.0
What filesystem should I be reformatting? Just the cache or the array as well?
-
Errors after updating to 7.3.0
This is the output from the GUI: Scrub started: Sat May 23 22:14:24 2026 Status: aborted Duration: 0:06:14 Total to scrub: 2.71TiB Rate: 4.08GiB/s Error summary: no errors foundFollowed in the logs by: May 23 22:20:32 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 23 22:20:32 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 23 22:20:32 BigNAS kernel: BTRFS info (device nvme0n1p1): scrub: not finished on devid 4 with status: -5 May 23 22:20:38 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 23 22:20:38 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 23 22:20:38 BigNAS kernel: BTRFS info (device nvme0n1p1): scrub: not finished on devid 3 with status: -5
-
Unraid's built-in wireguard VPN never works
I have been pulling my hair out of my head over this for years now. For as long as Unraid has had a built-in VPN client, I have tried to use it. It has never worked properly for longer than a day. I am trying to use it on both a iphone and a laptop. Sometimes it works on the phone, then the next day it doesn't. Sometimes it works on the laptop, sometimes it doesn't. Things I've tried: reinstalling the app on my phone or my laptop removing all tunnels from unraid and starting from scratch changing any and all settings, in any combination. trying 0.0.0.0/0 as allowed IPs setting different IPs, different access modes, different devices, different networks, etc. letting my router do the NAT or not I've had it running reliably for a while on my laptop. Then I decided to try if I could get it running again on my phone. I deleted the tunnel, started over and then it worked on my phone for a few days and I could not get it running on my laptop again WITH THE EXACT SAME SETTINGS AS BEFORE I DELETED THE TUNNEL. Today I woke up and neither my phone nor my laptop complete a handshake anymore. This has been like this through any and all versions of Unraid. I'm so done with this. I just want it to work reliably with no fuss. How is it being this obtuse?
-
Errors after updating to 7.3.0
I ran Memtest86 and it passed with no errors.
-
[SUPPORT] TEMPLATE MASTERWISHX/REDISINSIGHT
I tried both solutions in this thread, neither work for me. I'm getting the exact same error: Error: EACCES: permission denied, open '/data/logs/redisinsight-errors-2026-05-21.log.0' Emitted 'error' event on FileStreamRotator instance at: at WriteStream.<anonymous> (/usr/src/app/redisinsight/api/node_modules/file-stream-rotator/lib/FileStreamRotator.js:177:45) at WriteStream.emit (node:events:519:28) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { errno: -13, code: 'EACCES', syscall: 'open', path: '/data/logs/redisinsight-errors-2026-05-21.log.0' } Node.js v22.22.0
-
[Support] Linuxserver.io - Transmission
Is there a way I can change the default layout? I have a layout I like, but every time I open it in a new browser or new computer I have to spend a while setting up my preferred layout. It would be nice if I could just change the default on the server side.
-
Errors after updating to 7.3.0
After updating from 7.2.1 to 7.3.0 I get this message concerning my cache pool: Id Path Write errors Read errors Flush errors Corruption errors Generation errors -- -------------- ------------ ----------- ------------ ----------------- ----------------- 3 /dev/nvme0n1p1 0 0 0 255 0 4 /dev/nvme1n1p1 0 0 0 255 0I have been trying to find out what the specific errors are, but I can't find them anywhere. I would like to know which specific files or data is affected. Both devices successfully complete an extended SMART self test. But when I do a scrub, it aborts with these errors: May 18 18:01:52 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 18 18:01:52 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 18 18:01:52 BigNAS kernel: BTRFS info (device nvme0n1p1): scrub: not finished on devid 4 with status: -5 May 18 18:02:03 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 18 18:02:03 BigNAS kernel: BTRFS critical (device nvme0n1p1): unable to find chunk map for logical 6180170305658470400 length 16384 May 18 18:02:03 BigNAS kernel: BTRFS info (device nvme0n1p1): scrub: not finished on devid 3 with status: -5What can I do about this? And how do I get more detailed information? Edit: I've added the diagnostics. NAS-diagnostics-20260521-0909.zip
-
[Support] CoolerControl in Docker
Looking at your screenshot, I see what I did wrong. I added the runtime=nvidia and gpus=all as variables instead of putting them under Extra Parameters. I changed it and it works!
-
[Support] CoolerControl in Docker
I can't get my Nvidia GPU to be detected. The drivers are installed correctly though, because I can see the temps display correctly on the unraid dashboard. I've tried adding --gpus=all and --runtime=nvidia, but no dice. I'm running in privileged mode and can see and control other devices just fine. This is what I get in the logs: [2026-04-20T18:06:25Z INFO coolercontrold] Super-I/O hardware detection disabled by environment variable [2026-04-20T18:06:25Z INFO coolercontrold] Initializing Devices... [2026-04-20T18:06:25Z INFO coolercontrold] Liquidctl Integration is Disabled [2026-04-20T18:06:25Z INFO coolercontrold::repositories::service_plugin::service_plugin_repo] Initialized Service Plugin Devices: {} [2026-04-20T18:06:25Z INFO coolercontrold::repositories::gpu::gpu_repo] Initialized GPU Devices: {} [2026-04-20T18:06:25Z INFO coolercontrold::repositories::hwmon::devices] Could not read PCI ID database: pci.ids database not found at any known path, device name information will be limited
-
Zip Manager for unRAID
Thanks for the making the extractor. It's really handy. :) Is it possible for the extractor to remember the directory I extracted from last? Or to set a default directory? I'm usually extracting multiple files from my downloads folder and right now I have to start at / every time.
BreakfastPurrito
Members
-
Joined