dlandon

In several earlier posts, I reported some issues I was seeing with errors in the log. After updating to the newest version, I am not seeing any issues at all.

I have a USB Disk that I back up some of my unraid files to for off-site storage. What I do is plug in the USB Drive and walk away until the backup is complete. I then want to just remove the USB Drive when the backup is complete. I don't want to have to go to the webgui to unmount the drive. This is my script: #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # AVAIL : available space # USED : used space # SIZE : partition size # SERIAL : disk serial number # ACTION : if mounting, ADD; if unmounting, REMOVE # MOUNTPOINT : where the partition is mounted # FSTYPE : partition filesystem # LABEL : partition label # DEVICE : partition device, e.g /dev/sda1 # OWNER : "udev" if executed by UDEV, otherwise "user" case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 sleep 2 if [ $OWNER = "udev" ] then LOGFILE=/var/log/WeeklyBackups PROG_NAME=WeeklyBackup beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 // Doing my stuff logger Synching... -t$PROG_NAME sync beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 beep -r 5 -l 100 -f 2000 sleep 2 /usr/local/sbin/unassigned_umount $DEVICE fi ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; esac The idea is that the device is unmounted after the work is complete. I had to insert the "sync" before the unmount to be sure all writes to the disk are completed before unmounting the disk or I would get some errors. Should the "sync" be part of the built in unmount procedure to prevent problems by unmounting too soon after writing?

My USB disk formatted NTFS will mount but not execute the script. Please PM me your /var/log/unassigned.devices.log file. The log shows that everything worked as it should. Let me work with it some more. I think I just found a script error. I hadn't tried this drive script until the latest version. I had another USB disk that I worked with on RC5 and it worked fine. EDIT: OK. Subtle script problem kept the script from running.

My USB disk formatted NTFS will mount but not execute the script.

This is the serial ID, the same unRAID uses to identify the disks. You can set different mount points if you want. How do you set a different mount point? look at OP on the Video Thank you. That was pretty obvious.

