Frank1940

What version are you running? Check on the plugin page to find out. The reason is that this was an issue for several of us (Look back a couple of pages in the thread) but it was fixed for us with an update.

Typedf and see what you have for available space in tmpfs. Well on my Media server, the available space in tmpfs is 128,476. On the Test Bed Server, the available space is 129297. However, both servers have been rebooted to get rid of the extra two buttons so the present available space number (on the Media server) is not really a good indicator of what it was when the plugin installation was being run. See here for some discussion and a fix for tmpfs allocation. Interesting reading. I had a look at the syslog file which was saved (Thanks, dlanson, for including this in the Powerdown plugin) when I did the last reboot. I found hundreds of lines of error similar to these: Jul 22 08:33:22 Elsie1 logger: plugin: creating: /boot/config/plugins/dynamix.schedules/dynamix.schedules-2015.07.20.txz - downloading from URL https://raw.github.com/bergware/dynamix/master/archive/dynamix.schedules-2015.07.20.txz Jul 22 08:33:23 Elsie1 logger: plugin: running: /boot/config/plugins/dynamix.schedules/dynamix.schedules-2015.07.20.txz Jul 22 08:33:23 Elsie1 logger: plugin: running: anonymous Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null Jul 22 08:35:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null Jul 22 08:41:17 Elsie1 kernel: mdcmd (145): spindown 0 Jul 22 08:41:17 Elsie1 kernel: mdcmd (146): spindown 5 Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null Jul 22 08:45:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.daily 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.weekly 1> /dev/null Jul 22 09:05:01 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.monthly 1> /dev/null Jul 22 09:25:11 Elsie1 crond[1340]: failed parsing crontab for user root: /usr/bin/run-parts /etc/cron.hourly 1> /dev/null I attached the syslog for your information. syslog.zip

Typedf and see what you have for available space in tmpfs. Well on my Media server, the available space in tmpfs is 128,476. On the Test Bed Server, the available space is 129297. However, both servers have been rebooted to get rid of the extra two buttons so the present available space number (on the Media server) is not really a good indicator of what it was when the plugin installation was being run.

Took the big leap of faith and installed System Buttons plugin on my Media Server. Had to reboot it to get rid of the two extra buttons. Used the plugin to do the reboot. (So it works on this server, too.) Only thing that I noticed were some errors on install logging screen. I don't know if these errors are the indication of any problems or not but thought you might want to have a look-see. plugin: updating: dynamix.system.buttons.plg plugin: downloading: https://raw.github.com/bergware/dynamix/master/archive/dynamix.system.buttons-2015.08.02.txz ... done +============================================================================== | Installing new package /boot/config/plugins/dynamix.system.buttons/dynamix.system.buttons-2015.08.02.txz +============================================================================== Verifying package dynamix.system.buttons-2015.08.02.txz. expr: syntax error /sbin/installpkg: line 432: [: -lt: unary operator expected /sbin/installpkg: line 434: [: -lt: unary operator expected expr: syntax error /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 466: echo: write error: No space left on device /sbin/installpkg: line 469: echo: write error: No space left on device cat: write error: No space left on device Installing package dynamix.system.buttons-2015.08.02.txz: PACKAGE DESCRIPTION: /sbin/installpkg: line 537: echo: write error: No space left on device /sbin/installpkg: line 538: echo: write error: No space left on device /sbin/installpkg: line 539: echo: write error: No space left on device /sbin/installpkg: line 540: echo: write error: No space left on device /sbin/installpkg: line 545: echo: write error: No space left on device /sbin/installpkg: line 550: echo: write error: No space left on device /sbin/installpkg: line 559: echo: write error: No space left on device WARNING: Package has not been created with 'makepkg' Package dynamix.system.buttons-2015.08.02.txz installed. chmod: missing operand after '644' Try 'chmod --help' for more information. ----------------------------------------------------------- Plugin dynamix.system.buttons is installed. This plugin requires Dynamix webGui to operate Copyright 2015, Bergware International Version: 2015.08.02 ----------------------------------------------------------- plugin: updated

