Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

dlandon · February 13, 2016

Hi

I use this plugin for mounting 4 x SSDs and it works very well. However, I noticed a strange issue, maybe bug?

On the main UNRAID tab under Unassigned Devices, the SMART status of each drive changes from green to grey and the Temperature disappears. I need to click the drive and poll SMART for it to turn green again and display the temp. Not sure why this is, can it be fixed?

thank you!

Grey means spun down or on standby and temperatures are unavailable in that state.

Since they are SSDs, can I prevent them from spinning down or going to standby?

Do you have a script defined? If you create a script file, the drive will be monitored for spin down status and temperature. Read the second post about best practices.

No, I do not have a script defined. What would a script look like that allows me to monitor the SMART/Temp even if the SSD is unmounted or in standby? I really do appreciate your guidance with this.

thank you.

The check is for the existence of a script file. It can be empty or use the default script that really does nothing. Just click on the edit script icon, select the default script, and then save it.

This was done because some users want a "hot standby" disk and don't want it checked for spin up status and temperature. The existence of a script file implies that you are going to use the device and want it monitored.

A lot of the support questions coming up here can be easily resolved by reading my second post about "best practices" and looking at the UD log file. I realize everyone is in a hurry these days and wants a quick answer, but the first two posts are an easy read and will answer a lot of your questions. If I have not been clear enough, let me know and I will elaborate as needed.

Videodr0me · February 13, 2016

Hi, one thing i noticed with the dlandon version of the plugin is, that if you log into the unraid frontend in tabbed view and click on the main tab - all sleeping unassigned devices are woken up (it seems to occur often but not always - maybe if you open the tab after a reboot for the first time and the drives already have spun down?!). This is no biggie - but maybe there is a way to avoid this. Now that USB Automount is included, the only thing missing is the iso mounting and sharing - then we have an essential plugin, which should maybe be included into the core unraid os.

RobJ · February 13, 2016

Hi, one thing i noticed with the dlandon version of the plugin is, that if you log into the unraid frontend in tabbed view and click on the main tab - all sleeping unassigned devices are woken up (it seems to occur often but not always - maybe if you open the tab after a reboot for the first time and the drives already have spun down?!). This is no biggie - but maybe there is a way to avoid this.

This may or may not be, but it sounds like a sync behavior. If there are unwritten writes to a device, then a sync will require spinning up that device to flush them.

Off-topic, but I've never understood why Linux has write caching, but allows the writes to be delayed essentially forever. 5 seconds should be more than long enough. I'm probably not understanding something fundamental though. I also don't understand why sync can't be limited to a single device, not everything.

heffe2001 · February 14, 2016

Just updated the plugin to 2016.02.13, now I'm getting some errors in the ui, but functionality seems to not be impaired.

Getting these errors on the main page UI:

Warning: preg_grep(): Unknown modifier '0' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: array_values() expects parameter 1 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: natsort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 805 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 826 Warning: array_map(): Argument #2 should be an array in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: in_array() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 192

dlandon · February 14, 2016

Just updated the plugin to 2016.02.13, now I'm getting some errors in the ui, but functionality seems to not be impaired.

Getting these errors on the main page UI:

Warning: preg_grep(): Unknown modifier '0' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: array_values() expects parameter 1 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: natsort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 805 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 826 Warning: array_map(): Argument #2 should be an array in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: in_array() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 192

Download your UD log and post it. Click 'Help' and you'll see the 'Download' log button. There is something unique about your setup that is causing this error.

heffe2001 · February 14, 2016

Log doesn't contain much, this is the entire contents of the log after I rebooted my machine this morning (after updating UD and Community Apps):

Feb 14 11:37:48 Adding disk '/dev/sdi1'...
Feb 14 11:37:48 Mount drive command: mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdi1' '/mnt/docker-appdata'
Feb 14 11:37:48 Successfully mounted '/dev/sdi1' on '/mnt/docker-appdata'
Feb 14 11:37:48 Partition 'OCZ TRION100 952B54S2KMCX' is not set as sharable and will not be shared...
Feb 14 11:37:48 Command not available.  Cannot execute script.

Just updated the plugin to 2016.02.13, now I'm getting some errors in the ui, but functionality seems to not be impaired.

Getting these errors on the main page UI:

Warning: preg_grep(): Unknown modifier '0' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: array_values() expects parameter 1 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: natsort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 805 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 826 Warning: array_map(): Argument #2 should be an array in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: in_array() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 192

Download your UD log and post it. Click 'Help' and you'll see the 'Download' log button. There is something unique about your setup that is causing this error.

dlandon · February 15, 2016

Log doesn't contain much, this is the entire contents of the log after I rebooted my machine this morning (after updating UD and Community Apps):

Feb 14 11:37:48 Adding disk '/dev/sdi1'...
Feb 14 11:37:48 Mount drive command: mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdi1' '/mnt/docker-appdata'
Feb 14 11:37:48 Successfully mounted '/dev/sdi1' on '/mnt/docker-appdata'
Feb 14 11:37:48 Partition 'OCZ TRION100 952B54S2KMCX' is not set as sharable and will not be shared...
Feb 14 11:37:48 Command not available.  Cannot execute script.

Just updated the plugin to 2016.02.13, now I'm getting some errors in the ui, but functionality seems to not be impaired.

Getting these errors on the main page UI:

Warning: preg_grep(): Unknown modifier '0' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: array_values() expects parameter 1 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804 Warning: natsort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 805 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 826 Warning: array_map(): Argument #2 should be an array in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: in_array() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 144 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 192

Download your UD log and post it. Click 'Help' and you'll see the 'Download' log button. There is something unique about your setup that is causing this error.

I cannot reproduce this and I see no reason for it. The errors don't make any sense. I've tried to break things to create the problem and I can't.

Can you uninstall and re-install the plugin? The only thing I can come up with is there is a problem with your installation of the plugin.

heffe2001 · February 15, 2016