This is the serial ID, the same unRAID uses to identify the disks. You can set different mount points if you want. How do you set a different mount point?

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 also getting this in the middle of running a backup script. Jun 7 14:49:41 MediaServer udevd[18542]: timeout: killing '/usr/local/sbin/unassigned_mount' [18558] Jun 7 14:49:41 MediaServer udevd[18542]: '/usr/local/sbin/unassigned_mount' [18558] terminated by signal 9 (Killed) The backup seems to run fine, I just get these log entries. I'm not sure if this is a problem or not. EDIT: I've found a few more issues. When I have a USB drive set to not auto mount and plug it in and then unplug it I get the following: Jun 7 15:29:11 MediaServer kernel: usb 1-5: new high-speed USB device number 21 using xhci_hcd Jun 7 15:29:11 MediaServer kernel: usb-storage 1-5:1.0: USB Mass Storage device detected Jun 7 15:29:11 MediaServer kernel: usb-storage 1-5:1.0: Quirks match for vid 1058 pid 070a: 200000 Jun 7 15:29:11 MediaServer kernel: scsi host24: usb-storage 1-5:1.0 Jun 7 15:29:12 MediaServer kernel: scsi 24:0:0:0: Direct-Access WD My Passport 070A 2018 PQ: 0 ANSI: 4 Jun 7 15:29:12 MediaServer kernel: sd 24:0:0:0: Attached scsi generic sg11 type 0 Jun 7 15:29:12 MediaServer kernel: sd 24:0:0:0: [sdm] 1952151552 512-byte logical blocks: (999 GB/930 GiB) Jun 7 15:29:12 MediaServer kernel: scsi 24:0:0:1: Enclosure WD SES Device 2018 PQ: 0 ANSI: 4 Jun 7 15:29:12 MediaServer kernel: sd 24:0:0:0: [sdm] Write Protect is off Jun 7 15:29:12 MediaServer kernel: sd 24:0:0:0: [sdm] Mode Sense: 2b 00 10 08 Jun 7 15:29:12 MediaServer kernel: sd 24:0:0:0: [sdm] No Caching mode page found Jun 7 15:29:12 MediaServer kernel: sd 24:0:0:0: [sdm] Assuming drive cache: write back Jun 7 15:29:12 MediaServer kernel: scsi 24:0:0:1: Attached scsi generic sg12 type 13 Jun 7 15:29:13 MediaServer kernel: sdm: sdm1 Jun 7 15:29:13 MediaServer kernel: sd 24:0:0:0: [sdm] Attached SCSI disk Jun 7 15:29:29 MediaServer kernel: usb 1-5: USB disconnect, device number 21 Jun 7 15:29:29 MediaServer kernel: sd 24:0:0:0: [sdm] Synchronizing SCSI cache Jun 7 15:29:29 MediaServer kernel: sd 24:0:0:0: [sdm] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 When I mount and unmount it from the webgui I get the following: Jun 7 15:33:13 MediaServer kernel: usb 1-5: new high-speed USB device number 22 using xhci_hcd Jun 7 15:33:13 MediaServer kernel: usb-storage 1-5:1.0: USB Mass Storage device detected Jun 7 15:33:13 MediaServer kernel: usb-storage 1-5:1.0: Quirks match for vid 1058 pid 070a: 200000 Jun 7 15:33:13 MediaServer kernel: scsi host25: usb-storage 1-5:1.0 Jun 7 15:33:14 MediaServer kernel: scsi 25:0:0:0: Direct-Access WD My Passport 070A 2018 PQ: 0 ANSI: 4 Jun 7 15:33:14 MediaServer kernel: sd 25:0:0:0: Attached scsi generic sg11 type 0 Jun 7 15:33:14 MediaServer kernel: scsi 25:0:0:1: Enclosure WD SES Device 2018 PQ: 0 ANSI: 4 Jun 7 15:33:14 MediaServer kernel: sd 25:0:0:0: [sdm] 1952151552 512-byte logical blocks: (999 GB/930 GiB) Jun 7 15:33:14 MediaServer kernel: sd 25:0:0:0: [sdm] Write Protect is off Jun 7 15:33:14 MediaServer kernel: sd 25:0:0:0: [sdm] Mode Sense: 2b 00 10 08 Jun 7 15:33:14 MediaServer kernel: sd 25:0:0:0: [sdm] No Caching mode page found Jun 7 15:33:14 MediaServer kernel: sd 25:0:0:0: [sdm] Assuming drive cache: write back Jun 7 15:33:14 MediaServer kernel: scsi 25:0:0:1: Attached scsi generic sg12 type 13 Jun 7 15:33:14 MediaServer kernel: sdm: sdm1 Jun 7 15:33:14 MediaServer kernel: sd 25:0:0:0: [sdm] Attached SCSI disk Jun 7 15:33:26 MediaServer emhttp: sendOutput: write Jun 7 15:33:52 MediaServer emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Jun 7 15:34:11 MediaServer php: /usr/local/sbin/unassigned_mount /dev/sdm Jun 7 15:34:12 MediaServer ntfs-3g[17885]: Version 2015.3.14 integrated FUSE 27 Jun 7 15:34:12 MediaServer ntfs-3g[17885]: Mounted /dev/sdm1 (Read-Write, label "WeeklyBackups", NTFS 3.1) Jun 7 15:34:12 MediaServer ntfs-3g[17885]: Cmdline options: rw,nosuid,nodev,umask=000 Jun 7 15:34:12 MediaServer ntfs-3g[17885]: Mount options: rw,nosuid,nodev,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdm1,blkdev,blksize=4096 Jun 7 15:34:12 MediaServer ntfs-3g[17885]: Global ownership and permissions enforced, configuration type 1 Jun 7 15:34:17 MediaServer emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Jun 7 15:34:24 MediaServer php: /usr/local/sbin/unassigned_umount /dev/sdm Jun 7 15:34:24 MediaServer ntfs-3g[17885]: Unmounting /dev/sdm1 (WeeklyBackups) Jun 7 15:34:24 MediaServer php: Jun 7 15:34:24 MediaServer php: Warning: rmdir(/mnt/disks/WeeklyBackups): Device or resource busy in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 205 Notning was done but mount and unmount. The device shows as busy. I'm not a php expert but I believe this function is not right: function do_unmount($dev, $dir) { if (is_mounted($dev) != 0){ debug("Unmounting ${dev}..."); $o = shell_exec("umount '${dev}' 2>&1"); for ($i=0; $i < 10; $i++) { if (! is_mounted($dev)){ if (is_dir($dir)) rmdir($dir); debug("Successfully unmounted '$dev'"); return TRUE; } else { sleep(0.5);} } debug("Unmount of ${dev} failed. Error message: $o"); return FALSE; } } It looks like you want to walk through all the partitions to unmount them ($i). I don't see where that is happening.

I have converted from SNAP to the unassigned devices plugin. I managed to get the beeps working like I want. I have a few suggestions: - When editing a drive script and "Done" is clicked, return to the "Unassigned Devices" tab and not the "Array Devices" tab. - When a drive is "Unmounted" from the webpage and the drive can't be unmounted because it is busy, bring up a message to indicate that, or show a "busy" indicator on the webpage, or better yet disable (grey out) the "Unmount" button until the drive is no longer busy. It is logged, but is a bit confusing when "Unmount" is clicked and it returns showing "Unmount" again. Other than that, the plugin works quite well and is more in line with the V6 Dynamix layout than SNAP.

