ljm42

Remove the volume mapping for /config -> /mnt/cache/appdata/crashplan-desktop. that conflicts with --volumes-from CrashPlan

This is a great tip! It reminds me of the techniques Jon used here: https://lime-technology.com/forum/index.php?topic=40777.msg385753 I was previously backing my desktop computer up to a "CrashplanTower" share that was set to use disk1 only. This meant the Crashplan docker kept disk1 and the parity drive spun up the entire time my desktop computer was on. So I changed the CrashplanTower share to be "cache only", and then moved all the standalone files and the most recent subfolder from disk1 to the cache drive. I left all of the older folders on disk1. Now my array stays spun down even when my desktop computer is running a backup! There are two downsides I can think of: 1) If I ever lose my cache drive, I'll probably lose these backups too. But since my desktop is also backing up to the Crashplan cloud, that isn't really a big deal. 2) It looks like Crashplan will create a new directory on the cache drive every few weeks, so I'll need to remember to periodically move older directories to the array to keep my cache drive from filling up.

I agree it does sound like the extended attributes are getting wiped, I am opening the files with MS Word 2010 and then clicking save when I exit the file. I suppose you have mapped the share as a disk under windows, but I am afraid that Windows applications are not aware of extended attributes (read: destroy them) when working this way. Actually, that sounds ideal. Is there any way to get unraid to wipe the attributes whenever the file is modified? Then you wouldn't have to worry about checking file modification times at all.

That sounds incredible! Thanks for this gfjardim!

This could be challenging, since someone may wish to preclear a drive using an USB external enclosure. Good point! That use case should trump mine

Look at this: Would this work for you? Looks great! Especially if it only displays for hard drives (non-mounted) and not for USB card readers and such. Thanks!

I like the way Needo's handles it, although I'd prefer to have Limetech host the helper script. Assuming Plex doesn't object. I really like that it allows you to pass a VERSION environment variable to the container so you know exactly what version you are going to get. The only problem I see is that by default Needo's gives you the latest PlexPass version, it seems like it should default to the latest Public version instead. Perhaps to get the latest PlexPass you should pass in a VERSION=PLEXPASS environment variable? So: * VERSION=PUBLIC (default) - get the latest public version of Plex * VERSION=PLEXPASS - get the latest PlexPass version of Plex * VERSION=0.9.12.4 - get the 0.9.12.4 version of Plex, available versions are listed here: https://plex.tv/downloads/1/archive

1) The spin down feature is incomplete right now, and all drives will spin down after 15 minutes of inactivity. When complete, it will use the system's default spin down interval. 2) No. Preclear requires a separate feature set, and join them will result in a massive increase of complexity. I can add a link in front of the disk serial, if this make things easier... 4) I'll do that, thanks for pointing out. 5) Only one get installed - the most recent one. 1) That sounds great, thanks! 2) Ah, didn't realize that. You did a great job hiding the complexity I think a link to the preclear plugin would be helpful if you can find room for it. 3) Cool to see that the pull request has been accepted, so perhaps an upcoming version of Docker will be able to handle this. Until then mc should work 4) thanks! 5) ok, I'll delete the one from 2014.

Hi gfjardim, This Unassigned Devices plugin is amazing! I do have a couple of questions / requests: 1) Would it be possible to add spin up/spin down icons next to the hard drives in the list of unassigned devices? 2) Have you considered merging your preclear plugin into this plugin? It would be more natural to kick off a preclear from the Unassigned Devices tab than from Settings -> Preclear. 3) When I use Sparkly's Krusader docker, it isn't able to see any content in the /mnt/disks/[xxx] folders. Is there any way to give that docker access to these mount points? 4) I noticed the /var/log/unassigned.devices.log file includes smb passwords. Can that be sanitized? 5) My /flash/config/plugins/unassigned.devices directory includes both of these: * ntfs-3g-2014.2.15-x86_64-1.txz - dated 4/28/15 * ntfs-3g-2015.3.14-x86_64-1.txz - dated 4/18/15 Is that going to cause a conflict? Should I delete one? Thanks!

It seems like this would work... Load your current Crashplan interface and go to Destinations -> Folders to see where your local backups are currently stored. Pass that folder as a new volume to Docker, and then go to that same screen in the Docker version of Crashplan and configure it to use that folder.

oh excellent, can't wait to try it. thanks! edit: this works great!

