AndroidCat

Thank you Sir.

You have to provide hostname which can be resolved to IP address. Resolution can happen e.g in your home router. In other words Observium only accepts hostnames.

Great work! Very useful application. Do you know why Tonido docker ignores (or maybe any docker in general) read-only volume mapping? In my case /unRAID <-> /mnt/disks/ is mapped as :ro but I can still delete/write files there from within Tonido. I checked how the docker gets invoked and it indeed uses :ro following what had been configured in "Volume Mappings" Does it somehow ignores read-only statement because /mnt/disks contains samba mountpoints? ls -al /mnt/disks total 8 drwxrwxrwx 6 root root 120 Jul 6 19:12 ./ drwxr-xr-x 14 root root 280 Jul 6 19:12 ../ drwxrwxrwx 3 root root 4096 Dec 31 1969 BOOTUNRAID/ drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_unraid/ drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_video/ drwxrwxrwx 1 root root 4096 Jun 16 14:28 wd2t/ docker exec -it Tonido bash root@423b4d2af636:/# ls -al /unRAID/ total 8 drwxrwxrwx 6 root root 120 Jul 6 19:12 . drwxrwxrwx 1 root root 198 Jul 6 20:08 .. drwxrwxrwx 3 root root 4096 Dec 31 1969 BOOTUNRAID drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_unraid drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_video drwxrwxrwx 1 root root 4096 Jun 16 14:28 wd2t /usr/bin/docker run -d --name="Tonido" --net="bridge" -e TZ="America/Chicago" -p 10001:10001/tcp -v "/mnt/user/appdata/tonido":"/config":rw -v "/mnt/disks/":"/unRAID":ro captinsano/tonido

I second RobJ, some kind of two-stage approach would be beneficial. Probably 1st threshold to try to spin down and 2nd to unconditionally shut down.

Latest update (2015.06.15a) broke my export of USB drive to NFS. It is independent if I check or not 'run script in background'. And manual unmount followed by mount properly exports NFS i.e. script is executed. Tue Jun 16 0:10:34 CDT 2015: Drive found with the following attributes: serial='WD_Elements_10B8_575841314131353253354850-0:0', serial_short='575841314131353253354850', device='/dev/sdk1', part='1', label='Elements', fstype='ntfs', target='', size='2000364240896', used='0', avail='2000364240896', mountpoint='/mnt/disks/wd2t', owner='user', automount='1', shared='1', command='/boot/config/plugins/unassigned.devices/wd2t.sh', command_bg='false' Tue Jun 16 0:10:34 CDT 2015: Adding disk ... Tue Jun 16 0:10:34 CDT 2015: Mounting drive with command: mount -t ntfs -o auto,async,nodev,nosuid,umask=000 '/dev/sdk1' '/mnt/disks/wd2t' Tue Jun 16 0:10:43 CDT 2015: Successfully mounted '/dev/sdk1' on '/mnt/disks/wd2t' Tue Jun 16 0:10:43 CDT 2015: Defining share 'wd2t' on file '/etc/samba/unassigned-shares/wd2t.conf' . Tue Jun 16 0:10:43 CDT 2015: Adding share wd2t to /boot/config/smb-extra.conf Tue Jun 16 0:10:43 CDT 2015: Reloading Samba configuration. Tue Jun 16 0:10:43 CDT 2015: Directory '/mnt/disks/wd2t' shared successfully. Tue Jun 16 0:10:43 CDT 2015: Running command '/boot/config/plugins/unassigned.devices/wd2t.sh' with action 'ADD'. Tue Jun 16 0:10:43 CDT 2015: Disk Elements shared successfully. cat /tmp/WD_Elements_10B8_575841314131353253354850-0\:0.log exporting *:/mnt/disks/wd2t In case you can't figure it out can I revert to the previous code?

Just for reference, that seems to be a good case: Fri Jun 12 12:49:35 CDT 2015: Drive found with the following attributes: serial='WD_Elements_10B8_575841314131353253354850-0:0', serial_short='575841314131353253354850', device='/dev/sdg1', part='1', label='Elements', fstype='ntfs', target='', size='2000364240896', used='0', avail='2000364240896', mountpoint='/mnt/disks/wd2t', owner='user', automount='1', shared='1' Fri Jun 12 12:49:35 CDT 2015: Adding disk ... Fri Jun 12 12:49:35 CDT 2015: Mounting drive with command: mount -t ntfs -o auto,async,nodev,nosuid,umask=000 '/dev/sdg1' '/mnt/disks/wd2t' Fri Jun 12 12:49:44 CDT 2015: Successfully mounted '/dev/sdg1' on '/mnt/disks/wd2t' Fri Jun 12 12:49:44 CDT 2015: Defining share 'wd2t' on file '/etc/samba/unassigned-shares/wd2t.conf' . Fri Jun 12 12:49:44 CDT 2015: Adding share wd2t to /boot/config/smb-extra.conf Fri Jun 12 12:49:44 CDT 2015: Reloading Samba configuration. Fri Jun 12 12:49:44 CDT 2015: Directory '/mnt/disks/wd2t' shared successfully. Fri Jun 12 12:49:44 CDT 2015: Running command '/boot/config/plugins/unassigned.devices/wd2t.sh' with action 'ADD'. Fri Jun 12 12:49:44 CDT 2015: Disk Elements shared successfully