Removed the plugin and removed the configuration folder, then did a reinstall and got this:

plugin: installing: https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg
plugin: downloading https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg
plugin: downloading: https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg ... done
plugin: downloading: "https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2016.02.13.tgz" ... done
plugin: downloading: http://slackbuilds.org/mirror/slackware/slackware64-current/slackware64/a/ntfs-3g-2015.3.14-x86_64-1.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz
+==============================================================================

Verifying package ntfs-3g-2015.3.14-x86_64-1.txz.
Installing package ntfs-3g-2015.3.14-x86_64-1.txz:
PACKAGE DESCRIPTION:
# ntfs-3g (NTFS read-write filesystem driver)
#
# The NTFS-3G driver is an open source, freely available NTFS driver
# for Linux with read and write support. It provides safe and fast
# handling of the Windows XP, Windows Server 2003, Windows 2000 and
# Windows Vista file systems. Most POSIX file system operations are
# supported, with the exception of full file ownership and access
# rights support.
#
# Homepage: http://www.tuxera.com/community/open-source-ntfs-3g/
#
Executing install script for ntfs-3g-2015.3.14-x86_64-1.txz.
Package ntfs-3g-2015.3.14-x86_64-1.txz installed.


plugin: downloading: http://packages.slackonly.com/pub/packages/14.1-x86_64/system/exfat-utils/exfat-utils-1.2.1-x86_64-1_slack.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.2.1-x86_64-1_slack.txz
+==============================================================================

Verifying package exfat-utils-1.2.1-x86_64-1_slack.txz.
Installing package exfat-utils-1.2.1-x86_64-1_slack.txz:
PACKAGE DESCRIPTION:
# exfat-utils (exFAT system utilities)
#
# This project aims to provide a full-featured exFAT file system
# implementation for GNU/Linux and other Unix-like systems as a FUSE
# module and a set of utilities.
# module.
#
# This package contains the utilities.
#
# Homepage: https://github.com/relan/exfat
#
Executing install script for exfat-utils-1.2.1-x86_64-1_slack.txz.
Package exfat-utils-1.2.1-x86_64-1_slack.txz installed.


plugin: downloading: http://packages.slackonly.com/pub/packages/14.1-x86_64/system/fuse-exfat/fuse-exfat-1.2.1-x86_64-1_slack.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.2.1-x86_64-1_slack.txz
+==============================================================================

Verifying package fuse-exfat-1.2.1-x86_64-1_slack.txz.
Installing package fuse-exfat-1.2.1-x86_64-1_slack.txz:
PACKAGE DESCRIPTION:
# fuse-exfat (exFAT FUSE module)
#
# This project aims to provide a full-featured exFAT file system
# implementation for GNU/Linux and other Unix-like systems as a FUSE
# module and a set of utilities.
# module.
#
# This package contains the FUSE module.
#
# Homepage: https://github.com/relan/exfat
#
Executing install script for fuse-exfat-1.2.1-x86_64-1_slack.txz.
Package fuse-exfat-1.2.1-x86_64-1_slack.txz installed.


plugin: downloading: http://slackware.org.uk/slacky/slackware64-14.1/system/hfsprogs/332.25/hfsprogs-332.25-x86_64-2sl.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz
+==============================================================================

Verifying package hfsprogs-332.25-x86_64-2sl.txz.
Installing package hfsprogs-332.25-x86_64-2sl.txz:
PACKAGE DESCRIPTION:
# hfsprogs - hfs+ user space utils
#
# The HFS+ file system used by Apple Computer for their Mac OS is 
# supported by the Linux kernel. Apple provides mkfs and fsck for 
# HFS+ with the Unix core of their operating system, Darwin.
#
# This package is a port of Apple's tools for HFS+ filesystems. 
#
# http://www.opensource.apple.com
Package hfsprogs-332.25-x86_64-2sl.txz installed.


plugin: downloading: http://slackware.org.uk/slacky/slackware64-14.1/libraries/libbsd/0.6.0/libbsd-0.6.0-x86_64-1sl.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz
+==============================================================================

Verifying package libbsd-0.6.0-x86_64-1sl.txz.
Installing package libbsd-0.6.0-x86_64-1sl.txz:
PACKAGE DESCRIPTION:
# libbsd - Utility functions from BSD systems
#
# This library provides useful functions commonly found on BSD systems,
# and lacking on others like GNU systems, thus making it easier to port
# projects with strong BSD origins, without needing to embed the same
# code over and over again on each project.
#
# http://libbsd.freedesktop.org/wiki
Executing install script for libbsd-0.6.0-x86_64-1sl.txz.
Package libbsd-0.6.0-x86_64-1sl.txz installed.


plugin: downloading: http://slackware.osuosl.org/slackware64-14.1/slackware64/l/parted-3.1-x86_64-1.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz
+==============================================================================

Verifying package parted-3.1-x86_64-1.txz.
Installing package parted-3.1-x86_64-1.txz:
PACKAGE DESCRIPTION:
# parted (GNU disk partitioning tool)
#
# GNU Parted is a program for creating, destroying, resizing, checking
# and copying partitions, and the filesystems on them. This is useful
# for creating space for new operating systems, reorganizing disk
# usage, copying data between hard disks, and disk imaging.
#
Executing install script for parted-3.1-x86_64-1.txz.
Package parted-3.1-x86_64-1.txz installed.


plugin: downloading: http://slackware.osuosl.org/slackware64-14.1/slackware64/l/libnl-1.1.4-x86_64-1.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz
+==============================================================================

Verifying package libnl-1.1.4-x86_64-1.txz.
Installing package libnl-1.1.4-x86_64-1.txz:
PACKAGE DESCRIPTION:
# libnl (netlink socket library)
#
# libnl is a library for applications dealing with netlink sockets.
# The library provides an interface for raw netlink messaging and
# various netlink family specific interfaces.
# 
# Homepage: http://people.suug.ch/~tgr/libnl/
#
# 
Executing install script for libnl-1.1.4-x86_64-1.txz.
Package libnl-1.1.4-x86_64-1.txz installed.





