TheLinuxGuy

Hi newbie question, according to changelog this image should support `syslog` - how do I go about enabling and using it? I see 514 port exposed and when shipping logs to the observium it does not seem to be getting processed. Are other settings need be changed in the web UI or files to make this work? The instructions from observium discuss rsyslogd but this is not installed in the docker container.

Not sure where else to post this question. "Unraid digest" email today included a blurb I wanted to know more about what "Hybrid ZFS pools" means in this context? Any information about the technical details of it yet?

@JSE that's fair, I am not married to the idea of bcachefs. There could be a similar caching solution achieved with lvmcache + dm-cache with btrfs under the hood too, this option should be much more stable and proven than bcachefs.

Almost exactly a year ago, I made this feature request which got 19 people upvoting. One possible solution for my feature request is to add "experimental" bcachefs support into unraid. Another option could be btrfs if they ever implement https://github.com/kdave/btrfs-progs/issues/610 bcachefs is available in mainline kernel 6.7... given this plus the amount of interest about this in the unraid community, I feel that @limetechshould really consider working on this feature.

I ended up rebooting, and that solved the issue.

My unraid 6.12.6 "Main" page no longer shows the disk drives members of the array. Everything else is working except the total array size, disks etc. It is not a web browser cache issue; tried multiple web browsers and cleared cache. Is this a known issue? I have not tried a full system reboot but rebooting to fix this doesn't make sense to me.

Curious if this ever got fixed for you? I am seeing the same thing on 6.12.6 in multiple browsers.

My unifi network keeps alarming me like this Its my unraid server; the NIC interface is used in two distinct VLANs. root@tower:~# ifconfig | grep 02:d2:39:7f:d8:4e -B4 -A4 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vhost0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.20.28 netmask 255.255.255.0 broadcast 0.0.0.0 ether 02:d2:39:7f:d8:4e txqueuelen 500 (Ethernet) RX packets 798506 bytes 114513804 (109.2 MiB) RX errors 0 dropped 3 overruns 0 frame 0 TX packets 266397 bytes 325195494 (310.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 -- TX packets 1 bytes 90 (90.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vhost0.70: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 02:d2:39:7f:d8:4e txqueuelen 500 (Ethernet) RX packets 125353 bytes 7520476 (7.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7 bytes 586 (586.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 How can I change the MAC address that vlan70 is using (same physical NIC)?

I'm interested in keeping my media with the same quality as my current copy but improve the ability for files to play more smoothly on my Plex clients (Firestick 4K Max, Apple TV). Does anyone have some helpful TL;DR on how to achieve this goal? There is a bunch of information out there explaining all of the complex settings for Tdarr, while Unmanic seems more simple but also others seem to sugest that sometimes conversion of files may cause more storage to be used on raw disk vs. original copy. I also saw a comment that simply recommended replacing the video container (.mkv to .mp4) without changing anything else. I am not totally clear on how to do this since at least in unmanic you need to download the audic codec plugin of your choise like AAC, don;t you? or is the "remux plugin" enough?

Could this be confirmed for sure? I found a past discussion where I read that someone tested and verified with "File Activity Plugin" that actually you don't need to restart replaying anything; the FUSE picks it up without intervention. Here is the discussions: "Because of shfs mechanism accessing a file from /mnt/user will read/write fro cache if it exists, then from array. Duplicate data are not a problem and globally speed up things." Also "Edit 13-02-2020: yes, after checking with File Activity plugin, that's the case and its plex/transmission take the file on cache as soon as it is available!"

How does unraid's FUSE filesystem behave when: * share configured as cache+array * plex uses FUSE mount /mnt/user/movies * user from plex plays a movie not in cache (/mnt/cache/movies not hit; /mnt/diskX/movies finds the file - spins up hdd) 1. What would happen if rsync copies the file being played in plex and suddenly /mnt/cache now has the same data logically represented in /mnt/user/movies ? 2. Would the FUSE mount transparently refer to /mnt/cache/movies and allow the array disk to sleep? I vaguely remember reading something on reddit indicating this would be the behavior but I can't find that discussion now... asking to validate so a new feature to increase power effiency in unraid could be done in https://github.com/bexem/PlexCache/issues/20

I couldn't find this mentioned in the FAQ. The hotio qbittorrent-vpn package is giving me DNS issues; hotio says to use "--dns" flag to force the DNS fix. Where do I set this in unraid? https://docs.docker.com/network/ < there are other flags like "--hostname" that are also of interest for me to setup since I use macvlan. Thanks in advance.

I'm having issues with qbittorrent-vpn package, the DNS resolution is broken. `--dns 1.1.1.1` docker CLI flag according to the documentation is the way to fix it. How can I add this "--dns" flag to the docker startup command of this given container? I do not see a setting for it.

I am curious if you ever went back to macvlan or if you saw any issues? I have the same NIC; on latest unraid I get the kernel crashes macvlan.

There seems to be a bug in unraid - it seems like it deleted all of the docker macvlan networks when I switched from macvlan to ipvlan (via settings menu). But flipping the setting back to macvlan did not restore the networks that used to be there - which are still there in the server's network config page. root@tower:~# docker network inspect 390f44584cb6 [ { "Name": "none", "Id": "390f44584cb6ede959111c0ac6ab1caaf0de6bdc6ff9808596e5c837e88a6459", "Created": "2023-08-06T01:17:32.854369674-07:00", "Scope": "local", "Driver": "null", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ] root@tower:~# docker network ls NETWORK ID NAME DRIVER SCOPE 96c145534982 bridge bridge local 3e455c84393c host host local 390f44584cb6 none null local root@tower:~# root@tower:~# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 6: eth0: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 9000 qdisc fq master bond0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:e2:x8 brd ff:ff:ff:ff:ff:ff 7: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 00:e2:x brd ff:ff:ff:ff:ff:ff permaddr 24:8a:07:e3:14:b0 8: eth2: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 9000 qdisc mq master bond0 state DOWN mode DEFAULT group default qlen 1000 link/ether 00:e2x brd ff:ff:ff:ff:ff:ff permaddr 24:8a:07:e3:14:b1 9: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:e2:x brd ff:ff:ff:ff:ff:ff 10: bond0.70@bond0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9000 qdisc noqueue master br0.70 state UP mode DEFAULT group default qlen 1000 link/ether 00:e2x brd ff:ff:ff:ff:ff:ff 11: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:e2:x8 brd ff:ff:ff:ff:ff:ff 12: br0.70: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:e2:x8 brd ff:ff:ff:ff:ff:ff 13: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 02:42:e5:7d:53:3d brd ff:ff:ff:ff:ff:ff the containers i had configured with br0.70 complain of being unable to find br0.70 network looks like - but that isn;t everything. I cannot "edit" the containers themselves