dlandon

That's the way UD works. You can make the shares hidden in UD settings.

It's not a bug. The disk serial number must be unique. That's how UD identifies a disk. It applies to all UD operations like mounting, renaming, etc. You'll have to remove one of the duplicate disks.

That's not something you can adjust. I'll make a change in UD. It will be available in the next update.

Disk sdk does not have a serial number. This is a Linux issue and is probably the reason for the php error. Remove it from the system? Your sdd disk does not have a format that UD can mount. Why do you have it set to auto mount? Apr 23 13:41:12 Borgcube unassigned.devices: Mounting 'Auto Mount' Devices... Apr 23 13:41:12 Borgcube emhttpd: Warning: syntax error, unexpected '=' in Unknown on line 1 Apr 23 13:41:12 Borgcube emhttpd: in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1468 Apr 23 13:41:12 Borgcube unassigned.devices: Disk '/dev/sdk' does not have a serial number and cannot be mounted. Apr 23 13:41:12 Borgcube unassigned.devices: Adding disk '/dev/sdd1'... Apr 23 13:41:12 Borgcube unassigned.devices: Mount drive command: /sbin/mount -t linux_raid_member -o rw,auto,async,noatime,nodiratime '/dev/sdd1' '/mnt/disks/SEAGATE_ST2000NM0043-part1' Apr 23 13:41:12 Borgcube unassigned.devices: Mount of '/dev/sdd1' failed. Error message: mount: /mnt/disks/SEAGATE_ST2000NM0043-part1: unknown filesystem type 'linux_raid_member'. Apr 23 13:41:12 Borgcube unassigned.devices: Partition 'SEAGATE ST2000NM0043-part1' could not be mounted. Apr 23 13:41:12 Borgcube unassigned.devices: Adding disk '/dev/sdd2'... Apr 23 13:41:12 Borgcube unassigned.devices: Mount drive command: /sbin/mount -t linux_raid_member -o rw,auto,async,noatime,nodiratime '/dev/sdd2' '/mnt/disks/SEAGATE_ST2000NM0043-part2' Apr 23 13:41:12 Borgcube unassigned.devices: Mount of '/dev/sdd2' failed. Error message: mount: /mnt/disks/SEAGATE_ST2000NM0043-part2: unknown filesystem type 'linux_raid_member'. Apr 23 13:41:12 Borgcube unassigned.devices: Partition 'SEAGATE ST2000NM0043-part2' could not be mounted. Apr 23 13:41:12 Borgcube unassigned.devices: Adding disk '/dev/sdd3'... Apr 23 13:41:12 Borgcube unassigned.devices: Mount drive command: /sbin/mount -t linux_raid_member -o rw,auto,async,noatime,nodiratime '/dev/sdd3' '/mnt/disks/Subcube2' Apr 23 13:41:12 Borgcube unassigned.devices: Mount of '/dev/sdd3' failed. Error message: mount: /mnt/disks/Subcube2: unknown filesystem type 'linux_raid_member'. Apr 23 13:41:12 Borgcube unassigned.devices: Partition 'Subcube2' could not be mounted. Apr 23 13:41:12 Borgcube unassigned.devices: Disk with serial 'Cruzer_Blade_4C530000121123118320', mountpoint 'PA_WINPE' is not set to auto mount and will not be mounted.

Post diagnostics. You have not provided enough information to allow me to help you.

If Linux doesn't recognize the file system, UD can't mount it.

In UD settings be sure destructive mode is on.

UD thinks the disk is 'zfs_member' (obviously). I have no idea why that is happening. Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc1' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part1' Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount of '/dev/sdc1' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part1: unknown filesystem type 'zfs_member'. Apr 22 02:19:16 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part1' could not be mounted. Apr 22 02:19:16 UNRAID01 unassigned.devices: Adding disk '/dev/sdc2'... Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc2' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part2' Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount of '/dev/sdc2' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part2: unknown filesystem type 'zfs_member'. Apr 22 02:19:16 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part2' could not be mounted. Apr 22 02:19:55 UNRAID01 unassigned.devices: Adding disk '/dev/sdc1'... Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc1' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part1' Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount of '/dev/sdc1' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part1: unknown filesystem type 'zfs_member'. Apr 22 02:19:55 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part1' could not be mounted. Apr 22 02:19:55 UNRAID01 unassigned.devices: Adding disk '/dev/sdc2'... Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc2' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part2' Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount of '/dev/sdc2' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part2: unknown filesystem type 'zfs_member'. Apr 22 02:19:55 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part2' could not be mounted. The only suggestion I have is to format the disk with UD, then write the files to the drive on the other computer.

Now post diagnostics zip file. Tools->Diagnostics.

Very confusing. It shows the mount button but I don't see a file system. What happens when you click on the 'Mount' button?

Click on the '+' by the disk serial number and see if both partitions show. I think you'll see the second NTFS partition.

Try these things in order: Remove pre-clear plugin. Put the disk in another computer and confirm the file format is indeed NTFS and files can be accessed. Post diagnostics.

Correct.

Post diagnostics so we can see the issue.

UD will mount the NFS share without you entering the user name and password.

The .Recycle.Bin files are handled the same as the share files. It cannot be made to operate differently than the share with respect to the cache mover.

It's not a bug. UD mounts the remote share with the permissions set to 777. If you need that set differently, set up a default script on the share and do a chmod when the remote share mounts.

The 'vers=' option was added in UD to deal specfically with some security issues and remote servers that would not mount properly without the 'sec=' command set properly. If the remote server mounts the share but does not permit writting, it sounds like an issue with the remote server. The 'vers=' CIFS mount option is standard and the remote server needs to handle it properly. Maybe the remote server needs an update?

Upper right.

UD for quite a while has been mounting SMB mounts by attempting to mount them using SMB3, SMB2, and then SMB1. The idea is to mount the remote share with the highest security the remote server will support. If the remote server will mount the share using SMB3, then the server should support reads and writes. You can force UD to only mount SMB mounts with SMB1 in the UD settings to get past this issue. Keep in mind that SMB1 is not as secure as either SMB3 or SMB2.

Remote SMB mounts are always shared. The only thing you can do is control the permissions with UD settings.

Correct, you need at least one array disk. One last time, it is not advisable and you need to stop asking about it. The answer will not change.

It is not recommended to put SSDs in the array. Your SSD would be better suited as a cache drive.

UD mounts devices but has no control over how mounted devices are used. That is up to Linux. What you are probably seeing is the disk buffering. Install this plugin: and adjust the 'Disk Cache' values. These are Linux values that control disk buffering. Read the guide on suggested values. If you have a large amount of ram in your server, these values default to a very large value because they are a percentage of all available ram.

That's a VM discussion that is best handled on the VM forum.