Warning: preg_grep(): Unknown modifier '0' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804

Warning: array_values() expects parameter 1 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804

Warning: natsort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 805

Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned on line 50

-----------------------------------------------------------
unassigned.devices has been installed.
This plugin requires Dynamix webGui to operate
Copyright 2015, gfjardim
Copyright 2016, dlandon
Version: 2016.02.13
-----------------------------------------------------------

plugin: installed

The Unassigned Devices log:

Feb 14 11:37:48 Adding disk '/dev/sdi1'...
Feb 14 11:37:48 Mount drive command: mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdi1' '/mnt/docker-appdata'
Feb 14 11:37:48 Successfully mounted '/dev/sdi1' on '/mnt/docker-appdata'
Feb 14 11:37:48 Partition 'OCZ TRION100 952B54S2KMCX' is not set as sharable and will not be shared...
Feb 14 11:37:48 Command not available.  Cannot execute script.
Feb 14 23:29:53 Running command '/boot/config/plugins/unassigned.devices/docker-appdata.sh' with action 'REMOVE'.
Feb 14 23:29:53 Unmounting disk 'OCZ TRION100 952B54S2KMCX'...
Feb 14 23:29:53 Unmounting '/dev/sdi1'...
Feb 14 23:29:53 Unmount of '/dev/sdi1' failed. Error message: 
umount: /mnt/docker-appdata: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof( or fuser(1))

Feb 14 23:31:57 Disk with serial 'OCZ-TRION100_952B54S2KMCX is not set to auto mount and will not be mounted...'

I had hand-mounted the SDI1, as that's where everything docker is on my system..

I've got the latest nerd pack installed, but several packages not loading with it, wonder if that could be the problem?

It's worked fine previously, didn't have any issues until I updated to the version before the current (can't remember the number).

This is what it looks like on screen:

2016-02-14%2023_37_52-Photos.png

CHBMB · February 15, 2016

Heffe, what version of Unraid you on?

Videodr0me · February 15, 2016

This may or may not be, but it sounds like a sync behavior. If there are unwritten writes to a device, then a sync will require spinning up that device to flush them.

I doubt this because:

1) Nothing has been being written to these disks - EVER

2) All mounted (unassigned devices) disks spin-up (in my case seven 4tb drives)

3) This behaviour is new - and came with the dlandon version of the plugin

I believe it has something to do with the way the temp/spin-up status is checked to display it on the "main" page (you do not even need to activate the unassinged devices sub-tab). It should not check if the disks are spun-down - but it does check something (this is all in tabbed gui-mode - do not know what happens in non-tabbed view)

dlandon · February 15, 2016

Removed the plugin and removed the configuration folder, then did a reinstall and got this:

plugin: installing: https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg
plugin: downloading https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg
plugin: downloading: https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg ... done
plugin: downloading: "https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2016.02.13.tgz" ... done
plugin: downloading: http://slackbuilds.org/mirror/slackware/slackware64-current/slackware64/a/ntfs-3g-2015.3.14-x86_64-1.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/ntfs-3g-2015.3.14-x86_64-1.txz
+==============================================================================

Verifying package ntfs-3g-2015.3.14-x86_64-1.txz.
Installing package ntfs-3g-2015.3.14-x86_64-1.txz:
PACKAGE DESCRIPTION:
# ntfs-3g (NTFS read-write filesystem driver)
#
# The NTFS-3G driver is an open source, freely available NTFS driver
# for Linux with read and write support. It provides safe and fast
# handling of the Windows XP, Windows Server 2003, Windows 2000 and
# Windows Vista file systems. Most POSIX file system operations are
# supported, with the exception of full file ownership and access
# rights support.
#
# Homepage: http://www.tuxera.com/community/open-source-ntfs-3g/
#
Executing install script for ntfs-3g-2015.3.14-x86_64-1.txz.
Package ntfs-3g-2015.3.14-x86_64-1.txz installed.


plugin: downloading: http://packages.slackonly.com/pub/packages/14.1-x86_64/system/exfat-utils/exfat-utils-1.2.1-x86_64-1_slack.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/exfat-utils-1.2.1-x86_64-1_slack.txz
+==============================================================================

Verifying package exfat-utils-1.2.1-x86_64-1_slack.txz.
Installing package exfat-utils-1.2.1-x86_64-1_slack.txz:
PACKAGE DESCRIPTION:
# exfat-utils (exFAT system utilities)
#
# This project aims to provide a full-featured exFAT file system
# implementation for GNU/Linux and other Unix-like systems as a FUSE
# module and a set of utilities.
# module.
#
# This package contains the utilities.
#
# Homepage: https://github.com/relan/exfat
#
Executing install script for exfat-utils-1.2.1-x86_64-1_slack.txz.
Package exfat-utils-1.2.1-x86_64-1_slack.txz installed.


plugin: downloading: http://packages.slackonly.com/pub/packages/14.1-x86_64/system/fuse-exfat/fuse-exfat-1.2.1-x86_64-1_slack.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/fuse-exfat-1.2.1-x86_64-1_slack.txz
+==============================================================================

Verifying package fuse-exfat-1.2.1-x86_64-1_slack.txz.
Installing package fuse-exfat-1.2.1-x86_64-1_slack.txz:
PACKAGE DESCRIPTION:
# fuse-exfat (exFAT FUSE module)
#
# This project aims to provide a full-featured exFAT file system
# implementation for GNU/Linux and other Unix-like systems as a FUSE
# module and a set of utilities.
# module.
#
# This package contains the FUSE module.
#
# Homepage: https://github.com/relan/exfat
#
Executing install script for fuse-exfat-1.2.1-x86_64-1_slack.txz.
Package fuse-exfat-1.2.1-x86_64-1_slack.txz installed.


