CAL37

@bmartino1 Thank you for this, I forgot that I had to use docker network connect to add the docker to the network. I hadn't done it in so long and not sure how that container dropped from my br0 network

I am having a very weird issue. I have a docker container that is on the br0 network that I specify a local LAN address 192.168.10.125 and trying to communicate with another docker container using a custom docker network I created 172.18.0.16 which to my understanding would just be the Unraid server ip 192.168.10.50 and port number. When I go to the console for the container on 192.168.10.125 I can't ping ping the unraid server 192.168.10.50, but for the container 172.18.0.16 I can ping the unraid server 192.168.10.50. In theory there on the same IP range 192.168.10.x and I can ping any other ip address on 192.168.10.x, but I can't ping the unraid server. Any ideas what this could be?

Your configuration doesn't look complete and I think the port might be wrong. I was able to get mine up and working following this video:

My Unraid keeps rebooting and I have no idea why. Looking at the logs it seems like its loosing connection to the network? I tried too look up the errors saw maybe the UDP buffer is maxed out, but not sure how to resolve that. I've also attached the diagnostic log if anyone could assist. Sep 26 13:38:46 Thunder rsyslogd: omfwd/udp: socket 5: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Sep 26 13:38:46 Thunder rsyslogd: omfwd: socket 5: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Sep 26 13:38:46 Thunder rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Sep 26 13:38:46 Thunder rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] thunder-diagnostics-20230926-1341.zip

I was thinking it might be hardware too... I'll try doing that. Thank you for looking at the logs!

@JorgeB Just froze up again. Here are the syslogs and diagnostics thunder-diagnostics-20230311-1035.zip syslog-192.168.10.50.log

For the past few days my Unraid server has become unresponsive at random times. I can't connect to the GUI and can't ping it either. The only way to get it back online is a hard reboot. I originally thought it was my Home Assistant VM since my home automations stopped working and rebuilt the VM, but still the same issue so makes me believe it's something else. My first thought is check the logs (Tools > System Logs), but I only see events when Unraid comes back online. Unraid has been solid for the past year and I haven't installed anything new recently. What else can I do?

Maybe try a different USB port? When I run the command I can my sonoff 3.0 and my combo Zwave/Zigbee dongle.

I am trying to modify some config files from the appdata folder and i'm accessing it from my windows machine. I have a user that has read/write to that share, but I still am unable to edit the files. I have tried changing the security to Public as well, but no luck. Any idea what this could be?

Thank you

Movers finally got done so close to 419GB free on the cache now 😀. Makes since why it was not moving because I have VM running Blue Iris that records video to that security drive which is a WD Purple drive. I currently only have this WD purple drive in my array and I allocated a second VDisk that points to this array for the VM, but I put a max of 3TB so maybe I should of not used all of it so I could store other things? I was thinking that I keep the VDISK that has the OS installed on domain for speed on the VM. The only other VM I will have is a linux one running Home Assistant which shouldn't take too much space. The rest will be docker containers. Testing proof of concept that I can run everything on one machine right now since I'm using two older pc's, but so far so good before. Definitely wish I had known about unraid before I purchased this Dell Precision so I could use it as a NAS too. I'm planning on adding some additional disk to the array and maybe another SSD for cache. They don't have to be the same size right? Same for the parity?

thunder-diagnostics-20220314-0945.zip

Do I just post the whole zip file? Sorry I am very new to this and mainly using this to run some VM's and docker containers. Eventually may use it for storage.

Ahhh should of known! Just for my future reference, do I need to do this manually every time or is there a way to schedule it for my other shares that use the cache?

I just changed it back to use the cache pool and the VM running my surveillance is down. How do I manually run the mover?