Greetings,

I'm not sure what the value is for UD having an option to format NTFS. I wanted to use the function to backup my data, then be able to pull out the drive, attach to a PC, then transfer any files. The problem I've run into is that no drive formatted by UD can be used on any Windows PC. And any Windows PC NTFS formatted drive can't be used with UD. All I get is a "Format" option.

Am I missing something about the NTFS function? It seems to be rather ineffective and not much use to Windows users.

I appreciate any feedback about this.

/thx

27 minutes ago, mattm1121 said:

And any Windows PC NTFS formatted drive can't be used with UD.

Something is missing there, Windows formatted drives can be mounted with UD; that's the point of supporting NTFS, and they also can now be mounted in the array or a pool since Unraid 7.2 (basic volumes only, dynamic volumes won't work), and vice versa, you format a DRIVE NTFS with Unraid and then mount it in Windows.

All of a sudden unassigned devices is resetting the SMB share setting back to DISABLED after a reboot of the UNRAID host. I have to manually go in to settings and manually change the setting back to PRIVATE each time, very annoying.

Not sure when this started but im runnig 7.2 RC2 and latest plugin version.

15 hours ago, mikeyosm said:

All of a sudden unassigned devices is resetting the SMB share setting back to DISABLED after a reboot of the UNRAID host. I have to manually go in to settings and manually change the setting back to PRIVATE each time, very annoying.

Not sure when this started but im runnig 7.2 RC2 and latest plugin version.

It's a known/reported issue but have not seen a fix yet.

My slightly complicated solution is here but will continue to work once the plugin is fixed.

Another solution was proposed here. A modified version of that solution is to setup everything how you like it in Unassigned Devices settings. Then look at the contents of file /etc/samba/unassigned-shares/Shares-Pools.conf. Copy the entire [Shares-Pools] block and append to the bottom of the "Samba extra configuration" section in SMB Settings, though rename to Shares-PoolsFixed or something. Restart and that should work as well, though it leaves extra crud in the configuration that requires cleanup once the plugin is fixed.

9 hours ago, coffee1978 said:

It's a known/reported issue but have not seen a fix yet.

Does this happen always? I cannot reproduce, if you can reproduce it every time, please give the steps needed.

2 hours ago, JorgeB said:

Does this happen always? I cannot reproduce, if you can reproduce it every time, please give the steps needed.

All i do is enable a share in UD settings, mark it as private, select a user and apply. The setting sticks until I reboot UNRAID after which, the setting reverts back to disabled so I have to manually enable the share again.

1 hour ago, mikeyosm said:

mark it as private, select a user and apply.

Ahh, so the issue is not the export option getting disabled, but the private settings for UD resetting. I was testing with a public share, I can reproduce now.

Need some help.

I'm unable to change UD settings.
I get the following log message when I hit apply after making a change to settings.

Nov 2 12:34:10 Discovery webgui: File_put_contents_atomic failed to write / rename /tmp/unassigned.devices/config/unassigned.devices.cfg

I'm also having external drives come up as ARRAY and unable to mount until rebooting. Even drives I've previously mounted using UD.

