22 minutes ago, 6stringdesigns said:

WDC_WD40EFRX-68WT0N0

This is the model, but I assume it's disk11.

22 minutes ago, 6stringdesigns said:

UUID changes to

After a format, it's normal for the UUID to change.

I think I see what the issue is, possibly related to the latest changes to 1 MiB aligned sectors, and I think it's happening because you don't have parity, I'll need to do some tests to confirm, but for now, just do what I mentioned above; it's the faster way anyway and the standard procedure.

13 minutes ago, JorgeB said:

This is the model, but I assume it's disk11.

Correct, disk 11.

13 minutes ago, JorgeB said:

After a format, it's normal for the UUID to change.

Good to know, thanks.

13 minutes ago, JorgeB said:

I think I see what the issue is, possibly related to the latest changes to 1 MiB aligned sectors, and I think it's happening because you don't have parity, I'll need to do some tests to confirm, but for now, just do what I mentioned above; it's the faster way anyway and the standard procedure.

Correct, I do not have parity at the moment. Appreciate you taking the time to dig into this.

30 minutes ago, 6stringdesigns said:

Correct, I do not have parity at the moment. Appreciate you taking the time to dig into this.

I see the issue; it's not because of not having parity, it's similar to the current issue with the Preclear plugin, where a precleared disk is only detected correctly by Unraid after a reboot.

The problem is that you are booting with a disk partitioned on sector 2048, then erasing and reformatting with UD, which will reformat the disk with a standard Unraid partition layout on sector 64, but when you assign the disk to the array, Unraid still detects the old sector 2048 but records the disk as using sector 64, hence the "disk wrong" after a reboot.

So for now, if you want to keep doing what you were doing, you would need to reboot the server between steps 2 and 3, though, like I mentioned, the steps I posted before are much simpler.

27 minutes ago, JorgeB said:

I see the issue; it's not because of not having parity, it's similar to the current issue with the Preclear plugin, where a precleared disk is only detected correctly by Unraid after a reboot.

The problem is that you are booting with a disk partitioned on sector 2048, then erasing and reformatting with UD, which will reformat the disk with a standard Unraid partition layout on sector 64, but when you assign the disk to the array, Unraid still detects the old sector 2048 but records the disk as using sector 64, hence the "disk wrong" after a reboot.

So for now, if you want to keep doing what you were doing, you would need to reboot the server between steps 2 and 3, though, like I mentioned, the steps I posted before are much simpler.

Will do and thank again. Is there any sort of bug tracker or forum post I can follow regarding this issue?

24 minutes ago, 6stringdesigns said:

Is there any sort of bug tracker or forum post I can follow regarding this issue?

There isn't a big report for this, but you can follow the preclear plugin support thread; once the issue is fixed, I'll post an update there.

Is there or will there be a fix for the log spam when using root folder "Uploading Attachment...option and possibly be able to use root share and disk shares at the same time?

Thanks

I have a 14 TB drive that is full that I need to get the data off of that. I was using on my Mac just within an enclosure to USB. I tried mounting it on Unraid over USB but I would very often get to dangerous temperatures. I tried connecting it via SATA directly to Unraid, but for some reason, it would not mount now. The drive still works fine on Mac but I feel like transferring 14 TB over the network would take too long. Any suggestions?

4 hours ago, klnadler said:

I tried connecting it via SATA directly to Unraid, but for some reason, it would not mount now.

That suggests the USB bridge is not transparent.

4 hours ago, JorgeB said:

That suggests the USB bridge is not transparent.

What does that mean in terms of mounting it via sata

1 hour ago, klnadler said:

What does that mean in terms of mounting it via sata

It means the disk/partition info doesn't show up the same via USB and SATA

Ran into a snag where I couldn't format a USB drive as exFAT. It kept complaining that mkfs.exfat wasn't found. Wiped out the plugin and reinstalled. AHA!

Downloading plugin
plugin: installing: unassigned.devices-plus.plg
Executing hook script: CA_preHook
Clearing Community Applications plugin cache
Executing hook script: pre_plugin_checks
plugin: skipping: parted-3.6-x86_64-1.txz - Unraid version too high, requires at most version 7.1.9
plugin: skipping: exfat-utils-1.3.0-x86_64-1_slonly.txz - Unraid version too high, requires at most version 7.1.9
plugin: skipping: fuse-exfat-1.3.0-x86_64-1_slonly.txz - Unraid version too high, requires at most version 7.1.9

Alright... now what. As far as I can tell, it's the latest version of unassigned.devices-plus.plg. There was an update in the changelog, but the update just says "don't do it".

