boxer74

I can't get anthelia to start. I'm pretty sure my config is workable. The container won't start. I'm pulling my hair out with this.

Running 7.2. Always seeing this:

Is anyone able to create an icon for the 45HomeLab HL4?

Thanks for this guide. I've started playing with pangolin as well. Pretty nice software stack. Paired with one of their recommended racknerd VPS's, it costs almost nothing to operate. Curious why you included the section above? Seems this is only needed for "Clients", which I don't quite understand yet.

I noticed this as well. Would be nice to have a borgmatic plugin instead of docker container now that it support zfs hooks to create snapshots prior to backups running. It needs access to the zfs commands so that can't work in a container. If there was a spot in the unraid GUI to edit the config.yaml file that would also be nice.

Can't access SMB shares over tailscale after upgrading to beta 4. Attached is a plugin diagnostic. boxer-tailscale-diag-20241022-171848.zip

Just checking in to see if there is any guidance on this? Thanks.

Hi All, planning out the pools in my new server. I've got 8 disks for the unraid main XFS array, which has dual parity. I also have a pair of nvme drives which will be a zfs pool for docker and vms. I will also likely have a pair of Samsung 2.5" SATA SSD's as a zfs mirror for cache. I have a homelab 15 so lots of room for drives. I want to create a zfs storage pool for my critical shares, such as immich photos, nextcloud data, etc. I have 7x 4TB Ironwolf hard drives available. Some ideas: 1) 2x 2x-drive mirror vdevs 2) 4 disk raidz2 3) 6 disk raidz2 4) 7 disk raidz3. I have about 4TB of data to store on this pool currently. It will grow slowly as I add new family photos. Due to leaving some space for zfs headroom, options 1 and 2 may not give enough longterm capacity for growth, but at least with option 1, it is easy to expand. Since I already own 7 disks, is option 4 outrageous? Let me know your thoughts.

I am already using tailscale through a docker container. It is working as I would like. What is the advantage to the plugin? I suppose it would stay connected even if the array is down. Is that about it?

Any reason to keep using this? Will these features become built-in to 6.12?

Great, thanks!

Will this be updated to work with Unraid 6.12?

Will this be updated to support Unraid 6.12? I tried the new rc2 and this plugin isn't working and may be causing the dashboard to be blank.

How does one join the beta program?

Got this running nicely. Notice that the resolution is maxed at 1600x900 even with a dummy HDMI dongle inserted. Any idea how to increase resolution? This is fine for handhelds, but if I want to play on my 65" 4K TV using Android TV it's not ideal. Thanks.

I think it would be a bit much to expect ZFS feature parity with a project like TrueNAS that has always been ZFS focused for years. I think allowing ZFS in pools is a nice complement to unRAID. Snapshot/replication management would be nice, not only for ZFS but BTRFS as well, but I think the existing LUKS encryption implementation is a suitable compromise for now.

Would be great if ZFS snapshot and replication management was available natively through the web GUI, but I understand if this will be in a later update.

ZFS has been around much longer and is battle tested in production with many businesses. I would trust my data longterm with ZFS more than BTRFS. Other than this, they are pretty similar in terms of feature set.

Exciting to hear some official details on this. I will keep my media on a traditional unraid array but migrate important stuff to a zfs pool (likely a mirror of two 4TB hard drives). The important stuff would be documents, family photos, etc. I will likely also migrate docker and vms to a zfs pool of two nvme disks. Loving the potential here.

Thanks for this container. What a slick setup. While waiting for my new GTX 1650 to arrive (yes, I know - not a high-end card but still better than what's in the Steam Deck and should be fine for streaming), I was about to setup a Windows VM but then saw this. I tested Hades using a Quadro P400 that I have and it actually worked reasonably well. Obviously that card is no good for larger games. I also ordered a Retroid Pocket 3+ to use as a streaming handheld. I find the Deck too large, loud (fan) and with poor battery life, I don't feel the urge to use it. I am more often using my Nintendo Switch but the lack of AAA titles is tough to take at times. I think this could be the ideal setup. It's also nice having a nearly bottomless pit of Unraid storage to hold all the games.

I'm finding the same, but my situation is unique. I'm trying to run unraid as a VM in proxmox. I'd like to use the IPMI plugin to control fan speeds on the host based on the HD temps which are passed through on an LSI HBA via PCI passthrough. Can't get any sensors to show up.

For this to work, I had to add --dns=X.X.X.X to the plex container. What I've now found is that my 'arr containers cannot connect to plex without using an external address. They are on different subnets but allowed by my firewall to communicate. I think this might be due to docker networking. What is the ideal way to set this up. I assume most people just have a single subnet and so don't need to worry about this.

I believe I've enabled settings correctly to add a vlan, configure it in docker settings but when I try to assign a custom ip in that VLAN for my plex container, it has no DNS. I also see an error message during boot that eth0.3 can't be found. Any advice?

Every few hours, I see the following messages in my syslog: Nov 24 09:36:59 ur1 rsync[6282]: connect from 192.168.2.1 (192.168.2.1) Nov 24 09:36:59 ur1 vsftpd[6281]: connect from 192.168.2.1 (192.168.2.1) Nov 24 09:36:59 ur1 rsyncd[6282]: forward name lookup for DreamMachine.localdomain failed: Name or service not known Nov 24 09:36:59 ur1 rsyncd[6282]: connect from UNKNOWN (192.168.2.1) Nov 24 09:37:10 ur1 smbd[6284]: [2021/11/24 09:37:10.442874, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Nov 24 09:37:10 ur1 smbd[6284]: read_fd_with_timeout failed for client 192.168.2.1 read error = NT_STATUS_END_OF_FILE. Nov 24 09:39:22 ur1 vsftpd[7804]: connect from 192.168.6.1 (192.168.6.1) Nov 24 09:39:22 ur1 rsync[7805]: connect from 192.168.6.1 (192.168.6.1) Nov 24 09:39:23 ur1 rsyncd[7805]: forward name lookup for DreamMachine.localdomain failed: Name or service not known Nov 24 09:39:23 ur1 rsyncd[7805]: connect from UNKNOWN (192.168.6.1) Nov 24 09:39:33 ur1 smbd[7807]: [2021/11/24 09:39:33.981382, 0] ../../source3/smbd/process.c:341(read_packet_remainder) Nov 24 09:39:33 ur1 smbd[7807]: read_fd_with_timeout failed for client 192.168.6.1 read error = NT_STATUS_END_OF_FILE. 192.168.2.1 is my LAN gateway IP. 192.168.6.1 is a VLAN gateway IP for the VLAN on my UniFi network that all my docker containers are isolated on. I have firewall rules that prevent communication from the docker VLAN to my LAN. I have WireGuard running on Unraid and setup a static route as well as allowed host communication with docker containers using custom networks as recommended in setup instructions. Any ideas what is causing these constant connection attempts?

Thanks. That's a good script to have running. Any other recommended scripts to schedule when using btrfs? I have scrubs scheduled already.