NVMe cache device is on the unassigned devices list with a strange identifier:

2 hours ago, johnnie.black said:

NVMe cache device is on the unassigned devices list with a strange identifier:

Do you have the preclear plugin installed?

2 minutes ago, dlandon said:

Do you have the preclear plugin installed?

 

Nope.

19 minutes ago, johnnie.black said:

 

Nope.

Post a diagnostic.

3 hours ago, johnnie.black said:

NVMe cache device is on the unassigned devices list with a strange identifier:

 

Are you running unRAID 6.4?

 

1 hour ago, bonienl said:

Are you running unRAID 6.4?

 

Yes, I know the NVMe is not identified correctly, still it shouldn't appear as an available unassigned device.

 

1 hour ago, dlandon said:

Post a diagnostic.

 

Attached.

tower1-diagnostics-20170716-1213.zip

I don't see the issue.  I'd like to get some debug information from your system so I can see more of what is happening.  On the command line do the following:

nano /usr/local/emhttp/plugins/unassigned.devices/include/lib.php

Change the following:

$plugin = "unassigned.devices";
// $VERBOSE=TRUE;

to

$plugin = "unassigned.devices";
$VERBOSE=TRUE;

Then go to the unassigned devices page and download the UD log and post it.   After that you'll want to comment out the '$VERBOSE=TRUE;' to keep the log from growing too large.

1 hour ago, dlandon said:

Then go to the unassigned devices page and download the UD log and post it.

 

Attached.

tower1-unassigned.devices-20170716-1445.zip

UD is finding four unassigned devices.  Your cache disk is excluded.  The disk device id doesn't look right, but it is not the cache disk.  I don't like the truncated nvme-TOSHIBA-RD400_.  That may be part of the issue,

 

Jul 16 14:45:12 UNRAID DISKS:
  /dev/sda
  /dev/sde
  /dev/sdf
  /dev/sdg
  /dev/sdh
  /dev/nvme0n1

Jul 16 14:45:12 Unassigned disk: '/dev/disk/by-id/ata-TOSHIBA_HDWD130_37F65K8AS'.
Jul 16 14:45:12 Unassigned disk: '/dev/disk/by-id/ata-TOSHIBA_MQ01ABD100_Z3AJC14TT'.

Jul 16 14:45:12 Discarded: => '/dev/disk/by-id/ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T1300432' '(/dev/sde)'.
Jul 16 14:45:12 Discarded: => '/dev/disk/by-id/ata-WDC_WD30EZRX-00MMMB0_WD-WMAWZ0425030' '(/dev/sdh)'.
Jul 16 14:45:12 Discarded: => '/dev/disk/by-id/ata-WDC_WD30EZRX-00SPEB0_WD-WCC4E1ZH8492' '(/dev/sdg)'.
Jul 16 14:45:12 Discarded: => '/dev/disk/by-id/ata-WDC_WD30EZRX-22D8PB0_WD-WCC4N1YP88NY' '(/dev/sdf)'.

Jul 16 14:45:12 Unassigned disk: '/dev/disk/by-id/ata-WDC_WD60EZRX-00MVLB1_WD-WX31D944CS0X'.
Jul 16 14:45:12 Unassigned disk: '/dev/disk/by-id/nvme-TOSHIBA-RD400_'.
Jul 16 14:45:12 Discarded: => '/dev/disk/by-id/nvme-eui.e83a9702000018f5' '(/dev/nvme0n1)'.   <===== cache disk is ignored

Please show a screen shot of all unassigned devices.  Try to make it more readable.  I can barely read the device id.

29 minutes ago, dlandon said:

 I don't like the truncated nvme-TOSHIBA-RD400_.  That may be part of the issue,

 

Probably.

 

 

10 minutes ago, johnnie.black said:

 

Probably.

 

 

That's the one.  Give me the results of this command:

ls /dev/disk/by-id/

 

7 minutes ago, dlandon said:

That's the one.  Give me the results of this command:

