dlandon

You're UD settings have not been set to share SMB: Jun 7 17:05:06 Unraid kernel: xfs filesystem being mounted at /mnt/disks/cctv_4tb_storage supports timestamps until 2038 (0x7fffffff) Jun 7 17:05:06 Unraid unassigned.devices: Successfully mounted 'sdf1' on '/mnt/disks/cctv_4tb_storage'. Jun 7 17:05:06 Unraid unassigned.devices: Warning: Unassigned Devices are not set to be shared with SMB. Jun 7 17:05:06 Unraid unassigned.devices: Warning: Unassigned Devices are not set to be shared with NFS. Go to UD Settings->SMB Settings and set up SMB to share UD devices with the type of sharing you want. For security, SMB and NFS sharing default to disabled.

Tha preclear page was not accessible for whatever reason. My point is that it is not an error directly from a preclear operation. As you say, you were not running a preclear. I don't understand this: Docker?

That's an nginx error, not a preclear error.

Edit the ownCloud docker template and change the PHP Version setting:

I'm not seeing that. root@BackupServer:~# whereis emhttp emhttp: /usr/local/sbin/emhttp /usr/local/emhttp root@BackupServer:~# and #!/bin/bash # # Start the Management Utility. # /usr/local/sbin/emhttp &

Post diagnostics. That generally happens when the drive drops offline and then comes back online again. Linux assigns a new disk drive designation. Does the 'Mount' button change to say 'Boot'?

What size field do you think you need? Currently it is set at 256 characters.

It doesn't look you unmounted it before removing it. There is no unmount log entry.

Post diagnostics.

NFS cannot deal with a symlink. You can use the actual storage location. For example if you have Syslogs as a cache only share, use the /mnt/cache/Syslog reference rather than /mnt/user/Syslog. This avoids shfs when using /mnt/user/Syslog.

You have a lot of network settings and assignments to varying NICs. I would delete /flash/config/network.cfg to get back to the default network settings and slowly add back your settings, watch your log, and see if any of those is causing the issue.

Post the link for me.

I suggest you post that in the general support section.

When you set up a user share, 'user' or 'user-pool' is added to the mount point to distinguish between all shares and pool devices ('user-pool') and just user shares ('user'). Click on the Mount Point for the share and change the Mount Point to anything you'd like that is not a reserved name. When it won't unmount because the share is busy, something is using it. A PC having the share open in a browser or a terminal having the /mnt/rootshare/user.root open will prevent an unmount. Only one root share for 'user0' is allowed. The same for 'user'. Why do you need two?

Historically ISOs are downloaded for use with a VM and are stored in the isos share. For security reasons, UD limits the ISO selections to the isos share. I don't think copying an ISO file is that difficult. The Unraid file browser makes it very easy.

This is the best way to handle this situation. Mount the remote share, backup files, then unmount the remote share. There is no User Script that I know of that will do what you want, but it is not hard. If you turn on the Help while on the UD page, you can see the commands needed to mount and unmount the remote share. You can add a script to User Scripts on a cron to run at a specific time, or add the script to the Remote Share in UD that will run when it is mounted. The script would look something like this: /usr/local/sbin/rc.unassigned mount source rsync /usr/local/sbin/rc.unassigned umount source The source is "//Tower/remote share" for a SMB remote share. The issue you are running into is the downside of remote shares. Your network and remote server have to be very robust and reliable to maintain the connection. Both CIFS and NFS have these issues. There is little recovery that I've found except to unmount and remount the remote share.

I believe this has been fixed. Renove the remote share and add it back again.

You mounted it at user.root: Jun 4 10:23:47 Tardis unassigned.devices: Mounting Remote Share '//TARDIS/mnt/user0'... Jun 4 10:23:47 Tardis unassigned.devices: Mount ROOT command: /sbin/mount -o rw --bind '/mnt/user0' '/mnt/rootshare/user.root' Jun 4 10:23:47 Tardis unassigned.devices: Successfully mounted '/mnt/user0' on '/mnt/rootshare/user.root'. You would access the root share at //TARDIS/user.root. It won't unmount because someone or something is accessing //TARDIS/user.root: Jun 4 10:26:49 Tardis unassigned.devices: Unmount of 'user0' failed: 'umount: /mnt/rootshare/user.root: target is busy. It's busy.

How are you trying to access it?

ISO files have to be in an isos share.

You don't have to have a script to mount the remote share. There is a bug in the latest UD that doesn't show the default button. It will be fixed in the next release. The best way to get help is to post your diagnostics.

What does the UD page show when this is happening?

Check your cables: Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3115 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3115 CDB: opcode=0x88 88 00 00 00 00 00 8b c8 1e 08 00 00 05 70 00 00 Jun 2 11:43:56 Tardis kernel: I/O error, dev sdk, sector 2345147912 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0 Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3121 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3121 CDB: opcode=0x88 88 00 00 00 00 00 8b c8 28 00 00 00 02 00 00 00 Jun 2 11:43:56 Tardis kernel: I/O error, dev sdk, sector 2345150464 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 0 Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3117 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3117 CDB: opcode=0x88 88 00 00 00 00 00 8b c8 24 00 00 00 04 00 00 00 Jun 2 11:43:56 Tardis kernel: I/O error, dev sdk, sector 2345149440 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0 Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3116 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Jun 2 11:43:56 Tardis kernel: sd 11:0:7:0: [sdk] tag#3116 CDB: opcode=0x88 88 00 00 00 00 00 8b c8 23 78 00 00 00 88 00 00 Jun 2 11:43:56 Tardis kernel: I/O error, dev sdk, sector 2345149304 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 Jun 2 11:43:57 Tardis kernel: sd 11:0:7:0: Power-on or device reset occurred

I see several issues: Your network is dropping offline: May 27 21:19:39 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list May 27 21:27:57 TESSERACT webGUI: Successful login user root from 192.168.10.201 May 27 21:30:02 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list May 27 21:38:22 TESSERACT kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Down May 27 21:38:22 TESSERACT kernel: bond0: (slave eth0): link status definitely down, disabling slave May 27 21:38:22 TESSERACT kernel: device eth0 left promiscuous mode May 27 21:38:22 TESSERACT kernel: bond0: now running without any active interface! May 27 21:38:22 TESSERACT kernel: br0: port 1(bond0) entered disabled state May 27 21:38:31 TESSERACT kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None May 27 21:38:31 TESSERACT kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex May 27 21:38:31 TESSERACT kernel: bond0: (slave eth0): making interface the new active one Remove the rootshare from your smb-extra.conf and set up a UD rootshare. Setting shares in smb-extra.conf can cause problems because settings in smb-extra.conf are supposed to be global settings, not share settings.

Post diagnostics so we can assist you better.