dlandon

I don't understand what you are asking. /boot/config/plugins/unassigned.devices/packages/nmap-6.40-x86_64-1.txz I don't understand the need for nmap for this package, sorry. Could you explain what it's used for? I don't understand either. I can't imagine why it is there. I took over the work that gfjardim started and didn't pay any attention to what packages were installed because I have been concerned with getting the plugin working. I will look into that, but I am thinking it has no business being there. This I somewhat remember from gfjardim's release notes it for detecting NFS or SMB servers I think. Correct. It is supposed to find SMB hosts. It is not working, is overkill, and I have read some information on the net that there may be security issues with nmap. I am removing the package. The only downside is that you have to type in the host name or IP address. Not a big deal and because it only found the host name you were on (i.e. Tower was the only host name found), it wasn't working anyway. and not worth the time to troubleshoot.

I've been doing that since the SNAP days. Really cool just to plug in a disk, have it backup on its own and notify me when it is done. Saves time and keeps me from making mistakes.

I don't understand what you are asking. /boot/config/plugins/unassigned.devices/packages/nmap-6.40-x86_64-1.txz I don't understand the need for nmap for this package, sorry. Could you explain what it's used for? I don't understand either. I can't imagine why it is there. I took over the work that gfjardim started and didn't pay any attention to what packages were installed because I have been concerned with getting the plugin working. I will look into that, but I am thinking it has no business being there.

I don't understand what you are asking.

Please post any issues on the new thread I've started here: http://lime-technology.com/forum/index.php?topic=45807.0. I won't be visiting this thread much so your post may not get a timely response.

I have started a new thread. I suggest that the following be added to the op. "This plugin is no longer being supported. There is a modified version of unassigned devices available here: http://lime-technology.com/forum/index.php?topic=45807.0. This modified version works on all V6 versions and some fixes have been applied. Please post about this plugin on the new thread."

Unassigned Devices Best Practices Here are some best practices I recommend when using unassigned devices. Be sure each device you use with Unassigned Devices has a unique label. The mount point is the device label if there is one, but it can be changed. Don't use the 'UNRAID' label on any devices. That label is reserved for the boot flash drive. Rename the device mount point from the default. Unmount the disk, click on the '+' icon by the serial number, and change the mount point name to something that makes sense to you. Turn on the run in the background switch for all scripts. This will keep the webgui from hanging if a script starts while you are on the web page. Don't share devices and SMB/NFS Shares unless necessary and enable SMB Security for user access when you do. Leave destructive mode off until you need it. It is too easy to delete a partition by accident. Try to use a file format other than ntfs when writing to disks unless the disk needs to be accessed by a Windows PC. Ntfs is not native to Linux. While this might be quite obvious, you should not uninstall the unassigned devices plugin if you are using a drive for Dockers or VMs. Uninstalling will unmount all mounted drives. If the disk is busy, the unmount will be forced and you will lose access to the disk. Updating the plugin with drives mounted is not an issue at all because they are not unmounted. To keep a drive in a standby mode, set the "Passed Through" switch on. There is a log file available that will log any errors from running your script file. It is located at /tmp/ and is by the serial number or label of your drive/SMB Mount point. You can test your disk script in a window. click on the '+' icon by the serial number when the disk is mounted and you'll see a lightning bolt icon. Click on the lightning bolt icon and a window will open and run your drive script. You'll then see any errors in your script and can make changes to fix the errors. If you want to pass a device to a VM or Docker, set the 'Pass Through' switch to on. This will insure that UD does not try to mount the disk. You can then pass it to a VM or Docker. Unassigned devices will show it as unmounted after you pass it through to the VM or Docker. You can mount a physical disk as read only using a 'Read Only' switch. This can be useful if you have an array drive you'd like to browse, but don't want any changes made to the disk that would invalidate parity. It can also be useful if you want to mount a disk and just transfer files off the disk. If you mount a remote share with NFS, you might experience 'Stale file handle' errors in the log. To solve this change the following settings: Settings->NFS->Tumable (fuse_remember) to -1. Settings->Global Share Settings->Tunable (support Hard Links) to 'No'. In Unraid 6.10 you can set UD to mount all NFS remote mounts with NFSv4. Go to Settings->Unassigned Devices and set 'NFS Version to use when Mounting Remote Shares:' to mount NFSv4 only. This should stop the stale file handle situation. If any of your UD disks get a gray mount button with the 'not' symbol and the 'Array' text, an array disk probably disconnected and was assigned a new sdX designation by Linux. You'll need to stop the array and fix this situation. If the mount button shows the 'not' symbol and 'Unmount' text, you have the "Disable Mount Button" switch set. If the device was not unmounted before being removed from the server you will see a not symbol and the 'Reboot' text on the mount button. If you remove a disk without unmounting it, a new sdX is assigned when you reconnect the disk which confuses UD as to the mounted status of the disk. You'll need to reboot to clear up this situation.

