dandus

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by dandus

  1. I dont think you have to the share. It pops up in Mac's Time Machine by itself. I think once Avahi has listed the share, Time Machine will pick it up. Have you checked from the log that if Avahi reload after you have changed the config file?
  2. Yes. It works perfectly. Yet, I have not digged into how to allow more than one one TimeMachine share. That is, if I want to allow more than one Mac backing up to my UnRAID, I need another share. How would the Avahi configuration file be like for more than one share.
  3. I have also encountered my Mac Time Machine cannot find the Time Machine share I created based on the UnRAID wiki ( this ). I have done some googling on how others (ie. not UnRAID way) are setting up SMB Time Machine share. I come across this article that uses Samba and Avahi to setup Time Machine share on Raspberry Pi. I compare the UnRAID avahi configuration file for Samba (ie. /etc/avahi/services/smb.service) against that being suggested in the Raspberry Pi article. I have tested adding the third <service></service> of type "_adisk._tcp" as in the Raspberry article. It works and my share can now be found by Time Machine I am sharing my amended smb.service below. My Time Machine share is called "TM-MacMini-Late2012". FYI, I did not include "<txt-record>sys=adVF=0x100</txt-record>" in the third <service></service> as in the Raspberry article. It is because my Time Machine share is "public" to start with. Yet, when I ask Time Machine to use this share, it still ask for credential. I guess there is global setting asking for credential anyway. <!-- Generated settings: --> <service-group> <name replace-wildcards='yes'>%h</name> <service> <type>_smb._tcp</type> <port>445</port> </service> <service> <type>_device-info._tcp</type> <port>0</port> <txt-record>model=Xserve</txt-record> </service> <service> <type>_adisk._tcp</type> <port>0</port> <txt-record>dk0=adVN=TM-MacMiniLate2012,adVF=0x82</txt-record> </service> </service-group>
  4. I have two NICs. They are IP 192.168.1.247 and 192.168.1.248 When mapping containers to the host ports, it will always be mapping to ports on 192.168.1.247. How can I map the containers to ports on 192.168.1.248? I want to map some containers to 192.168.1.247 and some to 192.168.1.248. eth0 MAC address: xx:xx:xx:xx:xx:xx Enable bonding: No Enable bridging: Yes Bridging members: eth0 Interface description: IP address assignment: Automatic IP address: Network mask: 255.255.255.0 Default gateway: DNS server assignment: AutomaticStatic DNS server: 192.168.1.254 Desired MTU: Enable VLANs: No eth1 MAC address: yy:yy:yy:yy:yy:yy Enable bridging: Yes Interface description: IP address assignment: Automatic IP address: 192.168.1.248 Network mask: 255.255.255.0 Desired MTU: Enable VLANs: No
  5. Just curious, why don't you consider SuperMicro X11SSL-CF? I has 6xSATA and 8xSAS
  6. I dont know if anybody is still reading this thread but id like to add if you dont mind, i tried to Google this case to see if anybody did a build in it as it is a cheap case i was going to go with a fractal case because it had 8 bays but after reading peoples post i will buying the case and i will keep you all updated on a new thread for anybody who is interested I will document how my build goes with any other useful information, i will be buying the case at the end of the month im going to do some more research but will keep you all posted. Regards Callum I have also bought the same case. I am putting in the following (a) 1x iStarUSA BPN-DE340SS (can hold 4 x 3.5 drives) (b) 1 x ICY DOCK MB974SP-2B (can hold 4 x 3.5 drives) © 1 x ICY DOCK MB994IPO-3SB (can hold 1 slim optical + 2 SSD ) I should have three 5.25 space left. Will put in another 4-in-3 cage later for expansion. I intended to go for 5-in-3 cages, but there are rails along the 5.25 drive bays in the case. 5-in-3 cages do not have the ditches and therefore cannot be used. But anyway, my URAID licence allows 12 drives only, I might not need using 5-in-3 cages. I attached a photo without © yet.