ls /dev/disk/by-id/

 

 

ata-TOSHIBA_HDWD130_37F65K8AS@
ata-TOSHIBA_MQ01ABD100_Z3AJC14TT@
ata-TOSHIBA_MQ01ABD100_Z3AJC14TT-part1@
ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T1300432@
ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T1300432-part1@
ata-WDC_WD30EZRX-00MMMB0_WD-WMAWZ0425030@
ata-WDC_WD30EZRX-00MMMB0_WD-WMAWZ0425030-part1@
ata-WDC_WD30EZRX-00SPEB0_WD-WCC4E1ZH8492@
ata-WDC_WD30EZRX-00SPEB0_WD-WCC4E1ZH8492-part1@
ata-WDC_WD30EZRX-22D8PB0_WD-WCC4N1YP88NY@
ata-WDC_WD30EZRX-22D8PB0_WD-WCC4N1YP88NY-part1@
ata-WDC_WD60EZRX-00MVLB1_WD-WX31D944CS0X@
ata-WDC_WD60EZRX-00MVLB1_WD-WX31D944CS0X-part1@
nvme-TOSHIBA-RD400_@
nvme-eui.e83a9702000018f5@
nvme-eui.e83a9702000018f5-part1@
usb-Kingston_DataTraveler_2.0_64006A7807FAB031D96709AA-0:0@
usb-Kingston_DataTraveler_2.0_64006A7807FAB031D96709AA-0:0-part1@
wwn-0x10501182279695618049x@
wwn-0x10501182279695618049x-part1@
wwn-0x11233951013753212929x@
wwn-0x11233951013753212929x-part1@
wwn-0x12438954472907100161x@
wwn-0x12438954472907100161x-part1@
wwn-0x16616003131295092736x@
wwn-0x3635306224004976640x@
wwn-0x3635306224004976640x-part1@
wwn-0x6330196881211281409x@
wwn-0x6330196881211281409x-part1@
wwn-0x8622904561878847489x@
wwn-0x8622904561878847489x-part1@

 

Quote

nvme-TOSHIBA-RD400_@

This is the problem.  You should report this to LT as a Linux or unRAID issue.  Probably Linux.

On 7/1/2017 at 10:15 AM, nicr4wks said:

Hi Guys,

 

Just installed UD on unraid 6.3.5, there's 1 unassigned SSD in my system that I'm trying to mount for VM/Dockers.

I've formatted the drive as xfs and 1 partition is showing after clicking the + (Samsung_SSD_840_EVO_250GB_S1DBNSAF553821F).

I type in a new mount name, press enter and nothing happens, the cursor just keeps flashing waiting for more text input.

If I click outside of the text box, the label changes back to the original drive name, if I mount it mounts as the original drive name,

 

Tried 3 different browsers thinking that could be the issue (firefox/ie/vivaldi) and tried on a second PC, any ideas how to get the new label to stick? Or maybe a manual entry I can make to .cfg file to bypass it.

 

Cheers.

Having the same issue, with the same SSD (Evo 840).  Can't get the name to stick for the life of me, even tried the trick of adding a line to the .cfg file to force it.

Does the Unassigned Devices plug in allow for data to be copied from a mounted unassigned device into an Unraid share ?

I shoot about 1TB of photos per month which are captured onto portable hard disks in the field, when I return home I want to copy them to Unraid as quickly as possible. I'm hopeful that a direct connected USB drive will be faster than across my LAN.

20 minutes ago, Tybio said:

Having the same issue, with the same SSD (Evo 840).  Can't get the name to stick for the life of me, even tried the trick of adding a line to the .cfg file to force it.

Need more information.  Post diagnostics.

1 minute ago, dlandon said:

Need more information.  Post diagnostics.

 

Was just working on that when I did a last pass to "Check for stupid".  Unfortunatly for me, I found where I was stupid.  I had the old plugin installed (Last updated in 2015!).  Uninstalled, added the new version and life is good.

 

Sorry about the miss-fire!

