asnt

Thank you!

What did you end up doing? I have a very similar array and am trying to find the best way to replace two old 3tb disks.

It worked! Thank you!

I updated my Tailscale container yesterday, and after it was done, the container was not on my list of Docker containers. I tried adding it again, but it failed. Here is the command execution: docker run -d --name='Tailscale' --net='host' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="M93p" -e HOST_CONTAINERNAME="Tailscale" -e 'UP_FLAGS'='--advertise-exit-node' -e 'ENABLE_DOWNLOADS'='TRUE' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/deasmi/unraid-tailscale/master/logo.png' -v '/mnt/user/appdata/tailscale':'/state':'rw' -v '':'/downloads':'rw' --cap-add=NET_ADMIN --hostname=unraid 'deasmi/unraid-tailscale:latest' docker: invalid spec: :/downloads:rw: empty section between colons. See 'docker run --help'. Any ideas in what can I do to try to get it running again? Thank you

My server has been stable for 6 days now after switching to ipvlan. Thank you for the help! I will change the post to solved.

Thank you! I switched to ipvlan and hopefully this willl fix the crashes.

After 3 days, another crash. Here is the syslog and diagnostics after the crash. Do you see something that stands out to be the reason for the crash? thanks! syslog-192.168.50.156.log m93p-diagnostics-20230405-0926.zip

I didn't have a crash after I turned on the syslog server. I did update the plex docker two days ago, so if it was a problem in this docker, it is fixed. I'll update here if something changes. I hope you can identify the problem with your server.

Thank you! I just enabled it (unfortunately not fast enough, since I had another crash before reading your reply). Thanks, that's good to know. I have the official Plex version, I'll keep it running until I have another crash, to see if I can get it logged as per JorgeB's suggestion. I might stop Plex after and see if the server is stable again. I am getting weird messages from Unraid that my docker size is over 70% and than it returns to normal. I used to get this messages when I was updating a docker, but never got it when the server is idle.

I've been dealing with my server crashing several times last month. At first, I didn't pay much attention since my server is usually stable, and I never had any problems with it. But since it started crashing again and again, I started looking into what could be the reason. Today I had another crash and decided to look at the logs. I saw a lot of errors that, unfortunately, I don't know what it means. Can someone help me? The crash today resulted in an unclean shutdown, and I am currently in the middle of a parity check. I tested my all my drives and smart data came back OK. I have attached the diagnostics files. The errors I mentioned are shown around the 18:29:18 timestamp of the syslog file. Thank you m93p-diagnostics-20230327-1842.zip

Here is an update: Asrock has a tool to update the MAC Address on their motherboards when something like this happens. I'm not sure what is the rules around external links here, but a quick google search for "Asrock Mac Tool" will take you there. I did this procedure and updated the BIOS. Unraid is now recognizing both ethernet ports with different MAC addresses, and I did test bonding the two ports and it worked. When there is just one ethernet cable connected, even if I set bonding to "no", Unraid stills shuts down the second port. All is working, so for now I will consider this done. Thanks for all the help!

Thanks! I'll try that and report back. I was planning to update the BIOS anyway because the version that I'm using is pretty old.

Now it's not renaming eth1 to eth117 anymore, but it is still down: Attached is the diagnostics from the last boot. m93p-diagnostics-20200504-1046.zip

Here it is: m93p-diagnostics-20200504-0909.zip

Hi All, I'm having a hard time understanding what is happening with one of my Ethernet ports. My motherboard is an Asrock Xs X99 and has dual gigabit LAN ports. I had been using the my motherboard LAN port 2 (eth117 - in the picture) since I upgraded the hardware in my Unraid server, but after the last shutdown when I changed my video card from PCI slot 2 to PCI slot 1, every time the server comes up again it shuts the port down. The port is enable in the BIOS and the lights (green and yellow) come up when I plug the cable in, but it shuts down, with no lights, during Unraid boot. I know the port is not bad, because I tested booting a Ubuntu distro through an USB stick and all network features were working fine. Has anyone had a similar problem? Is there a way that I can test the port or try to bring it up within Unraid? thanks!