furian

method 1 with --memory=8G --tmpfs /unifi/log:exec,uid=99,gid=100 --tmpfs /unifi/run:exec,uid=99,gid=100 from the start 2 devices adopted directly (1 was behind another switch, which seems funny), waiting for the rest as they popped up 1 by 1 was fun to see. no errors so far.

i have all my config etc on the nvme for plex and the arrs.. i just disabled my bazarr docker.. trying to see if that changes anything.. edit: disk 1 just started: Dec 6 13:20:19 emhttpd: read SMART /dev/sdk disk activity under tools shows nothing..

i was just wondering.. are any of you guys using all the arrs while trying to maintain a as low as possible power usage? my idle for my i5-11600 with 32gb memory and 5x 3,5 inch and 7 ssd/nvme doesnt go below 60 to 65 watt.. i cant power down disks though, it will fire them up constantly due to plex/arrs..

prior to updating i wasn't having these issues.. but after 48 hours it kinda stabilized.. the amount of notifications has dropped as well. dont know where it came from, but it seems better now.

i updated yesterdat to the latest version. but i'm seeing stuff like this a lot since updating the controller: energysocket PC roamed from U7 Pro to NanoHD. Connection Info: Ch. 6 (2.4 GHz, 20 MHz), -71 dBm. Roaming Decision: -44 dBm to -71 dBm. the energy socket is like 3 meters away from the u7 and like almost 15 meters with a couple of walls in between from the nanohd.. since yesterday (24 hours now) i've got almost a 1000 entry's in the log about disconnects and reconnecting. thinking about going back to the previous version.

running the linuxserver version right now, i added the rules below to the config.php but previews are still not working for videos.(yes i tried a restart of the container) I want to switch over to this docker. Can i just replace the repository or should i go the long way around and move everything config based? 'enable_previews' => true, 'preview_max_x' => 800, 'preview_max_y' => 600, 'enabledPreviewProviders' => array ( 0 => 'OC\\Preview\\IMAGE', 1 => 'OC\\Preview\\MOVIE', 2 => 'OC\\Preview\\GIF', 3 => 'OC\\Preview\\BMP', 4 => 'OC\\Preview\\XBitmap', 5 => 'OC\\Preview\\MP3', 6 => 'OC\\Preview\\TXT', 7 => 'OC\\Preview\\MarkDown', 8 => 'OC\\Preview\\OpenDocument', 9 => 'OC\\Preview\\PDF', 10 => 'OC\\Preview\\MP4', 'preview_max_memory' => 1024, 'preview_max_x' => NULL, 'preview_max_y' => NULL, 'preview_max_filesize_image' => 400, 11 => 'OC\\Preview\\MOV', 12 => 'OC\\Preview\\MKV', 13 => 'OC\\Preview\\HEIC', 14 => 'OC\\Preview\\JPEG', 15 => 'OC\\Preview\\PNG', 16 => 'OC\\Preview\\AVI', ),

09:04:23.047 ***************************************************** Mover Tuning Plugin version 2025.03.11 ****************************************> 09:04:23.055 ----------------------------------------------------------------- Global settings ---------------------------------------------------> 09:04:23.060 Using global (cache) moving threshold: 80 % 09:04:23.062 Using global (cache) freeing threshold: 40 % 09:04:23.069 Age: 15 09:04:23.088 Notify: no 09:04:23.091 Debug Logging: yes 09:04:23.094 Validate Filenames: yes 09:04:23.112 ***************************************************************** FILTERING FILES ***************************************************> 09:04:23.120 -------------------------------------------------------------- Processing [4K] share ------------------------------------------------> 09:04:23.152 Primary storage: download_pool - size: 1.9TiB - used: 93 % (1.7TiB) 09:04:23.154 Secondary storage: user0 nothing more in the logs... (this was from the mover_tuning log). Summary log is empty and only Filtered_files log remain.. edit: when trying to stop the mover i got this mover stop /usr/local/sbin/mover.old: line 123: kill: (3881860) - No such process mover: stopped also when i try to enable the normal mover logging i get this: Mar 19 08:57:54 nginx: 2025/03/19 08:57:54 [error] 2291550#2291550: *4162441 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.0.100, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "server", referrer: "http://server/Settings/Scheduler" might have found the issue... the recycle bin plugin was stuck.. trying to reboot wont even work.. so forcing it off might be the only way.. i'll post here when trying again. well turned out that was it.. nice

