[unRAID 6 beta14+] Unassigned Devices [former Auto Mount USB]


Recommended Posts

I'm fairly new to unRAID.. I've installed this plugin and I have two 4Tb hard drives that contain NTFS data partitions from pre-unRAID days.. Both have a grayed out mount and format icons and I'm not sure why or how to fix it?

 

I just want to mount them, transfer the data off to the unRAID array and then join them to the array afterwards.

I use this to mount NTFS all the time. Possibly you have multiple partitions on these disks. You have to mount a specific partition. Is there a '+' icon next to the drives that would let you expand to see the partitions? Maybe post a screenshot showing what you are talking about.

 

here's a screenshot http://i.imgur.com/64mcHGn.png

 

There are 3 partitions on each of the drives. I can get the format button to enable if I turn on the destructive setting but that's not helpful.

 

As for the log, it contains nothing but the same error John_M is talking about, a new entry every 2 seconds. These are devices that were initially formatted in Windows 10, but not OS drives.

 

EDIT: I gave up and just added them to the array, none of the data lost was replaceable and I wanted to move on.

Link to comment

As for the log, it contains nothing but the same error John_M is talking about, a new entry every 2 seconds. These are devices that were initially formatted in Windows 10, but not OS drives.

 

Since these error messages appear in the plugin's own log, not the general syslog, I suspect most users never see them. But for me at least they are a major problem and for now I've had to uninstall the plugin. I'd like to ask others to check their /var/log/unassigned.devices.log please.

Link to comment

As for the log, it contains nothing but the same error John_M is talking about, a new entry every 2 seconds. These are devices that were initially formatted in Windows 10, but not OS drives.

 

Since these error messages appear in the plugin's own log, not the general syslog, I suspect most users never see them. But for me at least they are a major problem and for now I've had to uninstall the plugin. I'd like to ask others to check their /var/log/unassigned.devices.log please.

 

I have not been able to update from the 2015.09.19 because of this issue and some other outstanding issues that prevent me from mounting and using my backup drives.  gfjardim doesn't seem to be active right now, so I wouldn't expect an update to the plugin.

Link to comment

As for the log, it contains nothing but the same error John_M is talking about, a new entry every 2 seconds. These are devices that were initially formatted in Windows 10, but not OS drives.

 

Since these error messages appear in the plugin's own log, not the general syslog, I suspect most users never see them. But for me at least they are a major problem and for now I've had to uninstall the plugin. I'd like to ask others to check their /var/log/unassigned.devices.log please.

 

I have not been able to update from the 2015.09.19 because of this issue and some other outstanding issues that prevent me from mounting and using my backup drives.  gfjardim doesn't seem to be active right now, so I wouldn't expect an update to the plugin.

Ah, I see. So it is a general problem with the current version. I was beginning to think it was peculiar to my setup and that of a few others. Is there any way I could install the older version? Is it archived somewhere?

Link to comment

As for the log, it contains nothing but the same error John_M is talking about, a new entry every 2 seconds. These are devices that were initially formatted in Windows 10, but not OS drives.

 

Since these error messages appear in the plugin's own log, not the general syslog, I suspect most users never see them. But for me at least they are a major problem and for now I've had to uninstall the plugin. I'd like to ask others to check their /var/log/unassigned.devices.log please.

 

I have not been able to update from the 2015.09.19 because of this issue and some other outstanding issues that prevent me from mounting and using my backup drives.  gfjardim doesn't seem to be active right now, so I wouldn't expect an update to the plugin.

Ah, I see. So it is a general problem with the current version. I was beginning to think it was peculiar to my setup and that of a few others. Is there any way I could install the older version? Is it archived somewhere?

 

It is archived, but you'd have to create a modified plugin to install the older version and not the latest version.

Link to comment

As for the log, it contains nothing but the same error John_M is talking about, a new entry every 2 seconds. These are devices that were initially formatted in Windows 10, but not OS drives.

 

Since these error messages appear in the plugin's own log, not the general syslog, I suspect most users never see them. But for me at least they are a major problem and for now I've had to uninstall the plugin. I'd like to ask others to check their /var/log/unassigned.devices.log please.

 

