heffe2001

Far as setup guide, the GUI is pretty easy to use (not as flashy as Jackett though). I transferred all my stuff over from Jackett, and it's been working fine for me so far. MUCH more stable than Jackett on my system as well (Jackett required me to restart it every few days, it would stop responding to polls and the UI). Also, resources-wise it feels lighter than Jackett.

I have a Seagate Ironwolf ST4000VN008 4tb Hard Drive for sale, still sealed in it's antistat bag, in the NewEgg hard drive box. Overspent on Christmas, so I'm going to let this go slightly less than I paid for it, 140.00 shipped via Paypal (US Only, if outside the US, you'll need to cover shipping). I've got a couple already installed in my Unraid box, and have had no issues with them at all. They seem to be a bit faster than my WD Reds as well, but I haven't verified that with any testing other than file copies. I'd rather offer it up here and save the 10% ebay fees on top of paypals cut (paypal fees are decent, ebay 10% flat is robbery). I'm in Conover, NC, USA, and would prefer US shipping. Picture is of actual unit being shipped. My Ebay info for feedback: http://feedback.ebay.com/ws/eBayISAPI.dll?ViewFeedback2&userid=heffe2008&ftab=FeedbackAsSeller&searchInterval=30

I'm seeing the same thing on my end. Are you on unRAID 6.1.9? If so update the plugin. Just tried that and got an error while trying to update: plugin: updating: speedtest.plg +============================================================================== | Skipping package tablesorter-2.27.6-x86_64-1 (already installed) +============================================================================== plugin: skipping: python-2.7.12-x86_64-1.txz - unRAID version too low, requires at least version 6.2 plugin: downloading: https://raw.githubusercontent.com/dmacias72/unRAID-plugins/master/packages/6.2/python-2.7.9-x86_64-1.txz ... failed (Invalid URL / Server error response) plugin: wget: https://raw.githubusercontent.com/dmacias72/unRAID-plugins/master/packages/6.2/python-2.7.9-x86_64-1.txz download failure (Invalid URL / Server error response)

I'm thinking about doing the same, 60/year for unlimited storage would be a great backup for my Unraid box...

I would say it'd be safe to do so. I'm currently running it without any further errors after using that set variable after upgrading to it. *I edited my post on the forums here that contained the seedbox script I'm using for automatic downloads with the new info just in case someone else is using it and has the same errors. It's here just in case anybody else has the issue and comes to this thread: http://lime-technology.com/forum/index.php?topic=42250.0

The error has something to do with the new version passing a new SSL key to the remote host (maybe something to do with the 6.2 beta cycle and SSL changes?), and it not matching the key on file on the remote. On the 4.6.1 version, it appears to be sending the old key info, in the 4.6.5 version it's sending a new key. In trying to connect the same way with the new version, I'm currently passing the username/password and site info like this: lftp -p 22 -u $login,$pass sftp://$host If you do that from a command line, or through a script, it never asks you if the new key is valid or not with the 4.6.5 version (it didn't when I hand-logged in either). Apparently in 4.6.5 they added a net set variable for lftp (sftp:auto-confirm true), which you can pass with any other set variables in your script, and it will acknowledge the new key-change and actually work. This variable wasn't included with 4.6.1, so I'm going to assume that the older version just accepted the sftp key change and went about it's business. Once that keychange has been accepted with the 4.6.5 version, you can remove the set variable and it will continue to work (I did leave it in my sync watchdir script though). Just wanted to let you know I was able to get it working with 6.2 & the 4.6.5 version, and say sorry for the extra work for you to revert it back to 4.6.1 when the new version can be made to work..

Having issues with the lftp that's been included with the 6.2 repo (4.6.5). It won't pass ssl credentials correctly, and won't connect a sftp connection. I reverted to the version included in the 6.1 repo (4.6.1), and it works fine with that one. Not sure if it's a problem with the specific build you've included, or with LFTP in general. It's getting "Host key verification failed" when attempting to connect to the remote SFTP server.

I forgot to let you know that the update did fix the issue. With a raid drive sent through with the default name on it (with the # sign in it), the display works fine without the errant text. 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.

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"

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.

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).

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:

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. 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.

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

Would it be possible to add: cksfv v1.3.14: http://www.iki.fi/shd/foss/cksfv/ I use it in my download script to check the downloads against their supplied .sfv files.

Would it be possible to make the Cache SSD Trim configurable as to what drive(s) it actually runs on? I don't use a SSD for cache, but I do use it for everything docker. I'm currently using a script installed into the daily cron job list to do it, but would rather be able to manage it via the UI if possible.

Think you could add cksfv to the tools pack? http://zakalwe.fi/~shd/foss/cksfv/

Anybody know if the ARC-1680IX-24-2G cards work in Unraid? Getting one this weekend.

Dropped the # and changed it to a _ without any issues at all. Restarted after the change, assigned it, now the system finds the drive every time. One less thing to worry about lol.

Going to remove the 2tb drives tomorrow, will rename the raidset at that time, and regen parity. Thanks for the tip!

You're actually correct, the drive only shows the ARC-1231-VOL when added, there's a # and long number string (guess it treats it like a serial number). Wonder if there's any way to fix that. Example:

I also restart mine rarely, and if I do it's usually either a unraid core update, or hardware update. It's not been a huge deal for the array to not start, as I usually remember it. As far as I can tell currently, the volume identification for that volume is: ARC-1231-VOL, and that's it. I'll check it when I restart for the RC6 update after parity finishes this evening (replaced 4 emptied 2tb's for a new 8tb last night, leaves me with 3 2tb and 1 3tb left to move data from and remove.. I'm going to have a bunch of 2tb paperweights, lol.

Ever since I set up a 4tbx2 (8tb) parity array on my Areca (so I can use my Seagate Archive 8tb drives as data drives), I've not been able to autostart the array. It always comes up that it's missing the parity drive (which is the Areca array ARC-1231-VOL), even though it's on the dropdown for you to select. All the other drives on the controller have the correct naming (using the instructions at the start of the thread for that). Hopefully this weekend I'll get all the drives moved over to the Areca (Still have 6 drives on the MV8, although 3 of those will be pulled after the data is moved to my latest 8tb). I will say the Areca card is FAST, getting 132MB/sec on a parity check at the moment.. I've tried setting the delay after issuing the udevadm trigger, I've tried it up to 60s total, with the same result (I don't think this is the problem though, as even at 5, all the drives except parity are in their proper place in the array config). Any ideas? It'd also be great if Limetech supported temp and spindown/spinup on these cards, not sure how much trouble that'd be though.

Switched over to your nzbmegasearch, seems to work fine.

Running this on my AMD FX-8520-based unraid box, with the light power setting, and set to run when I'm working it's getting my CPU up to about 41c, and says it's using 4 of my cores (I show 6 cores pegged at 3500, so it's either using more, or other processes on my box are maxing the others). Ran it since yesterday afternoon, and it didn't appear to affect my deluge processes, plex (at least 2 clients running), sonaar or nzbget (I have others running, but they are light use compared to those processes). Also running one VM under KVM. I'm using a Corsair H60 water-cooling system in my server with push-pull fans, and so far it's kept the system from overheating at all (before the H60, without FaH I was hitting high between 48-58 depending on what was going on at the time, too close to the FX thermal overload temp for my taste). Prior to FAH I was sitting at about 28c constant on the CPU. SO make sure you have proper cooling if you're going to be pushing your CPU usage up with something like this... Other than bumping up the CPU temps a bit, it seems to run fine (I did have to add another subnet to the allow list, as I manage it from work across a hardware VPN connection, if you need additional subnets allowed, just put them in the same line as the existing ones, seperated by a comma).