Unassigned Devices Plugin Unassigned Devices (UD) includes a lot of functionality and has become a bit complex. Please read the first and second post. You will find answers to most of your questions. Note: You will need to install the Unassigned Devices Plus (UD+) plugin to enable HFS+ and APFS (Apple file formats) and exFAT (flash larger than 64MB) disk mounting, and to enable 'Destructive Mode' for formatting of some UD supported disk formats. UD and UD+ are available in Community Applications (CA). Hover your mouse over any active area on the UD page and a tool tip will show you what clicking that area does. UD supports all Unraid native disk formats. You will need to install the 'Unassigned Devices Plus' plugin to mount HFS+, APFS and exFAT file formats. UD has a destructive mode that allows deleting disk partitions and formatting disks. If Destructive Mode is not turned on in the UD Settings, you WILL NOT be able to format a disk. Go the the Settings page and scroll to the bottom to see the UD settings. To format a disk: Destructive Mode must be enabled. You will need to install the 'Unassigned Devices Plus' plugin to enable Destructive Mode. UD Plus will install the 'parted' package needed for formatting and deleting partitions. Disk must have all partitions removed. Unmount the disk, click on the '+' icon next to the serial number, and click on all red-X to delete partitions. You can also click on the red-X next to the disk serial number to delete all partitions. A precelared disk will have a partition without a file system and will show a grayed 'Mount' button. You can assign this disk directly to the array and Unraid will see the disk as 'pre-cleared' and will not clear it again. If you want to format the disk for use in UD, you need to first click on the red-X on the preclear status line to remove the preclear stats and then remove all partitions by clicking on the red-X icon next to the serial number and then you'll be able to format the disk. There are different operations in various active areas (especially the disk serial number) based on whether or not the disk drive is mounted. If the disk is not mounted, click on the '+' icon by the serial number, click on the partition name, you will get a pop-up dialog to change the mount point name. This will now become the mount point and the share name when the disk is shared. In order to share any UD device, sharing needs to be enabled in the UD Settings and the switch turned on to share the particular device. SSD disks formatted with xfs, btrfs, or ext4 will be mounted with 'discard' if the "Mount SSDs with 'discard' option?" is set to "Yes". This includes encrypted disks. Reiserfs does not support discard. This enables TRIM on SSD devices. If you have the trim plugin installed, it is recommended to not mount SSD disks with discard. Disks formatted XFS or BTRFS will be partitioned compatible with the array disks and can be installed in the array without a re-format. SSD devices are now partitioned with a 1MiB offset as of Unraid 6.9 Beta 25 and cannot be installed as a cache or pool device on earlier versions. Because of security issues with samba, the mounting of remote SMB shares with CIFS has become more complicated. The default protocol is now SMB3 and not SMB1; the default security is now ntlmv2 and not ntlm. UD will try to mount SMB shares with SMB3, then SMB2, and then SMB1 to try to get the mount to use the most secure protocol it supports and the ntlmv2 protocol. If you have an older server that only supports SMB v1, you need to update that server so it will support SMB v2 or v3. SMB v1 is being phased out and will probably eventually be removed from samba. You will not be able to mount a remote SMB share using SMBv1 if NetBIOS is disabled in Unraid. It is recommended to disable NetBIOS on Unraid servers. Note: UD disks add to the total disks allowed by the Unraid license you have purchased except for a Pro license. See here for details. Unassigned Devices allows you to mount and share disk drives that are not managed as part of the array. Some users are mounting a drive specifically for Dockers and/or VMs rather than having them on a cache or array drive. You can also mount a UNC share on another system (SMB or NFS) and have it show in the Unraid shares when browsing the Unraid shares with Windows. This is called Remote Share Mount. The UNC path is mounted locally and shared as a \\Tower share that can be accessed by SMB or NFS. Access to Unassigned Devices shares defaults to Public with everyone having read/write access. User access can be enabled in the Unassigned Devices Settings. Access can be enabled by user for read/write, read only, or no access to Unassigned Devices shares. Installing the plugin You can install the plugin from the Community Applications (Apps tab); Remote Mounted Shares You can remote mount SMB and NFS shares. SMB shares are accessed through \\Tower\share. There are several special cases of remote mounting SMB shares. Windows. You have to provide user login credentials to be able to show the shares with the 'Load Shares' button. Even if the shares are not password protected, Windows insists on login credentials. Domains. You can remote mount shares on a domain by specifying a domain. It is preferred to use the server name and not the IP address. Let UD search for the servers and then make a selection, then load shares and make a selection. This is much less error prone than manually entering the information. Unless you use a static IP address on the server, it can change making the remote mount fail. Note: With NetBIOS disabled on a remote server or computer on your LAN, UD may only be able to look up the server and show its IP address because the name cannot be resolved. It is recommended that you type in the name of your other server or computer instead of using the IP address. UD will make an adjustment so the name can be resolved when mounting the remote share. UD also keeps the IP current if it is changed by a DHCP server. When a USB device is plugged in or mounted an event is initiated to run a user defined script. This is useful for backing up files from the server initiated by plugging in the USB device or copying pictures from a camera to the array. Scripts are created unique for each device. You can also setup one script to run whenever any device is plugged in or mounted. Mount Points and Shares There seems to be a lot of confusion over a mount point vs. a share. The mount point is where the device is mounted locally on Unraid. A share makes the mount point available in Windows at '\\Tower' as a browseable folder. When disk devices and ISO Mounts are mounted, they are mounted at /mnt/disks/. They are not a part of the Unraid array and are not mounted at /mnt/disk/ which is for Unraid disk drives. As an example, you have a device named 'MyDisk'. When it is mounted, it is accessed locally at /mnt/disks/MyDisk. If you want to use 'MyDisk' in a Docker Container or VM, you would refer to it by '/mnt/disks/MyDisk'. It is not automatically shared at '\\Tower\MyDisk' unless you enable sharing the device. To share 'MyDrisk', you would turn on the 'Share' switch for the drive and 'MyDisk' would be shared at '\\Tower\MyDisk'. The share 'MyDisk' is not accessed at /mnt/user/MyDisk' because it is not an Unraid user share. When remote shares are mounted, they are mounted at /mnt/remotes/. They are not a part of the Unraid array and are not mounted at /mnt/disk/ which is for Unraid disk drives. As an example, you have a share named 'MyShare'. When it is mounted, it is accessed locally at /mnt/remotes/MyShare. If you want to use 'MyShare' in a Docker Container or VM, you would refer to it by '/mnt/remotes/MyShare'. It is not automatically shared at '\\Tower\MyDisk' unless you enable sharing the device. To share 'MyShare', you would turn on the 'Share' switch for the remote share and 'MyShare' would be shared at '\\Tower\MyShare'. The share 'MyShare is not accessed at /mnt/user/MyShare' because it is not an Unraid user share. If you are using the legacy mapping of remote shares at /mnt/disks/ for your Docker Containers or VMs, and it is not practical to remap them in your Docker Containers or VMs, you can set a legacy mapping option in UD Settings that will put symlinks in /mnt/disks/ to the remote shares in mnt/remotes/. When you map to the /mnt/disks/MyShare be sure to have a trailing '/' on the mapping so the symlink will be treated as a directory and not a file. Mount points and shares are two separate things. Partitions and Formatting If you turn on the destructive mode in the Unassigned Devices Settings, you will be able to delete partitions and format disks. It is defaulted off as a safety measure. Scripts Here is an example script that will back up a Pictures share to a USB drive when plugged in. The USB drive is unmounted once the script completes so you just plug in the drive, wait for it to be completed, and then unplug the drive. The beeps in the script will make speaker sounds if you have a speaker to let you know when the drive is plugged in, when the backup has started, and when the backup has finished and the drive unmounted. The nice thing about this script is that all you have to do is plugin the drive and wait for it to finish. You will also be notified when it is done if you have turned on Unraid notifications. Set the drive to auto mount. Set the script to run in the background. If you mount and unmount the drive from the Unassigned Devices gui, the drive will mount and unmount but the script will not run because it has detected the 'OWNER' as 'user' and will skip the backup. #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # ACTION - if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # DEVICE - partition device, e.g. /dev/sda1 # UD_DEVICE - unassigned devX designation # SERIAL - disk serial number # LABEL - partition label # LUKS - if the device is encrypted, this is the partition device, e.g. /dev/sda1 # FSTYPE - partition filesystem # MOUNTPOINT - where the partition is mounted # OWNER - "udev" if executed by UDEV, otherwise "user" # PROG_NAME - program name of this script # LOGFILE - log file for this script case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 sleep 2 if mountpoint -q $MOUNTPOINT; then if [ $OWNER = "udev" ] then beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 logger Started -t$PROG_NAME echo "Started: `date`" > $LOGFILE logger Pictures share -t$PROG_NAME rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1 >> $LOGFILE logger Syncing -t$PROG_NAME sync -f $MOUNTPOINT beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 beep -r 5 -l 100 -f 2000 logger Unmounting PicturesBackup -t$PROG_NAME /usr/local/sbin/rc.unassigned umount $DEVICE echo "Completed: `date`" >> $LOGFILE logger Pictures Backup drive can be removed -t$PROG_NAME /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Pictures Backup completed" -i "normal" fi else logger Pictures Backup Drive Not Mounted -t$PROG_NAME fi ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; 'ERROR_MOUNT' ) /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Could not mount Pictures Backup" -i "normal" ;; 'ERROR_UNMOUNT' ) /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Could not unmount Pictures Backup" -i "normal" ;; esac Here is a nice UD script for importing photos from a camera/memory card into the array: Photo Script Thanks to ljm42. Cron Task A better way of running cron scripts is the 'User Scripts' plugin. You can set up a script to run at a particular time to perform disk operations. It is best to leave the device mounted so the script can access the drive. This is a simple way to set up a cron task to run a script to copy files to a backup. This method is a little cumbersome, but does work well. You will need to set up your drive to auto mount and it has to be left mounted. You can use the default script or the following one if you want beeps when the drive is mounted and unmounted. Set the drive to auto mount. he drive has to stay mounted for the script to work. Set the script to run in the background. #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # ACTION - if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # DEVICE - partition device, e.g. /dev/sda1 # UD_DEVICE - unassigned devX designation # SERIAL - disk serial number # LABEL - partition label # LUKS - if the device is encrypted, this is the partition device, e.g. /dev/sda1 # FSTYPE - partition filesystem # MOUNTPOINT - where the partition is mounted # OWNER - "udev" if executed by UDEV, otherwise "user" # PROG_NAME - program name of this script # LOGFILE - log file for this script case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; esac Now set up a cron file in the /flash/config/plugins/dynamix/ directory. Name the file 'custom.cron' (or a name of your own choosing.cron) with the following contents. This will set up a cron task to run at 4:30 AM every day. It runs a script in the /boot/custom/ directory called DailyBackup. # Custom cron scripts: 30 4 * * * /boot/custom/DailyBackup &> /dev/null Sample Daily Backup script #!/bin/bash # # Perform daily backup. # MOUNTPOINT=/mnt/disks/DailyBackup PROG_NAME=DailyBackup logger Started -t$PROG_NAME if mountpoint -q $MOUNTPOINT; then logger Pictures share -t$PROG_NAME rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1 logger Completed -t$PROG_NAME /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Daily Backup completed" -i "normal" else logger Daily Backup Drive Not Mounted -t$PROG_NAME fi After you have copied your cron file to the dynamix directory you will have to load the cron file manually one time to get it started. Unraid will manage the cron file after that and insert it into the crontab for you. Use the following command to load the cron file the first time. /usr/local/sbin/update_cron Encrypted Dsks You can format a xfs or btrfs encrypted disk with UD that is compatible with the array. The disk is created with the array password/passphrase. You must have at least one encrypted disk in the array. Unraid 6.8 and greater only. You can format an encrypted disk for use outside the array without having an encrypted array. The disk password is entered when the disk is formatted. You need to set the disk password in UD settings so the disk will mount. Unraid 6.8 and greater only. A disk encrypted with a different password than the array can be mounted with a disk password set in the UD settings. A different password can be set for each disk. Pooling Disks You can create multiple pools with UD, with some limitations, details here. Starting with Unraid 6.9, there is a 'Pool' feature that should be used for pooling disks. Click on the 'Help' button on the main menu bar of Unraid to get some additional help. If you hover your mouse over an active area on the gui, you will see tool tips that will help you understand the operation of the active area. Verify you have the latest version installed and check the syslog for information if you are having any issues. Many questions can be answered by reading this post and checking the syslog. Root Share You can create a root share in UD and collect all your shares in /mnt/user/ into one named root share. The root share is then accessible at /Tower/rootshare. There are some advantages and disadvantages to this approach: You control the root share permissions in UD Security settings. You may increase your risk of a malware attack by having all your shares accessible on one root share. Use secure passowrds! Addon Mount Folder UD adds the folder '/mnt/addons' where you can mount anything you need mounted. A protected mount is added to '/mnt/addons' so a misconfigured app cannot fill the rootfs and crash the system. FCP will ignore this mount folder so you won't see any warnings. If you mount something at '/mnt/addons' before UD is installed, you will see a reboot message over the banner. If this is the case, you need to delay your mount until after UD installs. Mount Button Indicators Disks In order to point out to users normal operation and situations that may prevent UD from operating on a disk device properly, the 'Mount' button will show some greyed out text that indicates status on the disk. If the text shows with the not symbol, the disk is in an error conndition. 'MOUNT' or 'UNMOUNT' - when the 'Mount' button shows either of these grayed out, the 'Disable Mount Button' switch is on. This situation lets UD do auto mount and unmount, but operator actions are not permitted. Theere are occasions when these indicators are grayed out because of disk drive issues. 'PASSED' - This indicates the 'Passed Through' switch is set. This is used to tell UD that a VM or Docker Container is using the disk and for UD to not manage the disk in any way. 'PRECLEAR' - The UD Preclear or binhex Preclear Docker is preclearing the disk. 'POOL' - This is used to indicate that a disk is part of a BTRFS pool. 'PARTITION' - This will show when a disk is detected that has a file system but no partition. UD cannot mount a disk in this situation. If it is a disk introduced to UD that you want to use in UD, you can clear the disk and reformat it for use with UD. 'ARRAY' - This indicates that a disk has not been detected by Unraid as an Unassigned Device and UD thinks the disk is a part of the array. This generally happens when an array disk drops from the array. 'UDEV' - UD has detected that the disk format reported by udev does not match the format as reported by lsblk. This can sometimes be rectified by clicking on the double arrows on the UD UI to refresh the udev data in UD. 'REBOOT' - This shows when UD has detected a disk was probably removed before being unmounted and then re-installed. The best way to clear this up is to reboot. If this happens because of several disks having the same mount point, unmount the disk with this mount point and change mount points on all disks to be unique. Remote Shares 'MOUNT' or 'UNMOUNT' - when the 'Mount' button shows either of these grayed out, the remote sever is off-line. When these indicators are grayed out on an ISO mount, the iso file is not available.

