trurl

Working for me now. Thanks.

You can do this in Windows, but Disk Manager is not exactly intuitive. I have repartitioned/formatted several of my old unRAID disks to NTFS using only Windows.

The plugin appears to by wiping out some other smb-extra.conf settings I had. Does it create the file from scratch, or does it append onto what's already there?

Unfortunately not working for me though, perhaps because I was one of the few that removed it before upgrading to 6.1 After pasting in the link from the first post to the install page, it appears to install, but then I am left with the generic puzzle piece icon on the plugins page, and nothing appears in the Main page for Unassigned Devices. I tried clearing browser, refreshing browser, uninstalling, rebooting, manually removing all traces of the plugin, rebooting, reinstalling. No joy. plugin: installing: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/unassigned.devices.plg plugin: downloading https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/unassigned.devices.plg plugin: downloading: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/unassigned.devices.plg ... done plugin: downloading: https://raw.github.com/gfjardim/unRAID-plugins/master/archive/unassigned.devices-2015.09.07.txz ... done +============================================================================== | Installing new package /boot/config/plugins/unassigned.devices/unassigned.devices-2015.09.07.txz +============================================================================== Verifying package unassigned.devices-2015.09.07.txz. Installing package unassigned.devices-2015.09.07.txz: PACKAGE DESCRIPTION: Package unassigned.devices-2015.09.07.txz installed. plugin: downloading: http://slackbuilds.org/mirror/slackware/slackware64-current/slackware64/a/ntfs-3g-2015.3.14-x86_64-1.txz ... done +============================================================================== | Installing new package /boot/config/plugins/unassigned.devices/ntfs-3g-2015.3.14-x86_64-1.txz +============================================================================== Verifying package ntfs-3g-2015.3.14-x86_64-1.txz. Installing package ntfs-3g-2015.3.14-x86_64-1.txz: PACKAGE DESCRIPTION: # ntfs-3g (NTFS read-write filesystem driver) # # The NTFS-3G driver is an open source, freely available NTFS driver # for Linux with read and write support. It provides safe and fast # handling of the Windows XP, Windows Server 2003, Windows 2000 and # Windows Vista file systems. Most POSIX file system operations are # supported, with the exception of full file ownership and access # rights support. # # Homepage: http://www.tuxera.com/community/open-source-ntfs-3g/ # Executing install script for ntfs-3g-2015.3.14-x86_64-1.txz. Package ntfs-3g-2015.3.14-x86_64-1.txz installed. plugin: downloading: https://raw.github.com/gfjardim/unRAID-plugins/master/source/packages/exfat-utils-1.1.1-x86_64-1_SBo.tgz ... done +============================================================================== | Installing new package /boot/config/plugins/unassigned.devices/exfat-utils-1.1.1-x86_64-1_SBo.tgz +============================================================================== Verifying package exfat-utils-1.1.1-x86_64-1_SBo.tgz. Installing package exfat-utils-1.1.1-x86_64-1_SBo.tgz: PACKAGE DESCRIPTION: # exfat-utils (ExFat filesystem utilities) # # This project aims to provide a full-featured exFAT file system # implementation for GNU/Linux other Unix-like systems as a FUSE # module. # # This package contains the file-system utilities for use with # the ExFAT file system. # # Current status of the project: beta. # Executing install script for exfat-utils-1.1.1-x86_64-1_SBo.tgz. Package exfat-utils-1.1.1-x86_64-1_SBo.tgz installed. plugin: downloading: https://raw.github.com/gfjardim/unRAID-plugins/master/source/packages/fuse-exfat-1.1.0-x86_64-1_SBo.tgz ... done +============================================================================== | Installing new package /boot/config/plugins/unassigned.devices/fuse-exfat-1.1.0-x86_64-1_SBo.tgz +============================================================================== Verifying package fuse-exfat-1.1.0-x86_64-1_SBo.tgz. Installing package fuse-exfat-1.1.0-x86_64-1_SBo.tgz: PACKAGE DESCRIPTION: # fuse-exfat (ExFat module for the FUSE) # # This project aims to provide a full-featured exFAT file system # implementation for GNU/Linux other Unix-like systems as a FUSE # module. # # In other words, you need this package to mount drives formatted # with the ExFAT file system. # # Current status of the project: beta. # Executing install script for fuse-exfat-1.1.0-x86_64-1_SBo.tgz. Package fuse-exfat-1.1.0-x86_64-1_SBo.tgz installed. plugin: downloading: http://slackware.org.uk/slacky/slackware64-14.1/system/hfsprogs/332.25/hfsprogs-332.25-x86_64-2sl.txz ... done +============================================================================== | Installing new package /boot/config/plugins/unassigned.devices/hfsprogs-332.25-x86_64-2sl.txz +============================================================================== Verifying package hfsprogs-332.25-x86_64-2sl.txz. Installing package hfsprogs-332.25-x86_64-2sl.txz: PACKAGE DESCRIPTION: # hfsprogs - hfs+ user space utils # # The HFS+ file system used by Apple Computer for their Mac OS is # supported by the Linux kernel. Apple provides mkfs and fsck for # HFS+ with the Unix core of their operating system, Darwin. # # This package is a port of Apple's tools for HFS+ filesystems. # # http://www.opensource.apple.com Package hfsprogs-332.25-x86_64-2sl.txz installed. plugin: downloading: http://slackware.org.uk/slacky/slackware64-14.1/libraries/libbsd/0.6.0/libbsd-0.6.0-x86_64-1sl.txz ... done +============================================================================== | Installing new package /boot/config/plugins/unassigned.devices/libbsd-0.6.0-x86_64-1sl.txz +============================================================================== Verifying package libbsd-0.6.0-x86_64-1sl.txz. Installing package libbsd-0.6.0-x86_64-1sl.txz: PACKAGE DESCRIPTION: # libbsd - Utility functions from BSD systems # # This library provides useful functions commonly found on BSD systems, # and lacking on others like GNU systems, thus making it easier to port # projects with strong BSD origins, without needing to embed the same # code over and over again on each project. # # http://libbsd.freedesktop.org/wiki Executing install script for libbsd-0.6.0-x86_64-1sl.txz. Package libbsd-0.6.0-x86_64-1sl.txz installed. ----------------------------------------------------------- unassigned.devices has been installed. This plugin requires Dynamix webGui to operate Copyright 2015, gfjardim Version: 2015.09.07 ----------------------------------------------------------- plugin: installed Done

