Anybody else having issues with the rootshare feature?

It's only showing 4 of the 15 folders that are in my /mnt/user directory.

On 7/7/2025 at 5:23 PM, philbar715 said:

Ive also had this same issue, from what I can remember I had it on version 6.xx, currently on version 7.14. SMB settings here revert to "no access" for each user after a reboot. "private", "auto, and "no" setting do not change after a reboot, only the permissions for each user.

I had the same issue - reported on April 20 and no responses whatsoever. My hacky but effective workaround until the plugin is fixed was to create two User Scripts to save the permissions on shutdown and reinstall them on array startup.

Script 1 - scheduled to run At Startup of Array

#!/bin/bash

target_file="/tmp/unassigned.devices/config/unassigned.devices.cfg"

source_file="/boot/config/plugins/unassigned.devices/smb_saved.txt"

echo "Target = $target_file"

echo "Source = $source_file"

# add line ending at end of file

sed -i -e '$a\' "$target_file"

# iterate over each config line and append if the key does not aready exist

while IFS= read -r line; do

line_to_check="${line%%=*}"

if ! grep -Fqe "${line_to_check}" "$target_file"; then

echo "${line_to_check} not found. Appending line: ${line}"

printf "%s\n" "$line" >> "$target_file"

else

echo "${line_to_check} already exists - not overwritting or appending"

fi

done < "$source_file"

echo "Applying and restarting"

/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings apply

/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings save

echo "Done"

Script 2 - scheduled to run At Stopping of Array

#!/bin/bash

source_file="/boot/config/plugins/unassigned.devices/smb_saved.txt"

echo "Saving to ${source_file}"

egrep "^smb_" /boot/config/plugins/unassigned.devices/unassigned.devices.cfg > ${source_file}

#cat ${source_file}

Not the best solution but it works. From what I was able to gather during my debugging, it seems the plugin is initialized before unraid configures security and any configured users, so the plugin thinks the existing permissions are for non-existent users, so it drops them. Since the entire plugin system is essentially undocumented, so I stopped trying to figure out a better solution.

Edited July 13, 2025Jul 13 by coffee1978

Look at this first screen in the "ADD REMOTE SMB/NFS SHARE":

There are two icons for choosing either NFS or SMB which is fine for folks are who are semi-Gurus in both Windows and Linux but it can easily confuse the less knowledgeable Unraid user. I feel that NFS and SMB in text should be shown under (or part of) each icon. (BTW, the two icons are in the reverse order from what is implied from the start link!)

IF you are wondering why I am making this request, please see this thread:

https://forums.unraid.net/topic/191965-im-new-to-truenas-and-trying-to-connect-the-truenas-smb-share-to-my-unraid-server-im-having-problems-using-unassigneddevices-app-to-see-the-smb-server-for-some-reason/

Edited July 14, 2025Jul 14 by Frank1940

On 7/7/2025 at 5:23 PM, philbar715 said:

Ive also had this same issue, from what I can remember I had it on version 6.xx, currently on version 7.14. SMB settings here revert to "no access" for each user after a reboot. "private", "auto, and "no" setting do not change after a reboot, only the permissions for each user.

Thanks, I'll check it out

On 7/14/2025 at 7:54 AM, Frank1940 said:

There are two icons for choosing either NFS or SMB which is fine for folks are who are semi-Gurus in both Windows and Linux but it can easily confuse the less knowledgeable Unraid user. I feel that NFS and SMB in text should be shown under (or part of) each icon. (BTW, the two icons are in the reverse order from what is implied from the start link!)

Completely agree and already on a todo list to show that and more importantly not give the option of NFS if NFS isn't enabled

Hovering your mouse over the radio icon will show a tooltip of what protocol it represents. If the protocol is not enabled, the icon is disabled.

3 hours ago, dlandon said:

Hovering your mouse over the radio icon will show a tooltip of what protocol it represents. If the protocol is not enabled, the icon is disabled.

I discovered that AFTER I had posted up my request. But to see those tooltips you either (1) have to know it is there or (2) find it by dumb luck.

33 minutes ago, Frank1940 said:

I discovered that AFTER I had posted up my request. But to see those tooltips you either (1) have to know it is there or (2) find it by dumb luck.

Tooltips are used all over Unraid. It's not just a UD thing. I do agree that ordering the icons with SMB first might make sense.

2 minutes ago, dlandon said:

Tooltips are used all over Unraid. It's not just a UD thing. I do agree that ordering the icons with SMB first might make sense.