the mover suddenly stopped working for me.. test run shows no issues, but when run to move files from share on ssd to array it just does nothing.. test: /mnt/download_pool/4K Mover tuning plugin done! real move: Mar 19 08:54:01 Plex move: init_debugging: 0 nothing happens.. reinstalled the mover plugin as well.. edit: mover start in cli however did work.. so now its moving stuff.. no idea why pressing the start button did nothing. edit2: i take that back.. it looked like it for a moment... but its actually not doing anything...

i'm also seeing this issue, but on only 1 of my servers.. what should i change to get this fixed and where do i change this

would appear that 8.4.59-unraid is now available. (11 days now)

yeah i did. you need to change the DOCKER-USER to FORWARD ## Version 2022/08/06 # Fail2Ban jail configuration for authelia # Works OOTB with defaults [authelia-auth] enabled = true port = 0:65535 protocol = tcp logpath = %(remote_logs_path)s/authelia/authelia.log #CHAIN = DOCKER-USER CHAIN = FORWARD action = iptables-multiport-log[name=authelia-auth, port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"] ignoreip = 127.0.0.1/8 ::1 172.18.0.0/16 192.168.0.0/24 bantime = -1 findtime = 24h maxretry = 1

i have the same issue as @Bovin. no zfs, no netdata, bazarr is disabled since a couple of days *bazarr was visible in file activity monitor, no disk location plugin. the logs show: Jul 9 15:58:13 Plex emhttpd: read SMART /dev/sdb Jul 9 15:58:22 Plex root: Total Spundown: 1 Jul 9 16:03:22 Plex root: Total Spundown: 1 Jul 9 16:08:22 Plex root: Total Spundown: 1 Jul 9 16:13:22 Plex root: Total Spundown: 1 Jul 9 16:18:22 Plex root: Total Spundown: 1 Jul 9 16:23:22 Plex root: Total Spundown: 1 Jul 9 16:27:46 Plex emhttpd: spinning down /dev/sdc Jul 9 16:28:22 Plex root: Total Spundown: 2 Jul 9 16:29:37 Plex emhttpd: read SMART /dev/sdc Jul 9 16:30:04 Plex emhttpd: read SMART /dev/sdg Jul 9 16:30:14 Plex emhttpd: read SMART /dev/sdf when the disks finally spin down they spin up quite fast again. looking at the file activity monitor i can see stuff happening on the cache and nvme drives (home assistant and vm's). but the disks show no activity.. yet they still spun up.. keeping record now: Jul 10 14:12:02 Plex emhttpd: spinning down /dev/sdb Jul 10 14:12:04 Plex emhttpd: spinning down /dev/sdg Jul 10 14:28:43 Plex emhttpd: spinning down /dev/sde Jul 10 14:37:49 Plex emhttpd: spinning down /dev/sdc Jul 10 16:24:49 Plex kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 10 16:24:59 Plex kernel: ata4.00: configured for UDMA/133 Jul 10 16:24:59 Plex emhttpd: read SMART /dev/sde yet nothing in the share or disk activity

update ran without issues so far.

Yup, I had the exact same thing.. diasbled tailscale and everything works again. Found out that resolv.conf is being overwritten instead of adding. Took me a few hours to find this..

i have been running my custom network for over 1,5 year now without issues as created by ibracorp method. since yesterday however the external dns function for all my dockers stopped working. i tried everything in the docker settings to get it working again.. i just dont know what else to try. current settings docker: Docker custom network type: ipvlan Host access to custom networks: Disabled Preserve user defined networks: Yes pinging to an ip works without issue, its just name resolving.. sh-5.2# ping nu.nl ping: nu.nl: Temporary failure in name resolution sh-5.2# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=6.68 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=6.99 ms for example authelia now says: {"error":"failed to dial connection: dial tcp: lookup smtp.gmail.com: i/o timeout","level":"error","msg":"Error occurred running a startup check","provider":"notification","time":"2024-05-15T13:51:52+02:00"} {"error":"error occurred during dial: dial udp: lookup time.cloudflare.com on 127.0.0.11:53: server misbehaving","level":"warning","msg":"Could not determine the clock offset due to an error","time":"2024-05-15T13:52:16+02:00"} {"level":"fatal","msg":"One or more providers had fatal failures performing startup checks, for more detail check the error level logs","providers":["notification"],"stack":[{"File":"github.com/authelia/authelia/v4/internal/commands/root.go","Line":150,"Name":"doStartupChecks"},{"File":"github.com/authelia/authelia/v4/internal/commands/root.go","Line":88,"Name":"(*CmdCtx).RootRunE"},{"File":"github.com/spf13/[email protected]/command.go","Line":983,"Name":"(*Command).execute"},{"File":"github.com/spf13/[email protected]/command.go","Line":1115,"Name":"(*Command).ExecuteC"},{"File":"github.com/spf13/[email protected]/command.go","Line":1039,"Name":"(*Command).Execute"},{"File":"github.com/authelia/authelia/v4/cmd/authelia/main.go","Line":10,"Name":"main"},{"File":"runtime/internal/atomic/types.go","Line":194,"Name":"(*Uint32).Load"},{"File":"runtime/asm_amd64.s","Line":1695,"Name":"goexit"}],"time":"2024-05-15T13:52:16+02:00"}

same reason i came here..

bump?

for a good while i had fail2ban working in a seperate docker with nginx proxy manager and authelia in seperate dockers. now suddenly (worked like a charm so i stopped checking the logs, stupid) it stopped working. in the fail2ban logs i can see that it is actually banning the ip, in the console of fail2ban i can also see this happening with iptables -nL. however it is no longer pushing the chain through to the unraid host and so it is not blocking the actual incoming connections.. here is my authelia jail.local The docker is running with the network type Host btw. The below output is from inside the docker container: and in the log from fail2ban itself: on the unraid host: no matter what i try, im not able to get it running again

Hi, I wanna see how my cache drive is doing, however i have no idea what the wear lvl is of this drive.. looking on google intel says you should look at the E9 media wear-out indicator.. thats 233 for unraid.. However added picture shows what i'm seeing.. and i got no idea how to convert this to reliable information.. thnx in advance.

i just cant get this to work..my fail2ban log shows that my work ip is blocked.. but the page still loads and i can still enter my username and password and keep trying and refreshing.. i'm just at a loss here... tried everything i could think of.. only thing i just changed is the priviliged mode and going to try that now. edit: priviliged mode did not change anything.. i can still keep pressing F5 and trying new passwords etc.. also added my iptables -nvL from the host. as you can see the reject tables are present.. but something is preventing them from being blocked.. authelia.txt fail2banlog.txt filter authelia-auth.local.txt jail authelia-auth.local.txt iptables -nvL.txt

i just noticed while trying to get fail2ban working (damn hard btw.. I could really use some help with fail2ban to work with authelia and nginx.. with docker) There is a red dot showing the error: incorrect autostart order.. i dont know where i can check what the order should be then... this is my list as it is right now: mariadb redis fail2ban adguard-home nginx authelia unifi-controller adguard-sync nextcloud *arrs and downloaders

thank you! My GUI stopped responding after starting the array when i replaced the parity disk (14tb) for a new 18tb disk i had no idea what the server was doing.. i selected the 14TB disk as a replacement for a old 4tb disk, i can't format it right now as the gui stopped responding and i had no idea how long it would take.. Now i see this, i think i will have to wait for it to complete... but at least now i know what is happening!

so i know there is the smb bug with unraid 6.12.2 (rc included). but i dont know if below is also part of that error.. this is when trying to use remote smb through unassigned plugin. (removed ip's and hostnames) Jul 12 13:12:05 unassigned.devices: Mount SMB share '///Backup' using SMB 1.0 protocol. Jul 12 13:12:05 unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=1.0,credentials='/tmp/unassigned.devices/credentials_Backup' '///Backup' '/mnt/remotes/Backup' Jul 12 13:12:05 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jul 12 13:12:05 kernel: Jul 12 13:12:05 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Jul 12 13:12:05 kernel: CIFS: Attempting to mount \\\Backup Jul 12 13:12:06 kernel: CIFS: VFS: Error connecting to socket. Aborting operation. Jul 12 13:12:06 kernel: CIFS: VFS: cifs_mount failed w/return code = -111 Jul 12 13:12:06 unassigned.devices: SMB 1.0 mount failed: 'mount error(111): could not connect to IP Unable to find suitable address. '. Jul 12 13:12:06 unassigned.devices: Share '///Backup' failed to mount.

i went back to 6.12.0-rc5 to get it fixed

wonderfull.. any idea how long i would have to wait for it?