I have not been able to update from the 2015.09.19 because of this issue and some other outstanding issues that prevent me from mounting and using my backup drives.  gfjardim doesn't seem to be active right now, so I wouldn't expect an update to the plugin.

Ah, I see. So it is a general problem with the current version. I was beginning to think it was peculiar to my setup and that of a few others. Is there any way I could install the older version? Is it archived somewhere?

 

It is archived, but you'd have to create a modified plugin to install the older version and not the latest version.

Hmmm, thanks but I don't feel I could manage that right now. I think I'll wait and monitor this thread to see if the author responds. Shame it's broken - it's a great plugin when it works.

Link to comment

I'm seeing the same errors too. I never bothered to look since I thought all errors would populate in the syslog and my unassigned devices plugin "seems" to be working fine.

 

 

 

 

Tue Jan 12 17:19:34 EST 2016:

Tue Jan 12 17:19:34 EST 2016: Mounting 'all'

Tue Jan 12 17:19:34 EST 2016: Disk with serial 'Samsung_SSD_840_EVO_120GB_S1D5NSBFB10859N' auto mount is disabled, aborting.

Tue Jan 12 17:19:34 EST 2016:

Tue Jan 12 17:19:34 EST 2016: Mounting 'all'

Tue Jan 12 17:19:34 EST 2016: Drive found with the following attributes: name='sdg1', device='/dev/sdg1', part='1', disk='/dev/sdg', label='WDC_WD2002FAEX-007BA0_WD-WMAY01552774-part1', fstype='xfs', mounted='', mountpoint='/mnt/2TB', size='2000398901760', used='0', avail='2000398901760', shared='1', command='/boot/config/plugins/unassigned.devices/unassigned.sh', owner='user'

Tue Jan 12 17:19:34 EST 2016: Adding disk  ...

Tue Jan 12 17:19:35 EST 2016: Mounting drive with command: mount -t xfs -o rw,noatime,nodiratime '/dev/sdg1' '/mnt/2TB'

Tue Jan 12 17:19:35 EST 2016: Successfully mounted '/dev/sdg1' on '/mnt/2TB'

Tue Jan 12 17:19:35 EST 2016: Partition '/dev/sdg1' successfully mounted.

Tue Jan 12 17:19:35 EST 2016: Defining share '2TB' on file '/2TB.conf'.

Tue Jan 12 17:19:35 EST 2016: Reloading Samba configuration.

Tue Jan 12 17:19:35 EST 2016: Directory '/mnt/2TB' shared successfully.

Tue Jan 12 17:19:35 EST 2016: Running command '/boot/config/plugins/unassigned.devices/unassigned.sh' with action 'ADD'.

Tue Jan 12 17:23:49 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(276) : eval()'d code on line 550

Tue Jan 12 17:23:49 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Tue Jan 12 17:23:49 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Tue Jan 12 17:23:49 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Tue Jan 12 17:23:50 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Tue Jan 12 17:23:50 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Tue Jan 12 17:23:51 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Tue Jan 12 17:23:51 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Wed Jan 13 16:41:59 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(276) : eval()'d code on line 550

Wed Jan 13 16:42:01 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Wed Jan 13 16:42:01 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Wed Jan 13 16:42:01 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Wed Jan 13 16:42:03 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Wed Jan 13 16:42:03 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Thu Jan 14 12:39:00 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(276) : eval()'d code on line 550

Thu Jan 14 12:39:01 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Thu Jan 14 12:39:01 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Thu Jan 14 12:39:01 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Thu Jan 14 12:39:04 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Thu Jan 14 12:39:04 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Thu Jan 14 12:39:06 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Thu Jan 14 12:39:06 EST 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Link to comment

One problem is that the log file grows so rapidly there's a danger of running out of ramdisk space. The tmpfs mounted on /var/log normally sits at around 3% used shortly after a reboot and the plugin not installed. You can monitor it via the Dashboard page of the web UI (flash : log : docker). Two days after installing the plugin the log usage was at 34% and two days later at 52%, at which point I uninstalled the plugin and rebooted. 3 days and 12 hours of uptime later log usage is at 4%.

