tdcnzb Posted April 11, 2021 Share Posted April 11, 2021 (edited) I have run into an odd issue after updating my Unraid servers from 6.8.3 to 6.9.2. The issue presented as my secondary server failing to mount the remote share I use in my backup script and has been traced to the name 'SERVER' resolving to an incorrect ip address 172.30.1.100. Primary Server Name = SERVER Primary Server IP = 192.168.1.100 Secondary Server Name = BACKUP Secondary Server IP = 192.168.1.110 root@backup:~# ping SERVER PING SERVER (172.30.1.100) 56(84) bytes of data. --- SERVER ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1005ms If I modify the mount commands to use the ip address instead of the server name it works properly. Originally I thought this was an issue with Unassigned Devices but can duplicate the behavior with krusader as well. Other devices on my network can ping by name successfully and there are no 172.30.x.x addresses in my environment. backup-diagnostics-20210411-1555.zip Edited April 11, 2021 by tdcnzb Add Diagnostics Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.