SOLVED epair errors in logs/SMB shares missing

[Wisdom]

Hey ya'll,

I've been working through some problems with Transmission over in this thread: https://forums.freenas.org/index.ph...ansmission-with-openvpn-and-pia.24566/page-20
and have encountered some unusual network issues. I've lost sight of my SMB shares over the network, despite my FreeNAS box showing up in the window's explorer. Any time I try to access it, whether directly through an IP/file tree or through the file explorer, it returns a connectivity problem. However, I'm under the impression that the data is still intact, since all the media I have hosted through PLEX, stored on the windows share, is still accessible/playable through PLEX.

Furthermore, my log on the GUI keeps on displaying issues like this, which I suspect has something to do with the process:

Code:

Jan 17 14:16:57 Wisdom_FreeNAS bridge0: Ethernet address: 02:ff:1e:88:3f:00
Jan 17 14:16:57 Wisdom_FreeNAS kernel: bridge0: link state changed to UP
Jan 17 14:16:57 Wisdom_FreeNAS kernel: bridge0: link state changed to UP
Jan 17 14:16:57 Wisdom_FreeNAS kernel: igb0: promiscuous mode enabled
Jan 17 14:16:57 Wisdom_FreeNAS epair0a: Ethernet address: 02:ff:20:00:05:0a
Jan 17 14:16:57 Wisdom_FreeNAS epair0b: Ethernet address: 02:ff:70:00:06:0b
Jan 17 14:16:57 Wisdom_FreeNAS kernel: epair0a: link state changed to UP
Jan 17 14:16:57 Wisdom_FreeNAS kernel: epair0a: link state changed to UP
Jan 17 14:16:57 Wisdom_FreeNAS kernel: epair0b: link state changed to UP
Jan 17 14:16:57 Wisdom_FreeNAS kernel: epair0b: link state changed to UP
Jan 17 14:16:57 Wisdom_FreeNAS kernel: epair0a: promiscuous mode enabled
Jan 17 14:16:57 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 17 14:16:57 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 17 14:17:04 Wisdom_FreeNAS epair1a: Ethernet address: 02:ff:20:00:06:0a
Jan 17 14:17:04 Wisdom_FreeNAS epair1b: Ethernet address: 02:ff:70:00:07:0b
Jan 17 14:17:04 Wisdom_FreeNAS kernel: epair1a: link state changed to UP
Jan 17 14:17:04 Wisdom_FreeNAS kernel: epair1a: link state changed to UP
Jan 17 14:17:04 Wisdom_FreeNAS kernel: epair1b: link state changed to UP
Jan 17 14:17:04 Wisdom_FreeNAS kernel: epair1b: link state changed to UP
Jan 17 14:17:04 Wisdom_FreeNAS kernel: epair1a: promiscuous mode enabled
Jan 17 14:17:04 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jan 17 14:17:04 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jan 17 14:17:08 Wisdom_FreeNAS epair2a: Ethernet address: 02:ff:20:00:07:0a
Jan 17 14:17:08 Wisdom_FreeNAS epair2b: Ethernet address: 02:ff:70:00:08:0b
Jan 17 14:17:08 Wisdom_FreeNAS kernel: epair2a: link state changed to UP
Jan 17 14:17:08 Wisdom_FreeNAS kernel: epair2a: link state changed to UP
Jan 17 14:17:08 Wisdom_FreeNAS kernel: epair2b: link state changed to UP
Jan 17 14:17:08 Wisdom_FreeNAS kernel: epair2b: link state changed to UP
Jan 17 14:17:08 Wisdom_FreeNAS kernel: epair2a: promiscuous mode enabled
Jan 17 14:17:08 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 17 14:17:08 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 17 14:17:10 Wisdom_FreeNAS kernel: pid 7275 (Plex DLNA Server), uid 972: exited on signal 11
Jan 17 14:17:15 Wisdom_FreeNAS epair3a: Ethernet address: 02:ff:20:00:08:0a
Jan 17 14:17:15 Wisdom_FreeNAS epair3b: Ethernet address: 02:ff:70:00:09:0b
Jan 17 14:17:15 Wisdom_FreeNAS kernel: epair3a: link state changed to UP
Jan 17 14:17:15 Wisdom_FreeNAS kernel: epair3a: link state changed to UP
Jan 17 14:17:15 Wisdom_FreeNAS kernel: epair3b: link state changed to UP
Jan 17 14:17:15 Wisdom_FreeNAS kernel: epair3b: link state changed to UP
Jan 17 14:17:15 Wisdom_FreeNAS kernel: epair3a: promiscuous mode enabled
Jan 17 14:17:15 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
Jan 17 14:17:15 Wisdom_FreeNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
Jan 17 14:17:21 Wisdom_FreeNAS kernel: tun0: link state changed to UP
Jan 17 14:17:21 Wisdom_FreeNAS kernel: tun0: link state changed to UP
Jan 17 14:36:39 Wisdom_FreeNAS kernel: arp: 192.168.0.130 moved from 02:ff:20:00:08:0a to d0:50:99:c1:2d:c9 on epair3b

As usual, I've poked around the forum and the internet at large and not seen much that relates to this - if there's more information I could provide, or if there's something obvious I'm overlooking, then please let me know and I'd be happy to supply whatever information I might be missing.

I've double checked my permissions, tried restarting a couple of times, and made sure that there weren't any changes to the network. I'm not sure why all of a sudden this would drop off, so any help someone can supply would be great.

 

[Wisdom]

Alright, so I managed to fix this on my own. For any poor soul that finds their way here after me with a similar problem, here's what I did to address the two problems:

epairXa/b constantly resetting: I believe this stems from an issue with the jails that were housing Transmission, and maybe CouchPotato. I went back through the guides I had been using (also located on the forum) and had to make a few changes to how Transmission was interacting with my network through my VPN.

SMB share missing: made a new dataset through the GUI at the same level as the share I was missing (so they should be like big folders right next to each other, basically), shared the new one, and low and behold, it became a browsable location on my network. Right next to it, in the same larger tank, was the share I was trying to find initially. I just deleted the new dataset and the permissions/visibility stuck with the old one, so I remade my network mapping and it seems fine. Everything is right where I left it, and perfectly readable.

Throughout this whole process, one additional change I made was setting the time clock through actual NTP servers, rather than the built in ones that FreeNAS comes with. Fester's FreeNAS guide has a great little section on this that makes an easy process very straightforward. I'm not sure if that had much of a bearing on the network issues I was having, but if nothing else it ironed out the problems with time stamps that are also showcased in my original post (e.g., events happening very quickly or delayed by minutes, which is inaccurate).

 

[DrKK]

Out of curiosity, the jails in question, they did, or did not, have VIMAGE enabled? I assume they did, based upon the above...

 

[Wisdom]

Out of curiosity, the jails in question, they did, or did not, have VIMAGE enabled? I assume they did, based upon the above...

They did indeed. I've been mucking around with my network settings a lot thanks to the help of the kind folks over in this thread:

https://forums.freenas.org/index.ph...ith-openvpn-and-pia.24566/page-21#post-342035