1 minute ago, MPR Files said:

Does the Unassigned Devices plug in allow for data to be copied from a mounted unassigned device into an Unraid share ?

I shoot about 1TB of photos per month which are captured onto portable hard disks in the field, when I return home I want to copy them to Unraid as quickly as possible. I'm hopeful that a direct connected USB drive will be faster than across my LAN.

Read the first post in this thread.

1 minute ago, Tybio said:

 

Was just working on that when I did a last pass to "Check for stupid".  Unfortunatly for me, I found where I was stupid.  I had the old plugin installed (Last updated in 2015!).  Uninstalled, added the new version and life is good.

 

Sorry about the miss-fire!

That is a very old version.  How about keeping your plugins up to date.

Just now, dlandon said:

That is a very old version.  How about keeping your plugins up to date.

 

I have the update running weekly, I believe that it was the prior maintainers version, so was not getting updated.  Everything else is up to date, just hadn't needed this one in years so never caught the change.

17 minutes ago, dlandon said:

Read the first post in this thread.

I read the first few pages of this thread (inc first post) before posting my query. I understand that files can be copied from a share to an unassigned device (external USB) using a script. That makes sense to me. I assume then, that copying files from the unassigned device into a specific share can also be scripted.

Can someone confirm that assumption please ?

Editing the sample scripts to work reliably in the opposite direction is beyond my meagre talents.

I'm happy to reward someone who can provide a script to me that will copy the contents of a fixed named USB device into a specific share.

24 minutes ago, MPR Files said:

I read the first few pages of this thread (inc first post) before posting my query. I understand that files can be copied from a share to an unassigned device (external USB) using a script. That makes sense to me. I assume then, that copying files from the unassigned device into a specific share can also be scripted.

Can someone confirm that assumption please ?

Editing the sample scripts to work reliably in the opposite direction is beyond my meagre talents.

 

This is the script I use to move files from my camera's sdcard onto the array:

  https://gist.github.com/ljm42/02b54ce9cc36f992515b

1 hour ago, ljm42 said:

 

This is the script I use to move files from my camera's sdcard onto the array:

  https://gist.github.com/ljm42/02b54ce9cc36f992515b

 

Thanks, I'm nearly there.

The script is running, but throwing up this error message :

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

 

Secondly, I've tried to alter this line to define the destination, but suspect I have it wrong :

## DESTINATION="/mnt/user/Photos/To Be Filed/incoming/$(date +"%Y-%m-%d-%H-%M-%S-%N")/"
DESTINATION="/mnt/Private/Photos/To Be Filed/incoming/$(date +"%Y-%m-%d-%H-%M-%S-%N")/"

 

The complete path to the target directory is :

smb://Tower._smb._tcp.local/Private/Photos/To Be Filed

 

I've created a folder on the USB device called DCIM and dropped some photos into there.

I assume by doing this, I don't need to alter the source in the script

Changed this line to remove date suffix, didn't seem to fix it, but seeing more activity

DESTINATION="/mnt/user/Private/Photos/To Be Filed/"

 

/boot/config/plugins/unassigned.devices/IFLASHDRIVE.sh 2>&1

Wed Jul 19 17:11:48 NZST 2017 IFLASHDRIVE-Started
/mnt/user/Private/Photos/To Be Filed/
processing /mnt/user/Private/Photos/To Be Filed/
... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/user/Private/Photos/To Be Filed/
... chown -R nobody:users /mnt/user/Private/Photos/To Be Filed/
... sync

completed, elapsed time: 00:00:04
 

Solved my problem by making this change

 

## VALIDDIRS=("/DCIM/[0-9][0-9][0-9]___[0-9][0-9]" "/DCIM/[0-9][0-9][0-9]CANON" "/DCIM/[0-9][0-9][0-9]_FUJI")

VALIDDIRS=("/DCIM/")

 

It's probably not as smart as it was before, but at least the files are copying over. I'll work backwards now and put the date suffix back in