dlandon

This is fixed in the 2016.02.01 release.

Version 2016.02.01 is available. I fixed the situation where the unraid boot flash drive would show up as an unassigned device when another flash drive is installed with an 'UNRAID' label. The inserted flash drive will show in unassigned devices, but won't mount because it has the 'UNRAID' label. Any device with the label of 'UNRAID' will not mount or unmount. The boot flash device will not show up in the unassigned devices. Because of the changes, please confirm that all your unassigned devices show properly, and the parity, array disks, cache disk(s), and boot flash drive don't show up.

Trurl, Thank you that helped. I now have my new scheme working. I want to test a bit more, then I'll release a new version.

Could someone with a cache pool send me their /usr/local/emhttp/state/disks.ini file in a pm? I'm working on a better way to determine all the array devices (Parity, array disks, flash, and cache drives) to be sure UD does not pick up devices like the flash reported earlier. I've already found the answer to that, but now I need to verify the cache pool drives. I do not have a system with a cache pool.

The problem is that you have multiple USB flash devices with the same 'UNRAID' label and both get mounted to the same mount point. The mount point that UD creates is /mnt/disks/UNRAID. Two devices cannot be mounted to the same mount point. I've added some checks so the added flash device doesn't get mounted. The unRaid flash drive will show mounted in UD, but the second flash with the 'UNRAID' label won't mount. UD won't mount a USB DVD Drive and I have no plans to support that.

I understand. Having a reliable backup power source for unraid is pretty important. So, a thought occurred to me, I know, it's not often I have a Eureka moment. But i had recently migrated my system to a new case and changed which USB ports I use for VMs etc. So I tried my UPS in a different port and Bob's your uncle. Time left now has reappeared along with percentage load. I am still missing nominal power and UPS load, but I'm at least back to where I started... Could this possibly be a USB2 or USB3 compatibility issue? Some motherboard bios's have a legacy USB setting. Maybe that would help.

It is rather subtle. It came up from a request to not poll the disk if it is a "hot standby" disk. i.e. pre-cleared and ready to put into the array as necessary. Some disks will spin up when you query them for idle status. I did the check for an existing script file thinking it was a good way to decide not to poll the disk. I'm not sure I like it, but until I can think of something better I'll leave it. EDIT: I'm going to implement the spin status and temperature check when a disk is pre-clearing regardless of the existence of the script file. I'm sure this will come up again.

Just set the script to the default and the spin status and temperature will show. I've said several times that there is a special case when the drive is not mounted and there is no script file, the spin status and temperature are not shown.

Release 2016.01.30 is available. The major change is the scripts. All scripts have been put together into one script named rc.unassigned. This is consistent with unraid standards. If you were using the unassigned devices mount and umount scripts you will have to make some changes. /usr/local/sbin/unassigned_mount [device,'all'] =====> /usr/local/rc.unassigned mount [device,'auto'] /usr/local/sbin/unassigned_umount [device,'all'] =====> /usr/local/rc.unassigned umount [device,'auto'] 'all' has been changed to 'auto' to better describe the operation. 'auto' means auto mounted devices. 'all' now means unmount all devices when used with 'rc.unassigned umount all'. I have changed the sample script in the OP to reflect this change. I won't be making any more structural changes, I will only be fixing bugs at this point. If nothing major comes up in the next week, I'll take this plugin out of beta.

The plugin sets a 15 minute idle time with 'hdparm -S180' to the device when it is mounted. You could issue a no idle time to the device in the script when it is mounted with 'hdparm -S0'. This tells the drive to never go to the idle (spin down) mode. The script will look like this: #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # AVAIL : available space # USED : used space # SIZE : partition size # SERIAL : disk serial number # ACTION : if mounting, ADD; if unmounting, REMOVE # MOUNTPOINT : where the partition is mounted # FSTYPE : partition filesystem # LABEL : partition label # DEVICE : partition device, e.g /dev/sda1 # OWNER : "udev" if executed by UDEV, otherwise "user" case $ACTION in 'ADD' ) // do your stuff here echo "Added" hdparm -S0 $DEVICE ;; 'REMOVE' ) // do your stuff here echo "Removed" ;; esac You'll have to do the same thing on unmount if you want the drive to not enter the idle mode. This won't work until the next release because currently the sleep time is set after the drive script is executed. I changed this to be before the drive script is executed in the next release. Caveat: The drive has to accept the 'hdparm -S0' command.

What happens if I upgrade but don't have the mount points in the disks folder? Will it try and remap them? No. Only if you make a change to the mount point. But it shows them as being changed..... I use the ZFS plugin and its setup to mount "appdisk" in /mnt (/mnt/appdisk) - but the plugin is displaying the path wrong - /mnt/disks/appdisk Myk The mount point is not changed until you edit it by clicking on it when the drive is unmounted. It appears you may have edited the mount points.

