ljm42

Administrators
  • Content Count

    1859
  • Joined

  • Last visited

  • Days Won

    8

ljm42 last won the day on September 2 2019

ljm42 had the most liked content!

Community Reputation

245 Very Good

5 Followers

About ljm42

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Personal Text
    the answer to life, the universe, and everything

Recent Profile Visitors

7319 profile views
  1. I'm assuming you are on 6.9.0-rc2? If you hover over the disabled checkbox you should get a tooltip saying "In use by Unraid". Go to Settings -> Network Settings and remove the nic from any bonds (note: you will need to stop the array to make any changes to the network setup). Once it is no longer in use by Unraid, the checkbox will be active. If you get stuck, please upload your diagnostics (from Tools -> Diagnostics)
  2. To summarize the issue for @limetech: Here are diags from beta 30: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/2/?tab=comments#comment-10968 And here are the results of `hexdump -C -n 512 /dev/sdh` https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/3/?tab=comments#comment-10972 limetech said: Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it
  3. It looks like you have Tips and Tweaks installed, what is your "CPU Scaling Governor" set to? If it is "Power Save", try "On Demand". Made a big difference for me. There is more discussion here: https://forums.unraid.net/bug-reports/prereleases/690-beta-30-pre-skylake-intel-cpus-stuck-at-lowest-pstate-r1108/
  4. These are configurable settings. If the defaults don't work for you, then you need to set them up for your particular system: "Settings->VM Manager->VM Shutdown time-out": must be long enough to allow your VMs to shutdown "Settings->Disk Settings->Shutdown time-out": must be long enough for the array to stop *after* VMs have shutdown. So 60 to 120 seconds longer than the VM timeout. If a parity check starts after shutting down, then you Disk Settings->Shutdown time-out setting is too short for your particular system. If you would l
  5. You should whitelist your Unraid system from any popup blockers, antivirus, or other browser extensions or applications that modifies web pages. Looks like Bitdefender has instructions for this here: https://www.bitdefender.com/consumer/support/answer/13427/
  6. Do you have the Tips and Tweaks plugin installed? Check your "CPU Scaling Governor" setting. I'm guessing it is set to "Power Save", change it to "On Demand" and your CPUs should no longer be throttled. For more background see https://forums.unraid.net/bug-reports/prereleases/690-beta-30-pre-skylake-intel-cpus-stuck-at-lowest-pstate-r1108/
  7. See this post for the various shutdown timeouts that need to be synchronized:
  8. Hi @lman30, I think I've worked out a fix, PM me if you'd like to try it
  9. OK your hash.unraid.net url still resolves to the original IP for me as well. It is possible that the solution only works with non-routable IPs, I'll see what I can find out. Along those lines... unless you actually own that 20.2.x.x IP range, I highly recommend you use one of the non-routable networks specified here: https://en.wikipedia.org/wiki/Private_network If you don't own 20.2.x.x, then somebody else does and it will cause networking issues down the road if you use it. Your original 192.168.x.x address is an example of a valid IP range for internal networks.
  10. OK that's good. So your trial had a 192.168.x.x IP address, is this now on a different network? Is there any DNS caching that you know of on your network? Is the 20.2.x.x IP address that you blanked out on the screenshot the correct IP of the server? Please PM me the xxxxxx.unraid.net address that you blanked out of the screenshot, I want to see if it resolves correctly for me
  11. Is that 20.2.x.x IP address directly on the Internet? You should not do that, Unraid is not hardened to be placed directly on the Internet. Unraid should be behind a firewall with specific ports opened as needed.
  12. Hmm... it isn't exactly clear what state the system is in now. It may just be that you need to setup SSL on the new system. Go to Settings -> Management Access. If you have an Update DNS button, press that. It may take a few minutes for the DNS change to propagate. If you have a Provision or Renew button, press that. If you get a DNS rebinding error, wait a few minutes and try again. If none of this helps, please post a screenshot of the Management Access page along with your diagnostics (from Tools -> Diagnostics)
  13. Wireguard only affects the network when a tunnel is up. But if you want to be absolutely sure Wireguard is not doing anything, remove the plugin (you've already done that) and delete the config/wireguard folder from your flash drive and reboot.
  14. Hmm... OK, the fact that this resolves for you: ping 7064337de712ccf69be1c7f7762091b345f6cf66.unraid.net means that rebind protection is not an issue. But for some reason it resolves to 192.168.1.91 instead of the server's IP of 192.168.2.42. I was thinking perhaps you had two network cards in your system but that doesn't seem to be the case. Any chance you are in a double-nat situation, behind two routers?