Please understand that I am not trying to be difficult. As someone who is reasonably knowledgeable about both Linux and Windows, I instantly recognized which one indicated the NFS and which one indicated SMB. But I have given a lot of help in solving problems and I realize that there are a fair number of users who have very little insight about either of these OS's. And I would even more larger percentage don't associate NFS to Linux and SMB to Windows! After all, I would imagine that many Linux distributions now contain Samba and Windows PRO has NFS included. (You do have to turn it on as the default is off...)

The original poster in that thread that I linked to basically made that mistake. If I had not asked him to walk through the steps that he was using try to set things up, it would have a much longer troubleshooting process.

Just now, Frank1940 said:

Please understand that I am not trying to be difficult. As someone who is reasonably knowledgeable about both Linux and Windows, I instantly recognized which one indicated the NFS and which one indicated SMB. But I have given a lot of help in solving problems and I realize that there are a fair number of users who have very little insight about either of these OS's. And I would even more larger percentage don't associate NFS to Linux and SMB to Windows! After all, I would imagine that many Linux distributions now contain Samba and Windows PRO has NFS included. (You do have to turn it on as the default is off...)

The original poster in that thread that I linked to basically made that mistake. If I had not asked him to walk through the steps that he was using try to set things up, it would have a much longer troubleshooting process.

The choice to use those icons was made by the original author of UD. I thought at the time it was a bit too "folksy". If tags were added "SMB" and "NFS" would that make much difference? Do users understand the difference between "SMB" and "NFS"?

Maybe more explanation on the dialog just above the warning statement?
"Select the Penguin icon for Linux NFS. Select the Window icon for Windows SMB"

2 minutes ago, dlandon said:

Maybe more explanation on the dialog just above the warning statement?
"Select the Penguin icon for Linux NFS. Select the Window icon for Windows SMB"

That would definitely work. If I were doing it, I would say "Linux NFS protocol" and "Windows SMB protocol". (But that is because I am a bit anal about nomenclature. 😈 )

Definitely think at least labels below the icons to say what they are would be useful. Some people may not know what they are but those who do would at least have a clearer description.

54 minutes ago, Frank1940 said:

That would definitely work. If I were doing it, I would say "Linux NFS protocol" and "Windows SMB protocol". (But that is because I am a bit anal about nomenclature. 😈 )

Hi!

New to unraid and this plugin. I have successfully had one drive recgonzied and started a preclear operation on it. I've installed a new drive while this was happening as well; should unassigned devices see this new drive right away even while the first preclear is still running? So far it's been about ten minutes and hasn't shown up yet. Not sure if it's an issue with my drive/enclosure as it's a new enclsoure I'm adding - or if I simply need to wait until the first preclear is done for it to show up.

Thank you!

53 minutes ago, kamcknig said:

should unassigned devices see this new drive right away even while the first preclear is still running?

Yep.

1 minute ago, JorgeB said:

Yep.

OK, thanks, My old enclosure is full now so I can't put it in there to try, but at least it shouldn't be a plugins issue. 👍

Edited July 21, 2025Jul 21 by kamcknig

2 minutes ago, kamcknig said:

OK, thanks, My old enclosure is full now so I can't put it in there to try, but at least it shouldn't be a plugins issue. 👍

Well I simply power-cycled the new enclosure and reconnected the USB; worked like a charm. Thank you.

Hi. Good day to all. I hope someone can shed light in this issue. Clicking the settings icon will (try) to go to the settings page but will immediately go back to the main page. What is causing this?

Thanks in advance.

mckanor-diagnostics-20250725-0256.zip

A friend of mine also found an easier workaround. Even with SMB disabled in unassigned devices he was able to share a folder through SMB extra settings from Unraid Settings:

[backup]
       path = /mnt/disks/backup
       comment =
       browseable = yes
        public = no
       writeable = yes
       valid users =  username
       short preserve case = yes
       vfs objects =

Note: one will have to stop the array to make changes to SMB Unraid settings

Edited August 5, 2025Aug 5 by jcsantos

Hello

Running into an issue with remote SMB shares.

I've got my primary unraid server mounted to my backup storage server via UD's remote SMB share.

The remote is my main server, so I have it mounted via its IP address on my backup server.

I can search and mount the remote share just fine but as soon as I try to either browse the files with the unraid file manager or try to navigate to the "remotes" folder in something like Appdata Backup, it locks up and starts throwing errors.

 

Source and Target: 6.12.15

Ive had this set up and working for almost a year and nothing about my setup has changed recently. So unsure as to what the issue is.