It's an additional container on my repository. Wow, I'm not sure how I missed this! I want to try it out, but I've been reviewing the code: https://github.com/gfjardim/docker-containers/tree/master/crashplan-desktop and it seems like it stores everything inside the Docker container? Would you considering setting it up a little more like the standard crashplan: https://github.com/gfjardim/docker-containers/blob/master/crashplan/config.sh so we don't have to adopt the account and re-synchronize every time the docker changes?

The container port needs to stay at 8080, but you can change the host port to something else. I used 8081.

This is the first time I've run one of the RDP Dockers, it is awesome! We need this kind of setup for Crashplan Handbrake sure pegs the processor, my CPU fan sounds like it will achieve orbit any minute

Wow, awk is pretty impressive I took a look at this file on my server: plugins/dynamix.system.temp/include/SystemTemp.php And tweaked it slightly to pull data from impitool: ipmitool sdr| awk -F \| 'BEGIN{cpu="-";mb="-";fan="-"}{if(/^CPU Temp/) cpu=$2*1; else if (/^MB Temp/) mb=$2*1; else if (/FRNT_FAN1/) fan=$2*1} END {print cpu,mb,fan}' The only bummer is I don't see a way to redefine FRNT_FAN to "Array Fan" in ipmitool, so I had to hard code FRNT_FAN in the awk command. That could complicate making this into a generic IPMI solution. Also, do you have your stuff in github? I found this, but it is a bit old: https://github.com/bergware/dynamix/tree/master/source/dynamix.system.temp/usr/local/emhttp/plugins/dynamix

Hi bonienl, I installed ipmitool from this thread: http://lime-technology.com/forum/index.php?topic=34557.15 And I was wondering if you would be open to giving your temp/fan plugins the option to use the output from "ipmitool sensor" instead of "sensors"? Here's the output for my board: root@Tower:/boot/packages# ipmitool sensor ATX+5VSB | 4.890 | Volts | ok | 4.050 | 4.260 | 4.500 | 5.490 | 5.760 | 6.030 +3VSB | 3.460 | Volts | ok | 2.660 | 2.800 | 2.960 | 3.620 | 3.800 | 3.980 Vcore | 1.780 | Volts | ok | 1.620 | 1.670 | 1.720 | 1.870 | 1.920 | 1.980 VCCM | 1.500 | Volts | ok | 1.140 | 1.210 | 1.280 | 1.650 | 1.730 | 1.810 +1.05V | 1.070 | Volts | ok | 0.850 | 0.900 | 0.940 | 1.150 | 1.210 | 1.270 CPU VCCIO_OUT | 1.010 | Volts | ok | 0.850 | 0.900 | 0.940 | 1.150 | 1.210 | 1.270 BAT | 3.240 | Volts | ok | 2.500 | 2.640 | 2.780 | 3.400 | 3.540 | 3.680 +3V | 3.380 | Volts | ok | 2.660 | 2.800 | 2.960 | 3.620 | 3.800 | 3.980 +5V | 5.130 | Volts | ok | 4.050 | 4.260 | 4.500 | 5.490 | 5.760 | 6.030 CPU_FAN1 | 2500.000 | RPM | ok | na | na | 300.000 | na | na | na REAR_FAN1 | 800.000 | RPM | ok | na | na | 300.000 | na | na | na FRNT_FAN1 | 1100.000 | RPM | ok | na | na | 300.000 | na | na | na MB Temperature | 47.000 | degrees C | ok | na | na | na | 80.000 | na | na CPU Temperature | 70.000 | degrees C | ok | na | na | na | 91.000 | na | na +12V | 12.000 | Volts | ok | 9.600 | 10.200 | 10.700 | 13.100 | 13.800 | 14.500 "sensors" does not provide any fan info for my board, so ipmi is the only way I can get fan information. Thanks for considering it! edit: "ipmitool sdr" might be easier to parse: root@Tower:/boot/custom# ipmitool sdr ATX+5VSB | 4.89 Volts | ok +3VSB | 3.44 Volts | ok Vcore | 1.79 Volts | ok VCCM | 1.51 Volts | ok +1.05V | 1.07 Volts | ok CPU VCCIO_OUT | 1.01 Volts | ok BAT | 3.26 Volts | ok +3V | 3.38 Volts | ok +5V | 5.13 Volts | ok CPU_FAN1 | 2400 RPM | ok REAR_FAN1 | 800 RPM | ok FRNT_FAN1 | 1100 RPM | ok MB Temperature | 46 degrees C | ok CPU Temperature | 70 degrees C | ok +12V | 12 Volts | ok edit 2: This script could be the basis for parsing the data: https://github.com/phalenor/nagios_plugins/blob/master/check_ipmi_sensors/check_ipmi_sensors.pl

