dlandon

I have forked a copy of unassigned devices that reverts back to 2015.09.19 that doesn't have the issues the later versions have. I have updated the plugin for unraid 6.1.7 and cleaned up the update/removal that was a bit messy. The plugin will work properly on 6.1.6 also. I'd like to get someone to give it a try and let me know if there are any issues. You don't have to uninstall the current version of unassigned devices. Just paste the following link in the install plugin tab and the current version of unassigned devices will be updated. https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg Treat this as a beta that may have issues. If all seems to be ok, I will release it through ca and Squid can add the appropriate link to the gfjardim version. Be sure to check the unassigned devices log for the repeating log entries that some have seen. I believe there may be one outstanding issue that I will look into. It seems that SMB mounted devices may not be unmounted on an array shutdown. If anyone can test that would be great as I don't currently use that functionality and will have to set up my test server so I can check this out.

Thank you. I am just about done with a forked version that reverts back to 2015.09.19 and adds the fix for the color issue with 6.1.7. I'll ask a few to give it a test run and if ok, I'll make it available as one of my plugins and you can then refer to my forked plugin.

One of the things you'd see in the latest version is the run in the background switch for the script is missing. I have devices the are not recognized properly. The serial numbers are all zeroes so I can't mount them. I'll do what I can to fix this plugin. Rolling back the version fixes most, if not all of the issues that I know of and is the best starting point to move forward.

I'll work up an alternate plugin hosted on my github that will be based on the 2015.09.19 version and fix the install/update so it will be cleaner. I can then address the color issue from the dynamix bleeding edge plugin. It would then show up in ca as one of my plugins. Squid, you can help with how to differentiate the versions in ca? Maybe say the original author is indisposed at the moment and the dlandon plugin is a temporary alternate? I'm really reluctant to do this because I am nowhere as good as gfjardim and don't know if I can fill his shoes. I'll do what I can to help those that depend on this plugin like I do though.

The issue is package management. Older packages for the gui are not removed or updated in place but the gui files are deleted. This confuses the package manager and things get out of sync causing issues. I've pointed this out in a development post that it is an issue in many plugins. The dynamix plugins have been fixed and don't have this problem. I will fix it eventually in the unassigned devices plugin.

It's not really a 6.1.6 compatibility problem. It is just buggy past the 2015.09.19 version. Why don't you say the latest version is not currently working properly and will be worked on?

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.

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.

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.

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.

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

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.

Minor error that only happens during install. Was going to wait til the next update to issue the fix I know. I just don't like to see those messages because it can alarm the uninitiated and cause extra support effort that is not necessary.

The last update gives an error message on the console: "rm: cannot remove '/usr/local/emhttp/plugins/community.applications/AppStore.page.bak': No such file or directory"

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.

Look in the unassigned devices log and see what it says about the partitions. You can view the log by clicking on 'Help' and then reading the help instructions. I've tried to mount Windows 10 partitioned disks and it has been unsuccessful because of the recovery partitions from what I remember.

I understand. Having a reliable backup power source for unraid is pretty important.

Your ups status is missing the nominal power setting so unraid cannot calculate the load. It should look like this: NOMBATTV : 24.0 Volts NOMPOWER : 865 Watts This is from my Back-UPS BX1500G. It is a UPS firmware issue. The UPS is not reporting the nominal power. It's very curious though that it reports the time left on the battery so it knows the nominal power. I want to think about this for a bit, but I think the answer is for bonienl to add another parameter setting in the dynamix apcupsd plugin built into unraid for nominal power that would be used if the UPS does not provide a value. That way the load level could be determined and displayed. What confuses me is that in my screenshots I was also missing nominal power, but it was calculating load percentage.... The load % comes from the UPS: LOADPCT 34.0 Percent This is shown on your screen shot of the UPS Details. It is not calculated. It's no longer being shown which was what's confused me... The load % will come from a current sensor in the UPS. Is this unit new? If so then maybe you should consider an RMA.

I don't know the internal workings of the apcupsd daemon, but there is a remote possibility that the problem is in apcupsd. I was under the impression that the status was just taken from the ups and not processed in any way. Maybe there is a glitch in the status returned that confuses apcupsd.

I see what you are saying. That's guite strange. So now whenever you look at the ups status, you don't get the load %?

Your ups status is missing the nominal power setting so unraid cannot calculate the load. It should look like this: NOMBATTV : 24.0 Volts NOMPOWER : 865 Watts This is from my Back-UPS BX1500G. It is a UPS firmware issue. The UPS is not reporting the nominal power. It's very curious though that it reports the time left on the battery so it knows the nominal power. I want to think about this for a bit, but I think the answer is for bonienl to add another parameter setting in the dynamix apcupsd plugin built into unraid for nominal power that would be used if the UPS does not provide a value. That way the load level could be determined and displayed. What confuses me is that in my screenshots I was also missing nominal power, but it was calculating load percentage.... The load % comes from the UPS: LOADPCT 34.0 Percent This is shown on your screen shot of the UPS Details. It is not calculated.

The UPS is not reporting enough information for unraid to determine the missing values. The load % is missing. There isn't much that can be done to address this except another UPS.

Your ups status is missing the nominal power setting so unraid cannot calculate the load. It should look like this: NOMBATTV : 24.0 Volts NOMPOWER : 865 Watts This is from my Back-UPS BX1500G. It is a UPS firmware issue. The UPS is not reporting the nominal power. It's very curious though that it reports the time left on the battery so it knows the nominal power. I want to think about this for a bit, but I think the answer is for bonienl to add another parameter setting in the dynamix apcupsd plugin built into unraid for nominal power that would be used if the UPS does not provide a value. That way the load level could be determined and displayed.

The current version in unRaid is 3.14.13. Dan, was it updated recently to account for these problems? I'd been posting about my UPS in another thread only a couple of days or so before this issue... As far as I know it has been that version since being included in V6 during beta testing. For those of you having issues, go to a terminal session and type '/sbin/apcaccess > /boot/apcstatus.txt' and post the the apcstatus.txt file so I can look at it. This will tell us if the issue is with the apcupsd not giving the missing parameters, or with unraid having an issue with processing the data. Be sure to tell me which parameters you seem to be missing.

The current version in unRaid is 3.14.13.