amiskell
Members
-
Joined
-
Last visited
-
It hasn't been merged into OpenZFS yet, it's still a pending item. You can follow along on the status at https://github.com/openzfs/zfs/pull/15022, when it gets merged and into a release of OpenZFS it can be included into UnRAID. Work on the feature had stalled for awhile but was picked back up in June with backing from iXSystems to sponsor the work to get it completed and merged into OpenZFS.
-
Docker doesn't/won't do this natively because it doesn't run a DHCP client. Registering hostnames in DNS is a function of the DHCP protocol and since the docker containers don't run a DHCP client, it'll never register those things in DNS. The hostname parameter only allows you to specify the hostname of the container itself otherwise it uses the containers randomly assigned ID number as the hostname (it's useful if you have an application that requires a static hostname).
-
But as I mentioned, not even a manual run appears to be working. It says it completed successfully but there's no backup files generated. I took that diagnostics zip right after attempting a manual run. I suspect that it is actually running at 3am, but just not generating any output of the backup data.
-
scarif-diagnostics-20201205-1408.zip
-
Is there a way to troubleshoot why the backups aren't getting automatically executed? I have the plugin configured to backup everything on Sunday morning at 3am, but nothing appears to be happening during that time. I get no backup files in the defined backup locations or anything. I also tried a manual backup and it says it completed successfully, but still nothing is generated in any of the defined locations (appdata, vm or usbflash).
-
I built a template xml for mariadb from scratch (but still using the lsio docker image) and CA Common Problems is flagging it for having the template URL not as the author intended (although I'm technically the author of the template and the template URL is pointing to my personal GitHub account). It wants me to set the template URL to the one for the mariadb in the CA applications store. It even shows up as being installed from the CA applications store, which it was not, it was hand built by me and stored in my personal GitHub repo. I suspect I might run into this again as for some of my other dockers, I'm building custom template xml files for dockerMan because the ones in CA keep enforcing configuration directives I don't want/need and have deleted from the docker containers and it winds up breaking them occasionally when the containers are updated. Which also leads me to a question, I understand that defining and using a repo directly defined in the Docker tab is the older way for custom templates, but I don't see a way in CA to define a custom or private repo. Is something like that possible?
-
Attempting to open items that open a pop-up window (Logs, Docker Console, VM Console, etc) force a re-authentication into the UI in order to proceed. Upon re-authentication it dumps me back at the main UI screen (within the little pop-up window) and I have to re-navigate to the item I wanted to open in the first place. Client side is macOS Catalina 10.15.6 under Safari scarif-diagnostics-20200804-0955.zip
-
Is anyone seeing an issue with the preclear plugin were it repeatedly puts the preclear icons on the footer of the page? Whenever I run a preclear on a drive, it just keeps adding the icons at the bottom of the footer over and over.
-
I just created a new service file timemachine.service with the following, <?xml version="1.0" standalone='no'?> <!DOCTYPE service-group SYSTEM "avahi-service.dtd"> <service-group> <name replace-wildcards="yes">%h</name> <service> <type>_adisk._tcp</type> <txt-record>sys=waMa=0,adVF=0x100</txt-record> <txt-record>dk0=adVN=macos_backups,adVF=0x82</txt-record> </service> </service-group> Replacing "macos_backups" with the exact name of your TM share. Works fine, problem is that it's not persistent across reboots, etc. So I created it as a file and used the go script to copy it to the /etc/avahi directory at every reboot. Haven't had any issues yet.
-
I'm fairly new to UnRAID and attempting to setup a time machine share for backing up the various macOS systems in the house. I've followed the guide to configure a new share with all the appropriate settings. However, it's not being detected by any of the macOS machines as an available time machine share. I noticed that UnRAID isn't creating an registering a service entry for the time machine share in mDNS. If I query available mDNS services on the network, I see the ssh and smb services that UnRAID is advertising but not the adisk service for time machine. If I manually register the appropriate avahi configuration the share is immediately detected by all macOS clients. However, it's only temporary until the system is restarted which rebuilds the entire /etc/avahi/services directory and undoes the manual registration. It appears that UnRAID is relying on the functionality of Samba to automatically register services with avahi instead of static creating them and Samba is failing to do so for some reason. Since UnRAID already creates static configuration files based on it's own configuration maybe it would be a better solution to get generate the avahi .service file for time machine shares instead of relying on Samba's auto-registration. unraid-diagnostics-20200409-0643.zip
-
It looks like @limetech is relying on Samba to auto-register the time machine service with Avahi's mDNS, but for some reason it's broken/not working. Even running avahi-browse locally on the unraid server doesn't show any _adisk._tcp entries being advertised over mDNS, but I do see the smb and ssh services that UnRAID's local mDNS service is advertising. unraid-diagnostics-20200330-0845.zip
-
mDNS works fine on the network. UnRAID uses avahi for it's mDNS system, the problem appears to be that UnRAID isn't creating the appropriate service configuration in avahi for it to advertise the time machine share via mDNS. As soon as I *manually* create the appropriate avahi service configuration file on the UnRAID server in /etc/avahi/services, the share is instantly available as a time machine target on all macOS systems on the network. So it's one of three scenarios occurring. UnRAID isn't creating the appropriate service configuration files in /etc/avahi/services for Time Machine UnRAID isn't supposed to create the appropriate service configuration files and it's supposed to be manually done, but not covered in the guide. UnRAID handles the mDNS for Time Machine shares in some other way I've not figured out so I'm not troubleshooting properly. I'd suspect it's the first scenario over the second/third scenario as it would make a lot more sense for UnRAID to create all of the appropriate configuration items to support time machine samba shares or maybe handle it in some other way. Maybe when someone at @limetech has a few moments they can chime in and elaborate on how it's supposed to work.
-
I'm fairly new to UnRAID and attempting to setup a time machine share for backing up the various macOS systems in the house. I've followed the guide to configure a new share with all the appropriate settings. However, it's not being detected by any of the macOS machines as an available time machine share. I noticed that UnRAID isn't creating an avahi service entry for the time machine shares in /etc/avahi/services. If I manually create the appropriate avahi configuration file the share is immediately detected by all macOS clients. Is something wrong and UnRAID isn't creating that avahi configuration? I'm assuming that it should be, or does it not? Am I missing some step in the setup to have the shares detected properly?