Yes, thanks a lot. This is the most valuable and used plugin for me.

The ability to "hide" dotted files is a new feature which you can supposedly turn on or off under SMB Settings, which is off by default (i.e., don't hide). I just turned it on but I can still see RecycleBin. Windows has always shown it to me without the dots, I assume because that is how that section is named in smb-extra. I tried logging out and back in to Windows but it still shows. Don't know if that's Windows fault or not. I also browsed to it using my wife's account on the PC, and that user has never seen it so I don't know if Windows is caching it across all users or what, but I can't get it to "hide" using the SMB Setting. I see while I was typing BRiT added some ideas about hiding it, which I will use with another custom mount point I have. Thanks

Wow! A quadruple post and I still don't get it.

Dockers should not be affected by the changes from 6.0 to 6.1, only some plugins.

Noticed a typo, I assume from this plugin, when starting the array. The message that shows at the bottom of the webui as part of the starting messages says "Startinig Recycle Bin"

The path that got created but not used was on disk1, so maybe it was just trying to create a folder for the share, but then when it did the move, it moved it to the disk it was on, which also created the path. In any case, I expect some of these details are not under the control of the plugin, but instead is just the way SMB and shfs are handling things.

So you use Recycle.Bin? Yes I also remember it moving the deleted file on diskX to Recycble.Bin on that same diskX drive.... Myk My deleted file did get moved to the same drive it was on. Probably that is just the way shfs makes it happen if the Recycle.Bin share can be on the same disk. Don't know why it also created a path on another disk, maybe something else about the way shfs works.

Make sure your appdata user share is set to Use cache disk: Only I would recommend mapping all of those docker's /config to /mnt/cache/appdata, just to be consistent. Map transmission /downloads to /mnt/user/downloads. Definitely don't want it downloading directly to /mnt/cache or you are going to accidentally create a new user share for every torrent folder. Map nzbget /data to /mnt/user/downloads just to be consistent. I don't use couchpotato but it looks OK to me.

Not sure you noticed the recent change to the behavior of the mover script. The default setting for a user share is Use cache disk: NO. And mover will not move a share unless it is Use cache disk: YES. This is a recent change to the mover script to help with the (surprise!) issue of people specifying apps to use /mnt/cache/something and then having mover move it to the array. The way it worked prior to this change is mover skipped cache-only shares, now it only moves cache-yes shares. Just started exercising this plugin a little to see what it does. Looking at the new config/smb-extra.conf entries the plugin made, it doesn't mention cache, just /mnt/user, so the cache drive should not be involved since the share isn't configured to Use cache disk: Yes or Only. I deleted a file from one of my user shares. I got new paths on 2 of my disks (not cache), and the deleted file is in one of them. Not sure why it would have created the path on 2 disks. I don't think it should be necessary to have the folder hidden. Even if the user configures the Recycle Bin share to Use cache disk: Yes or Only seems like it should still work as intended. Not sure what the purpose of hiding the folder was originally. If it was for hiding it from mover, it's not obvious to me why that would be a good thing.

I've been following this thread very closely, and I know there was work on it by dlandon, but I don't see anywhere that says there was a new release updated for 6.1 except for a couple of users who said they got an update, but those posts were unclear about the official status. Since I uninstalled this plugin when I upgraded to 6.1, I also did not get any notification that it was updated. Nothing new in the first post of the thread either. So do the bugs mean that it shouldn't be moved to 6.1 compliant? Do the bugs mean it no longer works on 6.0? Not intending to sound impatient here, just would like some official statement.

Not yet compliant with 6.1

Unraid 6 right? On my system, it's at /usr/lib64/libutempter.so.0 Not in bzroot, so probably installed as part of screen, maybe by Nerdpack.

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.

Bumping this to see if the author can confirm that it is compatible with 6.1. I am using it under 6.1 without issues.

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.