Aug  7 02:21:55 Parallax kernel: CIFS: Attempting to mount \\ZENITH.LOCAL\ZenithArray
Aug  7 02:22:10 Parallax kernel: CIFS: VFS: cifs_mount failed w/return code = -512
Aug  7 02:22:10 Parallax unassigned.devices: Warning: shell_exec(/sbin/mount -t cifs -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_ZenithArray' '//ZENITH.LOCAL/ZenithArray' '/mnt/remotes/ZenithArray' 2>&1) took longer than 15.0s!
Aug  7 02:22:10 Parallax unassigned.devices: Mount SMB share '//ZENITH.LOCAL/ZenithArray' using SMB 3.0 protocol.
Aug  7 02:22:10 Parallax unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,vers=3.0,credentials='/tmp/unassigned.devices/credentials_ZenithArray' '//ZENITH.LOCAL/ZenithArray' '/mnt/remotes/ZenithArray'
Aug  7 02:22:10 Parallax kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified
Aug  7 02:22:10 Parallax kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified
Aug  7 02:22:10 Parallax kernel: CIFS: Attempting to mount \\ZENITH.LOCAL\ZenithArray
Aug  7 02:22:10 Parallax unassigned.devices: Successfully mounted '//ZENITH.LOCAL/ZenithArray' on '/mnt/remotes/ZenithArray'.
Aug  7 02:22:10 Parallax unassigned.devices: Device '//ZENITH/ZenithArray' is not set to be shared.
Aug  7 02:22:24 Parallax unassigned.devices: Unmounting Remote SMB/NFS Share '//ZENITH/ZenithArray'...
Aug  7 02:22:24 Parallax unassigned.devices: Synching file system on '/mnt/remotes/ZenithArray'.
Aug  7 02:22:24 Parallax unassigned.devices: Unmount cmd: /sbin/umount -t cifs -l '/mnt/remotes/ZenithArray' 2>&1
Aug  7 02:22:24 Parallax unassigned.devices: Successfully unmounted '//ZENITH.LOCAL/ZenithArray'
Aug  7 02:24:13 Parallax kernel: CIFS: VFS: \\ZENITH.LOCAL has not responded in 180 seconds. Reconnecting...

parallax-diagnostics-20250807-0250.zip

Hey Everyone!
I have unassigned devices Installed and wanna mount a Fat32 formated USB drive. It's also MBR and not GPT

the mount button is greyed out. I don't know why :-\ I am pretty new to Unraid. Can someone help?

18 hours ago, psxmicha said:

the mount button is greyed out.

Does it have a partition?

Post the output from blkid /dev/sdX and blkid /dev/sdX1

Replace X with the correct identifier.

@dlandon First off, thank you so much for your hard work on developing this plugin - as a (newish) Unraid user, it has been quite helpful! Recently I bought some NVMe modules in preparation for a new server I'm going to build. I bought a couple Sabrent USB NVMe enclosures (Model EC-SNVE) for the NVMe modules to test out Unraids pool functionality. However, I noticed a couple problems:

1. UA recognizes the Sabrent enclosure, but not the NVMe modules.

2. UA sees both of the enclosures as the same device, showing each drive as separate partitions of the same device.

3. UA seemingly can't distinguish between the two Sabrent enclosures because the controller on each one is programmed with the same serial.

4. To get UA to recognize the NVMe modules (and thus see each device as distinct devices), I had to do the following:

   • # Edit the udev rule

     nano /etc/udev/rules.d/99-nvme-serial-mapping.rules

   • # Create unique by-id entries based on NVMe serials and USB port location

     SUBSYSTEM=="block", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000001*", ENV{ID_SERIAL}="Sabrent_NVMe_1000000001", ENV{ID_SERIAL_SHORT}="1000000001", SYMLINK+="disk/by-id/nvme-Sabrent_1000000001%n"

     SUBSYSTEM=="block", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000002*", ENV{ID_SERIAL}="Sabrent_NVMe_1000000002", ENV{ID_SERIAL_SHORT}="1000000002", SYMLINK+="disk/by-id/nvme-Sabrent_1000000002%n"

   • # Also create unique USB-style identifiers by port location

     SUBSYSTEM=="block", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="9210", KERNELS=="1-3:*", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000001*", SYMLINK+="disk/by-id/usb-Sabrent_SSD_1000000001-0:0%n"

     SUBSYSTEM=="block", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="9210", KERNELS=="1-1:*", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000002*", SYMLINK+="disk/by-id/usb-Sabrent_SSD_1000000002-0:0%n"

   • # Reload rules

     udevadm control --reload-rules

     udevadm trigger

Do you have any recommendations on any other way to work with this issue?

I am no longer working on this plugin. LT has taken over the maintenance and support. You will need to contact them about any issues or concerns you have. Future releases will come from them, and not me.

14 hours ago, RockTheCatbox said:

because the controller on each one is programmed with the same serial.

This is a problem with UD and also Unraid in general. It requires that all the devices have a unique serial number, since that is used to track the devices. The best bet is to replace one of the enclosures with a different brand/model.