Works now for me also. (Sorry to be so late with a report but we had a High Class Reunion Picnic today.)

The normal sequence is that after pressing the button a popup windows appears (see picture) telling that preparations are taking place, once these are done the normal shutdown or reboot screen is shown. You are saying none of this happening? Nope. This is the only screen that appears and it has been there like that for for more than two minutes. As I said, if I click on the browser bookmark, the Main GUI page returns. It appears to be that nothing happens beyond that point. PS------ I do have the dlandon Powerdown (ver 2.17) Plugin installed. Does any else who is having an issue have this configuration also? (I like that logging feature when it runs!)

This morning I decided to try again. I first uninstalled the Systems Button plugin. The plugin was gone but the buttons were still there. So I rebooted the server using the "Array Operation' tab. When the server came back up, all the buttons were gone! So far, so good. I now reinstalled the System Buttons plugin using the 'Install Plugins' page. That worked. I now have only one button. And clicking on that button, displays the dropdown menu. Now for the problem. When I click on either option on the dropdown menu, The appropriate banner appears BUT nothing else happens! The server will neither reboot nor shutdown. Now remember that it just did a reboot, two minutes prior to this attempt (using the button), using the old sequence in the 'Array Operation' tab. I even ran the two commands in the above post and both times the file or directory was not there. This is a 'plain Jane' server and the only other plugin installed is the dlandon Powerdown (ver 2.17) plugin.

I have the same three buttons and none of the buttons seems to result in any action when click. The left button provides a dropdown menu which gives a choice of shutdown or reboot. The 'reboot' option displays the "System is rebooting..." banner" but, after clicking on the server bookmark, the GUI reappears immediately! The center 'Reboot" button results in the same sequence. I have not tried either the 'Powerdown' option on the dropdown option or the right 'Powerdown' button but I suspect a similar behavior.

Worked. Although in my case, the plugin was actually there and on checking for updates, there was one. I updated (somewhat tentatively) but everything went smoothly. Current version is 2015.08.01c.

Can you clear your browser cache (CTRL-F5) and reload the page ? I have rebooted both the Server and my Win7 computer and the problem still exists. (I have not installed the latest version of System Bottoms on my other server and it is working properly.)

I have an issue with I believe the Dynamix-System Buttons plugin. After I updated to the latest release, The Plugin page is now sitting there with the following message: Please wait, retrieving plugin information ... I have attached the Diagnostics file. rose-diagnostics-20150801-1510.zip

Thank you!!! I have been looking for this feature for three years!

I can tell you are almost certainly a long time Windows user! You've a lot to learn about Linux! First thing to learn is Linux is case-sensitive, and by convention prefers lower case, so you don't want to use all caps like you have been. You mentioned PACKAGES and Packages folders, and while you can create those, you absolutely don't want to, as the only one that unRAID uses is packages. You could create all 3 folders, and have them visible simultaneously, but anything you put in the other 2 won't be seen by unRAID. And I'm absolutely sure you did not see .TXZ files in that folder, they had to have been .txz files to be usable. Using all caps is going to create a lot of confusion for yourself. FAQ, unRAID Console section - old but still useful I strongly recommend you spend a little time on the info found in the FAQ, unRAID Console section. I think it will help answer some of your questions, such as the /boot folder. Even in Windows, paths can be different depending on how you map them. You can assign different drive letters and access the same file through a different path. If you were to name your unRAID server MyStuff, then assign a drive letter of U: to the flash drive, then you could access flash root files as \\MyStuff\flash\*.* or as U:\*.* . unRAID maps it as /boot, so you would access the same files on the console as /boot/* . As to the temp monitor, you can blame much of that on the manufacturers, as there hasn't been much call for standardization previously. Tools like SpeedFan on Windows have taken a long time and a lot of code and a built-in database of info in order to analyze and dig temps out of all the mobos out there. The Linux tools are catching up though, and sensors and sensors-detect and the lm-sensor project have been gathering up info to make it easier. The System Temp plugin is a fairly new tool to automate this, and except for a brief hiccup over Perl, has made it a lot smoother than it used to be. (It's almost too bad that you weren't here to see how much harder it used to be!) And I'm quite sure that it's going to be getting even smoother in the near future, great people behind it! The whole business of case can be a real problem area. Please see this Wikipedia article on the subject: https://en.wikipedia.org/wiki/Filename#Letter_case_preservation and https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations Now consider that most of us are using unRAID in mixed environment! And with SMB (usually) thrown into the mix for good measure! The best and only thing to do is to keep all file (and folder/directory) names as unique spellings. Even if you have Linux computer connected to an unRAID server and you are using SMB, you would have to double check all possible situations to see how SMB would actually handle two files named File and file. (As I recall, SMB came from Samba which basically was developed for Linux/UNIX around the Windows Networking scheme that MS developed way back in the Window for Workgroups era. There has been a lot of water under the bridge since that time but I would bet that a computer running Windows for Workgroups would still work over SMB today!)

