whwunraid

Members
  • Posts

    65
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    KC Mo

Recent Profile Visitors

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

whwunraid's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. Yes I got familiar with the route command and used it to set br0 and ip as the default route. Thanks for the input!
  2. I Installed a 10G ethernet card in my server and have it up and running. I can get to docker web GUIs via internal network as usual, VM can get on internet and resolve DNS names to address. Dockers are not able to resolve DNS apparently now as both Emby and Calibre are throwing connection errors to external hosts. I have disabled the original 1G nic in Network Settings (or so I thought, see pic). Log is showing an error of "Tower root: Fix Common Problems: Error: Multiple NICs on the same IPv4 network". Did not think something like this would be an issue if one is disabled? On the Docker settings page the new br0: is not showing a Gateway address, not sure how to rectify this. See attached screen shots... thanks in advance for your assistance.
  3. OK it was me, I did not complete all the items in Config Tab... LOL. TY for the help.
  4. Yes I have used "force scan" 3x and have the same issue. It does spin up the drives and do the scan as it should. The drop downs just do not function. I am using Edge browser and have tried in std mode and private mode, makes no difference.
  5. Hello just installed the app and trying to configure, when I choose the TRAYID drop down in the TRAY ALLOCATIONS tab there are no numbers to choose from nor can I type one in. I do have an add-blocker installed but it is turned off for my unRaid server IP address. Any help would be appreciated.
  6. This would seem simple enough to get around from an OS level if someone wanted to take the time to set it up. Maybe a feature request as I am sure this wastes serious amounts of time for many of our users. Thanks for your help... PS... The documentation for unRaid would be way more helpful with information like this in the appropriate sections. Making the assumption that the documentation makes itself fully transparent to users unfamiliar with the low level details of how a system operates is short sighted. Also might make less traffic on the forums. 😉
  7. Good day all, I swapped a 3TB drive for a 14TG drive in unRaid. I followed the instructions in the manual to the letter and everything is proceeding as per that document. The question is: The day before the drive upgrade I moved all the data/share off of the 3TB disk and onto another HDD. At this point parity should have known that the data had been moved (or some other indexing system) and when I added in the 14TB drive the rebuild should not have been needed, so why is a rebuild to an empty disk happening? Seems a severe waste of my time as I have other config items to do on the server. A few just like this, so how can I avoid a rebuild for an empty drive?
  8. Interesting... ok TY for you assistance.
  9. Attached - Thanks.... tower-diagnostics-20221222-0920.zip
  10. I have replaced a parity drive and the parity rebuild has started, but it is going extremely slow. I have turned off all VMs and Dockers to see if that would help and no positive gains. Would appreciate any thoughts you might have.
  11. Does anyone know of a docker or plugin that would work similar to the Dynamix System Stats but geared at Share information? I know you can use the Shares & Main tabs to hunt things down and get info, was hoping for something a little more of a GUI based tree type, at a glance kinda thing. Thanks...
  12. Original poster here - all I know is I did not run parity check this month and the docker crash did not happen. Will start one manually on 12-10 and see what happens, will post logs.
  13. Scrutiny - Nice!!!! BUT Celsius - really dude, c'mon at least gives us the Fahrenheit option!? 😱
  14. Hello All - I have verified that for the last three months (though issue has been happening for quite awhile) when my monthly parity check finishes all my docker applications enter a stopped state. I looked in the log file to see what is up, but I do not see the parity check being written in the log. It has a monthly schedule now I have seen instances of the CA App BU stopping docker but that is not happening here as I tested that with a daily BU and all is well there. As to the log for the parity check, is it written elsewhere or just not at all? Thanks...