thorzeen

Thanks for the reply. Ok now I get it, that explains somethings. I would be better served putting it on a IDSDM vs a SATADOM. I will look into that before I leap. This has been a long strange trip I do not wish to repeat

Thanks for the reply. I was able to delete /shadow and /smbpasswd and it is asking for my key I am curious as to why it does not automatically transfer when using the WEBGUI

Here is my Diagnostics TIA unraid-diagnostics-20260813-0658.zip

Duh.. Diagnostics incoming shortly

Looking at the "reset your password" involves (for me) taking that "new boot device" (which for me) is the SATADOM. The SATADOM is now part of a zfs pool. I am unable to just login to it on another computer and change the files. I have limited knowledge of zfs pools. I thought importing the zpool would allow me to do that, but I had no luck doing that. I did learn you have to export the zpool back or unraid would stop booting because of a "gap in the pool". Once I did that I am back at unraid booting "having no gap" and I have SSH access.

Thanks for the reply. I know my root password. After changing the boot to SATADOM the the WEBGUI says "Invalid username or password" Trying to log in using iDRAC says "Invalid username or password" Logging in as root SSH and I log right in! So if you would please direct me to the commands needed to fix the WEBGUI login? I wanted to at least turn on the array last night for the wife, but that time has passed What is the command to run Diagnostics and where can I find it after it has ran ? TIA

Ok so what is the SSH command to start the array?? Anyone??

Like the title says. I can boot into the "new unraid" on the SATADOM and can boot into the old USB UNRAID but can not "LOG IN" with any user/password on either (That includes trying to log in with user name root and no password). Put both old USB UNRAID and the SATADOM in a different linux machine. Copied the config directory off the old UNRAID USB. Can not get into the SATADOM to overwrite files. ERROR : wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. Trying to work through this error atm, as I watch the clock waiting for the wife to get home. Any guidance would be appreciated! Ohh and there is also a license key on this.

So every once in awhile I get O.C.D about something and this has turned into just that. I had this running in the post I made on page 2 but i just kept messing with it..some of you know how that goes. Anyway Let me preface this ... This is a docker network on it's own network port separate from the host system. Separate meaning: Unraid host and all network BUT one are under one router and THIS ONE docker network is under a separate switch and router. This is running atm using unraid 6.12.rc6 and Unifi UDMP 3.0.20. IF you are running VM's this is proably not for you. The only thing I really did different is how I created this network vs on page 2 and turning off bridge on both eth0 AND eth1. So first turn off bridging Then I created the network using docker run docker network create -d macvlan \ --subnet=192.168.50.0/26 \ --ip-range=192.168.50.0/27 \ --gateway=192.168.50.1 \ -o parent=eth1 proxy Under the docker settings you see the eth1 network but I did NO configuring left it blank. As I created containers I added --mac-address under "Extra Parameters" and gave them all a static IP UDMP: I let the router handle DHCP and configured it to use the same gateway as above BUT to had out leases from .33 to .62 I also directed the router to use a Pi-Hole I have set up in the network to handle DNS. As I created containers mac-address I configured DHCP reservations and DNS records in the router (even tho pi-hole does the DNS) Reason: UDMP atm floats what it see's. UDMP has had DNS issues from creation so this just kind of locks it in you my not have to do this. I was messing with this in the middle of them upgrading from 1.0.1 to 3.0.20. And of course DNS records in the pi-hole. Thats it works great no errors. Unraid Network Docker-Network Unraid routes Docker container network Docker Dash Have fun!!

I am just curious are you using a custom docker network on a vlan off br0, or on a separate ethernet port ?

Just to be clear "Host access" meaning unraid host?

There's a interesting discussion going on over here about this bugreports>prereleases 6.12.0-rc4 "macvlan call traces found", but not on <=6.11.x - Prereleases - Unraid Basically if your not using bridge (VM's) turn it off on br0 and br1 and eth1 shows up in docker for a custom network on v6.12.0-rc5

Are your NIC's configured for promiscuous mode ?

One thing I have run into with unraid networking is it has a memory. I have not researched this, it might be a bug or it might be a safe guard. I have deleted networks that still call out for dhcp untill I literally shutdown not reboot but shutdown. Clearing arp might help ip -s -s neigh flush all

Ya I am trying to remember I had to bridge something inorder to get it to show up as docker custom network and then it was definitely tied to br0. We are talking about a separate network port controled by a separate router

I had that same problem i just remembered it reading your post. IIRC it has to do how br0 is configured you have to enable bridging? It has to do with how your networks are set up and i also think i had to reboot the server after configured. It seems most of "Unraid Docker" underpinning is tied to br0. It has been a frustrating ordeal to figure it out and make it play nice (docker) with UDMP on something other then br0 and then UDMP changes OS but thats another story PS. UDMP changing OS is a good thing!

I am running JUST br1 network on a UDMP router all other networks are behind a different router. I remember reading that "unraid docker" uses the host netwok (br0) configured DNS server to resolve (I confirmed this by removing br1 dns entry from br0 and it left br1 in the dark) So I started adding --dns Labels are a way docker containers can reach each other using host names (vs IP addresses) when on same network in my case running "Traefik" and "Authentik" containers Docker DHCP allows docker to know which container is on the network thus "hostnames" = labels vs IP addresses. Just an easier way to configure containers that need to talk to each other

I have been using this setup for idk 2 months? I have not had any issues. I am running 6.11.5 Using Unifi UDMP pointing to pihole just for dns. Docker DHCP allows for labels NIC on unraid and UDMP are in promiscuous mode. I add the flag --mac-address <mac address> to every container under Extra Parameters: I also add --dns. I let docker DHCP add the IP address, then i add that to pihole DNS and make it a fixed address in UDMP. Also set the DHCP that UDMP hands out really low like 10 ip's 192.168.x.20 to 30.