trurl

Have you tried to unmount it from the command line?

Not clear at what point you intend to add it to the array. You should do this before you format it to XFS since unRAID will want a clear drive if adding it as an additional array drive. A clear drive is not at all the same as an empty filesystem drive. So I should 1. empty cache drive 2. format it to XFS 3. add to array 4. start moving files from existing array drives to the XFS drive formerly known as cache Assuming you don't want to do a new config and rebuild parity, you should preclear the drive, then add it to the array, then format it. If you try to add a drive that is not clear to the array, unRAID will clear it, taking the array offline until it's done, then you will have to format it. The only way to maintain valid parity when adding a drive is to add a clear drive. A clear drive is all zeroes, so has no effect on parity. A formatted drive is not all zeroes, because it has a filesystem written to it. So, you should: 1. preclear drive 2. add to array 3. format

Not clear at what point you intend to add it to the array. You should do this before you format it to XFS since unRAID will want a clear drive if adding it as an additional array drive. A clear drive is not at all the same as an empty filesystem drive.

Each container can only see the host paths that it has mapped.

Do you have any working dockers?

Also read the stickies in the docker subforums.

What volume mappings do you have now? From telnet or console ls -lah /mnt

I don't use this container, but firstly I would format the drive with xfs, secondly post your mappings that you're using because something isn't quite right if it's recording to a different location. I don't know if NTFS on Unraid is a format that can be written to, although I know you can read it. You have to use ntfs-3g to write. I do it all the time. Unassigned devices works for this. Would NTFS-3G have to be in the container or just on the host? Not actually tried this with a container. I would think just the host, that's where all the other filesystems are. Someone should try it.

I don't use this container, but firstly I would format the drive with xfs, secondly post your mappings that you're using because something isn't quite right if it's recording to a different location. I don't know if NTFS on Unraid is a format that can be written to, although I know you can read it. You have to use ntfs-3g to write. I do it all the time. Unassigned devices works for this.

You might try this. On Windows 10, go to Control Panel - Credential Manager and delete any credentials for unRAID so they can be renegotiated. Make sure the first share you try to access is a Secure or Private share for the unRAID user you want to use and see if Windows will give you a login dialog.

Sorry I missed your reply. Very very intrersted in this. Once last question before I attempt to migrate away from my roll-your-own-solution; can you define which script run before umount? You can define the script that runs, but it runs on both mount and umount. See the example in first post.

Not 6.1 compliant

Looks like this plugin has not been updated for 6.1

Edit docker. Turn on Advanced slider in upper right. Enter Environment Variable Name and Value

If you used all 3 of those, 250, 240, 140, you would get 315. The extra space may not be worth using 2 extra ports, but you also get mirroring. btrfs disk usage calculator

Already saw the tentative changes to the templates (when the test templates caused havoc with the appfeed, which Kode then had to account for). Put two and two together and figured out the rest. I was impressed and think that it will be a huge boon for unRaid as a whole, and a welcome relief for everyone using containers that continually has those same problems. And a welcome relief for people trying to support everyone using containers. I get the impression there are a lot of docker users who still don't really get the whole mapping thing, but somehow got it to work by copying from others.

docker exec -it container-name bash will give you a bash session inside a container.

Good idea! If this plugin (and docker hub) weren't such a moving target I would ask for this functionality to be incorporated into the base product like some other community contributions have been.

If it is anything like Pushbullet, then you have to get it from your Pushover account. I login to the pushbullet website and go to my account settings. Maybe pushover is similar.

That's a recent change, I believe, and a significant one. Apart from a recent post by bonienl, I don't think I have seen any mention of it anywhere! It IS in the Help info for Enable disk shares. I'll make a note about it in the upgrade guide. bonienl, hoping you will see this, there's a misspelling in the Help info for this. I don't know what 'partiticapting' is, but it sounds like too much adult fun for this board! This is explained in more detail in the 6.1rc1 release announcement

Settings - Disk Settings - Enable auto start: No Then when you boot up the array will be stopped and you can change your Global Share Settings.

Notifications from this plugin seem to be broken on rc5. I know there was a change to the path for notify on rc3. See here Using the faster preclear script I got from here, which looks like a modification you made to bjp999 script and it does indeed have the old path for notify.

6.01 is the current stable release. 6.1 is still working through some issues.

See wiki: Upgrading to UnRAID v6 unMenu works in v6 stable built-in docker pretty sure a v6 plugin exists v6 plugin warning and critical notification built-in included in NerdPack plugin

Put your flash in your PC and let it checkdisk.