There is a special case when the Drive is not mounted and the script is deleted, the drive will show spun down and the smart report is not available.

What happens if I upgrade but don't have the mount points in the disks folder? Will it try and remap them? No. Only if you make a change to the mount point.

I never had a problem with the drive showing on the unassigned list. Whether using the motherboard ports or the Areca ports both always showed up. After rebooting the server, I had no problems mounting with the drive connected to the Areca. So problem solved with a reboot. Confession time: The previous problems followed uninstalling the gfardjim unassigned devices plugin, and then reinstalling your newer version without doing a reboot. It sort of worked, but not with this drive. Here are the log entries from around that time that you might find interesting as I was hot plugging drives in and out. Sometimes Areca ports and sometimes motherboard ports are being used in the list below. The drive in question is a WDC WD30EZRS, and I was also working with a Hitachi and a WD 2tb EARS both RFS formatted and connected to the Areca. Jan 27 16:25:34 Kim kernel: XFS (sdp1): Unmounting Filesystem Jan 27 16:26:06 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove unassigned.devices.plg Jan 27 16:26:06 Kim logger: plugin: running: anonymous Jan 27 16:26:29 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm down sdp Jan 27 16:26:34 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/hd_parm up sdp Jan 27 16:26:45 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdp Jan 27 16:27:55 Kim emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg Jan 27 16:27:55 Kim logger: plugin: running: anonymous Jan 27 16:27:55 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2016.01.26a.tgz Jan 27 16:27:56 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/unassigned.devices-2016.01.26a.tgz - MD5 Jan 27 16:27:56 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - downloading from URL http://slackbuilds.org/mirror/slackware/slackware64-current/slackware64/a/ntfs-3g-2015.3.14-x86_64-1.txz Jan 27 16:28:02 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz - MD5 Jan 27 16:28:02 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz Jan 27 16:28:02 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz Jan 27 16:28:03 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.1.1-x86_64-1_SBo.txz - MD5 Jan 27 16:28:03 Kim logger: plugin: running: anonymous Jan 27 16:28:03 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz Jan 27 16:28:04 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.1.0-x86_64-1_SBo.txz - MD5 Jan 27 16:28:04 Kim logger: plugin: running: anonymous Jan 27 16:28:04 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/system/hfsprogs/332.25/hfsprogs-332.25-x86_64-2sl.txz Jan 27 16:28:06 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz - MD5 Jan 27 16:28:06 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz Jan 27 16:28:06 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - downloading from URL http://slackware.org.uk/slacky/slackware64-14.1/libraries/libbsd/0.6.0/libbsd-0.6.0-x86_64-1sl.txz Jan 27 16:28:08 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz - MD5 Jan 27 16:28:08 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz Jan 27 16:28:08 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/parted-3.1-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz - MD5 Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: creating: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - downloading from URL http://slackware.osuosl.org/slackware64-14.1/slackware64/l/libnl-1.1.4-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: checking: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz - MD5 Jan 27 16:28:09 Kim logger: plugin: running: /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz Jan 27 16:28:09 Kim logger: plugin: running: anonymous Jan 27 16:29:35 Kim kernel: XFS (sdp1): Mounting V5 Filesystem Jan 27 16:29:36 Kim kernel: XFS (sdp1): Ending clean mount Jan 27 16:42:03 Kim kernel: ata1: exception Emask 0x50 SAct 0x0 SErr 0x40d0800 action 0xe frozen Jan 27 16:42:03 Kim kernel: ata1: irq_stat 0x00400040, connection status changed Jan 27 16:42:03 Kim kernel: ata1: SError: { HostInt PHYRdyChg CommWake 10B8B DevExch } Jan 27 16:42:03 Kim kernel: ata1: hard resetting link Jan 27 16:42:04 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300) Jan 27 16:42:09 Kim kernel: ata1: hard resetting link Jan 27 16:42:09 Kim kernel: ata1: SATA link down (SStatus 0 SControl 300) Jan 27 16:42:09 Kim kernel: ata1: limiting SATA link speed to 1.5 Gbps Jan 27 16:42:14 Kim kernel: ata1: hard resetting link Jan 27 16:42:15 Kim kernel: ata1: SATA link down (SStatus 0 SControl 310) Jan 27 16:42:15 Kim kernel: ata1.00: disabled Jan 27 16:42:15 Kim kernel: ata1: EH complete Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: [sdp] killing request Jan 27 16:42:15 Kim kernel: blk_update_request: I/O error, dev sdp, sector 2930276939 Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: sd 2:0:0:0: rejecting I/O to offline device Jan 27 16:42:15 Kim kernel: XFS (sdp1): metadata I/O error: block 0xaea87a0b ("xlog_iodone") error 5 numblks 64 Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_do_force_shutdown(0x2) called from line 1180 of file fs/xfs/xfs_log.c. Return address = 0xffffffff81275cff Jan 27 16:42:15 Kim kernel: XFS (sdp1): Log I/O Error Detected. Shutting down filesystem Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:42:15 Kim kernel: XFS (sdp1): Please umount the filesystem and rectify the problem(s) Jan 27 16:42:15 Kim kernel: ata1.00: detaching (SCSI 2:0:0:0) Jan 27 16:42:15 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronizing SCSI cache Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Stopping disk Jan 27 16:42:16 Kim kernel: sd 2:0:0:0: [sdp] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Jan 27 16:42:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:43:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:43:18 Kim kernel: scsi 1:0:0:7: Direct-Access WDC WD30EZRS-00J99B0 R001 PQ: 0 ANSI: 5 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] physical block alignment offset: 3276288 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: Attached scsi generic sg16 type 0 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write Protect is off Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Mode Sense: cb 00 00 08 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 27 16:43:18 Kim kernel: sds: sds1 Jan 27 16:43:18 Kim kernel: sd 1:0:0:7: [sds] Attached SCSI disk Jan 27 16:43:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:44:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:44:16 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:44:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:44:37 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:45:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:45:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:46:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:46:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:47:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:47:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:48:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:48:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:49:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:49:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): found reiserfs format "3.6" with standard journal Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): using ordered data mode Jan 27 16:49:51 Kim kernel: reiserfs: using flush barriers Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): journal params: device sdr1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): checking transaction log (sdr1) Jan 27 16:49:51 Kim kernel: REISERFS (device sdr1): Using r5 hash to sort names Jan 27 16:50:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:50:14 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:50:23 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:50:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:51:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:51:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:51:38 Kim apcupsd[11285]: Power failure. Jan 27 16:51:40 Kim apcupsd[11285]: Power is back. UPS running on mains. Jan 27 16:52:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:52:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:53:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:53:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:54:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:54:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:55:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:55:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:56:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:56:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:56:38 Kim kernel: sd 1:0:0:7: [sds] Synchronizing SCSI cache Jan 27 16:57:01 Kim kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen Jan 27 16:57:01 Kim kernel: ata1: irq_stat 0x00000040, connection status changed Jan 27 16:57:01 Kim kernel: ata1: SError: { CommWake DevExch } Jan 27 16:57:01 Kim kernel: ata1: hard resetting link Jan 27 16:57:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:57:07 Kim kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 27 16:57:11 Kim kernel: ata1: COMRESET failed (errno=-16) Jan 27 16:57:11 Kim kernel: ata1: hard resetting link Jan 27 16:57:17 Kim kernel: ata1: link is slow to respond, please be patient (ready=0) Jan 27 16:57:17 Kim kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: ATA-8: WDC WD30EZRS-00J99B0, WD-WCAWZ0361944, 80.00A80, max UDMA/133 Jan 27 16:57:17 Kim kernel: ata1.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jan 27 16:57:17 Kim kernel: ata1.00: configured for UDMA/133 Jan 27 16:57:17 Kim kernel: ata1: EH complete Jan 27 16:57:17 Kim kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD30EZRS-00J 0A80 PQ: 0 ANSI: 5 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: Attached scsi generic sg16 type 0 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] 4096-byte physical blocks Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write Protect is off Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Mode Sense: 00 3a 00 00 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 27 16:57:17 Kim kernel: sds: sds1 Jan 27 16:57:17 Kim kernel: sd 2:0:0:0: [sds] Attached SCSI disk Jan 27 16:57:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:57:51 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:58:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:58:11 Kim kernel: XFS (sds1): Filesystem has duplicate UUID 66b1241d-8dd2-4e4b-bd71-ad687c5cf146 - can't mount Jan 27 16:58:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:59:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 16:59:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 17:00:06 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. Jan 27 17:00:36 Kim kernel: XFS (sdp1): xfs_log_force: error -5 returned. The log I meant was the unassigned devices log. It is more useful to me in these cases. Just taking a guess here, it looks like the drive was not unmounted properly before it was mounted. Or, hot plug didn't work and Linux thought there were two drives with the same UUID?

