dlandon

Probably the best thing to d is re-install the docker. I'll also take a look at why it is not updating.

Read the help on the UD webpage and add the autostart command to User Scripts to start when the array is started. It will mount any automount devices that aren't mounted. Any devices already mounted will not be affected.

Look at the system log. You probably have a timing situation. Something is not ready when the server starts, but is available when you mount manually.

I find it hard to believe that the Zoneminder docker took down your server.

Remove the Zoneminder folder from appdata and install the docker again.

The latest release of LMS has added CORS security. "Add CORS support In Settings/Advanced/Security you can now define a list of hosts which are allowed to access your LMS. Please note that in order for CORS to work, you have to disable the CSRF protection (off by default)."

I have updated the docker image to install ownCloud 10.9.0 as the initial install. I have also set up the mariadb 10.3 stable repository so mariadb 10.3 it will be updated when the docker is started. When I tried to update my ownCloud to 10.9.0 using the built in updater, it did not handle the add on apps properly and got stuck in the maintenance mode. I ended up updating using the manual method in the second post of the thread. If you use a self-signed certificate, the built in updater won't work and you have to use the manual method. In any case, I recommend manually updating the docker in all cases. It's easy to roll back if the update fails because you make a copy of ownCloud before updating.

Your configuration is extremely confusing and I don't follow it at all. Sounds like you have a circular configuration. Simplify the setup.

Turn off the USB auto mount: Set "Settings->Unassigned Devices->Auto Mount USB Devices?" to "No". Reboot your server and try again. If it persists, post your diagnostics.

There is not currently enough room to add the read/write info. I won't redesign UD since LT has indicated that in will be eventually included in the base unRAID. They can add that feature. I really don't have the time or any interest in UD improvements. I will do maintenance only.

The $LOGFILE variable is the user log that your script writes to. For example: echo "Write to the log" > $LOGFILE The "/tmp/$SERIAL.log" is used by UD and generally doesn't have anything of importance. This is done so the user script log is only the information relating to the running of the script and not any UD information.

Give the docker a static ip address.

They don't have to be associated with the UD plugin to cause issues. Yes, start a new thread and get help sorting it all out.

My test server does not have any Dockers installed. Seems that was the issue.

Somehow or another I run into these bugs. Not really trying that hard. Thanks for fixing so quickly.

Version 2018.07.20 giving php error on gui: Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 1574 backupserver-diagnostics-20180722-0712.zip

You need to work through your log and solve the problems showing up: Jul 15 17:20:00 Tower root: Fix Common Problems Version 2018.06.21 Jul 15 17:20:02 Tower root: Fix Common Problems: Error: Docker application plex has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option ** Ignored Jul 15 17:26:10 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 15 17:26:10 Tower kernel: ata7.00: failed command: SMART Jul 15 17:26:10 Tower kernel: ata7.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 15 pio 512 in Jul 15 17:26:10 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jul 15 17:26:10 Tower kernel: ata7.00: status: { DRDY } Jul 15 17:26:10 Tower kernel: ata7: hard resetting link Jul 15 17:26:10 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 15 17:26:10 Tower kernel: ata7.00: configured for UDMA/133 Jul 15 17:26:10 Tower kernel: ata7: EH complete Jul 15 17:31:02 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 17:42:04 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 15 17:42:04 Tower kernel: ata10.00: failed command: SMART Jul 15 17:42:04 Tower kernel: ata10.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 24 pio 512 in Jul 15 17:42:04 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jul 15 17:42:04 Tower kernel: ata10.00: status: { DRDY } Jul 15 17:42:04 Tower kernel: ata10: hard resetting link Jul 15 17:42:05 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 15 17:42:05 Tower kernel: ata10.00: configured for UDMA/133 Jul 15 17:42:05 Tower kernel: ata10: EH complete Jul 15 17:43:06 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 15 17:43:06 Tower kernel: ata10.00: failed command: IDENTIFY DEVICE Jul 15 17:43:06 Tower kernel: ata10.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 11 pio 512 in Jul 15 17:43:06 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jul 15 17:43:06 Tower kernel: ata10.00: status: { DRDY } Jul 15 17:43:06 Tower kernel: ata10: hard resetting link Jul 15 17:43:06 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 15 17:43:06 Tower kernel: ata10.00: configured for UDMA/133 Jul 15 17:43:06 Tower kernel: ata10: EH complete Jul 15 17:46:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 17:51:43 Tower emhttpd: shcmd (192): /usr/sbin/hdparm -y /dev/sdb Jul 15 20:20:02 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 15 20:20:02 Tower kernel: ata8.00: failed command: IDENTIFY DEVICE Jul 15 20:20:02 Tower kernel: ata8.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 11 pio 512 in Jul 15 20:20:02 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jul 15 20:20:02 Tower kernel: ata8.00: status: { DRDY } Jul 15 20:20:02 Tower kernel: ata8: hard resetting link Jul 15 20:20:03 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 15 20:20:03 Tower kernel: ata8.00: configured for UDMA/100 Jul 15 20:20:03 Tower kernel: ata8: EH complete Jul 15 20:21:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 20:21:04 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 15 20:21:04 Tower kernel: ata8.00: failed command: IDENTIFY DEVICE Jul 15 20:21:04 Tower kernel: ata8.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 2 pio 512 in Jul 15 20:21:04 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jul 15 20:21:04 Tower kernel: ata8.00: status: { DRDY } Jul 15 20:21:04 Tower kernel: ata8: hard resetting link Jul 15 20:21:04 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 15 20:21:04 Tower kernel: ata8.00: configured for UDMA/100 Jul 15 20:21:04 Tower kernel: ata8: EH complete Jul 15 21:23:11 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 21:39:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 21:54:11 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 22:10:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 22:26:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 22:42:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 22:58:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 15 23:14:01 Tower crond[1589]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jul 22 04:25:58 Tower kernel: sdh: detected capacity change from 320072933376 to 0 Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208492, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208493, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208494, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208495, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208496, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208497, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208498, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208499, lost async page write Jul 22 04:25:58 Tower kernel: Buffer I/O error on dev sdh1, logical block 64208500, lost async page write Jul 22 04:25:58 Tower kernel: sd 7:0:0:0: [sdh] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jul 22 04:25:58 Tower kernel: sd 7:0:0:0: [sdh] tag#3 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jul 22 04:25:58 Tower kernel: print_req_error: I/O error, dev sdh, sector 65744 Jul 22 04:25:58 Tower kernel: REISERFS abort (device sdh1): Journal write error in flush_commit_list Jul 22 04:25:58 Tower kernel: REISERFS warning (device sdh1): journal-837 _update_journal_header_block: IO error during journal replay Jul 22 04:25:58 Tower kernel: print_req_error: I/O error, dev loop2, sector 25480 Jul 22 04:25:58 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0 It goes on and on. I would start by solving the disk issues.

Look in the Market for the "OwnBackup" app. It backs up the databases on a schedule.

You can specify a different location for the data if you don't want it on your cache drive.

Post your diagnostics.

The best way to update is through the builtin ownCloud updater. It will not update though with a self signed certificate. I use a proper certificate and it is worth it just to be able to use the builtin ownCloud updater.

Check app Marketplace to see if there is an app to do what you want. You will need an app built for ownCloud. You can't add anything onto ownCloud that is not a built app.

Stick with https.

Looks to me like they are. That's what the .Recycle.Bin directories are. Post a diagnostics for more help.

What is the problem you are having?