Link to comment

Right guys, getting these:

 

ri Jan 15 22:56:13 AEDT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428
Fri Jan 15 22:56:19 AEDT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

 

Errors every several seconds is crazy. It appears that the author of the plugin is not posting for now. He appears to be active on the forums regularly but not posting. I am sure he will be back but perhaps we need to take matters into our own hands in the meantime. I have been doing some searching on the code as these errors seem to be causing stability issues for some.

 

The only other instance of $ori_error_handler I can find is in the included file lib.php on on line 2

 

UnassignedDevices.php includes lib.php so it seems to me that the following is executed first:

 

$ori_error_handler = set_error_handler("log_error");

 

Then on the last line of UnassignedDevices.php the following is executed:

 

set_error_handler($ori_error_handler);

 

I have tried to find where set_error_handler is but I can't yet. I don't know if it is a global function for writing to the syslog? Looks a bit strange at first glance ....

 

It's been 15 years since I was a coder and was never much good with php! Anyone want to jump in? :)

Link to comment

I've come looking as i am also having this very same issue.

Installed an SSD to host my VMs and Docker, all seems to be good until i tried to mount the disk and the icon never goes green saying mounted.

That being said it does actually mount the disk and shares it. Another weird one is for some reason the share name is in lowercase (ssd), whereas in all config files i have defined it in uppercase (SSD), anyone have any idea to fix that?

 

Checked my logs and i also get the same php errors as you all (after reporting it is mounted correctly);

 

Fri Jan 15 18:29:56 GMT 2016: Mounting '/dev/sdf1'

Fri Jan 15 18:29:56 GMT 2016: Drive found with the following attributes: name='sdf1', device='/dev/sdf1', part='1', disk='/dev/sdf', label='SanDisk_SDSSDA240G_154608406660-part1', fstype='btrfs', mounted='', mountpoint='/mnt/dis$

Fri Jan 15 18:29:56 GMT 2016: Adding disk  ...

Fri Jan 15 18:29:56 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:29:56 GMT 2016: Mounting drive with command: mount -t btrfs -o auto,async,noatime,nodiratime '/dev/sdf1' '/mnt/disks/SSD'

Fri Jan 15 18:29:56 GMT 2016: Successfully mounted '/dev/sdf1' on '/mnt/disks/SSD'

Fri Jan 15 18:29:56 GMT 2016: Partition '/dev/sdf1' successfully mounted.

Fri Jan 15 18:29:56 GMT 2016: Defining share 'SSD' on file '/SSD.conf'.

Fri Jan 15 18:29:56 GMT 2016: Adding share 'SSD' to /boot/config/smb-extra.conf.

Fri Jan 15 18:29:56 GMT 2016: Reloading Samba configuration.

Fri Jan 15 18:29:56 GMT 2016: Directory '/mnt/disks/SSD' shared successfully.

Fri Jan 15 18:29:56 GMT 2016: Command not available, skipping.

Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:00 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:00 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:02 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:02 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:04 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:04 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:06 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:06 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:08 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:08 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:10 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:10 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

Fri Jan 15 18:30:12 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

 

Would moving back to SNAP be an option do you think?

Link to comment

Would moving back to SNAP be an option do you think?

I would be very surprised if SNAP works correctly on the 6.1.x series of unRAID releases as I do not think it was updated to take account of the changes to the security model.  However I have not tried it myself so I could be wrong.
Link to comment

SNAP is incompatible with unraid V6.1 and will not work.

 

Attached is a modified plugin I created to install the last version of unassigned devices that works for me.  Copy this file to your flash drive, then go to the Plugins->Install Plugin tab and select the 'unassigned.devices.plg' on your flash.  This will install the 2015.09.19 version and won't try to update to the later versions.

 

I don't know what features the later versions offered.  I think gfjardim was rewriting some things and left them half done.

 

This is the best I think we can do until gfjardim returns to update unassigned devices.  I am not interested in picking up yet another abandoned plugin, but if gfjardim does not return, I may move this version to my own github repository so users can at least have a version that works.  We'd have to see how it goes from there.