2025.08.05

• Changed: Don't install exFat or parted when running OS 7.2+

4 hours ago, Suspi said:

Ran into a snag where I couldn't format a USB drive as exFAT. It kept complaining that mkfs.exfat wasn't found. Wiped out the plugin and reinstalled. AHA!

Which Unraid release? Unraid 7.2.x includes exFAT support.

I have an issue after formatting an external disk (USB enclosure) as xfs encrypted. Everything works (it shows FS "luks" after formatting) but then after mounting it no longer seems to be encrypted.

In UD it does not contain the encryption symbol (on the left), and also when I open the disk in file manager there is no indication in the "source" column (Disk, not encrypted). In UD FS column after mounting changes to just plain xfs (without encryption).

What could be wrong?

Edited December 22, 2025Dec 22 by Bash2686

9 minutes ago, Bash2686 said:

I have an issue after formatting an external disk (USB enclosure) as xfs encrypted. Everything works (it shows FS "luks" after formatting) but then after mounting it no longer seems to be encrypted.

Please post the diagnostics.

Just now, JorgeB said:

Please post the diagnostics.

Already did, sorry. I attached it to the original post. Thanks :)

The disk was initially being mounted as~xfs encrypted.

Dec 21 11:34:26 MAINBASE unassigned.devices: Mounting partition 'sdf1' at mountpoint '/mnt/disks/WD-WCAY01333108'...

Dec 21 11:34:26 MAINBASE unassigned.devices: Using disk password to open the 'crypto_LUKS' device.

Dec 21 11:34:28 MAINBASE unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/mapper/WD-WCAY01333108' '/mnt/disks/WD-WCAY01333108'

Dec 21 11:34:28 MAINBASE kernel: XFS (dm-3): Mounting V5 Filesystem e93cf24b-c99e-46af-b4d4-f7bf018a7794

Dec 21 11:34:29 MAINBASE kernel: XFS (dm-3): Ending clean mount

Dec 21 11:34:29 MAINBASE unassigned.devices: Successfully mounted '/dev/mapper/WD-WCAY01333108' on '/mnt/disks/WD-WCAY01333108'.

But looks like you reformatted it with ntfs, that cannot be LUKS encrypted with UD:

Dec 21 11:52:45 MAINBASE unassigned.devices: Mounting partition 'sdf1' at mountpoint '/mnt/disks/WD-WCAY01333108'...

Dec 21 11:52:45 MAINBASE unassigned.devices: Mount cmd: /sbin/mount -t 'ntfs' -o rw,relatime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdf1' '/mnt/disks/WD-WCAY01333108'

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Version 2022.10.3 integrated FUSE 27

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Mounted /dev/sdf1 (Read-Write, label "", NTFS 3.1)

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Cmdline options: rw,relatime,nodev,nosuid,nls=utf8,umask=000

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Mount options: nodev,nosuid,nls=utf8,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sdf1,blkdev,blksize=4096

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Global ownership and permissions enforced, configuration type 1

Dec 21 11:52:48 MAINBASE unassigned.devices: Successfully mounted '/dev/sdf1' on '/mnt/disks/WD-WCAY01333108'.

2 minutes ago, JorgeB said:

The disk was initially being mounted as~xfs encrypted.

Dec 21 11:34:26 MAINBASE unassigned.devices: Mounting partition 'sdf1' at mountpoint '/mnt/disks/WD-WCAY01333108'...

Dec 21 11:34:26 MAINBASE unassigned.devices: Using disk password to open the 'crypto_LUKS' device.

Dec 21 11:34:28 MAINBASE unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/mapper/WD-WCAY01333108' '/mnt/disks/WD-WCAY01333108'

Dec 21 11:34:28 MAINBASE kernel: XFS (dm-3): Mounting V5 Filesystem e93cf24b-c99e-46af-b4d4-f7bf018a7794

Dec 21 11:34:29 MAINBASE kernel: XFS (dm-3): Ending clean mount

Dec 21 11:34:29 MAINBASE unassigned.devices: Successfully mounted '/dev/mapper/WD-WCAY01333108' on '/mnt/disks/WD-WCAY01333108'.

But looks like you reformatted it with ntfs, that cannot be LUKS encrypted with UD:

Dec 21 11:52:45 MAINBASE unassigned.devices: Mounting partition 'sdf1' at mountpoint '/mnt/disks/WD-WCAY01333108'...

