Helmonder

MC works fine, even with my mouse.. But it all depends on the terminal emulation program you use.. On Windows most use putty which is great.. But actually, krusader wil give you more then that.. So just do that. MC will not bring anything to play that you cannot use with KRusader and that will always work..

That is not correct..

If all the hardware is melted there is nothing to restore.. Your data is what you should backup If you area allready doing that then just install the Community Applications plugin and backup your dockers and VM's from there..

Personally, I would get rid of the redirect to /boot/logs/scrub_cache.log. That way user scripts can display the logs. But, the output is not persistent and will be lost over reboots. I allready took ik out on my side for the same reason.. :-)

The following will do a btrfs scrub and report back the results through the notification interface, I have scheduled this monthly: /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Scrub of cache drive started" -i "normal" -m "Scrubbing message" btrfs scrub start -rdB /mnt/cache > /boot/logs/scrub_cache.log if [ $? -eq 0 ] then /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Scrub of cache drive finished" -i "normal" -m /boot/logs/scrub_cache.log else /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Error in scrub of cache drive !" -i "alert" -m /boot/logs/scrub_cache.log fi The following does an hourly check on Out of Memory errors in the syslog, I scheduled this hourly: if grep -q "Out of memory" /var/log/syslog; then /usr/local/emhttp/plugins/dynamix/scripts/notify -e "OOM Checker" -s "Checked for OOM in syslog" -d "OOM error found in syslog" -i "alert" fi

Found a possible solution... Using the exitcodes.. I am now testing the following: /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Scrub of cache drive started" -i "normal" -m "Scrubbing message" btrfs scrub start -rdB /mnt/cache > /boot/logs/scrub_cache.log if [ $? -eq 0 ] then /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Scrub of cache drive finished" -i "normal" -m /boot/logs/scrub_cache.log else /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Error in scrub of cache drive !" -i "alert" -m /boot/logs/scrub_cache.log fi

Tested it and it works.. Now what I would need is an example of the btrfs output so I can tailer the notification.. I now did that bases on the text "error" and that failed since the positive outcome tells us there are "0 errrors"..

Mmm.. was testing with this yesterday and the scrub status looks weird... I have a few preclears running so cannot reset the system at this time.

If you don't redirect the output, user scripts will be able to display the output from the script (ie: log) with a simple button press Search for "scripts/notify" for examples of using the notifications. There are lots. /usr/local/emhttp/plugins/dynamix/scripts/notify will bring up all the options available. Woo.. that is really nicely done.. I wasn't aware the notification system was so easy to use... I am now testing with the following setup: I am now actually trying to get some finished logfiles so I can see the structure of what is comming back.. With some grep's I think I will be able to assess a possible error condition and change the color of the notification based on that... Should not be very difficult I think.. Without actually trying the following should work I guess: /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Scrub of cache drive started" -i "normal" -m "Scrubbing message" btrfs scrub start -rdB /mnt/cache > /boot/logs/scrub_cache.log if grep -q error /boot/logs/scrub_cache.log; then /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Error in scrub of cache drive !" -i "alert" -m /boot/logs/scrub_cache.log fi /usr/local/emhttp/plugins/dynamix/scripts/notify -e "start_scrub_cache" -s "Scrub cache drive" -d "Scrub of cache drive finished" -i "normal" -m /boot/logs/scrub_cache.log

Github is back, I installed trim (which is a gread addon, I missed that one). I also installed user scripts and have created a very crude little script to do a btrfs scrub of the cache drive: btrfs scrub start -rdB /mnt/cache > /boot/logs/scrub_cache.log When this is run in the background it works.. It is kind of crude in the sense that the fact that logfile is written does not mean that I will see it... Anyone any idea what I could look at to make this thing use the web browser notification system to report starting and finishing the scrub ?

Mmm... major service outage for github in western europe.. i'll try later.

Trim added is actually a good thought.. I will add that.. My whole array is setup of btrfs drives so scheduled scrub would be nice, I will check out your suggestion !

I've got parity, mover and fixed schedules in there.. Where should I find the btrfs scrub ?

+1

Same here (though with spotify). Itunes music librarys and syncing was a major pain.. Love apple.. hate itunes..

The parity drive needs to be at least as large as your largest data drive. Your data drives are 3TB so your parity should be at least 3 TB. Know that when you add a new drive in the future you cannot use a drive larger then your parity drive. So lets say you want to expand your array in the future and you want to add a 6TB data drive, then you would need to add 2 6TB drives, one for parity and one for data. Your current parity drive you can then reuse as a data drive. As far as 1 or 2 parity drives is concerned, that is up to you. With one parity drive one disk can fail and you loose nothing. With two parity drives you can loose two.

It would be nice if there were a plugin of some sort that would give an insight in storage growth. It could take a sample on a daily basis of: - Used storage per disk - Used storage per share - Used storage in total This could then be reported in a graph and preferably extrapolated based on the trend seen, therefor telling us when a system needs expansion..

For the benefit of the rest: 1) log into your unraid server 2) log into the crashplan docker: docker exec -it CrashPlan bash 3) go to /etc/my_init.d 4) vi 01_config.sh ${TCP_PORT_4242} on line 46 needs to be replaced with ${SERVICE_PORT} ${TCP_PORT_4243} on line 47 needs to be replaced with ${BACKUP_PORT} And indeed, then it works ! Just restart the docker

On the unraid server that its crashplan is now reporting a 0.0.0.0 address as local address (see above) I also have a win10 vm running with crashplan installed, it also shows a 0.0.0.0 address for the local IP... This crashplan version is ofcourse not a docker version but a windows version.. I therefor think that it is -not- the docker itself causing the issue.. That would mean it is either crashplan itself (but we should expect a lot to be google-able on that if crashplan itself would be borked, so i do not think that is it). Or there is some relation with the docker engine running on unraid. I have been having backup troubles for approx. 2 days which is about the same time unraid 6.2.1 is out..

I also notice that one of my two crashplans reports no internal ip address.. Weird thing is that they are both running the same unraid and same crashplan version.. Ofcourse both unraid webgui's are perfectly reachable on their respective internal addresses.. Hope this gets fixed soon.. I am missing my backups..

this is working fine for me..

do you not get in a fight with apple over this ?

Its also not working for me anymore... crashplan clients cannot connect anymore.. not only windows.. my main crashplan server can also not connect to the backupserver.. both running crashplan, on 6.2, same docker version..

I understand the point, but there are a couple of reasons why I'm holding back on this. - It wouldn't be any easier to set up than it is to set up OpenVPN and peter_sm has two OpenVPN plugins to make it as easy as possible. - I don't consider myself a security expert. Even OpenVPN (which is made by people definitely more knowledgeable than me in these matters) has security advisories as recent as Sep 12th. Which leads me to the last reason I'd like to bring up and it's a matter of liability. - Let's say this gets done and users can access their server over the internet, but then someone exploits a bug/flaw in the plugin (which would be required to make this work), a server is compromised and maybe there's data loss. I really don't want to be involved in such a scenario. To be honest, security is not an easy matter Personally I use pushbullet for push notifications towards my smartphone, that way if anything bad happens pushbullet notifies me, I then log in to the system using vpn... Works fine..

I am amazed by this tool.. It is extremely usefull.and seems to incorporate everything I need on the go.. Really nice !