GHunter

Paste your code into a text editor like Notepad++ or EditPad Lite and double check it. There is something extra in there when you copy and paste. Also, convert to UNIX/Linux Line Feed instead of Windows Carriage Return. This is a common problem when copying and pasting Linux scripts using Windows PC's.

Check out this thread.

Figured it was a CA problem. Thanks, I'll post there then.

Well, no luck there. Thanks anyways.

Thanks for the suggestion. I use Windows Defender. No other virus protection or adblockers. I can try disabling it to see if that is the cause.

I installed CA yesterday and tried to install a few docker containers. After clicking the install button to install a docker container, the page was blank. I tried a few other times with the same result and nothing installed. I tried uninstalling CA, reinstalling CA, rebooting the server and always had the same result. This shows up in my syslog when trying to install a docker: Apr 10 19:23:22 FileSvr root: error: /Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/linuxserversRepository/duckdns.xml: missing csrf_token CA installs plugins fine as I tried that with FCP and ran that to see if I had any errors. Nothing was found except a few minor warnings. I made sure that no other windows or apps were connected to unRAID as I know that can cause problems with csrf tokens. One other note is that i tired with 3 different browsers, Firefox, Edge, and Chrome. Anyways, here are my diags. Thanks for the help. filesvr-diagnostics-20180411-0512.zip

Thanks for updating this. I installed it yesterday and it works great.

You could simply bookmark http://tower/Dashboard I'd love this as well. The Dashboard page seems more appropriate as the Home page in my opinion. I've been using the bookmark suggested above now for ages.

I'd certainly take advantage of this feature if it were implemented!

Another approach to providing status details for yellow or red disks could be to have a "Status Details" tab on the "Main" page. Then the hover popup could be kept the way it is. On the "Status Details" tab you could list only the problem drives that might need attention with details for each one and maybe troubleshooting info. It's pretty common for users to ask questions when problems arise without providing any more info. Providing this info for troubleshooting on the "Status Details" page could help with that, like suggesting a syslog and smartdrive report for a red ball drive. Gary

I think this should be simplified. Rather than trying to come up with a color / shape / blink icon for each possible state, stick with 3 icons. Then in the hover over popup box, explain the state in text. I think it was mentioned earlier, all the user is concerned about are 3 states: Green: everything is ok Yellow: warning that something the user should know about Red: critical problem that needs some attention Choose a different shape for green, yellow, and red to make it easier for colorblind people to differentiate between them. If you want to add a blinking icon for them (besides the solid icon), that gives you 6 states. But the hover over text would provide the details of each state that the drive / array is in. The less is more approach is better here in my opinion. Provide details in the hover over popup. Also, I'm not a fan of the separate spinup / spindown icon either. I'd prefer a onclick dropdown like you use on the VM page or a link in the popup if that's possible. I'm just voicing my opinion here but I do feel for those that can't see the icons clearly whether that is due to being colorblind or old age like me . 16 x 16 is kind of small! Gary

I did it through a telnet session and used screen just in case I lost my telnet connection. If you have a monitor and keyboard attached directly to your unRaid server, screen isn't needed. There is info on using screen in the wiki here: http://lime-technology.com/wiki/index.php/Configuration_Tutorial#Install_Screen_without_using_UnMENU Yes, in that example code, I was moving files from disk6 to disk5. Gary

I just finished converting 9 data drives from RFS to XFS. I save 1.5 to 2.5GB on every disk. Most disks were media files but 2 of them had hundreds of thousands of small files. I think the space savings is just due to file system differences. Data transfer to and from the array is much more consistent now. The transfer rate is probably the same though but the consistency makes it seem a faster. I'm glad I took the time to do this as it was worth it. A near full 3TB drive (50GB free) took about 19 hours. This was pretty consistent too. I used this rsync method: rsync -av --progress --remove-source-files /mnt/disk6/ /mnt/disk5/ Thanks to everyone who helped with their ideas on this conversion. Gary

I did and think it is a nice enhancement! Really looks good and hope that it is easy for other plugin authors to implement. Thanks for the updates to these awesome plugins! Gary

I found a newer version of sensors-detect which found my super I/O chip correctly where the version in unRAID didn't. It might help those of you using the System Temp plugin on newer motherboards / chipsets. I just downloaded the file to my flash drive saving it as SD.sh and then ran it. You might have to set permissions to make it executable but I didn't. Here is a link to the lm-sensors page where the link can be found. http://www.lm-sensors.org/wiki/Devices. I'm going to post this in the system temp plugin thread too. Gary

I found a newer version of sensors-detect which found my super I/O chip correctly where the version in unRAID didn't. It might help those of you using the System Temp plugin on newer motherboards / chipsets. I just downloaded the file to my flash drive saving it as SD.sh and then ran it. You might have to set permissions to make it executable but I didn't. Here is a link to the lm-sensors page where the link can be found. http://www.lm-sensors.org/wiki/Devices. I'm going to post this in the system temp plugin thread too. Gary

JustinChase, I pretty much have the same board as you and get the same results from sensors-detect so you can use my sensors.conf file above below too. Here is my /boot/config/sensors.conf file: # sensor configuration chip "coretemp-isa-0000" label temp1 "MB Temp" label temp2 "CPU Temp" Don't forget to add modprobe coretemp in your go file. Gary

eroz, try this for your sensors.conf file and save on your flash drive. Since you are returning results from sensors -u coretemp-isa-0000, I am pretty sure it will work. /boot/config/sensors.conf # sensor configuration chip "coretemp-isa-0000" label temp1 "MB Temp" label temp2 "CPU Temp" Don't forget to add modprobe coretemp in your go file. Hope that helps, Gary

Check out the Wiki for information on setting up CPU and board temperature sensing here: http://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing You'll want to save your sensors.conf file to your flash drive here: /boot/config/sensors.conf Gary

Bonienl, Thanks for all your hard work on these plugins and the Dynamix integration into unRAID! This really looks great! Gary

Interesting! I had no idea that this had been changed. I'm not sure of the impact. I haven't played with the 6.0 beta yet, and never will as all I have is a production server. I might do a 6.0 release candidate, but will probably wait until final. -Paul Here is what I have found when using it with unRAID 6b10a. The script seems to work just fine. The disk settings only have md_num_stripes and md_sync_window as available options to change. In the disk.cfg file on your flash drive, there is still an md_write_limit value and it's default is 768. Changing the 2 available options seems to have no effect on the md_write_limit as it still has a value of 768, even if I choose really high values for md_num_stripes and md_sync_window. If you upgraded from unRAID v5 and had used custom values like I did, those values are retained in the upgrade to unRAID v6. However, changing the values in the webGUI will reset the md_write_limit back to it's default value of 768. Also, the default values for all 3 of these settings in v6 are still the same as they were in v5. There does seem to be a difference in the values for unRAID v5 vs. v6 so if you are running the v6 beta, I would use the script to re-calculate better values for unRAID v6. Gary