Sounds like a Plex issue.

Unassigned Devices are not mounted to /mnt/disk/ or /mnt/user/ and are not recognized as array managed shares. Unassigned Devices are mounted to /mnt/disks/ so your drive would be at /mnt/disks/VERTEX2_120gb. You don't have to share the drive to see it on the local computer and use it in a Docker.

I will post some example scripts and how to set up a corn to run scripts in a new thread for unassigned devices. I cannot maintain the op of this thread.

Is there a way to allow me to edit the first post to keep a mod from having to do it? If not maybe I can start a new post and refer to that one in the first post here? As you can see there is a lot of activity here and the plugin is pretty dynamic at this point so I can see more changes and enhancements coming. Dan, why don't you just create a new thread, might be easier.... It's what I did with the mediabuild stuff. If gfjardim returns and you want to hand back the reigns he can just bump this thread.. I'm thinking the same thing. Would be a lot cleaner and easier to maintain.

Is there a way to allow me to edit the first post to keep a mod from having to do it? If not maybe I can start a new post and refer to that one in the first post here? As you can see there is a lot of activity here and the plugin is pretty dynamic at this point so I can see more changes and enhancements coming.

Yes, it is 'kill'. I'll have to take a look at blocking the false positives.

I just released version 2016.01.20. The sharing of SMB Mounts has been implemented now so when you assign an SMB Mount from another system, it will always share and show up when you browse \\Tower with Windows along with the unraid user shares. Devices and SMB Mounts will default to being shared as Public with read/write privileges for everyone. User share privileges are set in the Unassigned Devices SMB Security settings. There you can set whether or not a user has read access, read/write access, or no access to unassigned devices shares.

