I have 7 Unassigned Drives connected via the HBA.  I had an 8th drive in a 4 bay USB 3.0 enclosure.  It was formatted and working fine.  I turned off the enclosure and added a 9th drive.  Now, both drives are listed as Dev 9 and the one that should be Dev 8 has no device label (should be sdaa) and both show the same mount point "tvshows2" which was the mount point for Dev 8 as the new Dev 9 is not formatted and has not been mounted.  This is the entries from the system log:

 

Apr 18 18:59:12 Tower kernel: usb 2-8: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Apr 18 18:59:12 Tower kernel: usb-storage 2-8:1.0: USB Mass Storage device detected
Apr 18 18:59:12 Tower kernel: scsi host11: usb-storage 2-8:1.0
Apr 18 18:59:13 Tower kernel: scsi 11:0:0:0: Direct-Access Hitachi HDS723030ALA640 0125 PQ: 0 ANSI: 6
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: Attached scsi generic sg0 type 0
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] Very big device. Trying to use READ CAPACITY(16).
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] 4096-byte physical blocks
Apr 18 18:59:13 Tower kernel: scsi 11:0:0:1: Direct-Access Hitachi HDS723030ALA640 0125 PQ: 0 ANSI: 6
Apr 18 18:59:13 Tower kernel: scsi 11:0:0:1: Attached scsi generic sg27 type 0
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] Write Protect is off
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] Mode Sense: 67 00 10 08
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] Very big device. Trying to use READ CAPACITY(16).
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] No Caching mode page found
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] Assuming drive cache: write through
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] 4096-byte physical blocks
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] Write Protect is off
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] Mode Sense: 67 00 10 08
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] No Caching mode page found
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] Assuming drive cache: write through
Apr 18 18:59:13 Tower kernel: sdaa: sdaa1
Apr 18 18:59:13 Tower kernel: sdab: sdab1
Apr 18 18:59:13 Tower kernel: sd 11:0:0:0: [sdaa] Attached SCSI disk
Apr 18 18:59:13 Tower kernel: sd 11:0:0:1: [sdab] Attached SCSI disk
Apr 18 18:59:14 Tower unassigned.devices: Disk with ID 'HDS723030ALA640_152D00539000 (sdaa)' is not set to auto mount.
Apr 18 18:59:14 Tower unassigned.devices: Disk with ID 'HDS723030ALA640_152D00539000 (sdab)' is not set to auto mount.
Apr 18 18:59:17 Tower emhttpd: Hitachi_HDS723030ALA640_152D00539000-0:1 (sdab) 512 5860533168
Apr 18 18:59:17 Tower emhttpd: read SMART /dev/sdab

 

I removed Dev 9 until I can get an answer, getting this error for the original and unchanged Dev 8. 

 

Apr 18 19:27:35 Tower kernel: usb 2-8: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
Apr 18 19:27:35 Tower kernel: usb-storage 2-8:1.0: USB Mass Storage device detected
Apr 18 19:27:35 Tower kernel: scsi host11: usb-storage 2-8:1.0
Apr 18 19:27:36 Tower kernel: scsi 11:0:0:0: Direct-Access Hitachi HDS723030ALA640 0125 PQ: 0 ANSI: 6
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: Attached scsi generic sg0 type 0
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] Very big device. Trying to use READ CAPACITY(16).
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] 4096-byte physical blocks
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] Write Protect is off
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] Mode Sense: 67 00 10 08
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] No Caching mode page found
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] Assuming drive cache: write through
Apr 18 19:27:36 Tower kernel: sdaa: sdaa1
Apr 18 19:27:36 Tower kernel: sd 11:0:0:0: [sdaa] Attached SCSI disk
Apr 18 19:27:37 Tower unassigned.devices: Disk with ID 'HDS723030ALA640_152D00539000 (sdaa)' is not set to auto mount.
Apr 18 19:28:22 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdaa
Apr 18 19:28:36 Tower unassigned.devices: Adding partition 'sdaa1'...
Apr 18 19:28:36 Tower unassigned.devices: Mounting partition 'sdaa1' at mountpoint '/mnt/disks/tvshows2'...
Apr 18 19:28:36 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/tvshows2'
Apr 18 19:28:36 Tower kernel: XFS (sdaa1): Filesystem has duplicate UUID 42df9b8c-66be-4d9a-986b-522f706f27ad - can't mount
Apr 18 19:28:36 Tower unassigned.devices: Mount of 'sdaa1' failed: 'mount: /mnt/disks/tvshows2: wrong fs type, bad option, bad superblock on /dev/sdaa1, missing codepage or helper program, or other error. '
Apr 18 19:28:36 Tower unassigned.devices: Partition 'tvshows2' cannot be mounted.

Also get this when trying to change the UUID.

 

Apr 19 09:51:18 Tower ool www[13312]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'uuid_change'
Apr 19 09:51:18 Tower unassigned.devices: Changed partition UUID on '/dev/sdaa1' with result: ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_admin. If you are unable to mount the filesystem, then use the xfs_repair -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

Please use the existing plugin support thread: