AnotherITGuy

@hedrinbc Just checked again and it's now working with the correct updated host paths! Thanks again for the quick work, I hope this helps users out going forward. Cheers

@hedrinbc You are most welcome, I'm glad you found my suggestions helpful. I'm not as familiar with the mechanics of how CA repositories update after code pushes, but just FYI it seems the template is still defaulting to your old personal host paths when I attempt to install as of this post time (11:43am EST). Cheers

Hi Ben, First of all, thanks very much for voluntarily maintaining an UnRAID compatible docker for mbentley's TP-Link Omada SDN controller. I wanted to make a quick suggestion from a software usability standpoint that I think is a low-effort way to avoid a lot of future headaches for users of your docker. As you probably know, many, if not most UnRAID dockers are preconfigured with host file paths that do not require careful manual entry, so UnRAID users have been "trained" to expect this behavior when installing a new docker. Your defaults on host paths, if left unchanged, produce behavior that is sort of the worst of both worlds - it appears to work normally, but in fact UnRAID creates a temporary path based on your hard-coded personal server settings with "extrassd" that does not persist after reboot, causing in some cases hours and days of confusion for users of this docker. To resolve this situation, I would recommend one of the following minor adjustments to the docker: 1) Set the default host paths to the following: /mnt/user/appdata/omada-controller/data/ /mnt/user/appdata/omada-controller/work/ /mnt/user/appdata/omada-controller/logs/ This solution would I believe clear up a lot of user frustration and confusion after they just accepted your default (personal) host paths of your "extrassd." Many / most UnRAID users opt to use a Cache drive and map the /appdata share exclusively to that drive, so it would not be stored on spinning drives with parity. If for some reason you believe this solution might create an issue (I believe you referenced file permissions "on the array"), please let me know. I assume UnRAID would create these directories if they do not yet exist in the appdata share. This could also be hard-coded into mnt/cache/appdata/ I suppose, but I'm not certain why that would be a more optimal solution. 2) Another solution could be to make a much more prominent note in the Docker Template settings themselves (via instructional text below the host paths and/or in the blue description text], the Community Apps description and/or this support thread that explicitly states that it is MANDATORY for the user to reset these host paths to fit their own system needs. However, I believe that if you make the changes in my suggestion above, these instructions may be unnecessary. Finally, someone (not me) has produced a YouTube video walking users through installation of your Docker, and you may wish to link to this video in the first posts of this support thread for future reference [note that this person manually creates folders in /mnt/cache/appdata (which I did not think was necessary) and then edits the default host paths]: I believe these changes could cut down on demands on your time as well as a lot of user frustration in this thread, on Reddit, and elsewhere. I hope these suggestions may be helpful and again, huge thanks to you @hedrinbc and @mbentley for supporting this useful docker. Cheers.

Thanks for the response, trurl. Wish there was some kind of tagging or permission-setting that made it easier, but sounds like separating shares is the way to do it. I'll remember to only copy between shares too - thanks for the reminder! Cheers.

Lunchtime bump - can anyone give me a little guidance here?

Hi all, Longtime happy unRAID user here. I have been using unRAID to serve up media for my family via home network to three separate Kodi frontend boxes for years now, but the kids are getting old enough to poke around and view content that isn't appropriate for their age, and I'd like to limit this on their particular Kodi box. When I originally set up my User Shares in unRAID I just used generic "TV Shows" and "Movies" and "Music" shares and did not separate it by suitability for kids vs. grownups. Does anyone know of a way to create a "virtual" share that only provides access to files I specifially select / approve for kid viewing? Could this be accomplished with permissions of some kind in unRAID or Kodi, or do I have to create a new user share and move all the kid content into it? If the latter, should I try to use Midnight Commander to do so? Thanks in advance for advice.

