Jump to content

phoenixcoder

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About phoenixcoder

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Found the problem when unraid would boot without the sata cables from the SAS backplate. Turns out, I had to activate the SAS controller on the motherboard
  2. I tried to upgrade my unraid server by replacing the motherboard. Replugged all the hard disks and moved the USB key to the new motherboard. It gets hung on this screen So I tried the advice here to take a backup of the /config, flash the USB then copy the /config back but it got hung on the same screen. Thinking it is a hardware issue, I reflashed the USB using the USB maker and did NOT copy the /config directory, this time it booted up fine and got a login prompt so the hardware and unraid are compatible so far However, after unplugging it, copying the /config again, then attempting to boot, it got hung at the screen above again Any assistance will be appreciated Thanks
  3. Wow! I totally did not expect that would work # docker network ls NETWORK ID NAME DRIVER SCOPE 6e05b4103d51 br0 macvlan local 4619d293ec0b bridge bridge local bb9929d48bc0 host host local 19eea3a1aa0b none null local THANK YOU!
  4. Tried that, all I see is this: The IPv4 looks fine but no way to bridge that network (macvlan) to IPv6 There is no way to add a network and even with those IPv4 and IPv6 selected, I only have bridge, host, none in my drop down for docker containers as seen below And per your original reply "Host and Bridge networks use IPv4 only." There is something missing
  5. I had some success but ran into a different issue Could not find a way to create the macvlan in the gui so I ran a slightly different version than the command above which is: docker network create -d macvlan \ --ipv6 \ --subnet=192.168.11.0/24 \ --subnet=2002:c0a8:0b00::/48 \ --gateway=192.168.11.1 \ -o parent=br0 \ --ip-range 192.168.11.5/27 \ -o macvlan_mode=bridge macvlan The reason is my local LAN range is 192.168.11.0/24 and the gateway is 192.168.11.1. Since my DHCP server assigns IPs from 192.168.11.100 to 192.168.11.149 and since I didn't want any IP collisions with the docker network, I went with ip-range 192.168.11.5/27 which has a Start IP of 192.168.11.0 and End IP of 192.168.11.31 When I assign the docker containers that macvlan network, it works and the docker containers surprisingly have perfect IPv4 and IPv6, that also pass the IPv6 test at https://test-ipv6.com/ The Problem: If I reboot the unraid, I lose the above network and have to re-run the command above and re-assign the docker containers that macvlan network If there a way to make it persistent? Thanks
  6. Thank you for your response, can you point me to a guide on how to set up macvlan on unraid. Is it as simple as the one mentioned here? For example: $ docker network create -d macvlan \ --subnet=192.168.216.0/24 --subnet=192.168.218.0/24 \ --gateway=192.168.216.1 --gateway=192.168.218.1 \ --subnet=2001:db8:abc8::/64 --gateway=2001:db8:abc8::10 \ -o parent=eth0.218 \ -o macvlan_mode=bridge macvlan216
  7. I have an issue that docker doesn't have IPv6, this is one of my containers # docker inspect 433692b3e691 | grep -i IPv6Gateway "IPv6Gateway": "", "IPv6Gateway": "", Looking at my docker networks, I see: # docker network ls NETWORK ID NAME DRIVER SCOPE 224d0c66e092 bridge bridge local bb9929d48bc0 host host local 19eea3a1aa0b none null local THE BRIDGE # docker inspect 224d0c66e092 | grep -i IPv6 "EnableIPv6": false, "IPv6Address": "" "IPv6Address": "" "IPv6Address": "" "IPv6Address": "" THE HOST # docker inspect bb9929d48bc0 | grep -i IPv6 "EnableIPv6": false, "IPv6Address": "" "IPv6Address": "" "IPv6Address": "" However on the GUI and the command line, the bridge is enabled and has IPv4+IPv6 and the tower itself has an IPv6 address Any help enabling docker to have IPv6 instead of "EnableIPv6": false will be appreciated
  8. I have an issue that docker doesn't have IPv6, this is one of my containers # docker inspect 433692b3e691 | grep -i IPv6Gateway "IPv6Gateway": "", "IPv6Gateway": "", Looking at my docker networks, I see: # docker network ls NETWORK ID NAME DRIVER SCOPE 224d0c66e092 bridge bridge local bb9929d48bc0 host host local 19eea3a1aa0b none null local THE BRIDGE # docker inspect 224d0c66e092 | grep -i IPv6 "EnableIPv6": false, "IPv6Address": "" "IPv6Address": "" "IPv6Address": "" "IPv6Address": "" THE HOST # docker inspect bb9929d48bc0 | grep -i IPv6 "EnableIPv6": false, "IPv6Address": "" "IPv6Address": "" "IPv6Address": "" However on the GUI and the command line, the bridge is enabled and has IPv4+IPv6 and the tower itself has an IPv6 address Any help enabling docker to have IPv6 instead of "EnableIPv6": false will be appreciated
  9. Was able to fix this by clear out my browser cache (ctrl-F5) which then showed me that it's registered and I was able to replace the key
  10. Two more pieces of info that might help zone in on the issue I was able to boot from my original USB A and see this: But when I go to the tools->Registration, I see this: Two observations, the Registration goes to "Trial 27 days remaining" and the Uptime is suddenly 15 hours while as you can see in the first picture, it's 13 minutes. ---------------------------------------- Also when I boot from USB B (that was written over by a new backup after registering), even though it detects the new GUID, the registration page show exactly like above: Not registered Doesn't give me the option where the GUID is mismatched and allow me to replace it My hypothesis is that the OS on USB A is stuck in limbo where it is actually registered but also not registered in the Tools->Registration
  11. Hello, I was recently trying out your product Was using the trial on a USB flash (will call that "USB A"), decided to switch to a better USB (will call that "USB B") I followed the instructions to change the USB here So now I am booted from USB B and it got the missing registration key, which I then clicked buy key However, when I used the URL to install the key it gave me "invalid key" So I am stuck on USB B with an "Invalid key" and I don't know how to get around it Any assistance will be appreciated Thanks