Nov  2 12:41:26 Discovery kernel: usb 4-5: new SuperSpeed USB device number 4 using xhci_hcd
Nov  2 12:41:26 Discovery kernel: usb-storage 4-5:1.0: USB Mass Storage device detected
Nov  2 12:41:26 Discovery kernel: scsi host13: usb-storage 4-5:1.0
Nov  2 12:41:27 Discovery kernel: scsi 13:0:0:0: Direct-Access     WD       Elements 2667    2007 PQ: 0 ANSI: 6
Nov  2 12:41:27 Discovery kernel: sd 13:0:0:0: Attached scsi generic sg11 type 0
Nov  2 12:41:27 Discovery kernel: sd 13:0:0:0: [sdk] Spinning up disk...
Nov  2 12:41:27 Discovery kernel: scsi 13:0:0:1: Enclosure         WD       SES Device       2007 PQ: 0 ANSI: 6
Nov  2 12:41:27 Discovery kernel: ses 13:0:0:1: Attached Enclosure device
Nov  2 12:41:27 Discovery kernel: ses 13:0:0:1: Attached scsi generic sg12 type 13
Nov  2 12:41:27 Discovery kernel: ses 13:0:0:1: Wrong diagnostic page; asked for 1 got 8
Nov  2 12:41:27 Discovery kernel: ses 13:0:0:1: Failed to get diagnostic page 0x1
Nov  2 12:41:27 Discovery kernel: ses 13:0:0:1: Failed to bind enclosure -19
Nov  2 12:41:33 Discovery kernel: ......ready
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] Very big device. Trying to use READ CAPACITY(16).
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] 9767475200 512-byte logical blocks: (5.00 TB/4.55 TiB)
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] 4096-byte physical blocks
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] Write Protect is off
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] Mode Sense: 3f 00 10 00
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] No Caching mode page found
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] Assuming drive cache: write through
Nov  2 12:41:33 Discovery kernel: sdk: sdk1
Nov  2 12:41:33 Discovery kernel: sd 13:0:0:0: [sdk] Attached SCSI disk
Nov  2 12:41:35 Discovery unassigned.devices: Disk with ID 'WD_Elements_2667_57584432444231363130534E-0:0 ()' is not set to auto mount.

7 hours ago, gamerkonks said:

I get the following log message when I hit apply after making a change to settings

Try uninstalling the plugin, then delete its folder from the flash drive, and reinstall.

7 hours ago, gamerkonks said:

I'm also having external drives come up as ARRAY and unable to mount until rebooting.

I've seen this before but cannot reproduce it consistently, recommend posting the ud_diagnostics (type that in thge CLI) after connecting a device that shows that issue.

20 hours ago, JorgeB said:

Try uninstalling the plugin, then delete its folder from the flash drive, and reinstall.

I've seen this before but cannot reproduce it consistently, recommend posting the ud_diagnostics (type that in thge CLI) after connecting a device that shows that issue.

Thanks, that seems to have fixed being able to change settings.

I'm also having an issue where sometimes the USED and FREE values are incorrect, i.e both 0 B.
Any ideas what could be causing this?

3 hours ago, gamerkonks said:

I'm also having an issue where sometimes the USED and FREE values are incorrect, i.e both 0 B.
Any ideas what could be causing this?

Not really, is it always with the same device, and sometimes it works?

1 hour ago, JorgeB said:

Not really, is it always with the same device, and sometimes it works?

Not sure. I'll see it I can experiment and find a pattern.

On 11/2/2025 at 8:32 PM, JorgeB said:

Try uninstalling the plugin, then delete its folder from the flash drive, and reinstall.

I'm unable to enable destructive mode again.
I've updated to 7.2 and rebooted, so maybe it broke again after the reboot?
uninstall / delete / reinstall fixes it again but annoying having to do it again.
Diagnostics attached.
discovery-diagnostics-20251104-2018.zip

On 11/4/2025 at 4:19 AM, gamerkonks said:

I'm unable to enable destructive mode again.
I've updated to 7.2 and rebooted, so maybe it broke again after the reboot?
uninstall / delete / reinstall fixes it again but annoying having to do it again.
Diagnostics attached.
discovery-diagnostics-20251104-2018.zip

When you see the failed to write / rename being logged, try it again. If it happens again, then go to Plugins, Install Plugin and enter in this URL

https://preview.dl.unraid.net/pr-plugins/pr-2446/webgui-pr-2446.plg

Then try it again. Same error should be logged, but with more information. Then repost your diagnostics. Your issue may be related to why some people have SMB settings reset after reboots. I can't replicate your issue, nor the SMB issue.

Foung bug: after click on device script in console:

DeviceSettings?s=ST12000NM000J-2TY103_ZRT19X77&l=&p=1&t=true:2003 Uncaught TypeError: crypto.randomUUID is not a function