Unassigned Devices and SMB Mounts are not mounted as unraid user shares (/mnt/user). Unassigned Devices and SMB Mounts are mounted at /mnt/disks and are shared using the smb_extra configuration file. The unassigned device and SMB Mount is shared and shows as an smb share, but unraid is not aware of it as a user share. Mount a device and look at the /boot/config/smb-extra.conf file and you'll see an include that inserts the share properties of the device. The include file is created by unassigned devices when the share is mounted and the share switch is turned on. The include file is located at /etc/samba/unassigned-shares/. I mostly knew all this but kizer is changing it from /mnt/disks/name-you-want-for-share to /mnt/user/share-that-he-created if I understand him correctly. Yes so it will show as a folder in my user shares. Otherwise I couldn't get it to show on my windows machine when I browsed my shares. Like I said its not something I have to do or anybody else, but I'm always trying to see what I can get things to do even if they are not intended half the time. I would like to know when a drive is Shared how do you view it/find it? A smb share that is mounted under /disks? I can find it in command line pretty easily. The unassigned devices shares (device or SMB Mounts) are not shared as unraid user shares and are not recognized by unraid as shares for the array. They show up in Windows when you browse to \\Tower.

I can't say right now that it is an issue or not. I have both USB and sata drives and am not seeing the no spin down problem.

