www_creedthoughts

In the UI, the max installable RAM is listed as 16GB: But the documentation for that motherboard lists the maximum at 32GB. How can I find out if I can safely put in 32GB? Or if unRAID will even recognize 32GB.

Ah thank you so much Squid! I know its a busy time of year. I just set up the application as you've described and its working perfectly. It feels nice to not have to worry about losing all of my VM configurations and docker data. Thanks again!

I'm slightly confused as to how I'm supposed to point the backup directory to an unassigned device. I've attached two images to this post, which represent how I have the plugin configured right now. Capture1.png shows how I've entered the address for the unassigned device drive. Capture2.png shows the message that shows up when I choose to backup, and I find the error message somewhat confusing. Why is the destination drive written as this: /mnt/disks/Temporary/Backups/ (/mnt/disks/Temporary) Maybe I'm being dense, but I'm confused as to what the parentheses mean. This is a remote server so I don't want to mess around with it and be unable to reconnect if that configuration message is not expected. Thanks in advance for any help!

Huh, worked fine this time when I restarted it. If I run into any issues I'll be sure to let you know. Sorry for the scare there.

UnRAID is 6.2.4. Attached is my UD log. Thanks! tower-unassigned.devices-20161213-1339.zip

Hi all, After updating my UD plugin to the latest version (2016.12.04), I've noticed that when restarting my server, my drives are not automatically shared. They are mounted, but not shared via SMB. If I uncheck the "share" button the main screen and then recheck it, they appear in the SMB share. I'm not sure if this is a bug introduced in the new update or a user error. Anyone have any thoughts?

Well I really really appreciate your efforts to help me CHBMB, I really do! Hopefully, someone else will stumble upon this page and be helped by your video! Thanks again!

Thank you all for your help! I discovered out how to do this thanks to your helpful words. I'd like to document how I completed it, partially just for me and partially for anyone else who may be trying this. Note: I initially installed the docker via command line with the following instruction (source: http://lime-technology.com/forum/index.php?topic=39209.msg424486#msg424486): docker run -d --name="Hamachi" --net="host" --privileged="true" -e ACCOUNT="[email protected]" -v "/mnt/cache/Apps/Hamachi/":"/config":rw -v "/etc/localtime":"/etc/localtime":ro gfjardim/hamachi I accidentally forgot to change the "config" mapping and wanted it on a different drive other than the cache drive. These are the steps to move it to the other drive. First, I copied all of the config files from the existing Hamachi installation location to a backup. As per Squid's instruction, I removed the docker that I created via command line. I then recreated the docker using the webui and specified the following parameters when creating it. I had to manually create the variable "ACCOUNT" and path "/config". Name: Hamachi Repository: gfjardim/hamachi Network type: Host Priveleged: on Container variable "ACCOUNT": [email protected] Container path "/config": /mnt/disks/TemporarySSD/Docker/Hamachi (Docker)/ Then I created the docker, and copied the files I backed up earlier to my new installation location and overwrote the existing ones. Those steps should allow you to move your docker, and by creating it via the webui, you can now change the container paths without headache. Thanks again everyone for your help!

I have every other docker container running on a solid state drive outside of the array. The Hamachi docker works just fine on the cache drive, but I'd like it to be consistent and store all dockers on the solid state, partially because the cache drive spins up whenever I use Hamachi. I'd like to change the location of the config, but there is no way to edit the mapping when I click on the docker. See the attached photo. Currently I'm thinking that I remove the docker container, and then readd it with the correct config location. I'm just concerned that it might not work correctly anymore, especially because the initial installation procedure was incredibly difficult since the container isn't actively updated or compatible anymore.

Hi all, I have Hamachi Logmein running in a docker container, but it has no webui and no "Edit" menu in the dropdown list when clicking on the Hamachi icon. There is currently one volume mapping: /config <-> /mnt/cache/appdata/Hamachi/ However I'd like to change that mapping to: /config <-> /mnt/disks/TemporarySSD/Docker/Hamachi (Docker) This change has to be done in the command line, but I'm not confident in my skills to make the change. Note, the name of the Logmein docker is simply "Hamachi". Can anyone walk me through the process? I can't imagine its overly difficult. Thank you in advance!

Thank you for all of the research dlandon! That is disappointing that you can't use an UD device for the docker. Hopefully that functionality will be restored in the future. Thanks again!

That means that I go to docker settings, and the docker status in the top right corner is "stopped". I click the dropdown menu next to enable docker, choose yes, and click apply. The page refreshes but the docker status stays as "stopped". The unassigned device has 368GB free on it. My cache drive is where I actually store my VMs and Docker information since storing it on the unassigned device is not working in 6.2. When you ask me to try something I change the docker location from the cache drive to an unassigned device in order to test what you've suggested. The docker runs normally when pointed to the cache drive. I have the exact same img on my cache drive. The docker works normally when pointed to the cache drive but does not start when pointed to the unassigned device. I have only used 4.02GB of my 10GB image. Auto start is off on all dockers. It still does not start.

Hi dlandon, I tried what you suggested and the docker did not start successfully. I attached diagnostics from the tower immediately after attempting to start the docker with the new paths as you've suggested. I'm not sure what you mean by "correcting permissions", nor am I sure how to do that. Any ideas or advice would be much appreciated. Thanks in advance! tower-diagnostics-20160924-2013.zip

Hi dlandon, the UD log was attached to my previous post. For completeness, I'm going to restart my server, upload a new UD log and the system diagnostics (which I meant to do last time). Hope this helps solve the issue! EDIT: Let me know if there is anything else you need. EDIT2: I tried to manually start the docker after restarting my machine, and the system diagnostics after attempting that are also attached. That diagnostic log is the "tower-diagnostics-20160921-1419.zip" file. tower-diagnostics-20160921-1410.zip tower-unassigned.devices-20160921-1410.zip tower-diagnostics-20160921-1419.zip

Alrighty here we go. Attached is the system log and UD log. I restarted the server so the log wouldn't be as obnoxious. Currently, the docker image is set to a hard drive mounted as an unassigned device and the docker won't start. Ignore unassigned device "ST380815AS_9RW1KHZV", that is an unused hard drive in my machine. I'm excited to hear back from anyone, let me know if there is anything else I can do to help. tower-syslog-20160921-1041.zip tower-unassigned.devices-20160921-1043.zip