Release 2016.01.28 is now available. There are two changes. - The samba host lookup has been changed so it should work on more systems. It was not working on either of my servers and is now working. The change shouldn't affect any systems where it was working before. - Mount points are now limited to /mnt/disks/. If you change the mount point name it will be set to /mnt/disks/ regardless of whether or not you try to change the mount point directory. You can just enter the name of the mount point you want and it will be set to /mnt/disks/.

The share permissions are controlled by unraid. Unassigned devices can't change that.

The plugin manager has a bug when a file is not downloaded, it is created and is empty. Because it exists when the next attempt at installing the plugin, it is not re-downloaded and the plugin installation fails. Best way for now to deal with it is to delete the /flash/config/plugins/unassigned.devices/packages/ folder and try installing the plugin again.

You have not said you rebooted or just plugged the drive in. If you didn't reboot, it may be a hot plug problem. The best way to see if a drive is recognized by unraid and subsequently by unassigned devices is to go to the 'Dashboard' and look at the row labeled 'Unassigned". You will see the disks that unraid sees as unassigned. If it does not show there, unassigned devices will not recognize it. Drive was always showing in the list of drives recognized by unassigned devices, you could change the mount name without problems, but pressing mount just brought it back to the same screen without any results. I did reboot the server and it (newly formatted XFS drive) is now mounted on a motherboard port without issue as un unassigned device. Perhaps mounting and unmounting multiple times from multiple ports gets things in a mishmash that only a reboot can cure??? What can we do to test the Areca mount issue? Check the log after a mount that doesn't succeed and it should have the error from the mount command. If the drive shows on the Dashboard as "Unassigned", then it will be available to unassigned devices to mount. If it doesn't, then unassigned devices cannot mount it. In order for unassigned devices to recognize a drive it has to be recognized by unraid Linux. It's my understanding that hot plug is supported by Linux, but not by unraid.