plugin: downloading: http://slackware.org.uk/slacky/slackware64-14.1/system/hfsprogs/332.25/hfsprogs-332.25-x86_64-2sl.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/hfsprogs-332.25-x86_64-2sl.txz
+==============================================================================

Verifying package hfsprogs-332.25-x86_64-2sl.txz.
Installing package hfsprogs-332.25-x86_64-2sl.txz:
PACKAGE DESCRIPTION:
# hfsprogs - hfs+ user space utils
#
# The HFS+ file system used by Apple Computer for their Mac OS is 
# supported by the Linux kernel. Apple provides mkfs and fsck for 
# HFS+ with the Unix core of their operating system, Darwin.
#
# This package is a port of Apple's tools for HFS+ filesystems. 
#
# http://www.opensource.apple.com
Package hfsprogs-332.25-x86_64-2sl.txz installed.


plugin: downloading: http://slackware.org.uk/slacky/slackware64-14.1/libraries/libbsd/0.6.0/libbsd-0.6.0-x86_64-1sl.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/libbsd-0.6.0-x86_64-1sl.txz
+==============================================================================

Verifying package libbsd-0.6.0-x86_64-1sl.txz.
Installing package libbsd-0.6.0-x86_64-1sl.txz:
PACKAGE DESCRIPTION:
# libbsd - Utility functions from BSD systems
#
# This library provides useful functions commonly found on BSD systems,
# and lacking on others like GNU systems, thus making it easier to port
# projects with strong BSD origins, without needing to embed the same
# code over and over again on each project.
#
# http://libbsd.freedesktop.org/wiki
Executing install script for libbsd-0.6.0-x86_64-1sl.txz.
Package libbsd-0.6.0-x86_64-1sl.txz installed.


plugin: downloading: http://slackware.osuosl.org/slackware64-14.1/slackware64/l/parted-3.1-x86_64-1.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/parted-3.1-x86_64-1.txz
+==============================================================================

Verifying package parted-3.1-x86_64-1.txz.
Installing package parted-3.1-x86_64-1.txz:
PACKAGE DESCRIPTION:
# parted (GNU disk partitioning tool)
#
# GNU Parted is a program for creating, destroying, resizing, checking
# and copying partitions, and the filesystems on them. This is useful
# for creating space for new operating systems, reorganizing disk
# usage, copying data between hard disks, and disk imaging.
#
Executing install script for parted-3.1-x86_64-1.txz.
Package parted-3.1-x86_64-1.txz installed.


plugin: downloading: http://slackware.osuosl.org/slackware64-14.1/slackware64/l/libnl-1.1.4-x86_64-1.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/unassigned.devices/packages/libnl-1.1.4-x86_64-1.txz
+==============================================================================

Verifying package libnl-1.1.4-x86_64-1.txz.
Installing package libnl-1.1.4-x86_64-1.txz:
PACKAGE DESCRIPTION:
# libnl (netlink socket library)
#
# libnl is a library for applications dealing with netlink sockets.
# The library provides an interface for raw netlink messaging and
# various netlink family specific interfaces.
# 
# Homepage: http://people.suug.ch/~tgr/libnl/
#
# 
Executing install script for libnl-1.1.4-x86_64-1.txz.
Package libnl-1.1.4-x86_64-1.txz installed.





Warning: preg_grep(): Unknown modifier '0' in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804

Warning: array_values() expects parameter 1 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 804

Warning: natsort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 805

Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned on line 50

-----------------------------------------------------------
unassigned.devices has been installed.
This plugin requires Dynamix webGui to operate
Copyright 2015, gfjardim
Copyright 2016, dlandon
Version: 2016.02.13
-----------------------------------------------------------

plugin: installed

The Unassigned Devices log:

Feb 14 11:37:48 Adding disk '/dev/sdi1'...
Feb 14 11:37:48 Mount drive command: mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdi1' '/mnt/docker-appdata'
Feb 14 11:37:48 Successfully mounted '/dev/sdi1' on '/mnt/docker-appdata'
Feb 14 11:37:48 Partition 'OCZ TRION100 952B54S2KMCX' is not set as sharable and will not be shared...
Feb 14 11:37:48 Command not available.  Cannot execute script.
Feb 14 23:29:53 Running command '/boot/config/plugins/unassigned.devices/docker-appdata.sh' with action 'REMOVE'.
Feb 14 23:29:53 Unmounting disk 'OCZ TRION100 952B54S2KMCX'...
Feb 14 23:29:53 Unmounting '/dev/sdi1'...
Feb 14 23:29:53 Unmount of '/dev/sdi1' failed. Error message: 
umount: /mnt/docker-appdata: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof( or fuser(1))

Feb 14 23:31:57 Disk with serial 'OCZ-TRION100_952B54S2KMCX is not set to auto mount and will not be mounted...'

I had hand-mounted the SDI1, as that's where everything docker is on my system..

I've got the latest nerd pack installed, but several packages not loading with it, wonder if that could be the problem?

It's worked fine previously, didn't have any issues until I updated to the version before the current (can't remember the number).

This is what it looks like on screen:

2016-02-14%2023_37_52-Photos.png

The error messages in the install of the plugin come from the command issued to mount all auto mounted devices. It is a php script. That's why the error messages are php errors. Part of that process is to determine what disks are in the array and which ones are outside the array and are unassigned. That's where the error messages are occurring in the script.

What is the ARC device? I think it might be related to that.

dlandon · February 15, 2016

This may or may not be, but it sounds like a sync behavior. If there are unwritten writes to a device, then a sync will require spinning up that device to flush them.

I doubt this because:

1) Nothing has been being written to these disks - EVER

2) All mounted (unassigned devices) disks spin-up (in my case seven 4tb drives)

3) This behaviour is new - and came with the dlandon version of the plugin

