Berg

Thank you both! I have a project tonight.

Alright, here it is; fileserver-diagnostics-20190227-2006.zip Thank you!

Well, my hope was premature I fear ... After deleting my Docker image, recreating an img file and reinstalling my apps, I seem to be running into problems again. After what first appeared to be a successful docker install, I'm now getting odd errors and an error 403 message when I try to start, update or reinstall my dockers. I've run my diagnostics files but I'm not sure what would be useful - I'd love some help.

Awesome - the perk of Docker. Thanks for your help and for giving me hope

Thanks - I suspected that this may be the case. Is there a way I can keep all my app data? so I don't have to lose all my settings?

Hello, I’m hoping someone can help me resolve an issue I just have run into with my Dockers apps. I run 3-5 docker typical images, like Plex, Sonarr, etc. and over the last couple of days, some/most of my Dockers are refusing to run. My Docker images run on a SSD cache drive pool that consist of two drives. When I try and restart or update one of the Dockers, I get this message: I’ve tried a couple of restarts and the issue remains, but the Dockers that don’t start seem to change. When I try to start a stopped Docker, I get an "error 403" which I believe is a disk permission's error, correct? Any my idea how I could troubleshoot or fix this? Thanks in advance.

All good - I've been off this forum for so long but I really appreciate your reply. I'm still working on this and your setup is really interesting. I'll keep plugging away at it but I may hit you up in the coming weeks/months. I suspect we are in pretty similar space. You can look up our overland vehicle and project on Instagram at @Wandering_Bison Cheers!

I was thinking 4-6 tb at the start and building somewhat over time. I think the real limit will be what size I can get to while still using 2.5” drive to keep the form factor smaller. Sent from my iPhone using Tapatalk

Yes, temperature is a concern that I might be under-estimating. More considerations .... Spin down might be a good solution that I need to learn how to control. More homework Thanks! Sent from my iPhone using Tapatalk

Thanks - that sounds like a good lead. Sent from my iPhone using Tapatalk

I’m in the planning stages to build an UNRAID array to be installed aboard a vehicle (think a truck or SUV) to be used to store media and content captured directly aboard the vehicle (think dash cams) as well as with video and photography gear that will capture high quality content but will be transferred for safe storage once back to “home base” (the vehicle) while travelling. I’d also like to store entertainment media while travelling aboard that vehicle. What I’m wondering is what types of hard drives should I consider to build this array? I’m assuming that solid state drives are most resistant to vibration , but is that true? And how do they handle the read/write cycles of an array? Or would laptop drives be more appropriate for the vibration environment? They would be cheaper than SSDs Does anyone have experience with this type of application? Thanks In advance. Sent from my iPhone using Tapatalk

Running into the exact same issue ... Looking forward to some input Thank you. Update: While I am getting the same 404 error as cardo, I can confirm that NZBGet appears to be working properly otherwise - it receives files to download and execute the download properly, handing the completed download back to the program that found the file.

Hello, I am running unRAID 6.0 RC2 on the system described in my signature with 19 data drives of mostly media content, from TV shows and movies to music. I have have a client running XBMC/Kodi set to scan for new content regularly along with running the Subsonic docker on my server scanning every night my music share looking for new content. I am very pleased with how everything is working and I'm finally getting to the last few tweaks to make my system just about perfect. I would love to limit the amount of times my drives spin up so I'm thinking that using my cache drives to save my content during the day along with caching my directory content would limit any (most?) drive spin up to overnight when Subsonic scans for new music and the cache script move new content to the array. Well, except for when I'm actually watching content So, I'm wondering if I should use the cache_dir script to cache my extensive media listing (40Tb+) to either memory or to a directory on my SSD cache drives to limit drive spin up to a minimum? Would this work? Is there just too much content to"index"? Is the other way to use the XBMC/Kodi docker to save my content "index" on my cache drive and prevent my client machine "poling" the server regularly? Of course, this would also have the benefit of allowing a multiple XBMC/Kodi client environment to share one "index". What would be best? I would love to hear your suggestions! TIA.