The plugin has been working very well, I managed to preclear more than 10 disks with it - no problems so far. Only cosmetic issue is that upon completion it displays "Preclear Successful^n Total TIme xxx^n ...etc". Basically there is an extra "^n" after each string. This has been happening on recent Chrome versions each time. Thanks for the plugin!

Happy to report that with latest update (.11a) your plugin executes my script to export a share under NFS. Thanks.

I have a sata drive formatted xfs that mounts and unmounts and initiates the script properly. I have a USB formatted ntfs that is mounting, but the script is not initiated. So it appears that something is not working in RC5. I'm on rc3 and it seems my script is not executed upon boot. I have to manually unmount and mount it again to get my script executed (script is related to exporting USB drive under NFS). I described my problem couple of posts back, but it seems your problem may be similar.

I added something like that (quick and dirty) as a script. It works when USB disk is mounted/unmounted manually from GUI. But it doesn't work when unRAID is restarted. It is not executed looking at /etc/exports contents. case $ACTION in 'ADD' ) // do your stuff here echo '"/mnt/disks/wd2t" -async,no_subtree_check,fsid=150 *(rw,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports exportfs -rav ;; 'REMOVE' ) sed '/wd2t/d' /etc/exports > /tmp/exp cp -f /tmp/exp /etc/exports exportfs -rav ;; esac

Excellent plugin! Could you please also enable NFS sharing or provide script to mount/umount the device?

Thanks for the update. Is the warning something to worry about? May 9 19:23:24 unraid emhttp: /usr/local/sbin/plugin install http://unraid.zeron.ca/plugins/open-vm-tools/openVMTools.plg 2>&1 May 9 19:23:24 unraid logger: plugin: skipping: /boot/packages/open_vm_tools-9.10.0.2476743_unRaid6.0beta15-x86_64-3Zeron.tgz already exists May 9 19:23:24 unraid logger: plugin: running: /boot/packages/open_vm_tools-9.10.0.2476743_unRaid6.0beta15-x86_64-3Zeron.tgz May 9 19:23:26 unraid kernel: vmw_vmci 0000:00:07.7: Found VMCI PCI device at 0x11080, irq 16 May 9 19:23:26 unraid kernel: vmw_vmci 0000:00:07.7: Using capabilities 0xc May 9 19:23:26 unraid kernel: Guest personality initialized and is active May 9 19:23:26 unraid kernel: VMCI host device registered (name=vmci, major=10, minor=57) May 9 19:23:26 unraid kernel: Initialized host personality May 9 19:23:26 unraid vmsvc[8416]: [ warning] [vmtoolsd] Opening plugin 'libdeployPkgPlugin.so' failed: libDeployPkg.so.0: cannot open shared object file: No such file or directory. May 9 19:23:26 unraid kernel: NET: Registered protocol family 40

Yes, IPMI version only for those who have server-grade boards equipped with it. If you want to tackle it in the future, just let me know, I can easily test your code. I believe the user base is quite big and growing as more and more go with Supermicro boards and ESXi. I'm curious whether lm-sensors work in KVM/XEN unRAID (if the VM has access to the MB chip)? Anyway, thanks for your efforts!

ogi-> As stated before that only works on bare-metal X9SCM-F. I just compiled freeIPMI package on separate Slackware VM and it works. I can only hope bonienl would be interested in adding that option to his plugin. That would require adding freeIPMI package and then parsing its output //see attachment//.

Anyone found a way to use lm-sensors on X9SCM-F but with unRAID running under ESXi? In that case modprobe w83627ehf complains 'no such device found'. Apparently such devices are not passed-through to a VM. I tried with other modules, but they do not work either. Maybe the only way is to read system temp via IPMI linux tools? Edit: I found this: http://www.thomas-krenn.com/en/wiki/Supermicro_X9SCM-F_Motherboard We would require FreeIPMI package then and modified/alternative version of System Temp plugin for IPMI.

Thanks guys! IDE disk works! Have a test server now

//You only need the one disk not two. It's volume label should be UNRAID. All files, including 'config' dir, should be on that one disk. //As long as the volume label is UNRAID there won't be any complaints from the system. Hmm,this doesn't work for me (5.0rc11). I tried a few times, volume inside virtual disk is surely called UNRAID. I use "hybrid solution" for production unRAID BTW and that works great.

Did I understand your advice correctly? -created new unRAID VM with two virtual disks: first 4GB labeled whatever containing all *.zip contents except for 'config' directory 2nd 1GB labeled UNRAID containing just 'config' dir both disks formatted as FAT32 and first one made bootable from windows by running .bat file unRAID boots from disk1, but at some point complains that UNRAID disk can't be located: "waiing for /dev/disk/by-label/UNRAID" It also didn't work when I had one virtual disk called UNRAID with all the files and dirs from *.zip. I got something wrong

Is it at all possible to set up an unRAID VM without having physical USB stick (or emulate such)? I'd like to set up another test VM with minimal unRAID version (which doesn't require a licence tied to USB drive). I'm under the impression that unRAID expects USB to be there as its config files are stored on USB itself. Any workaround for this? At least we know bzroot and bzimage can be a part of VM. Thanks.