unRaide

Hi @johnnie.black, thanks again for taking the time to respond... much appreciated! I forgot to get a breakout cable so I'm waiting on that before continuing with this project

Yep, that did it... thanks again @1812!!! I added the path as RW/Slave based on something I remember SpaceInvader One saying in the Krusader setup tutorial, so hopefully thats ok 👍

Any tips you can share on how to set it up Ive tried numerous combinatorics... basically just looking to access either a specific share or the entire /mnt/user/ folder.

Hi, is it possible to use the "External Storage" plugin to map and access my Unraid share through Nextcloud? Based on comments in this thread it would appear this is possible however I haven't had any luck getting this to work. So far I’ve tried connecting as either SMB / CIFS with username/password and login - session. Also tried adding a “.” in for domain… no luck. Has anyone gotten this to work? P.S. Another option I'm thinking of trying is to map the shares to the docker container and then try using local.

Thanks @johnnie.black! Will I need to do in anything in unraid after moving the spinners to the LSI or will it just pickup the changes automatically? Would you recommend moving all 4 data +1 parity HDDs to the LSI or just the data drives and keep the parity on mobo or does it even matter 😬 ?

I'm looking to upgrade my unraid setup by adding a 2TB SSD (Samsung 860 EVO) to use as an Unassigned disk for VMs and I'm looking for some guidance on the best way to configure/use this controller. I’ve maxed out all the data ports on my mobo (5 x HDDs + 2 x m.2 SSDs) thus the need for the new LSI Controller. The one I bought off eBay is supposedly already in IT Mode so hopefully I'm all good there. My question is around the best way to configure and use this controller: Should I just install the controller and plug the SSD into it and call it a day? Are there any pros/cons to connecting directly to the mobo vs the controler? Assuming the controller has more than enough bandwidth for this but has anyone seen any performance differences between connecting an SSD directly to the motherboard vs the LSI? Or should I instead move some of my data array spinners to the LSI as they likely don't need the bandwidth? Would this be as easy as unplugging/plugging them into the LSI? Something else? Thanks!

Thanks for the quick response @bshakil! Is there any specific order/steps that I need to follow when attaching/detaching? I've tried several different incantations numerous time with no success. Tried different USB ports as well... the phone shows the charging symbol but doesn’t want to connect.

Hi, trying to use this plugin to pass an iPhone XS through USB to a macOS High Sierra VM I created using @SpaceInvaderOne's tutorial. On the VM page the phone shows up in the dropdown as an "iPhone 4/5/6" and says "successful" when passing it through however it doesn’t show up in the macOS in iTunes?

Yea, I tried using Nas and some others. Did you need to do anything special on the Unraid side of things?

Hi, I’m trying to connect to my Unraid shares using an iOS app called FE File Explorer Pro. I’ve entered in the ip of my server however i keep gettin a permission denied error. Tried both my root and other admin accounts with no luck. My Shares are set to Export:Yes and Security:Public. Any ideas?

Hi, i try to use my iPad for most things these days and the latest update seems to have improved the layout a little on iPads. That said one place where the UI is very frustrating and essentially broken on iPad is the pop up dialogs that are used for certain types of tasks. For example i had to recreate my docker image so I’m in the process of re-installing all my previous tasks however as soon as the first docker was installed i can no longer see any progress in this dialog as it doesn’t scroll. So now I’m not sure what’s happening... if i should close the dialog, reload the page etc... Would be great to fix this in an upcoming release.

Yea, I ended fixing this by keeping the network type as host and following the steps outlined at the top of the plex sample config file. Can’t remember the exact steps but it’s laid out clearly and should work if you follow them closely.

[emoji106]

Hi, I’m really loving this new Krusader docker... game changer for managing files on my server!! I’ve started running into issues with my docker.img file being too large and as a result have been looking into the size of all my dockers. I noticed that this docker is 2.1G in size. Is that normal? I tried emptying the trash but that didn’t seem to make a difference. Any ideas on how to debug this?

Thanks @trurl, super helpful!! I ran the script and the total comes out to ~20GB which is clearly a lot less than the 300GB that’s allocated!!! Is there a way to tell how much of the allocated 300GB Docker is actually using? Looking at the advanced Docker settings i noticed something that there are two mentions of 23GB used and 100GB used. Is either of those the size of what’s actually being used within the image? Does that mean i can safely disable Docker, change size to say 30GB, and re-enable? Not sure if I’ve fixed the problem but I have deleted some older dockers and added the global log cap for all Dockers as described in the Docker FAQ.

Thanks for the replies and per @trurl‘s comment restarting the server got Docker up and running again. That said i clearly have an issue with 1+ dockers and will need to spend some time working through the steps you guys mentioned. Before re-creating the Docker.img file which as you mentioned would delete data that I may not be happy to loose is there a docker command that i can run within each docker to see how big the container is? Never realized it would be so difficult to debug this issue.

Thanks for the reply @Hoopster! Yea, there is definitely something going on with my containers... which I was trying to figure out before my docker service refocused to start up. My primary concern now is getting docker enabled so I can continue investigating further... I can’t survive without my dockers 😩 Any ideas on how to debug why my docker service wont start?

Hi, My docker instance shutdown earlier today because it ran out of space (currently 200GB). I increased the size to 300GB and was able to get it running again. I've been trying to figure out what the issue is by browsing the forum where i came across this thread and was currently tackling the suggestion of rotating logs. I stopped docker, enabled log rotation and set it to 20MB with 2 files. However when i tried enabling the docker it wouldnt start. Tried toggling log rotation and the docker off/on with no luck Does anyone know how i can get docker up and running again? Another piece of info...I also noticed that Fix Common Problems was reporting that "/var/log is getting full (currently 100 % used)" so i looked in there and saw that I have two docker log files one of which is 128M! It also seems that most of that file is showing the same error over and over time="2018-08-29T04:12:44.148202018-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.164261825-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.180545313-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.196581706-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.213155518-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.229533165-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.250082934-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.266417765-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.282693676-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.298779464-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.314660558-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.330609093-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.348824688-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.364960059-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.381099516-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.397724331-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.421475502-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.447766246-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.464297420-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.480990378-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" time="2018-08-29T04:12:44.497664613-07:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87/353c70186d935e4f278b66f9eab0f981e835f0ee8a643ad33130667175d80e87-json.log: no space left on device" whats strange is that i don't have a container at that path?!? Any ideas.... can i just delete that docker log? Also attached my diagnostics. unraid-diagnostics-20180830-2209.zip

Has anyone figured out how to get this type of setup working with a Plex Docker? I tried using the suddomain sample conf, updating the settings based on the other examples but I get a "502 Bad Gateway" when trying to load that page?

Hi @gridrunner, thanks for another amazing video!!! ? I've got everything setup and working per your video but I've run into two problems which I can't seem to figure out: How would I go about setting up a reverse proxy for Plex? I tried setting it up like the others however I couldn’t get it working. Do I need to do something special because it is using Host mode vs bridge mode? Should I still set it to use the custom proxynet? Is it possible to access all my dockers using the reverse proxy url when I'm inside my network? My router doesn’t support Nat Reflection and I'm not sure how to setup Nextcloud to work both inside and outside my network? Any guidance would be greatly appreciated. Thanks

Worked great, thx again!!!

Some quick follow-up... Do I need to stop/start the array for any of this? If a file on the array is newer will it overwrite an older one on the cache or is that what you meant by "delete the older one"? In which case I'd need to delete the older one and invoke/wait for the mover to run?

I'm almost back up and running, just trying to sort out all my shares. I ran the "Fix Common Problems" plugin and it seems like my AppData share is set to Cache = No when it should be Cache = Yes. I'm trying to figure out how to fix this as most of my files are already on the cache however the files that aren't are spread over all 3 disks it seems like. Any ideas on how to correct this? Do I have to go in manually and copy every file that is on one of the disks to the cache?

Woohoooooo....I'm back up and running, tkuuuu Johnnie!!! ??? Went to my dockers tab and noticed that all my dockers are running, a guess a lot of them were set to autostart. I've stopped them all and am now moving onto reinstalling them. @Squid, I'm assuming I simply need to select "Reinstall application using default values" and then update the template values as best as I remember? Is it possible for me to see what the previous settings were by looking at any files anywhere... or is that what was lost on the USBs config folder

Thanks again, I'd be lost without your help!!! Ok, I've figured out which drive is the parity and which one is the cache and stopped the array. On the New Config page do I need to select anything for "Preserve current assignments" or move ahead with None? Also how do I check "parity is already valid"? Is that another tool or a setting somewhere?