I believe it has something to do with the way the temp/spin-up status is checked to display it on the "main" page (you do not even need to activate the unassinged devices sub-tab). It should not check if the disks are spun-down - but it does check something (this is all in tabbed gui-mode - do not know what happens in non-tabbed view)

Just going to the main page will not cause any UD code to be executed. i.e check drive standby status and temperature. How do you know they are being spun up when browsing to the main page?

You say the drives have never been written to but are mounted in UD? Why are you doing that?

dlandon · February 15, 2016

Hi dlandon,

1. I have one of these multi-card USB card readers:

http://smile.amazon.com/SIIG-SuperSpeed-Multi-Slot-Reader-JU-MR0712-S1/dp/B004ZMF824

which looks like this in Unassigned Devices:

It shows a greyed out "format" button when a card has not been inserted, I was wondering if that could be changed to something like "Insert", since "format" doesn't really make sense in this case?

I have come up with an answer for a card reader without a device plugged in. UD will now show 'Insert' instead of 'Format' when a device is not plugged in. 'Mount', 'Format', etc will still be the same.

I'll release a new version later today once I do a bit more testing.

ljm42 · February 16, 2016

Hi dlandon,

1. I have one of these multi-card USB card readers:

http://smile.amazon.com/SIIG-SuperSpeed-Multi-Slot-Reader-JU-MR0712-S1/dp/B004ZMF824

which looks like this in Unassigned Devices:

It shows a greyed out "format" button when a card has not been inserted, I was wondering if that could be changed to something like "Insert", since "format" doesn't really make sense in this case?

I have come up with an answer for a card reader without a device plugged in. UD will now show 'Insert' instead of 'Format' when a device is not plugged in. 'Mount', 'Format', etc will still be the same.

I'll release a new version later today once I do a bit more testing.

Thanks dlandon! I can confirm it correctly identifies my card readers, very cool. Umm... would you be open to hiding the preclear links too?

dlandon · February 16, 2016

Hi dlandon,

1. I have one of these multi-card USB card readers:

http://smile.amazon.com/SIIG-SuperSpeed-Multi-Slot-Reader-JU-MR0712-S1/dp/B004ZMF824

which looks like this in Unassigned Devices:

It shows a greyed out "format" button when a card has not been inserted, I was wondering if that could be changed to something like "Insert", since "format" doesn't really make sense in this case?

I have come up with an answer for a card reader without a device plugged in. UD will now show 'Insert' instead of 'Format' when a device is not plugged in. 'Mount', 'Format', etc will still be the same.

I'll release a new version later today once I do a bit more testing.

Thanks dlandon! I can confirm it correctly identifies my card readers, very cool. Umm... would you be open to hiding the preclear links too?

I don't see those with the card reader I have. Let me see what I can do.

EDIT: Ok, I see where the preclear icon comes from - the pre-clear plugin. I have it fixed.

heffe2001 · February 16, 2016

Heffe, what version of Unraid you on?

6.1.8 currently. This all happened when I updated to this version, and updated the Unassigned Devices version (which required 2 updates for me to get current, the errant text on the main page was in both the current newest version, and the version right before it).

heffe2001 · February 16, 2016

The error messages in the install of the plugin come from the command issued to mount all auto mounted devices. It is a php script. That's why the error messages are php errors. Part of that process is to determine what disks are in the array and which ones are outside the array and are unassigned. That's where the error messages are occurring in the script.

What is the ARC device? I think it might be related to that.

The ARC drive is attached to an Areca controller (all my drives are with the exception of the OCZ SSD, which is connected to one of the motherboard ports). It's been in the system for about 4 months or so, without any issues at all. The Areca controllers don't pass drive names for hardware raid drives, just the ARC information. My parity drive (2x4tb WD Red drives) also shows up as an ARC device. I really wish Lime Tech would add more support for the Areca controllers, so they could grab temperature and other smart data (as well as spin up and spin down). I've mentioned it in the past without any response .

That drive didn't contain any data currently, so I removed the hardware raid assignment for it (just deleted it, since didnt' contain any data), and the errant text went away. Before the last 2 versions of UD it didn't have that errant text, so I wonder what's changed since then? I'm going to try it on a static pass through of the drive and see if it still does it (not a raid set, since it was a raid set of 1 anyway).

With that drive set as pass through, the text also doesn't show up. Apparently it's only when the drive is a raidset from the Areca hardware raid controller. Is this something you may be able to fix, as I was planning on setting up a hardware array of 2 480g SSD's to replace my aging Raptor cache drive, and also set up a 2x240gb SSD Docker drive.

dlandon · February 16, 2016

The error messages in the install of the plugin come from the command issued to mount all auto mounted devices. It is a php script. That's why the error messages are php errors. Part of that process is to determine what disks are in the array and which ones are outside the array and are unassigned. That's where the error messages are occurring in the script.

What is the ARC device? I think it might be related to that.

The ARC drive is attached to an Areca controller (all my drives are with the exception of the OCZ SSD, which is connected to one of the motherboard ports). It's been in the system for about 4 months or so, without any issues at all. The Areca controllers don't pass drive names for hardware raid drives, just the ARC information. My parity drive (2x4tb WD Red drives) also shows up as an ARC device. I really wish Lime Tech would add more support for the Areca controllers, so they could grab temperature and other smart data (as well as spin up and spin down). I've mentioned it in the past without any response .

That drive didn't contain any data currently, so I removed the hardware raid assignment for it (just deleted it, since didnt' contain any data), and the errant text went away. Before the last 2 versions of UD it didn't have that errant text, so I wonder what's changed since then? I'm going to try it on a static pass through of the drive and see if it still does it (not a raid set, since it was a raid set of 1 anyway).

With that drive set as pass through, the text also doesn't show up. Apparently it's only when the drive is a raidset from the Areca hardware raid controller. Is this something you may be able to fix, as I was planning on setting up a hardware array of 2 480g SSD's to replace my aging Raptor cache drive, and also set up a 2x240gb SSD Docker drive.

