56 minutes ago, wgstarks said:

Depends on how they are physically connected. Many external enclosures don’t support SMART (or at least most of mine don’t).

 

If they are installed into a slot in your server then they should have the same SMART features as all the other drives.

 

One is an ssd connected to the motherboard, the other is a Seagate Backup Plus connected by usb and shows smart info.

Hoping someone can give me some help here.. Trying to copy some content form my box to a new WD My Passport 4TB external. I know these drives are a strange format, so can UD/unraid mount them?  When I plug the disk in it looks OK....

 

Dec 16 18:41:37 knox kernel: usb 2-1.2: new high-speed USB device number 14 using ehci-pci
Dec 16 18:41:37 knox kernel: usb-storage 2-1.2:1.0: USB Mass Storage device detected
Dec 16 18:41:37 knox kernel: scsi host10: usb-storage 2-1.2:1.0
Dec 16 18:41:38 knox kernel: scsi 10:0:0:0: Direct-Access     WD       My Passport 25E2 4004 PQ: 0 ANSI: 6
Dec 16 18:41:38 knox kernel: sd 10:0:0:0: Attached scsi generic sg17 type 0
Dec 16 18:41:38 knox kernel: scsi 10:0:0:1: Enclosure         WD       SES Device       4004 PQ: 0 ANSI: 6
Dec 16 18:41:38 knox kernel: sd 10:0:0:0: [sds] Spinning up disk...
Dec 16 18:41:38 knox kernel: scsi 10:0:0:1: Attached scsi generic sg18 type 13
Dec 16 18:41:40 knox kernel: .
Dec 16 18:41:40 knox kernel: .
Dec 16 18:41:42 knox kernel: .
Dec 16 18:41:42 knox kernel: .
Dec 16 18:41:44 knox kernel: .
Dec 16 18:41:44 knox kernel: .
Dec 16 18:41:44 knox kernel: ready
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] Very big device. Trying to use READ CAPACITY(16).
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] 7813969920 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] 4096-byte physical blocks
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] Write Protect is off
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] Mode Sense: 47 00 10 08
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] No Caching mode page found
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] Assuming drive cache: write through
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] Very big device. Trying to use READ CAPACITY(16).
Dec 16 18:41:44 knox kernel: sds: sds1
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] Very big device. Trying to use READ CAPACITY(16).
Dec 16 18:41:44 knox kernel: sd 10:0:0:0: [sds] Attached SCSI disk
Dec 16 18:41:45 knox rc.diskinfo[26434]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 691
Dec 16 18:41:45 knox rc.diskinfo[26434]: SIGHUP received, forcing refresh of disks info.
Dec 16 18:41:45 knox unassigned.devices: Adding disk '/dev/sds1'...
Dec 16 18:41:45 knox unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sds1' '/mnt/disks/WD_My_Passport_25E2'
Dec 16 18:41:49 knox ntfs-3g[3787]: Version 2016.2.22 integrated FUSE 27
Dec 16 18:41:49 knox ntfs-3g[3787]: Mounted /dev/sds1 (Read-Write, label "", NTFS 1.2)
Dec 16 18:41:49 knox ntfs-3g[3787]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000
Dec 16 18:41:49 knox ntfs-3g[3787]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sds1,blkdev,blksize=4096
Dec 16 18:41:49 knox ntfs-3g[3787]: Global ownership and permissions enforced, configuration type 1
Dec 16 18:41:49 knox unassigned.devices: Successfully mounted '/dev/sds1' on '/mnt/disks/WD_My_Passport_25E2'.
Dec 16 18:41:49 knox unassigned.devices: Defining share 'WD_My_Passport_25E2' with file '/etc/samba/unassigned-shares/WD_My_Passport_25E2.conf'
Dec 16 18:41:49 knox unassigned.devices: Reloading Samba configuration...
Dec 16 18:41:49 knox unassigned.devices: Directory '/mnt/disks/WD_My_Passport_25E2' shared successfully.
Dec 16 18:41:49 knox unassigned.devices: Device '/dev/sds1' script file not found.  'ADD' script not executed. 

 

The mount seems ok...

 