at openFileBrowserDevice (DeviceSettings?s=ST12000NM000J-2TY103_ZRT19X77&l=&p=1&t=true:2003:45)

at HTMLInputElement.onclick (DeviceSettings?s=ST12000NM000J-2TY103_ZRT19X77&l=&p=1&t=true:1608:328)

3 hours ago, piciuok said:

Foung bug: after click on device script in console:

DeviceSettings?s=ST12000NM000J-2TY103_ZRT19X77&l=&p=1&t=true:2003 Uncaught TypeError: crypto.randomUUID is not a function

at openFileBrowserDevice (DeviceSettings?s=ST12000NM000J-2TY103_ZRT19X77&l=&p=1&t=true:2003:45)

at HTMLInputElement.onclick (DeviceSettings?s=ST12000NM000J-2TY103_ZRT19X77&l=&p=1&t=true:1608:328)

I'll catch that. But what it's caused by is that you've got Settings - Management Settings set to Use SSL: NO. Setting to Yes / Strict or accessing via TailScale's URL wouldn't have issued the error.

This is a browser enforced thing. But, I'll catch this and handle it on the next release.

Thanks.

Hi all, im having problems getting a reliable SMB connection.

I have two unraid servers, NAS and NASBACKUP.

I am trying to move all data from NAS -> NASBACKUP by mounting the backup server as a SMB mount on NAS. Then using FreeFileSync docker to move the data. There is a large amount of data to move, about ~100 TB.

The problem is the connection is not reliable. I get random CIF drops all the time like this:

Nov 14 16:51:58 nas kernel: CIFS: VFS: \\NASBACKUP.LAN.LOCAL sends on sock 0000000032302d62 stuck for 15 seconds

Nov 14 16:53:00 nas kernel: CIFS: VFS: \\NASBACKUP.LAN.LOCAL Send error in SessSetup = -11

Sometimes I can go 24 hours without an error, sometimes I get them within minutes of mounting. I can't tell what server the problem lies in, but i've attached diags from both of them. Even giving each server a separate NIC and directly attaching them gives the same behavior. Unfortunately, FreeFilySync does not gracefully recover from this and requires manual intervention every time this happens. It's greatly slowing down my backup progress.

nas-diagnostics-20251114-1653.zip nasbackup-diagnostics-20251114-1654.zip

Got some "new" behaviour from unassigned devices: log spam. For some weird reason since I updated to 7.2.1rc1 (I had to because of the ZFS array bug blocking writes after a mover operation) several days ago, then didn't think about it, but it seems that for some reason, the PHP log is now spammed with messages about some "undefined" entry (not sure what an "array key" is).

I haven't changed to even swapped drives in forever. Those are the same drives as pre 7.2 upgrade

I attached also the diagnostics file just in case

unraid-diagnostics-20251118-1133.zip

23 minutes ago, denishay said:

Got some "new" behaviour from unassigned devices: log spam. For some weird reason since I updated to 7.2.1rc1 (I had to because of the ZFS array bug blocking writes after a mover operation) several days ago, then didn't think about it, but it seems that for some reason, the PHP log is now spammed with messages about some "undefined" entry (not sure what an "array key" is).

I haven't changed to even swapped drives in forever. Those are the same drives as pre 7.2 upgrade

I attached also the diagnostics file just in case

unraid-diagnostics-20251118-1133.zip

Thinking a bit deeper about it, I am wondering if it was not since this morning. Even after a restart I see the log usage climbing at neck breaking speed. There is not way it stayed like that for several days.

Was there an update this morning? How can we install an "older" version of the plugin? (the Github is archived??)

Is there anyway to spin down my external hdd attached via USB using this plugin on the default Unraid spin down timer?

I've encountered a possible issue or it could just be me not following proper procedure; wanted to get some input.

Unraid version: 7.2.2

When I do the following steps:

1) Physically install disk formatted with NTFS