It shows up for me. I just browse down to it. Strange, I don't see mine at all. They're mounted, spun up, formatted XFS, nothing unusual, but they never appear under /Disks/ in the drop down. On a command line 'ls /mnt/disks'. You should see your disks. If not, let me know what you see. I get no return when running that command: login as: root Last login: Wed Jan 27 12:17:52 2016 from 10.0.1.11 Linux 4.1.15-unRAID. root@KingsLanding:~# ls /mnt/disks root@KingsLanding:~# The GUI shows them as mounted. I've tried rebooting, unmount/mounting, and reformatting. Any ideas? You have the mount point set to SSD_VM. It should be /mnt/disks/SSD_VM. This is one of the things I don't like about the renaming feature and will probably change it so this won't happen. EDIT: I made a change so the mount point cannot be changed from /mnt/disks/. If you enter just a mount point name 'MyDisk', it will be changed to /mnt/disks/MyDisk. The mount point has to be at /mnt/disks/ for everything to work properly. This will be fixed in the next release. Worked, thanks! And I agree on the change, sorry for the hassle. I'm glad you worked it out. It's a very easy thing to happen. The plugin should not allow this situation. Your situation has highlighted a hole that needs to be addressed. This is part of what I am trying to accomplish with the work I'm doing on the plugin. I'm adding and changing log entries for clarification, and adding code to make things more robust. When there is a problem, it should either be handled or the user should be told what is happening.

You have not said you rebooted or just plugged the drive in. If you didn't reboot, it may be a hot plug problem. The best way to see if a drive is recognized by unraid and subsequently by unassigned devices is to go to the 'Dashboard' and look at the row labeled 'Unassigned". You will see the disks that unraid sees as unassigned. If it does not show there, unassigned devices will not recognize it.

FWIW, I mount my 2 disks to /mnt/vmdisk and /mnt/vmdisk-2. I prefer not to have to go into the mnt/disks/ folder to access my shares. If you do decide to change the renaming feature, it would be nice to not be limited to only using the /mnt/disk folder. just my 2 cents Why do you feel the need to do that? 1. Because I am difficult 2. Because it is less mouse clicks and looks nice when browsing to my unRAID network shares (see photo). If you mount them at /mnt/disks and then share them, you get the same result.

You can count on it. Yes. And all the support issues when someone does it wrong.

FWIW, I mount my 2 disks to /mnt/vmdisk and /mnt/vmdisk-2. I prefer not to have to go into the mnt/disks/ folder to access my shares. If you do decide to change the renaming feature, it would be nice to not be limited to only using the /mnt/disk folder. just my 2 cents Why do you feel the need to do that?

It shows up for me. I just browse down to it. Strange, I don't see mine at all. They're mounted, spun up, formatted XFS, nothing unusual, but they never appear under /Disks/ in the drop down. On a command line 'ls /mnt/disks'. You should see your disks. If not, let me know what you see. I get no return when running that command: login as: root Last login: Wed Jan 27 12:17:52 2016 from 10.0.1.11 Linux 4.1.15-unRAID. root@KingsLanding:~# ls /mnt/disks root@KingsLanding:~# The GUI shows them as mounted. I've tried rebooting, unmount/mounting, and reformatting. Any ideas? You have the mount point set to SSD_VM. It should be /mnt/disks/SSD_VM. This is one of the things I don't like about the renaming feature and will probably change it so this won't happen. EDIT: I made a change so the mount point cannot be changed from /mnt/disks/. If you enter just a mount point name 'MyDisk', it will be changed to /mnt/disks/MyDisk. The mount point has to be at /mnt/disks/ for everything to work properly. This will be fixed in the next release.