MowMdown

@thewolf56 I've been running my Arc A310 for a few weeks now, it's been pretty good for plex transcoding. I was able to run 5 simultaneous 4K -> 1080p transcodes with HDR -> SDR tonemapping without any issues other than it was over WiFi so I might have been able to get up to 6 if I was plugged into my network. I'm even running mine in a PCIe Gen3 x1 slot as well. I don't think you could even saturate the PCIe Gen4 x4 link anyways. Since they're so cheap I may just pickup a 2nd A310 and throw it in one of my other PCIe Gen3 x1 slots since I have 3 of them. I have not really tested encoding with handbrake, I'll do a test and let you know how it goes later today.

I've got a MSI B550 Pro VC WiFi motherboard which dual M.2 PCIe, a Gen 4x4 and a Gen3x4. Currently the Gen3x4 slot is rocking a JBM585 SATA controller which I'm using for some of my drives. Im wondering if anybody has any creative uses for the Gen4x4 M.2 slot? I was thinking in order to free up my PCIe 4x16 slot I could get a M.2 to PCIe Slot (physical adapter) to throw in my Arc A310 GPU since it really does not need to occupy the PCIe x16 slot it's only electrically a x4 card anyways.

I can't help you with the VM issue but for the dockers, you just need to delete your docker.img and recreate your containers. (all of the data should be intact) Same thing probably applies to the libvert.img. I'd make a backup of both before you do anything. To recreate your dockers, just go to the docker tab, click "add container" and select them from the template drop-down. You'll have to do this for each docker container you had running.

I just ordered myself an A310 because it's a single slot and I value the space in my NAS case... honestly for video encoding/decoding the A310 is probably plenty unless you plan on doing other GPU heavy workloads besides video encoding. 4GB of VRAM in my experience with my GTX970 more than adequate for multiple concurrent 1080p transcodes. I've seen as much as 256MB per trancode which roughly means 16 trancodes to be maxed out. I never personally have anywhere near that number so it in theory should be more than I'll personally ever need.

An alternate suggestion is to separate the thumbnails from the photos and keep the thumbnails on the cache pool so you can browse your photos without your drives spinning up until you click on a photo. obviously there’s going to be a delay to view the full resolution photo while the drive spins up.

Any issues with the JMB585 SATA adapters for use with drives in the array? I recently picked one up and wondered if anybody had any issues. Mine is from SilverStone (SST-ECS07) and comes with a heatsink attached.

I never touched plex's remote access, I left that alone as enabled. As soon as I disabled unraid connect remote access, it started working and my plex server popped up in the plex streams plugin... I've since re-enabled unraid connect remote access and it's still working. Placebo maybe? who knows. It's working again so if it stops working, ill repeat what I did and see if that fixes it or not.

Edit: That was it, it's not plex's remote access, it's the Unraid Connect Plugin remote access... Disabling this fixes it. It works just fine when unraid connect remote access is set to disabled.

It outputs the same thing. {"serverList":{"2311dbbb86d3f69573340d3a23226a06d2e3e8ad":{"Name":"<redacted>","Identifier":"2311dbbb86d3f69573340d3a23226a06d2e3e8ad","Connections":[]}}} also in plex, the secure connections setting is set to “preferred”