2) Start Unraid and use Unassigned Devices to clear partitions and format to XFS (Destructive Mode enabled)

3) Stop array, add disk to array, and start array

4) Disk shows as Unmountable: unsupported or no file system. Unraid requests I format in order for the disk to be available for use

5) Format, disk goes green and becomes available in the array

6) Reboot Unraid

7) Array is not started with error "Too many wrong and/or missing disks!"

At this point, I can't seem to get the drive to come back. Tried xfs_repair, no luck. New config allowed me to get the array back online, but the disk showed as Unmountable due to missing filesystem and wanted to format it again.

This only happens to disks that start off as NTFS when physically installed. I normally don't use take this path, but had a drive I brought over from a Windows box that I used as an Unassigned Device (formatted with XFS) for a while before moving it into the array. If I skip using Unassigned Devices or bring over a drive that is XFS already, Unraid stays happy. Confirmed this also occurs on another Unraid box I have.

Logs attached from after reboot, step 6.

Is this expected behavior?

unraid-diagnostics-20251202-1656.zip

Edited December 8, 2025Dec 8 by 6stringdesigns

3 hours ago, 6stringdesigns said:

2) Start Unraid and use Unassigned Devices to clear partitions and format to XFS (Destructive Mode enabled)

3) Stop array, add disk to array, and start array

4) Disk shows as Unmountable: unsupported or no file system. Unraid requests I format in order for the disk to be available for use

This should not happen, but why are you preformatting the disk with UD? Assuming it's a new disk with no data, try this:

Add the new disk to the array

If the disk has a previous filesystem that you want to remove, click on the disk before arary start and then "erase"

start array

Format the disk.

5 minutes ago, JorgeB said:

This should not happen, but why are you preformatting the disk with UD? Assuming it's a new disk with no data, try this:

Add the new disk to the array

If the disk has a previous filesystem that you want to remove, click on the disk before arary start and then "erase"

start array

Format the disk.

Hey Jorge, thanks for responding.

Reason: I normally don't take this path, but had a drive I brought over from a Windows box that I used as an Unassigned Device (formatted with XFS) for a while before moving it into the array. If I skip using Unassigned Devices or bring over a drive that is XFS already, Unraid stays happy. I've also confirmed this same issue happens on my other Unraid box.

Yes, following your steps, no issue. This issue is only present when following my original steps.

Further investigating shows the UDEV UUID changing on the disk after clearing/formatting with UD. If I restart Unraid after my step 2, then proceed with the rest of the steps, no issue. Not sure if relevant, but jumped out at me.

13 hours ago, 6stringdesigns said:

This issue is only present when following my original steps.

Further investigating shows the UDEV UUID changing on the disk after clearing/formatting with UD. If I restart Unraid after my step 2, then proceed with the rest of the steps, no issue. Not sure if relevant, but jumped out at me.

I don't see that logged in the diags posted, reboot the server to clear the logs, do the steps you were doing that have the issue, and then post new diags.

6 hours ago, JorgeB said:

I don't see that logged in the diags posted, reboot the server to clear the logs, do the steps you were doing that have the issue, and then post new diags.

Disk serial: WDC_WD40EFRX-68WT0N0

After physically installed (steps 1 + power on Unraid box), UUID: 0f809849-8df2-414b-ae61-9f908a5bfacc

Log: tower-diagnostics-20251209-0949-one

After clearing partitions and formatting with UD (step 2, post power on), UUID changes to: b6eaeb81-b78a-4644-9d0a-2fe3f7679a20
Log: tower-diagnostics-20251209-0951-two

After adding disk to the array and formatting again (steps 3-5). Log: tower-diagnostics-20251209-0955-three

After rebooting and being met with 'wrong disk' error (step 6-7). Log: tower-diagnostics-20251209-0959-four

tower-diagnostics-20251209-0959-four.zip tower-diagnostics-20251209-0955-three.zip tower-diagnostics-20251209-0951-two.zip tower-diagnostics-20251209-0949-one.zip