I see the problem.  UD thinks you have 12 disks assigned to the array because you have set the number of slots to 12.  Don't leave any array slots as 'unassigned'.  Set the number of array slots to the number of disks actually in the array.

UD thinks all your disks are in the array and won't show them as unassigned devices.

Ahhhhh, awesome,, problem is im currently remote, and I can't stop the array, because im using a vpn docker to login.  But i'll look at it when i'm home at the end of the week  

Guess it was simple

Edited April 9, 20188 yr by alexdodd

Maybe not so simple.  I did some testing and can't reproduce the problem.

 

I will post a file to replace in the UD plugin that will do more extensive logging so I can see why UD is having a problem with your unassigned disks.

Unzip and copy the attached file to /usr/local/emhttp/plugins/unassigned.devices/include/.  Then go to the main page so the UD script will run.  Refresh the page to be sure.  Then post the diagnostics.  Once that is done, you will probably want to uninstall UD and re-install to restore the original lib.php file so the log doesn't get out of hand.

 

lib.zip

I can't find the folder /usr/local/emhttp/plugins/unassigned.devices/include/ do I create it ?

/usr/local/ doesnt have an emhttp, and I can't seem to find that anywhere?

1 hour ago, alexdodd said:

I can't find the folder /usr/local/emhttp/plugins/unassigned.devices/include/ do I create it ?

/usr/local/ doesnt have an emhttp, and I can't seem to find that anywhere?

Unless you are at the command line you won't be able to see /usr/local.

9 minutes ago, trurl said:

Unless you are at the command line you won't be able to see /usr/local.

Tools>Config file editor has a very handy file browser also.

3 minutes ago, wgstarks said:

Tools>Config file editor has a very handy file browser also.

Yes, I like that too. Won't let you copy a file to that folder though.

Took a little while trying to work out what i'm doing ? and i've been busy.

 

I believe i've done what you need, and this is the new disagnostics file, hope this is correct. I wont reinstall Unassigned Devices before I know you've got what you need.

alexserver-diagnostics-20180409-1750.zip

Edited April 9, 20188 yr by alexdodd

5 hours ago, alexdodd said:

Took a little while trying to work out what i'm doing ? and i've been busy.

 

I believe i've done what you need, and this is the new disagnostics file, hope this is correct. I wont reinstall Unassigned Devices before I know you've got what you need.

alexserver-diagnostics-20180409-1750.zip

I got what I needed.  It looks like you assigned your array disks as the first four disks, then seven unassigned, and then parity to the last slot.  Let me know if this is what you did.

 

Never mind.  You can't do that.

Edited April 9, 20188 yr by dlandon

37 minutes ago, dlandon said:

I got what I needed.  It looks like you assigned your array disks as the first four disks, then seven unassigned, and then parity to the last slot.  Let me know if this is what you did.

 

No probs

I can't actually check that until i'm back within my network, because I can't stop the array without losing my VPN access. 

 

But suffice to say there has been a previous "test" phase in this unraid setups life, where I had many drives connected testing how I would set things up and fit in cases etc... before I went wild with the 2tb SAS drives.  

Part of the switch over/upgrade ready for its final setup I was switching out many smaller drives with one 1tb drive, and switched the original parity drive over with a "final" 2tb SATA drive.  So no doubt i've done something none-standard along the way.

//Eurgh: One of my drives in the array has just went missing now too, like its suddenly died.  I need to really check things in person when i get back home. =/

 

Edited April 9, 20188 yr by alexdodd

51 minutes ago, alexdodd said:

 

No probs

I can't actually check that until i'm back within my network, because I can't stop the array without losing my VPN access. 

 

But suffice to say there has been a previous "test" phase in this unraid setups life, where I had many drives connected testing how I would set things up and fit in cases etc... before I went wild with the 2tb SAS drives.  

Part of the switch over/upgrade ready for its final setup I was switching out many smaller drives with one 1tb drive, and switched the original parity drive over with a "final" 2tb SATA drive.  So no doubt i've done something none-standard along the way.

//Eurgh: One of my drives in the array has just went missing now too, like its suddenly died.  I need to really check things in person when i get back home. =/

 

Please give this new lib.php a try and post diagnostics.

 

 

lib.zip

Edited April 9, 20188 yr by dlandon

Following the steps in this linked post to partition & format a NVMe drive allowed UD to be able to mount the NVMe drives. Formatting via UD wouldn't allow the NVMe drive to mount via UD.

 

 

11 hours ago, jbartlett said:

Following the steps in this linked post to partition & format a NVMe drive allowed UD to be able to mount the NVMe drives. Formatting via UD wouldn't allow the NVMe drive to mount via UD.

 

 

How about some diagnostics?

6 hours ago, dlandon said:

How about some diagnostics?

 

I wasn’t aware that a Diagnostics report would help with Plugins. Here you go.

nas-diagnostics-20180412-1021.zip

I just noticed that I’m getting a lot of PCI errors with the Threadripper motherboard, forgot to implement a fix put in my test rig with it so lots of noise in the syslog. I’ve got my NVMe devices set up so I won’t be able to test it again.

Auto-mounting a disk outside the array via UD and then adding it to an array without disabling the auto-mount leaves the drive mounted though UD and reported by unraid as having no file system in the array with a duplicate UUID.

 

nasbackup-diagnostics-20180412-1539.zip

 

On 10/04/2018 at 12:26 AM, dlandon said:

Please give this new lib.php a try and post diagnostics.

 

 

lib.zip

Finally getting a chance to try this for you, I shall report back tonight

Fresh diagnostics like before with the updated lib.php

 

sdg is now in my main array haven't worked out why the other drive disappeared yet either.

alexserver-diagnostics-20180414-0005.zip

On 4/12/2018 at 1:23 PM, jbartlett said:

 

I wasn’t aware that a Diagnostics report would help with Plugins. Here you go.

nas-diagnostics-20180412-1021.zip

Update your plugins.  Many are out of date.  The UD plugin you have installed is 01.09b.2018.  That's pretty old.

6 hours ago, dlandon said:

Update your plugins.  Many are out of date.

 

Ugh. I'm typically pretty fastidious about keeping them updated. Been a crap couple of months.

3 hours ago, jbartlett said:

 

Ugh. I'm typically pretty fastidious about keeping them updated. Been a crap couple of months.

Now format and mount your nvme disk with UD and post diagnostics.

36 minutes ago, dlandon said:

Now format and mount your nvme disk with UD and post diagnostics.

 

They're already "live" with VM's and Plex cache so I can't.

 

However, my syslog is full of the following:

Apr 14 03:40:16 NAS root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token

nas-diagnostics-20180414-0338.zip

12 hours ago, alexdodd said:

Fresh diagnostics like before with the updated lib.php

 

sdg is now in my main array haven't worked out why the other drive disappeared yet either.

alexserver-diagnostics-20180414-0005.zip

Did this change the devices showing up in UD?

40 minutes ago, jbartlett said:

 

They're already "live" with VM's and Plex cache so I can't.

 

However, my syslog is full of the following:

Apr 14 03:40:16 NAS root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token

nas-diagnostics-20180414-0338.zip

There is really no difference in the linked format procedure and what UD does to format an XFS file system.

 

The wrong csrf_token is because you have left open a web session on the server.  Close all web sessions with unRAID.