{"serverList":{"2311dbbb86d3f69573340d3a23226a06d2e3e8ad":{"Name":”<redacted>","Identifier":"2311dbbb86d3f69573340d3a23226a06d2e3e8ad","Connections":[]}}}

It doesn't load any servers, there are a couple of people up the page having the same issue. For example im running plex in host network mode on IP 10.0.0.2 and port 32400 and the picker is just blank, never loads my plex server. It used to work until I upgraded to 6.12.11 (token removed for privacy, it does load a plex token) Edit: Im just wondering if Im missing something obvious?

Im bumping this due to the bug where servers do not load on Unraid 6.12.xx. Any resolution on this issue?

My guess is that no data under /…/…/media/TV Shows was written to the array so it sonarr didn’t yet see the full array size. It was only looking at the SSD by itself. once a folder was created on the array, it probably picked up on the fact the storage size was now SSD+Array

Yes sonarr and radarr have an import function. It will rename and move the files when they’ve finished downloading. You shouldn’t have to do anything manually. the *arrs apps also have batch renaming for already imported files.

You would use the “unbalance” plugin but typically there’s no need to balance drives.

You tell the *arrs what to rename them on import. *arrs > settings > media management

Unraid biggest selling feature is being able to mix disks from all types of sizes and manufacturers.

Click the little icon to the left of “Disk1” it will let you browse the contents on that disk. alternativly, if you ssh into your machine or click on the webgui terminal, you can navigate through /mnt/user or /mnt/disk1 (never copy data from/to /mnt/user to another disk)

Use the array as unraid intends but you can have as many “cache pools” as you want. Cache pools can be just about any configuration you want them to be in. Just Disks, RAID0, RAID1, RAIDZ, ZFS MIRROR, etc each cache pool can be its own setup too. Pool1 can be 4 SSDs that aren’t in any kind of RAID. Pool2 can be a RAID1 pool.

Do you have "Cache Dirs" plugin installed?

I think I found the culprit maybe? nobody 19635 0.8 2.3 1609296 388820 ? Ssl 10:06 5:39 python3 -m homeassistant -c /config Before and After stopping HA docker and restarting unraid mDNS: After, clearly homeassinstant is what I think is the source for the mDNS conflicting issue

@JorgeB I went ahead and disabled IPv6 and that seemed to have worked however, It's not the most ideal solution as it doesn't fix the underlying cause. Here's some more log from yesterday before I shut IPv6 off. I'm thinking whatever is causing the WARNING is the cause for the log spam. The only docker I can think of that would maybe cause this is pi-hole? Do you see anything else in my diags pointing to a culprit? Mar 9 22:11:34 Tower emhttpd: Starting services... Mar 9 22:11:34 Tower emhttpd: shcmd (265570): chmod 0777 '/mnt/user/docker' Mar 9 22:11:34 Tower emhttpd: shcmd (265571): chown 'nobody':'users' '/mnt/user/docker' Mar 9 22:11:34 Tower emhttpd: shcmd (265574): /etc/rc.d/rc.avahidaemon restart Mar 9 22:11:34 Tower root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Mar 9 22:11:34 Tower avahi-daemon[17101]: Got SIGTERM, quitting. Mar 9 22:11:34 Tower avahi-daemon[17101]: Leaving mDNS multicast group on interface br0.IPv6 with address fdf0:6a76:b27e:1:ec4:7aff:fe64:9e01. Mar 9 22:11:34 Tower avahi-daemon[17101]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.4.100. Mar 9 22:11:34 Tower avahi-dnsconfd[17111]: read(): EOF Mar 9 22:11:34 Tower avahi-daemon[17101]: avahi-daemon 0.8 exiting. Mar 9 22:11:35 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Mar 9 22:11:35 Tower avahi-daemon[26563]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Mar 9 22:11:35 Tower avahi-daemon[26563]: Successfully dropped root privileges. Mar 9 22:11:35 Tower avahi-daemon[26563]: avahi-daemon 0.8 starting up. Mar 9 22:11:35 Tower avahi-daemon[26563]: Successfully called chroot(). Mar 9 22:11:35 Tower avahi-daemon[26563]: Successfully dropped remaining capabilities. Mar 9 22:11:35 Tower avahi-daemon[26563]: Loading service file /services/sftp-ssh.service. Mar 9 22:11:35 Tower avahi-daemon[26563]: Loading service file /services/ssh.service. Mar 9 22:11:35 Tower avahi-daemon[26563]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Mar 9 22:11:35 Tower avahi-daemon[26563]: *** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Mar 9 22:11:35 Tower avahi-daemon[26563]: Joining mDNS multicast group on interface br0.IPv6 with address fdf0:6a76:b27e:1:ec4:7aff:fe64:9e01. Mar 9 22:11:35 Tower avahi-daemon[26563]: New relevant interface br0.IPv6 for mDNS. Mar 9 22:11:35 Tower avahi-daemon[26563]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.4.100. Mar 9 22:11:35 Tower avahi-daemon[26563]: New relevant interface br0.IPv4 for mDNS. Mar 9 22:11:35 Tower avahi-daemon[26563]: Network interface enumeration completed. Mar 9 22:11:35 Tower avahi-daemon[26563]: Registering new address record for fdf0:6a76:b27e:1:ec4:7aff:fe64:9e01 on br0.*. Mar 9 22:11:35 Tower avahi-daemon[26563]: Registering new address record for 2604:2d80:968e:b300:ec4:7aff:fe64:9e01 on br0.*. Mar 9 22:11:35 Tower avahi-daemon[26563]: Registering new address record for 192.168.4.100 on br0.IPv4. Mar 9 22:11:35 Tower emhttpd: shcmd (265575): /etc/rc.d/rc.avahidnsconfd restart Mar 9 22:11:35 Tower root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Mar 9 22:11:35 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Mar 9 22:11:35 Tower avahi-dnsconfd[26572]: Successfully connected to Avahi daemon. Mar 9 22:11:35 Tower avahi-daemon[26563]: Server startup complete. Host name is Tower.local. Local service cookie is 2084411687. Mar 9 22:11:36 Tower avahi-daemon[26563]: Registering new address record for fd91:1ac0:7f43:c44:ec4:7aff:fe64:9e01 on br0.*. Mar 9 22:11:36 Tower avahi-daemon[26563]: Service "Tower" (/services/ssh.service) successfully established. Mar 9 22:11:36 Tower avahi-daemon[26563]: Service "Tower" (/services/sftp-ssh.service) successfully established.

I’ve searched the forums, Reddit, Google, etc. I’m struggling what’s causing avahi daemon to spam my logs with “withdrawing/registering” over and over. there are no host-name conflicts that I am aware of on my network. nothing else is using .local TLD either. there are no static IPv6 addresses assigned to any of my devices. It’s even set to automatic/dhcp in my network settings on unraid. attached are the diagnostics. tower-diagnostics-20240309-1118.zip

Well that's to be expected. You've set your share to be moved off of your pool onto the array. No idea why you'd want to snapshot an empty dataset that's never going to have data in it? Edit: @Iker I have a QOL suggest for the snapshot admin pop-up window. Instead of the pop-up window, can the snapshots just expand below the selected dataset? I have issues with the pop-up window on small screens where the width is very narrow requiring horizontal scrolling even when using landscape orientation.

@MilkSomelier Stop docker service entirely, enable destructive mode in ZFS Master settings, click the action button > Convert to Dataset, then you also need to convert each individual appdata folder too or else you won't be able to restore individual docker appdata.