JonathanM

Moderators
  • Posts

    15996
  • Joined

  • Last visited

  • Days Won

    65

Everything posted by JonathanM

  1. diagnostics may reveal something, as well as iperf tests both ways.
  2. Yes, you can format any data or pool drive that you want to erase. Unraid won't offer to format mountable drives, so you can temporarily change the disk or pool desired filesystem to a different option, then when the array is started it will show the unmountable drives and ask if you want to format them.
  3. As an example, lets say your IP's are as follows 192.168.1.1 router 192.168.1.2 daily driver 192.168.1.3 Unraid Try pinging the router and your desktop machine from Unraid, and try pinging the router and Unraid from your desktop machine. All should reply back. Did you assign a static IP to Unraid that is outside the range of addresses automatically assigned by your router? If not, it's possible some other device got that same IP and is causing issues.
  4. Looks correct to me. Is it not reachable at the IP address listed a little bit above the screenshot you posted? If not, at the prompt you are showing type ping<space><router ip> and see if it can see the router.
  5. The apps tab is fine, but some of the links in the app descriptions and such open external web pages, which aren't directly under Unraid's control like the GUI. I'm not yelling, just trying to get across the idea that the built in GUI browser isn't meant for anything beyond the Unraid GUI itself. Yes, which is why you need to only use addresses that are reachable when the array is stopped.
  6. That is what it is meant for. No outside browsing. Period. No browsing the web looking for apps or support or documentation for apps. If you want to browse the web casually, for whatever reason, you need to be doing it on another machine. That other machine can be a VM hosted on Unraid if you wish, which you can access using the GUI browser. The built in GUI browser is not regularly updated, and can't really be properly secured.
  7. GPU is sold, thanks for a smooth transaction. Everything arrived exactly as described in good working order.
  8. And if you (OP or anyone reading this) are using GUI mode as a general use desktop you need to stop immediately. Set up a VM for daily driver use.
  9. How does zfs handle the leftover space with 2 different sized disks?
  10. I believe BTRFS single profile is the only layout that will utilize different size drives fully in a pool. Since that will not be redundant, I recommend just setting up 2 different pools and using each for specific duties.
  11. I'm well aware of the behaviour, I was formulating an easy way to demonstrate it for someone who wanted to discover how it worked, sounds like you've got it figured out. Just be sure you keep in mind the write behaviour when using the user share, so you don't accidentally overwrite a newer version of something with an older version, and lose your changes when you "clean up"
  12. Depends on which container you are using. Click on the icon in the GUI and select support, that will link to the support area for your container where you can find out how your specific container handles updates.
  13. Yep, remove the folders that the container created in the icecast folder and replace them with the files.
  14. If you don't receive an automated response in a few minutes it didn't go through properly, try again.
  15. If the data layout is unchanged, then parity would be valid. However... I'm not sure how to figure that out without just doing what you said. I don't see any issue with your plan, I would definitely check the box stating parity is valid, that way there will be a parity check triggered instead of a parity build. If there are zero errors and the disk mounts, then you will be good to go. If there are immediately a wallop of parity errors and the disk doesn't mount, cancel the check, stop the array, unassign the disk, and start the array and see if the emulated disk mounts. If it does, then a rebuild on all the drives, one at a time, would fix it.
  16. If the containers don't have a built in permission fix setting, (some of binhex's do) then the easiest way is to delete the appdata and start over. That will lose all your settings and data however. Otherwise it's probably going to be a tedious process of manually setting the permissions to what is needed, the only way I can think of would be do a second install and see what the permissions were on a running install and emulate them. Each container will be different, so I recommend asking in the support thread for the specific containers you are working on to see if there may be a shortcut to fixing it.
  17. Make sure the power going to the drive is clean. Splitters and any push in connectors can cause issues.
  18. I hadn't thought of that, great point! Mounting with Unassigned Devices still requires the array to be started AFAIK, so whether it's UD or a pool is going to be the same in that regard, neither will allow logging to continue during shutdown.
  19. I can't solve that part of the question, but I can offer a workaround. Since there is no limit on additional pools, why not just assign the flash drive to a single device pool, call it logs or something? It's not like it has to be an unassigned device for removal purposes, since if the server is running it needs to be attached, and when the server is shut down and you need to read the logs it won't matter that it's in a pool. The only issue I can think of is if you need to read it on a windows system for some reason, in which case just use BTRFS and install https://github.com/maharmstone/btrfs
  20. First, I don't recommend using a database container for multiple apps. There is practically no benefit to doing so, and plenty of reasons not to. Set up a second identical container changing the name, appdata folder, and port. That way if you mess something up you only have to deal with one container being down instead of all the containers using that same database engine. Containers share application layers, so the only additional space used is for the data, which would be additional anyway. Second, you should look at the existing support area for the container you are trying to get running and see if your questions are already answered there, if not, post in that support thread. This general area is for OS issues, containers have their own area. Click on the icon in the GUI and select "support".
  21. Probably should post your docker run command in the support thread for your specific container. There are a bunch of different sonarr containers. You can find the support thread for yours by clicking on the icon in the gui and selecting support.
  22. binhex's vpn containers are locked down tight, all IP's that need to access the GUI must be whitelisted in the container template. See Q30 https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Probably a good idea to read the whole thing, there's a lot of good info about using his containers. p.s. Each container has it's own support thread, to keep all the information in one place. You are meant to post in the specific thread for container support, not start a new thread. For Unraid OS specific questions, you ARE meant to start your own thread in the general support area.