Tibbar

Just if anybody is wondering the fix was to load vbios.

Replaced GTX 750Ti with RTX 5060 Ti. Had hard time for VM to boot. Finally got it to boot after disabling "NVIDIA Corporation GB206 High Definition Audio Controller" (selecting no sound card in VM). Anybody have a solution or idea how to get HD audio to work in the VM. P.S Unraid v 7.2.1 Nvidia GPU and Nvida HD audio both : "Bind selected to VFIO at boot"

Well... Looks like I'm slowly answering my questions. I'm able to access the dockers in question by changing the "Network Type" to br0 and assigning an unused ip address. Still don't know why bridge mode is not working when it did before.

This is from Syslog. Can someone please explain whats all this entering blocking, forwarding, disabled state is : " Sep 26 21:03:32 Tower kernel: device vethbb043b0 entered promiscuous mode Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered blocking state Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered forwarding state Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered disabled state Sep 26 21:03:33 Tower kernel: eth0: renamed from vethf963646 Sep 26 21:03:33 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbb043b0: link becomes ready Sep 26 21:03:33 Tower kernel: docker0: port 2(vethbb043b0) entered blocking state Sep 26 21:03:33 Tower kernel: docker0: port 2(vethbb043b0) entered forwarding state Sep 26 21:03:35 Tower avahi-daemon[4528]: Joining mDNS multicast group on interface vethbb043b0.IPv6 with address fe80::c884:cbff:fe8f:fdb5. Sep 26 21:03:35 Tower avahi-daemon[4528]: New relevant interface vethbb043b0.IPv6 for mDNS. Sep 26 21:03:35 Tower avahi-daemon[4528]: Registering new address record for fe80::c884:cbff:fe8f:fdb5 on vethbb043b0.*. Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:24 Tower kernel: device veth929c61e entered promiscuous mode Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered forwarding state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:25 Tower kernel: eth0: renamed from veth192b2ad Sep 26 21:07:25 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth929c61e: link becomes ready Sep 26 21:07:25 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:25 Tower kernel: docker0: port 7(veth929c61e) entered forwarding state Sep 26 21:07:26 Tower avahi-daemon[4528]: Joining mDNS multicast group on interface veth929c61e.IPv6 with address fe80::fc1d:29ff:fea6:1f94. Sep 26 21:07:26 Tower avahi-daemon[4528]: New relevant interface veth929c61e.IPv6 for mDNS. Sep 26 21:07:26 Tower avahi-daemon[4528]: Registering new address record for fe80::fc1d:29ff:fea6:1f94 on veth929c61e.*. Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower kernel: veth192b2ad: renamed from eth0 Sep 26 21:07:26 Tower avahi-daemon[4528]: Interface veth929c61e.IPv6 no longer relevant for mDNS. Sep 26 21:07:26 Tower avahi-daemon[4528]: Leaving mDNS multicast group on interface veth929c61e.IPv6 with address fe80::fc1d:29ff:fea6:1f94. Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower kernel: device veth929c61e left promiscuous mode Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower avahi-daemon[4528]: Withdrawing address record for fe80::fc1d:29ff:fea6:1f94 on veth929c61e.

Just tried unplugging and plugging back network cable rebooting my two network switches. That didn't do anything. btw pfsense runs on 4 port network switch that is passed through to VM. tower-diagnostics-20210926-1155.zip tower-syslog-20210926-1554.zip

Hello. Need help. Yesterday I was redoing some network cabling (disconnecting cable, restarting server etc) and today I can not access any of my dockers that run in bridge mode. I can access Plex and HomeAssistent that run in "Host" mode. I didnt do any changes to Unraid until it all stoped working at that point I upgraded Unraid from 6.8.2 to 6.9.2. Same effect, still can not access Rutorrent and Krusader. RuTorrent : 172.17.0.2:51413/TCP192.168.1.122:51413 172.17.0.2:6881/UDP192.168.1.122:6881 172.17.0.2:9090/TCP192.168.1.122:9090 Krusader: 172.17.0.5:6080/TCP192.168.1.122:6080 Both docker are running but I can not access WebUI. btw. I'm running pfsense as my router in "VM"

