stlrox

Changed Status to Solved

It's been more than one week with 11 containers running. I don't know why ipvlan didn't work before, but after making the change, system is stable. root@Tower:/mnt/user/appdata# dnetworks NETWORK ID NAME DRIVER SCOPE 9dd32ab44a95 br0 ipvlan local 7bcb1926472d bridge bridge local 53da3ff4205d host host local 92ef905a9981 mosquitto_default bridge local 0f34678ea99b none null local root@Tower:/mnt/user/appdata# root@Tower:/mnt/user/appdata# docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 11 11 4.929GB 7.335MB (0%) Containers 11 11 103.8MB 0B (0%) Local Volumes 3 1 0B 0B Build Cache 0 0 0B 0B

How did you figure out the following from 'docker network ls' command? Just curious "it does confirm macvlan was enabled with bridging" I've installed a few containers (3 - host, 3 - bridge). I will hold off on adding more until tomorrow. 🤞

That's odd. I remember I switched network type to 'ipvlan'. I restarted the server and noticed 'Docker Service failed to start.' error message when I browsed to 'Docker' tab. I changed network from 'macvlan' to 'ipvlan' and rebooted the server. But same error message. I know Docker image is corrupted. I deleted vdisk file and created again with 'ipvlan' network type. root@Tower:~# docker network ls NETWORK ID NAME DRIVER SCOPE 9dd32ab44a95 br0 ipvlan local 7bcb1926472d bridge bridge local 53da3ff4205d host host local 0f34678ea99b none null local Before I manually add containers (via Apps -> Previous Apps), is there anything specific I need to keep in mind? Also, yesterday whenever I tweaked something in a container settings, the page took forever to load. Here are the network types from yesterday. I have no idea why there are two networks for mosquitto. root@Tower:~# docker network ls NETWORK ID NAME DRIVER SCOPE af663fcb60e1 br0 macvlan local e5ba80db4137 bridge bridge local 8a2b4457487a host host local b20c276505ed mosquitto_docker-compose_default bridge local 49e8289e979d mosquitto_docker_compose_default bridge local 4ff659169f3c none null local 5c6c047a2ff6 utils_default bridge local

Suddenly MQTT container stopped working. There is no information in the logs. This container worked without any issues for the last two years. Recently I upgraded to OS 6.10.3. I verified directory path and there is no issue with the permissions. I tried to restart this several times but didn't produce any helpful information in the logs. I appreciate any tips for solving this issue.

I have Dell T30 Server with default config (1 TB) which I use for Home Assistant and other containers. I bought a new 4 TB Western Digital Red Plus SSD drive which I would like to add to the array. I didn't install any parity drives. I don't have that much data. Few questions. 1. How do I transfer contents of 1 TB to 4 TB drive? 2. If the above is possible, how do I setup 1 TB drive as parity drive for now (later I will buy another 4 TB drive to upgrade that). Thank you