unassigned.devices.plg

Link to comment

SNAP is incompatible with unraid V6.1 and will not work.

 

Attached is a modified plugin I created to install the last version of unassigned devices that works for me.  Copy this file to your flash drive, then go to the Plugins->Install Plugin tab and select the 'unassigned.devices.plg' on your flash.  This will install the 2015.09.19 version and won't try to update to the later versions.

 

I don't know what features the later versions offered.  I think gfjardim was rewriting some things and left them half done.

 

This is the best I think we can do until gfjardim returns to update unassigned devices.  I am not interested in picking up yet another abandoned plugin, but if gfjardim does not return, I may move this version to my own github repository so users can at least have a version that works.  We'd have to see how it goes from there.

 

Thank you! :)

Link to comment

One problem is that the log file grows so rapidly there's a danger of running out of ramdisk space. The tmpfs mounted on /var/log normally sits at around 3% used shortly after a reboot and the plugin not installed. You can monitor it via the Dashboard page of the web UI (flash : log : docker). Two days after installing the plugin the log usage was at 34% and two days later at 52%, at which point I uninstalled the plugin and rebooted. 3 days and 12 hours of uptime later log usage is at 4%.

 

I just looked at my unassigned.devices.log and the error only repeated 4 times today. So it is not filling my log space up quickly. I wonder why yours is filling up so much so quickly?

 

Link to comment

SNAP is incompatible with unraid V6.1 and will not work.

 

Attached is a modified plugin I created to install the last version of unassigned devices that works for me.  Copy this file to your flash drive, then go to the Plugins->Install Plugin tab and select the 'unassigned.devices.plg' on your flash.  This will install the 2015.09.19 version and won't try to update to the later versions.

 

I don't know what features the later versions offered.  I think gfjardim was rewriting some things and left them half done.

 

This is the best I think we can do until gfjardim returns to update unassigned devices.  I am not interested in picking up yet another abandoned plugin, but if gfjardim does not return, I may move this version to my own github repository so users can at least have a version that works.  We'd have to see how it goes from there.

 

Thank you! :)

 

Unassigned devices does not uninstall very cleanly.  If you remove the plugin before installing my suggested version, you will have to reboot or you may experience a failure in the plugin because the previous plugin package is not removed.

Link to comment

SNAP is incompatible with unraid V6.1 and will not work.

 

Attached is a modified plugin I created to install the last version of unassigned devices that works for me.  Copy this file to your flash drive, then go to the Plugins->Install Plugin tab and select the 'unassigned.devices.plg' on your flash.  This will install the 2015.09.19 version and won't try to update to the later versions.

 

I don't know what features the later versions offered.  I think gfjardim was rewriting some things and left them half done.

 

This is the best I think we can do until gfjardim returns to update unassigned devices.  I am not interested in picking up yet another abandoned plugin, but if gfjardim does not return, I may move this version to my own github repository so users can at least have a version that works.  We'd have to see how it goes from there.

 

Thank you! :)

 

Unassigned devices does not uninstall very cleanly.  If you remove the plugin before installing my suggested version, you will have to reboot or you may experience a failure in the plugin because the previous plugin package is not removed.

 

Noted, good advice, Ta!

 

I wonder if it's worth a Mod amending the first post of this thread with this option/file to mark the plugin broken or something in the short term to prevent new users adding it in the first place? I wonder if there is a flag in CA to mark it as broken (and I use this term with a light heart because I know functionally 99% of it is sound) too?

Link to comment

SNAP is incompatible with unraid V6.1 and will not work.

 

Attached is a modified plugin I created to install the last version of unassigned devices that works for me.  Copy this file to your flash drive, then go to the Plugins->Install Plugin tab and select the 'unassigned.devices.plg' on your flash.  This will install the 2015.09.19 version and won't try to update to the later versions.

 

I don't know what features the later versions offered.  I think gfjardim was rewriting some things and left them half done.

 