Is there a way to add an event to a USB device just being plugged in and removed? The idea is similar to what Windows does. A sound is made when a device is plugged in or removed. I use the following in my SNAP notify configuration. Plugged in: beep -l 200 -f 600 -n -l 200 -f 800 Removed: beep -l 200 -f 800 -n -l 200 -f 600 This lets me know that the device was recognized when plugged in and that the script should start shortly. I make another sound when the script starts and stops so I can tell when it has started and stopped. This is nice because I can just plug a device into the server and listen for the sounds to know when the device is plugged in and the script completed.

I did a little testing and found the same issue. This plugin should probably run the script in the background so the webpage will come back and not get "stuck" while the script is running. Eventually I will replace SNAP with this plugin, but it has a little ways to go yet. This is one of the issues.

I have three VMs running off one 512GB SSD. They are noted in my signature. I don't see any performance issues with any of them.

there is that, i don't use the thing so i couldn't really say. personally i'd just pass the whole folder and have done with it, but that's just me. It's not quite that simple. ownCloud has many apps built that are pre-loaded in the apps directory. User apps are added to that directory for additional functionality. Both directories would have to combine to work properly. When I load ownCloud, I just get into the docker with a cli and copy the apps from the appdata/owncloud directory and I'm good to go. This only occurs when I update or make xml changes to the docker image.

I use eMCient email client software that uses caldav and carddav to also connect to the ownCloud calendar and contacts. Any application that can do caldav and carddav interface can connect to ownCloud. I know there is more capability that I'm not using. ownCloud is pretty awesome. If you haven't done it yet, be sure to use MySql and not the default SQL database. I installed the MariaDB Docker (MySQL compatible) and use that for the database. If you don't use MySQL or MariaDB, the responsiveness in a multi-user environment will be poor.

I started using ownCloud in a Xen VM and recently converted to Docker. I use many of its features for my business: - ownCloud app on Android phones to automatically upload and review pictures taken while on the job. - Contacts downloaded to phones from ownCloud managed from one place. - Calendars that can be seen on phones for scheduling. It's really improved our productivity.

How does that work for the apps from apps.owncloud.com They all seem to be downloadable compressed files. Download, uncompress, and copy to the apps directory in the Docker. You'll then see them in the ownCloud apps and you can enable the apps on the admin webgui of ownCloud. OK, daft question how do you copy from Host to Container? I'm assuming this is all via cmd line, if so, should be simple enough to make a script to do that I would have thought. Put the app in the /mnt/user/appdata/owncloud directory and the Docker has access to it. Copy from there by executing bash in the Docker. OK, that's so obvious I feel rather stupid. In my mind it was far more complicated. Sorry No problem. It is rather easy to do. Like I said a bit of a pain, but not difficult. I leave the uncompressed app in the /mnt/user/appdata/owncloud folder for future use. I think if ownCloud is updated inside the Docker, the apps won't get clobbered by updating the Docker. I haven't tried that yet.

How does that work for the apps from apps.owncloud.com They all seem to be downloadable compressed files. Download, uncompress, and copy to the apps directory in the Docker. You'll then see them in the ownCloud apps and you can enable the apps on the admin webgui of ownCloud. OK, daft question how do you copy from Host to Container? I'm assuming this is all via cmd line, if so, should be simple enough to make a script to do that I would have thought. Put the app in the /mnt/user/appdata/owncloud directory and the Docker has access to it. Copy from there by executing bash in the Docker.

How does that work for the apps from apps.owncloud.com They all seem to be downloadable compressed files. Download, uncompress, and copy to the apps directory in the Docker. You'll then see them in the ownCloud apps and you can enable the apps on the admin webgui of ownCloud.

I just installed the apps I needed inside the Docker. It works until you upgrade, then it has to be done again. Kind of a pain, but it works.

Found the answer. The config.php file needs the following line: 'proxy' => '192.168.1.x:8000' EDIT: The IP address is the IP of your server.

I see this error in the admin page of ownCloud: "Configuration Checks This server has no working internet connection. This means that some of the features like mounting of external storage, notifications about updates or installation of 3rd party apps don´t work. Accessing files from remote and sending of notification emails might also not work. We suggest to enable internet connection for this server if you want to have all features." Everything seems to work, but I'm wondering how to resolve this error or if it is even important.

This one is better. It has a transparent background.

How about this one.

I installed the apachephp docker and it is working for me, but the banner and icon files appear to be corrupted or non existent.

So what does Auto Mount on do? I'm hoping it will mount the drive on bootup when set on and mount/unmount with the array start/stop events.