Dec 21 11:52:45 MAINBASE unassigned.devices: Mount cmd: /sbin/mount -t 'ntfs' -o rw,relatime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdf1' '/mnt/disks/WD-WCAY01333108'

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Version 2022.10.3 integrated FUSE 27

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Mounted /dev/sdf1 (Read-Write, label "", NTFS 3.1)

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Cmdline options: rw,relatime,nodev,nosuid,nls=utf8,umask=000

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Mount options: nodev,nosuid,nls=utf8,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sdf1,blkdev,blksize=4096

Dec 21 11:52:48 MAINBASE ntfs-3g[1482682]: Global ownership and permissions enforced, configuration type 1

Dec 21 11:52:48 MAINBASE unassigned.devices: Successfully mounted '/dev/sdf1' on '/mnt/disks/WD-WCAY01333108'.

Yes, but the ntfs action was just to try VeraCrypt some time later. I will post a clean sequence where I just go from creating xfs-encrypted to mount and also post screenshots. It's really strange because the logs say it was created encrypted but after mount nothing in the GUI is indicating encryption (e.g. Disk column says "Not encrypted" and FS column says just "xfs").

P.S. Maybe it's just a visual bug? I am new to Linux so I have currently no easy way to verify the existing encryption besides what GUI and basic logs are showing me.

Edited December 21, 2025Dec 21 by Bash2686

6 minutes ago, Bash2686 said:

P.S. Maybe it's just a visual bug?

It's possible, at least that time the disk was really encrypted.

On 12/21/2025 at 6:56 PM, JorgeB said:

It's possible, at least that time the disk was really encrypted.

I managed to create the supposedly encrypted partition. I attached screenshots of the log showing encrypted mount, and then what is showing in the GUI, including file manager view.

What do you think? Something is wrong here, there is a green lock symbol on the left side in UD, but not on the right side in FS column (usually showing xfs-encrypted). Also in file manager in location column also showing no encryption.

Edited December 22, 2025Dec 22 by Bash2686

14 minutes ago, Bash2686 said:

What do you think? Something is wrong here, there is a green lock symbol on the left side in UD, but not on the right side in FS column (usually showing xfs-encrypted).

Nothing is wrong. That's how UD shows an excrypted disk. The file system shows 'luks' when the disk is not mounted, and the actual file system when it is mounted. The lock next to the orb will show when it is an encrypted disk. Closed when the disk is not mounted - locked, and open when the disk is mounted - unlocked.

UD has never shown 'xfs-encrypted' on the file system. That is the selection for an xfs encrypted partition when formatting the disk.

The disk is encrypted.

As for the file manager, it is probably not aware of the encrypted status of a UD disk.

1 minute ago, dlandon said:

Nothing is wrong. That's how UD shows an excrypted disk. The file system shows 'luks' when the disk is not mounted, and the actual file system when it is mounted. The lock next to the orb will show when it is an encrypted disk. Closed when the disk is not mounted - locked, and open when the disk is mounted - unlocked.

UD has never shown 'xfs-encrypted' on the file system. That is the selection for an xfs encrypted partition when formatting the disk.

The disk is encrypted.

As for the file manager, it is probably not aware of the encrypted status of a UD disk.

Thanks! I was not aware of the differences between what/how it is showing in the array section and in UD (assumed it would be identical). File manager not displaying encryption also threw me off, as array disks show the green icon just fine.

One last question, or 2 actually;

If I enter a disk password in UD settings, how is this password stored in the background? Plaintext? Is there any increased risk regarding compromising the password (e.g. stored somewhere on file level)?

How can UD - if the same password is used for unassigned disks and main array - "read" the password (from RAM I believe)?

Edited December 22, 2025Dec 22 by Bash2686

39 minutes ago, Bash2686 said:

One last question, or 2 actually;

If I enter a disk password in UD settings, how is this password stored in the background? Plaintext? Is there any increased risk regarding compromising the password (e.g. stored somewhere on file level)?

How can UD - if the same password is used for unassigned disks and main array - "read" the password (from RAM I believe)?

• A UD disk password is encrypted and stored on the flash drive - never in plain ascii. Don't share the flash drive (using SMB of NFS) if you'e concerned about file access security. If someone physically obtains your flash disk, you'd have bigger problems. A UD disk password is used momentarily (stored in a tmpfs file) to unlock a disk and then immediately shredded after the disk is mounted. The mount command uses the password from the tmps memory file so it is not exposed in the log in any way.

• UD asks Unraid through an api command to unlock an encrypted disk when the array password is used. UD has no visibility into the array password and has no ability to access it.