Hi again. Everything seems to work OK but... When i use Deltacopy client files backed up with it are showing in windows explorer as hidden files. Anybody (Weebotech) have idea what to do? Thanks. Here is what my rsyncd.conf looks like: uid = root gid = root use chroot = no max connections = 4 pid file = /var/run/rsyncd.pid timeout = 600 [backups] path = /mnt/disk1/backups comment = Backups read only = FALSE list = yes [photo] path = /mnt/disk1/photo comments = pictures read only = FALSE list = yes [music] path = /mnt/disk2 comments = music read only = FALSE list = yes

OK. Well we are getting somewhere. Now in Deltacopy client when I use IP address insted of Host Name (Tower) IT WORKS.

Ok, now I get this: root@Tower:/boot/custom/etc# /usr/bin/rsync rsync://192.168.1.122 backups Backups but when I use a name "Tower" I get this: root@Tower:/boot/custom/etc# /usr/bin/rsync rsync://Tower rsync: getaddrinfo: Tower 873: Temporary failure in name resolution rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9]

This is copy and paste from telnet(putty) Tower login: root Linux 2.6.24.4-unRAID. root@Tower:~# whereis rsync rsync: /usr/bin/rsync /etc/rsync.conf /usr/bin/X11/rsync root@Tower:~# ls -l /usr/bin/rsync -rwxr-xr-x 1 root root 276688 Jul 1 19:41 /usr/bin/rsync* root@Tower:~# /usr/bin/rsync rsync://Tower rsync: getaddrinfo: Tower 873: Temporary failure in name resolution rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9 ] root@Tower:~# I just redid rsyncd.conf file but still getting: root@Tower:/etc# /usr/bin/rsync rsync://Tower rsync: getaddrinfo: Tower 873: Temporary failure in name resolution rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9] root@Tower:/etc# Oops forgot this: root@Tower:/etc# echo $PATH /usr/local/sbin:/usr/sbin:/sbin:./:/usr/local/bin:/usr/bin:/bin root@Tower:/etc#

When I type at commend prompt on a server rsync://Tower I get a message: -bash: rsync://Tower: No such file or directory Tower is my UNRAID server name

I do not define these paths. The way I understand it. I define the paths to the target directory with rsyncd.conf file and then deltacopy client fetches it from the server by the name whatever you call it ex. "myshare" [myshare] path = /mnt/disk1/myshare comment = Backup read only = FALSE list = yes but in my case communication with rsync server works but I can not fetch "myshare". Then again I might be wrong

Hi. Weebotech thanks for all the help and patience. Well I do not know what to do next. An error message I get from Deltacopy client is: Executing: rsync.exe -v -rlt -z --delete "/cygdrive/D/MKV/" "/tower::backup/MKV/" building file list ... done rsync: mkdir "/tower::backup/MKV" failed: No such file or directory (2) rsync error: error in file IO (code 11) at /home/lapo/packaging/tmp/rsync-2.6.6/main.c(422) rsync: connection unexpectedly closed (8 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/tmp/rsync-2.6.6/io.c(434) Error in rsync protocol data stream Rsync.exe returned an error. Will try again. This is retry number 1 of 5 My rsyncd.conf file has an entry like: [backup] path = /mnt/disk1/Backup comment = Backup read only = FALSE I've created a directory called "Backup" on disk1 and I'm trying to backup directory called MKV with Deltacopy client on Windows XP machine. Any ideas what to do next? Thanks.

Hi. Me again Am I supposed to make any entry to /etc/inetd.conf file ?

What is a rsyncd.pid file. When I look inside /var/run that file does not exist.