Got it. Looks like unBalance does not yet support Unassigned Devices. So, I'm using Midnight Commander in a local session to make sure things go smoothly, and am copying top-level folders from the old drive mounted via Unassigned devices as /mnt/disks/[NameOfOldDisk] to /mnt/disk1 which is a new drive in the array. Will repeat with second old drive to another new drive, as suggested, and will then remove old drives permanently, install cache drives, start the array, and build parity. Thanks again!

Fantastic, thanks again. Since I only have 6 ports/bays and my new configuration as described above would have 6 devices including the two new cache drives, I'm unsure of which drives should remain uninstalled temporarily so that the old data drives can be mounted using Unassigned Devices. I suppose leaving the cache drives out for now makes sense? And so, does this look like the right procedure based on above: 1) Stop old array, power down 2) Remove old parity drive, replace with new larger parity drive (1 device) 3) Install 3 new data drives and retain 2 existing data drives (5 devices) 4) Start unRAID system 5) Go to Tools -> New Config and reset the array (Retain Current Config set to None?) 6) Assign new parity and 3 new data drives to array slots (leave old data drives unassigned) 7) Start new array, mount old data drives 1 and 2 8- Use (unBALANCE?/rsync via command line?) to copy data from old data drive 1 to new data drive 1 9) Use (unBALANCE?/rsync via command line?) to copy data from old data drive 2 to new data drive 2 10) Stop array, power down 11) Remove old data drives, install cache drive SSD's x 2 12) Start unRAID system, start array, verify proper settings 13) Sync parity 14) Enjoy a beverage Does this look right? Many thanks again.

Thanks for your response trurl! I do indeed have backups of essential files, and I very much like this strategy for simplicity and speed. My current array has User Shares though, and I was hoping to preserve those. Would I be able to preserve those using this method?

Hi all, I'm a longtime happy unRAID free version user (since v4.x I think) with a growing family and growing home data backup needs, and I decided it was time to purchase a Basic license and upgrade the aging disks in my array while adding some cache drives. I have already upgraded my array to unRAID 6.3 stable, and replaced an old USB flash drive with a more current unit. I have studied multiple wiki articles and forum posts but I'm still not sure what the best path is for my multi-stage upgrade in order to minimize downtime, maximize speed of data transfer, and preserve data integrity. Let me start with this: Goals: 1) replace all data and parity drives in array with new, larger drives 2) use XFS for all new data drives instead of ReiserFS 3) add one additional data drive 4) add a pool of two cache SSD's Use Case: Home file server supporting 6 users data backup needs (via rsync/syncthing) and media streaming to Kodi frontends on home 1 Gigabit wired network Existing Configuration: Software: unRAID OS v 6.3.3 stable with these apps installed: CA Preclear Disks, CA Unassigned Devices, unBALANCE CPU Hardware: 6-bay, 6-SATA port 2U rack server with Quad-Core AMD Opteron 1385 on SuperMicro H8SMi with 8GB DDR2 ECC RAM (Passmark=3442) Drives: 2TB Parity Drive 2TB Data Drive (Data 1 - ReiserFS) 2TB Data Drive (Data 2 - ReiserFS) Desired New Configuration: CPU Hardware/Software: no change Drives: 6TB Parity Drive 6TB Data Drive (Data 1 - XFS) 6TB Data Drive (Data 2 - XFS) 6TB Data Drive (Data 3 - XFS) 240GB Cache SSD Pool Drive 1 240GB Cache SSD Pool Drive 2 Steps taken: I have precleared all new data drives (WD Red 6TB) and all passed with flying colors. Tentative plan: I had thought to format these drives as XFS, copy data on old Drive 1 to new Drive 1, copy data on old Drive 2 to new Drive 2, remove all old drives, insert all new drives, and rebuild parity. This would have ensured that if anything went wrong, I still had three old drives with all data and parity intact. Once new config is up and running with valid parity, I would repurpose old drives in other family computer systems. But I can't seem to figure out how to do this in a way UnRAID allows given parity disk changes and filesystem changes. Can someone please advise on best procedure here? Many thanks!