Perhaps, LimeTech should get the Linux equivalent of make_bootable, include it in the plugin and run it as a part of the upgrade plugin.

I would be connecting up a monitor to your server and having a look. (Don't plug in a PS-2 style keyboard (or mouse) into a powered up Computer, though!!!) You did make a backup of your Flash Drive first... I did make a backup. Was running 5.0.6. My monitor is not getting a signal when I hook it up, which I thought was kinda weird. I guess I will revert back to v5 and see what happens. One Thing, what is the size of your Flash Drive? If it is a small one (1GB or less), it might have ended up 'Full'. You might also want to try to boot up with that updated Flash and the monitor connected, so you can see what is happening. Reason for Edit: Corrected formatting!

I would be connecting up a monitor to your server and having a look. (Don't plug in a PS-2 style keyboard (or mouse) into a powered up Computer, though!!!) You did make a backup of your Flash Drive first...

RobJ, you have undertaken a noble effort but I am afraid that this section will actually cause more problems than it solves. It seems to contain a mix of old and new folders--New ones that are new to (and required by) version 6 and Ones that may have been placed there by either earlier version of unRAID or by the user as they installed plugins. This makes it an extremely confusing read even for someone who is reasonably familiar with what should be there. First thing is that the list needs to reflect exactly which files and folders are required by a version 6 'virgin' install and their location. Second thing, it needs to indicate the files and folders that were placed there by early versions of unRAID. Then there needs to be an comment as to whether this file can be used by version 6. These would be primarily the configuration files that will properly configure the server to 'look and feel' like the old setup. The 'go' file and the 'syslinux.cfg' files should be treated as special cases to indicate that editing of them may be required to implement certain configuration changes. (As a complete aside, I don't believe, there is any explanation in this WIKI about how to edit the syslinux.cfg to change the default boot selection. This section should probably be called something like 'Change Default Boot Option'.) Third thing, there need to be a list of files and folders which might be there that are likely to cause issues with Version 6. Most likely these folders were created either directly by the user or by some plugin that the user installed. This section will have to describe what to do with these files. This may a big problem area as the issue of where to put folders and files was not defined until fairly recently and even then I don't know how many plugin writers observed these recommendations. In any case, that is my two cents... Frank

Perhaps, a suggestion that most users would be advise to use plugins only that are are necessary to the operation and/or maintenance of the basic unRAID OS. That Docker Containers and VM's should be used to provide those services which are ancillary to the basic NAS function. The reason being that the Ancillary services require dependencies that can be conflicting with each other as well as with the base OS. In Docker Containers, everything needed by that container is self-contained and isolated within that container from everything else on the hardware. The same claim can be made for VM's. Updates to one component, whether it is a Docker Container, a VM or unRAID itself, won't break anything else.

No cost. Any previously purchased license will active unRAID ver 6.0.0. with the current privileges for that license version. You must now put the .key file in the /config folder and it must be the only .key file in there! You, of course, have to use the Flash Drive that the .key file is registered with!

Version 6 is now here!!! It took a bit longer than I expected but I think it will be a good release with very few problems if the beta results are any indication. I did update the first post a bit to clarify some things and add a link to RobJ's WIKI.

I'll include it on my proposal to Joe L. Please note that this plugin based on his script, and I don't have control over it's development. The actual place that I found the command line ( grep preclear /var/log/syslog | todos >> /boot/preclear_results.txt ) for getting the preclear report was in the Configuration Tutorial at this section: http://lime-technology.com/wiki/index.php/Configuration_Tutorial#Preclearing_Without_Screen The todos utility is a part of unRAID and it will convert all lf's to lf/cr's. I just went back to my old unRAID v 5.0.6. backup and found that JoeL's script does generate three reports and they have only lf's. Wow, I learned something new today. (I must admit that I haven't read Joe's complete directions for use since I first installed the script a few years ago. I would occasionally check his thread to see if he had a new version and update if there was.)

I had a look at the generated files. My suggestions would be to add the extension .txt onto each file. It just makes it easier to open them from Windows (and probably most other OS's). The second thing is a bit of a quibble. What is everyone's opinion/feelings about line endings? Presently, the files are in the linux format of 'lf'. Should they be in the 'lf/cr' format for the Windows people. I know that the suggested command line for collecting the report using the original command-line script pipes the output through the 'todos' command to change it to the Windows format. I use EditPad lite so it doesn't present that much of an issue for me but I am wondering about which format is preferred when posting to the forum. I precleared the same drive again after the recent update and all went well. I am still having the issue where I have to double click to get things to start and, yet, a single click seems to work at other times. I can not seem to find a pattern as what is causing this behavior. I do want to thank gfjardim for adding the extension to the file names. It will be a big help to those who want to look at the files to make sure that 'nothing weird' is going on with the drive and help the forum gurus who will inevitably be asked to analyze the files uploaded by forum posters to see if their drives is OK. Since I was the only one who who even expressed a (albeit remote) preference for 'lf/cr' format, I assume that most people are OK with the present 'lf' formatting. Gfjardim, thanks again for all your effort, time and hard work on this project!

This file is part of the fast preclear that bjp999 created. But this file is in the root of my flash drive so it must have been copied there when this plugin was installed. What is its intended purpose in the current plugin? (I installed this plugin for the first time a couple of days ago. The last -modified date on the file is 6/12/2015. It was created on 6/11//2015. )

My bad. I totally missed that directory. Again, the need for the help feature. I had a look at the generated files. My suggestions would be to add the extension .txt onto each file. It just makes it easier to open them from Windows (and probably most other OS's). The second thing is a bit of a quibble. What is everyone's opinion/feelings about line endings? Presently, the files are in the linux format of 'lf'. Should they be in the 'lf/cr' format for the Windows people. I know that the suggested command line for collecting the report using the original command-line script pipes the output through the 'todos' command to change it to the Windows format. I use EditPad lite so it doesn't present that much of an issue for me but I am wondering about which format is preferred when posting to the forum.

I preclear a disk overnight and everything went fine. I have a request that you might want to consider implementing. Generate a report after the preclear is finished. (That way, if people have questions about the disk they have just precleared, they will have the information available to post with their query.) I know that there are instructions on how to do this from the command line using the following command: grep preclear /var/log/syslog | todos >> /boot/preclear_results.txt But this partially defeats the reason for the plugin. I also found that you can copy and paste the contents of the popup window into a text editor (copy of that action is attached) but I would think that could be automated also. (Quick comment--- I got a lot of extra lf's at the end of the report when I did it so you should probably strip those out before saving.) Using either method, the resulting text file could be stored in the /boot/config/plugins/preclear.disk folder on the flash drive. I would like to suggest that when you name the file you incorporate the serial number of the disk into it. That way there should not be a problem with overwriting the file of the preclear results of another disk. PreClearReport-JTTL.txt