I changed the way that UD gets the unraid drives and determines which drives are unassigned to be more robust several versions ago. I have some ideas on why this is happening.

In order to troubleshoot this issue, I will need more information so I can try to reproduce the error.

If you can get the drive back to producing the error and get the following information from a command line, I'll see what I can do to try to reproduce the error.

ls /dev/disk/by-id

Also post the /usr/local/emhttp/state/disks.ini file.

These two pieces of information should help me troubleshoot.

ljm42 · February 17, 2016

Hi dlandon,

1. I have one of these multi-card USB card readers:

http://smile.amazon.com/SIIG-SuperSpeed-Multi-Slot-Reader-JU-MR0712-S1/dp/B004ZMF824

which looks like this in Unassigned Devices:

It shows a greyed out "format" button when a card has not been inserted, I was wondering if that could be changed to something like "Insert", since "format" doesn't really make sense in this case?

I have come up with an answer for a card reader without a device plugged in. UD will now show 'Insert' instead of 'Format' when a device is not plugged in. 'Mount', 'Format', etc will still be the same.

I'll release a new version later today once I do a bit more testing.

Thanks dlandon! I can confirm it correctly identifies my card readers, very cool. Umm... would you be open to hiding the preclear links too?

I don't see those with the card reader I have. Let me see what I can do.

EDIT: Ok, I see where the preclear icon comes from - the pre-clear plugin. I have it fixed.

This works great! Here's my updated screenshot:

kizer · February 17, 2016

This Plugin is a life saver.

Dropped my 3.5 inch drive into a USB Hard drive dock and rsync to a NTFS formatted drive to restore every file that was lost on a windows machine. Luckily I made a backup of the files in the first place on my server, but this is saving me tons of work.

Heres the dock that I'm using. I'm sure lots will work...

http://www.amazon.com/dp/B00IKAQ538/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=2XV3YTFU12K0U&coliid=I2WD7F2X7PVFGS&psc=1

heffe2001 · February 17, 2016

I changed the way that UD gets the unraid drives and determines which drives are unassigned to be more robust several versions ago. I have some ideas on why this is happening.

In order to troubleshoot this issue, I will need more information so I can try to reproduce the error.

If you can get the drive back to producing the error and get the following information from a command line, I'll see what I can do to try to reproduce the error.
ls /dev/disk/by-id
Also post the /usr/local/emhttp/state/disks.ini file.

These two pieces of information should help me troubleshoot.

ls /dev/disk/by-id:

root@media01:~# ls /dev/disk/by-id/
ata-MKNSSDCR480GB-G2_MK151112AS2215611@            scsi-ST8000AS0002-1NA_Z84030D2-part1@
ata-MKNSSDCR480GB-G2_MK151112AS2215611-part1@      scsi-ST8000AS0002-1NA_Z8405313@
ata-OCZ-TRION100_952B54S2KMCX@                     scsi-ST8000AS0002-1NA_Z8405313-part1@
ata-OCZ-TRION100_952B54S2KMCX-part1@               scsi-WD30EFRX-68AX9N0_WD-WMC1T3481101@
scsi-ARC-1231-VOL#06_0000003895606702@             scsi-WD30EFRX-68AX9N0_WD-WMC1T3481101-part1@
scsi-ARC-1231-VOL_00_0000003274592794@             scsi-WD5000HHTZ-04N21_WD-WX61E62L3287@
scsi-ARC-1231-VOL_00_0000003274592794-part1@       scsi-WD5000HHTZ-04N21_WD-WX61E62L3287-part1@
scsi-SATA_MKNSSDCR480GB-GMK151112AS2215611@        usb-MUSHKIN_MKNUFDAM16GB_070B4262D199D096-0:0@
scsi-SATA_MKNSSDCR480GB-GMK151112AS2215611-part1@  usb-MUSHKIN_MKNUFDAM16GB_070B4262D199D096-0:0-part1@
scsi-SATA_OCZ-TRION100_952B54S2KMCX@               wwn-0x58889141000739ff@
scsi-SATA_OCZ-TRION100_952B54S2KMCX-part1@         wwn-0x58889141000739ff-part1@
scsi-ST8000AS0002-1NA_Z8402DA1@                    wwn-0x5e83a972002b8d00@
scsi-ST8000AS0002-1NA_Z8402DA1-part1@              wwn-0x5e83a972002b8d00-part1@
scsi-ST8000AS0002-1NA_Z84030D2@

And disks.ini:

["parity"]
idx="0"
name="parity"
device="sdb"
id="ARC-1231-VOL_00_0000003274592794"
rotational="1"
size="7814036428"
status="DISK_OK"
temp="*"
numReads="694304"
numWrites="545097"
numErrors="0"
format="GPT: 4K-aligned"
type="Parity"
comment=""
color="green-on"
exportable="no"
fsStatus="-"
fsColor="grey-off"
spindownDelay="-1"
spinupGroup="host1"
deviceSb=""
idSb="ARC-1231-VOL_00_0000003274592794"
sizeSb="7814036428"
["disk1"]
idx="1"
name="disk1"
device="sde"
id="ST8000AS0002-1NA_Z84030D2"
rotational="1"
size="7814026532"
status="DISK_OK"
temp="*"
numReads="13018140"
numWrites="85082"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="7811939620"
fsFree="487010472"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md1"
idSb="ST8000AS0002-1NA_Z84030D2"
sizeSb="7814026532"
["disk2"]
idx="2"
name="disk2"
device="sdf"
id="ST8000AS0002-1NA_Z8405313"
rotational="1"
size="7814026532"
status="DISK_OK"
temp="*"
numReads="16001758"
numWrites="450315"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="7811939620"
fsFree="836276820"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md2"
idSb="ST8000AS0002-1NA_Z8405313"
sizeSb="7814026532"
["disk3"]
idx="3"
name="disk3"
device="sdg"
id="ST8000AS0002-1NA_Z8402DA1"
rotational="1"
size="7814026532"
status="DISK_OK"
temp="*"
numReads="12613446"
numWrites="14560"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="7811939620"
fsFree="773954064"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md3"
idSb="ST8000AS0002-1NA_Z8402DA1"
sizeSb="7814026532"
["disk4"]
idx="4"
name="disk4"
device="sdc"
id="WD30EFRX-68AX9N0_WD-WMC1T3481101"
rotational="1"
size="2930266532"
status="DISK_OK"
temp="*"
numReads="2414973"
numWrites="4608"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="2928835740"
fsFree="963815736"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md4"
idSb="WD30EFRX-68AX9N0_WD-WMC1T3481101"
sizeSb="2930266532"
["cache"]
idx="24"
name="cache"
device="sdd"
id="WD5000HHTZ-04N21_WD-WX61E62L3287"
rotational="1"
size="488386552"
status="DISK_OK"
temp="*"
numReads="3816162"
numWrites="909037"
numErrors="0"
format="MBR: 4K-aligned"
type="Cache"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="yellow-on"
fsError=""
fsType="xfs"
fsSize="488148084"
fsFree="482845092"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="sdd1"
idSb="WD5000HHTZ-04N21_WD-WX61E62L3287"
sizeSb="488386552"
uuid=""
["flash"]
idx="25"
name="flash"
device="sda"
id="MKNUFDAM16GB"
rotational="0"
size="15141472"
status="DISK_OK"
temp="*"
numReads="1838"
numWrites="2709"
numErrors="0"
format="unknown"
type="Flash"
comment="unRAID Sever OS boot device"
color="green-on"
exportable="yes"
fsStatus="Mounted"
fsColor="yellow-on"
fsError=""
fsType="vfat"
fsSize="15133280"
fsFree="14926880"

dlandon · February 18, 2016

I changed the way that UD gets the unraid drives and determines which drives are unassigned to be more robust several versions ago. I have some ideas on why this is happening.

In order to troubleshoot this issue, I will need more information so I can try to reproduce the error.

If you can get the drive back to producing the error and get the following information from a command line, I'll see what I can do to try to reproduce the error.
ls /dev/disk/by-id
Also post the /usr/local/emhttp/state/disks.ini file.

These two pieces of information should help me troubleshoot.

ls /dev/disk/by-id:

root@media01:~# ls /dev/disk/by-id/
ata-MKNSSDCR480GB-G2_MK151112AS2215611@            scsi-ST8000AS0002-1NA_Z84030D2-part1@
ata-MKNSSDCR480GB-G2_MK151112AS2215611-part1@      scsi-ST8000AS0002-1NA_Z8405313@
ata-OCZ-TRION100_952B54S2KMCX@                     scsi-ST8000AS0002-1NA_Z8405313-part1@
ata-OCZ-TRION100_952B54S2KMCX-part1@               scsi-WD30EFRX-68AX9N0_WD-WMC1T3481101@
scsi-ARC-1231-VOL#06_0000003895606702@             scsi-WD30EFRX-68AX9N0_WD-WMC1T3481101-part1@
scsi-ARC-1231-VOL_00_0000003274592794@             scsi-WD5000HHTZ-04N21_WD-WX61E62L3287@
scsi-ARC-1231-VOL_00_0000003274592794-part1@       scsi-WD5000HHTZ-04N21_WD-WX61E62L3287-part1@
scsi-SATA_MKNSSDCR480GB-GMK151112AS2215611@        usb-MUSHKIN_MKNUFDAM16GB_070B4262D199D096-0:0@
scsi-SATA_MKNSSDCR480GB-GMK151112AS2215611-part1@  usb-MUSHKIN_MKNUFDAM16GB_070B4262D199D096-0:0-part1@
scsi-SATA_OCZ-TRION100_952B54S2KMCX@               wwn-0x58889141000739ff@
scsi-SATA_OCZ-TRION100_952B54S2KMCX-part1@         wwn-0x58889141000739ff-part1@
scsi-ST8000AS0002-1NA_Z8402DA1@                    wwn-0x5e83a972002b8d00@
scsi-ST8000AS0002-1NA_Z8402DA1-part1@              wwn-0x5e83a972002b8d00-part1@
scsi-ST8000AS0002-1NA_Z84030D2@

And disks.ini:

["parity"]
idx="0"
name="parity"
device="sdb"
id="ARC-1231-VOL_00_0000003274592794"
rotational="1"
size="7814036428"
status="DISK_OK"
temp="*"
numReads="694304"
numWrites="545097"
numErrors="0"
format="GPT: 4K-aligned"
type="Parity"
comment=""
color="green-on"
exportable="no"
fsStatus="-"
fsColor="grey-off"
spindownDelay="-1"
spinupGroup="host1"
deviceSb=""
idSb="ARC-1231-VOL_00_0000003274592794"
sizeSb="7814036428"
["disk1"]
idx="1"
name="disk1"
device="sde"
id="ST8000AS0002-1NA_Z84030D2"
rotational="1"
size="7814026532"
status="DISK_OK"
temp="*"
numReads="13018140"
numWrites="85082"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="7811939620"
fsFree="487010472"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md1"
idSb="ST8000AS0002-1NA_Z84030D2"
sizeSb="7814026532"
["disk2"]
idx="2"
name="disk2"
device="sdf"
id="ST8000AS0002-1NA_Z8405313"
rotational="1"
size="7814026532"
status="DISK_OK"
temp="*"
numReads="16001758"
numWrites="450315"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="7811939620"
fsFree="836276820"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md2"
idSb="ST8000AS0002-1NA_Z8405313"
sizeSb="7814026532"
["disk3"]
idx="3"
name="disk3"
device="sdg"
id="ST8000AS0002-1NA_Z8402DA1"
rotational="1"
size="7814026532"
status="DISK_OK"
temp="*"
numReads="12613446"
numWrites="14560"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="7811939620"
fsFree="773954064"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md3"
idSb="ST8000AS0002-1NA_Z8402DA1"
sizeSb="7814026532"
["disk4"]
idx="4"
name="disk4"
device="sdc"
id="WD30EFRX-68AX9N0_WD-WMC1T3481101"
rotational="1"
size="2930266532"
status="DISK_OK"
temp="*"
numReads="2414973"
numWrites="4608"
numErrors="0"
format="GPT: 4K-aligned"
type="Data"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="green-on"
fsError=""
fsType="xfs"
fsSize="2928835740"
fsFree="963815736"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="md4"
idSb="WD30EFRX-68AX9N0_WD-WMC1T3481101"
sizeSb="2930266532"
["cache"]
idx="24"
name="cache"
device="sdd"
id="WD5000HHTZ-04N21_WD-WX61E62L3287"
rotational="1"
size="488386552"
status="DISK_OK"
temp="*"
numReads="3816162"
numWrites="909037"
numErrors="0"
format="MBR: 4K-aligned"
type="Cache"
comment=""
color="green-on"
exportable="no"
fsStatus="Mounted"
fsColor="yellow-on"
fsError=""
fsType="xfs"
fsSize="488148084"
fsFree="482845092"
spindownDelay="-1"
spinupGroup="host1"
deviceSb="sdd1"
idSb="WD5000HHTZ-04N21_WD-WX61E62L3287"
sizeSb="488386552"
uuid=""
["flash"]
idx="25"
name="flash"
device="sda"
id="MKNUFDAM16GB"
rotational="0"
size="15141472"
status="DISK_OK"
temp="*"
numReads="1838"
numWrites="2709"
numErrors="0"
format="unknown"
type="Flash"
comment="unRAID Sever OS boot device"
color="green-on"
exportable="yes"
fsStatus="Mounted"
fsColor="yellow-on"
fsError=""
fsType="vfat"
fsSize="15133280"
fsFree="14926880"

I found the problem. It is with a '#' in the device id string.

'scsi-ARC-1231-VOL#06_0000003895606702@'

It was causing a failure with a php string function finding the partitions on a device. I'll release a new version this evening with a fix.

Videodr0me · February 18, 2016

Just going to the main page will not cause any UD code to be executed. i.e check drive standby status and temperature. How do you know they are being spun up when browsing to the main page?

You say the drives have never been written to but are mounted in UD? Why are you doing that?

The drives have never been written to when mounted on the unraid server. They contain data written by a windows machine. They are only being read through the unassinged devices share. How do I now they spin up - 1) I am standing right next to the unraid server and can see/hear/feel them spinning up one after another (its seven drives so it takes quite a while - and none of additonal 5 array drives spin up) 2) changing tabs on the unraid gui is not possible while the 7 unassinged devices drives spin up.

Also it might not be specific unassinged devices code that leads to the drives being spun up - maybe its unraid core code (maybe a change in 6.1.7 or 6.1.. Interestingly sometimes they do not spin up - i have a "feeling" it only happens under certain conditions, maybe the first time you log into the gui. It's no biggie, but kind of annoying to wake up seven drives for no reason that are perfectly happy being spun down.

Also the disks contain the typical windows bitlocker partition structure - so there is a small partition that is not mountable and the main partition (plain non encrypted ntfs) that gets mounted. But I do not know how or if this has anything to do with the behavior.

dlandon · February 18, 2016

Just going to the main page will not cause any UD code to be executed. i.e check drive standby status and temperature. How do you know they are being spun up when browsing to the main page?

You say the drives have never been written to but are mounted in UD? Why are you doing that?

The drives have never been written to when mounted on the unraid server. They contain data written by a windows machine. They are only being read through the unassinged devices share. How do I now they spin up - 1) I am standing right next to the unraid server and can see/hear/feel them spinning up one after another (its seven drives so it takes quite a while - and none of additonal 5 array drives spin up) 2) changing tabs on the unraid gui is not possible while the 7 unassinged devices drives spin up.

Also it might not be specific unassinged devices code that leads to the drives being spun up - maybe its unraid core code (maybe a change in 6.1.7 or 6.1.. Interestingly sometimes they do not spin up - i have a "feeling" it only happens under certain conditions, maybe the first time you log into the gui. It's no biggie, but kind of annoying to wake up seven drives for no reason that are perfectly happy being spun down.

Also the disks contain the typical windows bitlocker partition structure - so there is a small partition that is not mountable and the main partition (plain non encrypted ntfs) that gets mounted. But I do not know how or if this has anything to do with the behavior.

UD does not do any checking of the drive status unless you browse to the UD page. It is not doing any drive monitoring in the background. unraid does not monitor or check any UD mounted drives. Drives spinning up when going to the main unraid tab is probably something else.

If you are using cache_dirs, any disk mounted by UD will be included as a scanned directory unless specifically excluded, or not included. Cache_dirs will scan disks one at a time as you describe. I've also seen when cache_dirs does not have enough memory, it will have to un-cache and re-cache directories. You might try excluding the seven drives in cache_dirs you have mounted with UD.

tr0910 · February 18, 2016

I found the problem. It is with a '#' in the device id string.

'scsi-ARC-1231-VOL#06_0000003895606702@'

This is a problem for me as well. I have an areca 1231 and 1280.

My arecas were causing problems some months ago. When creating the raid 0 pair in areca, I had to edit and shorten the pair name removing the offending characters that areca insists on automatically creating as part of the name.

There are no # in my areca raid pairs any longer. You can edit this in the areca software accessed during boot or by IP with a web browser later.

I seem to recall this was an issue in the array as well as I use a raid 0 parity pair. I have had a spare raid 0 pair hanging out in UD for months now awaiting dual parity. (vb.grin)

Thanks dlandon for fixing.

Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

dlandon

dlandon

dlandon

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation