dlandon

I would do the following: Turn off auto mount. Click on the 'File System Check' and see if the file system needs repaired. Add '--bwlimit=X' to your rsync to slow things down. Turn on auto mount and let your script run. If the script still takes a long time, it is working and needs to copy everything.

The first time ownCloud runs, it has to configure php for the version you have set in the xml. It shouldn't take that long. If it happens again, watch the log and you'll see what's happening.

I'll have a fix later today or tomorrow.

This has been bugging me for a while. I'll see what I can do to clean this up.

Only if a developer decides to make an Unraid docker template.

Post diagnostics.

I just reviewed the UD code and see that I only mount a SMB v1.0 remote share when NetBIOS is enabled. NetBIOS does not have to be enabled to mount a remote share with SMB v1.0. It does have to be enabled for a remote server to mount a share with SMB v1.0. The next release of UD will fix this.

UD will mount the remote share with the highest protocol the remote server will support. It does a sequence of mounts starting at 3.X, then 2.X, then 1.X until the remote share mounts. Just try to mount the remote share with UD, It should mount it. You have to have NetBIOS enabled to mount with SMB v1.0. The "Specify SMB Version when Mounting Remote Shares?" setting when set to "No" will tell UD to mount the device on the first try without specifying a version. Newer servers will mount the share with the hghest protocol it can support. Legacy servers do not mount this way and the version needs to be speficied. The "Yes" setting tellls UD to specify the version when it sequences through mount attempts on the remote share.

Turn off "force user = nobody". Also go to a command line and do this command: chmod 777 -R /mnt/disks/disk mount point

Post another diagnostics.

Turn off the 'macOS Interroperability' in the SMB Settings and see if you still have the issue with the Windows PC.

You don't have enough user watches. Increase the 'Max User Watches' to at least 2,700,000.

Implemented in the next release of UD.

There are several issues: You are very far behind in updating UD. There are disk issues: Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 60976: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 721727062, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 60976: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read $MFT bitmap: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 721727062, async page read Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 37, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 5739: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 435373662, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 5739: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[8797]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[8797]: Failed to read vcn 0x0 from inode 5: Input/output error Mar 25 04:40:01 Jupiter kernel: Buffer I/O error on dev sdt1, logical block 435373662, async page read Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: Failed to read vcn 0x0 from inode 5739: Input/output error Mar 25 04:40:01 Jupiter ntfs-3g[11155]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error The 'Reboot' indicator on the 'Mount' Button indicates that the disk was not unmounted before being removed You can click the check mark icon next to the partition to check the disk.. Do This: Update UD. Turn off 'Auto Mount" on those disks. Reboot the server. Run a file system check on both disks. Mount the disks and verify everything is ok.

It is setup to be a .Recycle.Bin per share. That's how the Samba recycle bin works. It currently can't be a recycle bin for all shares. Just exclude the Recycle.Bin folders in your backups.

What is your use case?

Post your diagnostics.

You might try mounting the disk with UD. I believe UD will mount both partitions and you can copy data off the second partition if that would help. I saw this when first implementing ZFS in UD, but that was a while ago.

"Performance" means performance mode.

The only Scaling Governors that driver offers are "Performance" and "Power Save".

What CPU driver is shown on the right side if the Tips and Tweaks page?

It's not very clear what's going on. I see a format btrfs, followed by a format zfs, and then a mount of a vfat. Clear the drive and try again. After you do that, post your diagnostics.

Fixed in the next release of UD.

How are the drives connected? Post diagnostics and a screen shot of the UD page.

Click on the three gears icon and set the "Share" switch on. That will share the device with the permissions you set in UD Settings,