This is the best I think we can do until gfjardim returns to update unassigned devices.  I am not interested in picking up yet another abandoned plugin, but if gfjardim does not return, I may move this version to my own github repository so users can at least have a version that works.  We'd have to see how it goes from there.

 

Thank you! :)

 

Unassigned devices does not uninstall very cleanly.  If you remove the plugin before installing my suggested version, you will have to reboot or you may experience a failure in the plugin because the previous plugin package is not removed.

 

Noted, good advice, Ta!

 

I wonder if it's worth a Mod amending the first post of this thread with this option/file to mark the plugin broken or something in the short term to prevent new users adding it in the first place? I wonder if there is a flag in CA to mark it as broken (and I use this term with a light heart because I know functionally 99% of it is sound) too?

 

I want to wait and see if this really fixes issues for users.  I assume it is working for you?  Squid can black list this plugin in CA, but I don't want to be that dramatic yet.  If we go this route, I would spend a little time to clean up the removal and update of the plugin.  Even updating the plugin is messy and I've had to reboot after an update.

 

I'm really hoping gfjardim will come to the rescue and at least just fix the outstanding issues.  The plugin doesn't really need any enhancements at this point.  One of the later versions lets a drive be mounted as a NFS share but I don't see that as a desperate need right now.

Link to comment

I too have been having that log fill (Unraid 6.1.6 with the Unnasigned Devices plugin 2015.11.18).

 

I've been periodically deleting it...  I last purged it on Mon Jan 11 18:26:35 and today (Jan 15) it's at 81MBs:

 

81M Jan 15 18:00 unassigned.devices.log

 

Regards,

Jake

 

Link to comment

Checked and I also was getting the log messages. Installed the .plg and rebooted and the log error messages are gone; however, my "main" tab shows this"

Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 31 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 32 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 31 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 32 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 31 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 32 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 

 

I do the plugin "Dynamix Bleeding Edge" installed so I am guessing the that is why I am getting this.

Link to comment

 

I want to wait and see if this really fixes issues for users.  I assume it is working for you?  Squid can black list this plugin in CA, but I don't want to be that dramatic yet.  If we go this route, I would spend a little time to clean up the removal and update of the plugin.  Even updating the plugin is messy and I've had to reboot after an update.

 

I'm really hoping gfjardim will come to the rescue and at least just fix the outstanding issues.  The plugin doesn't really need any enhancements at this point.  One of the later versions lets a drive be mounted as a NFS share but I don't see that as a desperate need right now.

 

I never got to use it, but it would seem if this could be Feature locked and simply brought up to standard it would go along way.

Link to comment

Checked and I also was getting the log messages. Installed the .plg and rebooted and the log error messages are gone; however, my "main" tab shows this"

Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 31 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 32 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 31 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 32 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 31 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 
Warning: Missing argument 3 for usage_color(), called in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 32 and defined in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 75 

 

I do the plugin "Dynamix Bleeding Edge" installed so I am guessing the that is why I am getting this.

 

No.  That's a change in the "Dynamix Bleeding Edge" and is still a problem in the older unassigned devices.  If I stabilize this plugin and put it on my github, I'll have to see about fixing the color issue.

Link to comment

 

I want to wait and see if this really fixes issues for users.  I assume it is working for you?  Squid can black list this plugin in CA, but I don't want to be that dramatic yet.  If we go this route, I would spend a little time to clean up the removal and update of the plugin.  Even updating the plugin is messy and I've had to reboot after an update.

 

I'm really hoping gfjardim will come to the rescue and at least just fix the outstanding issues.  The plugin doesn't really need any enhancements at this point.  One of the later versions lets a drive be mounted as a NFS share but I don't see that as a desperate need right now.

 

I never got to use it, but it would seem if this could be Feature locked and simply brought up to standard it would go along way.

 

I agree and will see about doing that if I can find some time.  I'll contact bonienl and see what the color change means so I can fix that.

 

I was really hoping it would not come to this, but this plugin is awesome.  I don't want to revive SNAP because it was written a long time ago and is not current with the new unraid webgui.  Unassigned devices is so much better.

Link to comment
  • Squid locked this topic
Guest
This topic is now closed to further replies.