root@knox:/mnt/disks# mount
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /var/log type tmpfs (rw,size=128m,mode=0755)
/dev/sda1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed)
/mnt on /mnt type none (rw,bind)
/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md6 on /mnt/disk6 type xfs (rw,noatime,nodiratime)
/dev/md7 on /mnt/disk7 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md8 on /mnt/disk8 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md9 on /mnt/disk9 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md10 on /mnt/disk10 type xfs (rw,noatime,nodiratime)
/dev/md11 on /mnt/disk11 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/sdl1 on /mnt/cache type xfs (rw,noatime,nodiratime)
shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other)
/dev/sdc1 on /mnt/disks/downloads type xfs (rw,noatime,nodiratime)
/mnt/cache/VMs/docker.img on /var/lib/docker type btrfs (rw)
/dev/sdq1 on /mnt/disks/Media type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)
/mnt/cache/VMs/libvirt.img on /etc/libvirt type btrfs (rw)
/dev/sds1 on /mnt/disks/WD_My_Passport_25E2 type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)

 

But for some reason... I can't write to the disk...

 

root@knox:/mnt/disks/WD_My_Passport_25E2# mkdir TV
mkdir: cannot create directory ‘TV’: Input/output error

 

Anyone know what I'm doing wrong?

I am trying to move my appdata folders to my unassigned device but I am unable to select the share when adding the docker.  

 

I can only assign dockers under: mnt/user/appdata

 

I want to assign it to dockers to: mnt/disks/500_mSATA/appdata

 

What is the workaround to get this to run?

 

 

 

24 minutes ago, fonzie said:

I am trying to move my appdata folders to my unassigned device but I am unable to select the share when adding the docker.  

 

I can only assign dockers under: mnt/user/appdata

 

I want to assign it to dockers to: mnt/disks/500_mSATA/appdata

 

What is the workaround to get this to run?

 

 

Hit the path when editing the container, and then keep hitting the ".." until you get to /mnt then select your appropriate path

 

And adjust your default appdata path within Settings - Docker so that new apps added will get the new path automatically

Edited December 23, 20178 yr by Squid

The issue I'm having is that once I do that in the docker settings, the "apply" option is still greyed out as if it didn't notice that I made a change.  The only option I can click is "done" but no changes take effect on the docker screen.

14 minutes ago, fonzie said:

The issue I'm having is that once I do that in the docker settings, the "apply" option is still greyed out as if it didn't notice that I made a change.  The only option I can click is "done" but no changes take effect on the docker screen.

Yeah, kinda a nagging weird little GUI issue.  Way around it is to type a character after the path, then delete that character.  Once you click off the field, apply will appear

Thanks Squid.  That worked.

Fixed next release 

On 12/12/2017 at 8:21 AM, Endy said:

Should I be able to run the smart tests on unassigned drives? I click on the start buttons and nothing happens. It does work on my array drives. 

 

Still not working. Neither an SSD connected to the motherboard nor the Seagate backup drive connected by usb.

1 hour ago, Endy said:

 

Still not working. Neither an SSD connected to the motherboard nor the Seagate backup drive connected by usb.

Doesn't work.  Not sure what it will take to fix.

@bonienl I need some help with the SMART testing on UD devices.

 

 

As you can see, I am referencing the drive as /dev/sdg.  The SMART reports don't work.  I expect it is because the drive is not in the array.  What is the answer to this issue?

That should be correct, an unassigned device is referenced by its device name.

I did a quick test and made a unassigned device (not using your plugin) and entered the URL manually.

 

 

Ps. I see a bug in the self-test page, which won't allow unassigned devices. Made a correction.

 

Edited December 24, 20178 yr by bonienl

1 hour ago, bonienl said:

That should be correct, an unassigned device is referenced by its device name.

I did a quick test and made a unassigned device (not using your plugin) and entered the URL manually.

 

 

Ps. I see a bug in the self-test page, which won't allow unassigned devices. Made a correction.

 

Yes, that is the issue.  The rest works.

Encrypted disks created as part of the array on 6.4rc17b and then removed from the array and connected by unassigned devices, doesn't seem to work.  It correctly identifies the FS as crypto_LUKS, but doesn't want to mount the device.  This is after starting the array and giving unRaid the passphrase the encrypted drive requires for proper mounting.

 

Is it just me, or is this still not yet working?

I dont believe the pass phrase management of emhttp ui extends to unassigned devices (yet). You might need to submit a feature enhancement request for UD.

11 hours ago, tr0910 said:

Encrypted disks created as part of the array on 6.4rc17b and then removed from the array and connected by unassigned devices, doesn't seem to work.  It correctly identifies the FS as crypto_LUKS, but doesn't want to mount the device.  This is after starting the array and giving unRaid the passphrase the encrypted drive requires for proper mounting.

 

Is it just me, or is this still not yet working?

UD does not handle encrypted volumes.

14 hours ago, BRiT said:

I dont believe the pass phrase management of emhttp ui extends to unassigned devices (yet). You might need to submit a feature enhancement request for UD.

So @limetech needs to fix something before @dlandon can fix unassigned devices to support encrypted drives?

 

This won't be an easy fix??

3 hours ago, dlandon said:

UD does not handle encrypted volumes.

Ok

 

I recall @limetech expressed interest in taking over unassigned devices.  Is this still planned?

 

I appreciate that unassigned devices now can format drives in array compatible format.  In my opinion, unassigned devices is the most critical add-on to unRaid.  Well done @dlandon and others who have taken it this far.

Edited December 25, 20178 yr by tr0910

42 minutes ago, tr0910 said:

Ok

 

I recall @limetech expressed interest in taking over unassigned devices.  Is this still planned?

 

I appreciate that unassigned devices now can format drives in array compatible format.  In my opinion, unassigned devices is the most critical add-on to unRaid.  Well done @dlandon and others who have taken it this far.

Eventually, but their plate is very full.  Don't expect it any time before 6.4 is released.  I am in touch with LT and will try to deal with encrypted mounts.  Give me some time to work it out.

5 hours ago, tr0910 said:

So @limetech needs to fix something before @dlandon can fix unassigned devices to support encrypted drives?

 

This won't be an easy fix??

Not necessarily.  I am encrypting a UD disk manually now and I will see what it takes to mount.  What I need help with is accessing the key to decrypt the drive.  I may be able to find it on my own, but help from LT would be appreciated.

 

EDIT: I think I may have figured it out.  I've been able to mount an encrypted disk.

Edited December 25, 20178 yr by dlandon

On 12/26/2017 at 12:45 AM, dlandon said:

Not necessarily.  I am encrypting a UD disk manually now and I will see what it takes to mount.  What I need help with is accessing the key to decrypt the drive.  I may be able to find it on my own, but help from LT would be appreciated.

 

EDIT: I think I may have figured it out.  I've been able to mount an encrypted disk.

Great news....

A new  version of UD is available.  You can now mount array disks that are encrypted.  There are some restrictions:

• The array disk passphrase has to be defined. You cannot enter the passphrase for the disk in UD.
• The disk can only be mounted if the current array passphrase is the same as the encrypted disk.
• An array encrypted disk cannot be created with UD.

I recently upgrade my server hardware, during that process I decided to start with a fresh install of UnRAID. Added fresh pre-cleared hard drives with the intent of importing past data from my old UnRAID server to the new one via unassigned devices. But once I install the old discs and clicked on the mount button nothing happens. I noticed though that under FS it says "zfs_member". I did use these in a FreeNAS install prior to the old UnRAID install, but I have been using them in the old server with no issues. Any ideas of how to access this info via UnRAID? Thanks. 

7 hours ago, bpmckim said:

I noticed though that under FS it says "zfs_member". I did use these in a FreeNAS install prior to the old UnRAID install, but I have been using them in the old server with no issues. Any ideas of how to access this info via UnRAID? Thanks. 

They should mount in the cache slot, one at a time.

On 12/26/2017 at 5:51 PM, dlandon said:

A new  version of UD is available.  You can now mount array disks that are encrypted.  There are some restrictions:

• The array disk passphrase has to be defined. You cannot enter the passphrase for the disk in UD.
• The disk can only be mounted if the current array passphrase is the same as the encrypted disk.
• An array encrypted disk cannot be created with UD.

I have a 8tb disk that has been formatted XFS_encrypted with a 70 char keyfile.  Stopped the array and did a new config and then attempted to connect the encrypted drive via unassigned devices.  Here is the log file resulting....

 

Doesn't seem to want to mount.  After, I stopped the array again and reattached this encrypted disk via an unRaid array mount without problems.   Does unassigned devices only support keyboard entered passwords and not support keyfiles at present?   The 70 character keyfile uses A-Z, a-z, 0-9, !@#$%^&*() characters.

 

unassigned.log

Edited December 29, 20178 yr by tr0910