Rest assured, security has been considered in all Unraid and UD do to handle encrypted disks and passwords.

The encrypted lock was how Unraid used to show an encrypted disk. I don't currently have any encrypted array or pool disks, so I don't know how the UI is showing encrypted disks these days.

Post a screen shot of how Unraid is currently showing encrypted disks. I'd be interested in seeing how it is currenly being done.

Edit:

This is a log snippet of an encrypted UD mount using the Unraid api to get the password:
Dec 22 15:37:02 BackupServer unassigned.devices: Mounting partition 'sdf1' at mountpoint '/mnt/disks/Testing--dataset'...

Dec 22 15:37:02 BackupServer emhttpd: shcmd (422611): /usr/sbin/cryptsetup luksOpen '/dev/sdf1' 'Testing--dataset' --key-file=/root/keyfile <= Unraid api call opened the luks device

Dec 22 15:37:14 BackupServer unassigned.devices: Mount cmd: /sbin/mount -t 'ntfs' -o rw,relatime,nodev,nosuid,nls=utf8,umask=000 '/dev/mapper/Testing--dataset' '/mnt/disks/Testing--dataset'

Dec 22 15:37:14 BackupServer ntfs-3g[3702069]: Version 2022.10.3 integrated FUSE 27

Dec 22 15:37:14 BackupServer ntfs-3g[3702069]: Mounted /dev/mapper/Testing--dataset (Read-Write, label "Testing--dataset", NTFS 3.1)

Dec 22 15:37:14 BackupServer ntfs-3g[3702069]: Cmdline options: rw,relatime,nodev,nosuid,nls=utf8,umask=000

Dec 22 15:37:14 BackupServer ntfs-3g[3702069]: Mount options: nodev,nosuid,nls=utf8,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/mapper/Testing--dataset,blkdev,blksize=4096 <= mounted device is mapper, an encrypted disk

Edited December 22, 2025Dec 22 by dlandon

58 minutes ago, dlandon said:

Post a screen shot of how Unraid is currently showing encrypted disks. I'd be interested in seeing how it is currenly being done.

Thanks for the insight. Much appreciated. Screenshots below, it actually does not say "xfs-encrypted" in the FS column but shows a green lock next to it. In the file manager it seems to be more consistent as it does show a green lock and also hover text confirming the encryption while on UD mounted disks the file manager seems to be not recognizing the encryption (sadly).

So, to be protected against theft of the server/NAS (including the USB drive) it is more secure to use the array password (compared to UD disk password)?

Edited December 22, 2025Dec 22 by Bash2686

11 hours ago, Bash2686 said:

there is a green lock symbol on the left side in UD

That's how UD shows it's encrypted; it's not the same as for array or pools.

9 hours ago, Bash2686 said:

file manager seems to be not recognizing the encryption (sadly).

That is likely a file manager limitation/issue, but it's encrypted, so you can just ignore.

9 hours ago, Bash2686 said:

So, to be protected against theft of the server/NAS (including the USB drive) it is more secure to use the array password (compared to UD disk password)?

It's the same; they use the same encryption type and key.

Hi, I'm having trouble mounting an SMB share on my new Unraid setup. Specifically, the error I'm getting is this:

Dec 26 15:44:08 LibraryAlpha04 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,retrans=3,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,credentials='/tmp/unassigned.devices/credentials_DESKTOP-43E8SE5_D' '//DESKTOP-43E8SE5.LOCAL/D' '/mnt/remotes/DESKTOP-43E8SE5_D'
Dec 26 15:44:08 LibraryAlpha04 kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified
Dec 26 15:44:08 LibraryAlpha04 kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified
Dec 26 15:44:08 LibraryAlpha04 kernel: CIFS: Attempting to mount //DESKTOP-43E8SE5.LOCAL/D
Dec 26 15:44:08 LibraryAlpha04 kernel: CIFS: VFS: cifs_mount failed w/return code = -13
Dec 26 15:44:08 LibraryAlpha04 unassigned.devices: Remote Share '//DESKTOP-43E8SE5.LOCAL/D' failed to mount.

I understand that return code -13 is likely a permissions issue, but I can't figure out where I'm going wrong. The share I'm trying to connect do is a drive on my Windows 10 machine, I have the drive setup for sharing in Windows, and I have file & printer sharing enabled in my network settings.

I've also created a user for my NAS in both Unraid & Windows Credential manager, but using those credentials in the SMB share setup still results in a failure.

What I suspect is that there's some Windows setting I'm overlooking, but I have no idea what it could be. Any help would be appreciated.