In case anyone is interested, I expanded a bit on gfjardim's sample script and posted it here: https://gist.github.com/ljm42/02b54ce9cc36f992515b Once it is configured, all you have to do is insert a memory card, wait for the beep, and remove the memory card. The script will automatically move/copy files from the USB's DCIM subdirs onto the array, you just need to configure it so it knows what dirs your camera uses and where you want the files to go. If you install jhead as described in the comments, it will also automatically rotate the images according to the exif data, which is my favorite part

Ah, thanks! I saw you started implementing this, nice! So far for me it does a non-error correcting check: /sbin/fsck -n /dev/sdi1 2>&1 not sure how to make it actually fix the errors yet. But I'm not trying to be pushy

This would be great as a plugin, where it could potentially be incorporated into the Disk Health tab in the gui, and send notifications when it detects problems.

Wow gfjardim, this is awesome! The sample script made it pretty easy to figure out how to do what I wanted, although replacing "echo" with "logger" might help people get started faster. The imperial theme song was awesome You were right about the serial number, each card I plugged in to the reader called the same script. I was able to differentiate them using: if [ "${LABEL}" == "EOS DIGITAL" ] etc. The only strange thing I noticed was that the script is named: EOS_DIGITAL.sh it seems like the name should be based on the card reader's serial number rather than the label of the first thing I plugged into it? Would it be possible for the system to detect when a drive needs to have dosfsck run on it? It would be nice to automatically run: dosfsck -av ${DEVICE} if it was needed. Thank you very much for this!

I have not tried using USB devices on unRAID yet, can you explain how this is different from SNAP? One thing I'd like to do is run a script that detects when I plug in a particular microsd card (from my camera), moves the files to a particular location on unraid, then unmounts the card and beeps so I know it is safe to remove it. Would this or SNAP be better starting point for that sort of thing? Thanks!

Having a plugin to install these and keep them current would be great! There are a lot of people who are moving an entire disk's worth of data from one disk to another so they can switch filesystems. These utilities seem to operate around shares, could there be an option (or a third script) to move entire disks? It would be great to tell people to add a plugin and run a simple command to move an entire disk's worth of data around.

Oh dang, you're right. Thanks, it is working now.

Hmm, I was just prompted to update to the 2015.02.03 version of Dynamix System Temperature, and the /Settings/TempSettings page no longer works. The "available drivers" is empty by default, although if I click "Detect" it does display the correct ones (coretemp nct6775). Load / Add to Startup don't seem to do anything, but my go script already contains them, so nothing additional should be needed: modprobe coretemp modprobe nct6775 /usr/bin/sensors -s All of the dropdowns on the page are disabled, and nothing I do allows me to select anything: <select name="cpu_temp" disabled> I made the mistake of hitting "Apply" and all of the values changed to "not used" when the page reloaded, and the temperatures disappeared from the footer. The dropdowns are still disabled, although when I view the source of the page the correct values are listed, I just can't choose them: <select name="cpu_temp" disabled> <option>Not used</option> <option value='coretemp-isa-0000|temp1|CPU Temp' >coretemp - Physical id 0 - 37.0 °C</option> <option value='coretemp-isa-0000|temp2|CPU Temp' >coretemp - Core 0 - 37.0 °C</option> <option value='coretemp-isa-0000|temp3|CPU Temp' >coretemp - Core 1 - 34.0 °C</option> <option value='coretemp-isa-0000|temp4|CPU Temp' >coretemp - Core 2 - 33.0 °C</option> <option value='coretemp-isa-0000|temp5|CPU Temp' >coretemp - Core 3 - 36.0 °C</option> <option value='nct6776-isa-0290|temp1|CPU Temp' >nct6776 - SYSTIN - 35.0 °C</option> <option value='nct6776-isa-0290|temp2|CPU Temp' >nct6776 - CPUTIN - 37.0 °C</option> <option value='nct6776-isa-0290|temp3|CPU Temp' >nct6776 - AUXTIN - 26.0 °C</option> </select> Hopefully that is enough information to help figure out what happened?

Thanks! I was easily able to remove the fan speed from the footer using the new checkboxes. Works perfectly Thank you very much bonienl!