Where did you see the smart values? I assume in the latest gfjardim version. I assume so, from "main" you could click the device "sda" and see the drive details just like if you clicked "disk1" I'll look at gfjardim's last version and try to reproduce. Much appreciated! I cannot thank you enough for taking the time over the last few weeks to keep on improving this. Added in the next release.

Unassigned Devices and SMB Mounts are not mounted as unraid user shares (/mnt/user). Unassigned Devices and SMB Mounts are mounted at /mnt/disks and are shared using the smb_extra configuration file. The unassigned device and SMB Mount is shared and shows as an smb share, but unraid is not aware of it as a user share. Mount a device and look at the /boot/config/smb-extra.conf file and you'll see an include that inserts the share properties of the device. The include file is created by unassigned devices when the share is mounted and the share switch is turned on. The include file is located at /etc/samba/unassigned-shares/.

I intend for the SMB Shares to show in the unraid shares. It wasn't working that way and I have it fixed. If it isn't shared, what is an SMB Share for? I got it to work. I just had to make sure I added a share and mounted it to a share. Just wasn't perfectly clear at first, but knowing how unRAID works in general I was able to make it work. It was readonly, but it worked unless your fix takes care of that then even better. That does work, but unassigned devices will do the share automatically now when it is mounted. I just finished that fix and will look into the read only issue now.

Where did you see the smart values? I assume in the latest gfjardim version. I assume so, from "main" you could click the device "sda" and see the drive details just like if you clicked "disk1" I'll look at gfjardim's last version and try to reproduce.

You aren't being ignored. I do have a life. This is a part time effort on my part with zero compensation. The least you can do is to have a bit of patience. I read your posts and understand the issue. I am looking into it.

Where did you see the smart values? I assume in the latest gfjardim version.

I intend for the SMB Shares to show in the unraid shares. It wasn't working that way and I have it fixed. If it isn't shared, what is an SMB Share for?

I don't think you can expect to have SMB shares show up as unRAID user shares or get unRAID to share SMB shares if that is what you are trying to do. User shares takes place at a lower level than I think this plugin does or even should work. An SMB Mount will show as an unraid share. Why else would you do an SMB Share? I have fixed in the next version.