-
CooperKC started following Supermicro chassis & LSI 9300-8e PCI-Express 3.0 HBA
-
Supermicro chassis & LSI 9300-8e PCI-Express 3.0 HBA
I currently have a custom built unRAID server with internal drive bays, but it's a pain in the ass to add or remove drives. Now I have the opportunity to buy these 2 components pretty cheap, but wanted to verify if these 2 pieces will work together in unRAID and what else I may need or expect. Supermicro SuperChassis (216BE1C-R741JBOD) 2U 24 Bay JBOD SAS 12Gb/s Storage Chassis LSI 9300-8e PCI-Express 3.0 SATA / SAS 8-Port SAS3 12Gb/s HBA - Single (Avago) Thanks in advance for your help.
-
[Support] omada-controller
Thanks for the assist. It turns out when I changed my DNS to utilize PiHole, it messed things up with my UnRAID server. Thanks again!
-
[Support] omada-controller
Interesting... As it turns out I can't. Time to look and see what's going on with DNS.
-
[Support] omada-controller
Greetings, Having trouble with the Omada Controller container. It fails to pull the image. I get the following (see below). Any idea what could be causing this? ---------------------------------------------------------------------------------------------------------------------------------------- Pulling image: mbentley/omada-controller:latest TOTAL DATA PULLED: 0 B Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='Omada-controller' --net='host' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'MANAGE_HTTPS_PORT'='18043' -e 'MANAGE_HTTP_PORT'='18088' -e 'PORTAL_HTTPS_PORT'='18843' -e 'PORTAL_HTTP_PORT'='18088' -v '/mnt/cache_nvme_apps_docker/appdata/Omada Controller/data/':'/opt/tplink/EAPController/data':'rw,slave' -v '/mnt/cache_nvme_apps_docker/appdata/Omada Controller/work/':'/opt/tplink/EAPController/work':'rw,slave' -v '/mnt/cache_nvme_apps_docker/appdata/Omada Controller/logs/':'/opt/tplink/EAPController/logs':'rw,slave' 'mbentley/omada-controller' Unable to find image 'mbentley/omada-controller:latest' locally Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.10.20:53: read udp 192.168.10.10:52651->192.168.10.20:53: i/o timeout The command failed.
CooperKC
Members
-
Joined
-
Last visited