For some reason, 'imagemagick' software is not available within 'Home Assistant' container. I need this software for one of Home Assistant components to run. I have added following script to install this software whenever 'HA' updates gets installed. (for now, I want to install when the container is running). But this script is not working. I used Erik Kristensen's 'check_docker_container.sh' script as a base for this. #!/bin/bash # Author: Erik Kristensen # Email: [email protected] # License: MIT # Nagios Usage: check_nrpe!check_docker_container!_container_id_ # Usage: ./check_docker_container.sh _container_id_ # # Depending on your docker configuration, root might be required. If your nrpe user has rights # to talk to the docker daemon, then root is not required. This is why root privileges are not # checked. # # The script checks if a container is running. # OK - running # WARNING - restarting # CRITICAL - stopped # UNKNOWN - does not exist # # CONTAINER=$1 CONTAINER="home-assistant" COUNT=300 if [ "x${CONTAINER}" == "x" ]; then echo "UNKNOWN - Container ID or Friendly Name Required" exit 3 fi if [ "x$(which docker)" == "x" ]; then echo "UNKNOWN - Missing docker binary" exit 3 fi docker info > /dev/null 2>&1 if [ $? -ne 0 ]; then echo "UNKNOWN - Unable to talk to the docker daemon" exit 3 fi RESTARTING=$(docker inspect --format="{{.State.Restarting}}" $CONTAINER) if [ "$RESTARTING" == "true" ]; then echo "WARNING - $CONTAINER state is restarting." # Wait five minutes # echo COUNT $count sleep 300 # exit 1 else now=$(date) echo $now # Wait five minutes # echo COUNT $COUNT echo "SLEEP FOR 60 SECS" #sleep 60 echo "Installing ImageMagick" echo $CONTAINER #RUN apk add ImageMagick docker exec -i $CONTAINER apk add ImageMagick #apk add -no-cache imagemagick echo "Completed installing of imagemagick" #echo "WARNING - $CONTAINER state is NOT in restarting mode." exit 1 fi STARTED=$(docker inspect --format="{{.State.StartedAt}}" $CONTAINER) NETWORK=$(docker inspect --format="{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}" $CONTAINER) /usr/local/emhttp/webGui/scripts/notify -i normal -s "OK - $CONTAINER is running." -d "StartedAt: $STARTED" When I tried to run this script manually, I get this error message. What am I missing in the script? Script location: /tmp/user.scripts/tmpScripts/install imagemagick/script Note that closing this window will abort the execution of this script Sat Dec 12 15:48:30 CST 2020 SLEEP FOR 60 SECS Installing ImageMagick home-assistant ImageMagick (missing): ERROR: unsatisfiable constraints: required by: world[ImageMagick] Completed installing of imagemagick

I got a new NIC and disabled onboard NIC. Everything worked great except for couple of docker containers (Pi-Hole and cops). I had to fix the network type (br0) for these containers to make them work.

It has four slots. https://www.dell.com/support/manuals/en-us/poweredge-t30/pet30_om/expansion-card-installation-guidelines?guid=guid-8ad95c18-83ce-4e26-90d7-34a3637ed22f&lang=en-us How about this one? https://www.newegg.com/intel-expi9301ctblk/p/N82E16833106033?Item=9SIA4RE8NV1471

Nope. I notice lights blink only once when I plug in and that's it. When I ran Dell diagnostics, there were no issues and all tests passed. This NIC is integrated to the motherboard. Looks like I have to get a new network card. How do I find out which network card is compatible with Dell T30?

I started 'System Diagnostics' via Boot manager to figure out any issues with the system.

There is only one ethernet port on T20. That's what I thought regarding NIC. Is there anyway to confirm that NIC is dead for sure? I thought cable company's outside equipment would suppress any weather related spikes. Btw, TP-link unmanaged router is not working. But Google Wifi router is working fine after I did the factory reset.

Last week I had a power outage due to the weather and for some reason, my cable router went kaput. I got a replacement router and now all of sudden my server couldn't connect to the network. I get 'Interface Ethernet Port 0 is down. Check cable' error message. My connection is like this. router -> Google Wifi router -> TP-Link router --> ethernet --> Server (unraid) I switched ethernet cables but the same issue and I tried connecting the cable from different places (directly from cable router and Google Wifi router) I attached diagnostics zip file. Could someone figure out this issue? tower-diagnostics-20201128-1403.zip

Aug 14 14:50:40 Tower root: Fix Common Problems Version 2019.06.30a Aug 14 14:50:42 Tower root: Fix Common Problems: Warning: Plugin community.applications.plg is not up to date Aug 14 14:50:42 Tower root: Fix Common Problems: Warning: Plugin rclone.plg is not up to date Aug 14 14:50:42 Tower root: Fix Common Problems: Warning: unRaid OS not up to date mounted by Unassigned Devices, but they are not mounted with the slave option ** Ignored Aug 14 14:50:50 Tower root: Fix Common Problems: Error: Out Of Memory errors detected on your server I am running unRaid OS 6.7.1 I attached the log files for experts to research. tower-diagnostics-20190814-1950.zip