dlandon

Start by removing the smb-extra.conf entries: path = /mnt/disks/gDrive comment = browseable = yes # Public public = yes writeable = yes vfs objects = That's a UD disk and UD can do the sharing for you.

A couple of comments: You have "Enhanced macOS interoperability:" enabled. If you aren't using Macs on your network, turn it off. You're using a Realtek NIC. They have been troublesome because the Linux driver has not been reliable. Try to use another NIC like Intel.

Try using the AUDIO-PC IP address instead of the name. If UD doesn't list the shares available on a remote server, it won't be able to mount it. One reason that shares may not be listed in UD is incorrect credentials. Work on getting UD to list shares. There are also some timeout issues with CIFS iun your log: May 13 19:19:34 SunLightPrime kernel: CIFS: VFS: \\VFX has not responded in 180 seconds. Reconnecting... But that is with another server. It would help in the future to turn off the mover logging. There are a lot of log messages from that in the log to go through.

Go to the Plugins->Install Plugins tab and enter this line: https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg It will install UD.

FYI, you can use the preclear docker with the UD Preclear plugin. When you select to preclear a disk with UD Preclear, you can choose the script or the docker (if it is installed) to run the preclear. You then can track the preclear progress with UD.

Someone please provide 6.12.rc5 diagnostics. 6.12 diagnostics include additional information that can help troubleshooting SMB issues.

The ntfs file system is unclean: May 11 07:42:10 Dominator unassigned.devices: Mount cmd: /sbin/mount -t 'ntfs' -o rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdb2' '/mnt/disks/Backup' May 11 07:42:10 Dominator ntfs-3g[4624]: Version 2022.10.3 integrated FUSE 27 May 11 07:42:10 Dominator ntfs-3g[4624]: Mounted /dev/sdb2 (Read-Only, label "Backup", NTFS 3.1) May 11 07:42:10 Dominator ntfs-3g[4624]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 May 11 07:42:10 Dominator ntfs-3g[4624]: Mount options: nodiratime,nodev,nosuid,nls=utf8,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/sdb2,blkdev,blksize=4096 May 11 07:42:10 Dominator ntfs-3g[4624]: Global ownership and permissions enforced, configuration type 1 May 11 07:42:11 Dominator unassigned.devices: Successfully mounted 'sdb2' on '/mnt/disks/Backup'. May 11 07:42:11 Dominator unassigned.devices: Mount warning: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) Could not mount read-write, trying read-only . Normally this occurs when the disk is removed from a Windows PC and not properly disconnected first.

At a command line, what is the output of these commands: ls -la /var/lib/ and ls -la /var/lib/samba/

And it looks like UD is reporting what it got with the 'df' command,

Go to a command line and do this command: /bin/df /mnt/remotes/mountpoint --output=size,used,avail and show the result.

An unclean file system is the normal cause of this as the user has found out. I'm not sure a chkdisk will fix it.

Not everyone needs the functionality of UD+.

Unraid manages UD spin ups and downs.

Works for me.

There were no changes in the latest Zoneminder container. It was to catch up the Ubuntu updates and refresh the docker container. That problem normally happens with database issues. I've kept up with all the updates on my own Zoneminder and never had an issue with the DB. Restore the database from a backup and see if it doesn't fix it.

You can set up the syslog server to log to itself and logs will go to the syslog share. You have to set it up on the syslog server itself. i.e. if the syslog server is 192.168.1.10, you can set the syslog server on 192.168.1.10 to log to itself by setting 192.168.1.10 in the syslog setup.

UD+ is an add on to UD and is required to do things like enable the destructive mode. It is not required for normal UD functions.

El complemento de Unassigned Devices (UD) puede montar discos NTFS y EXT4 y luego puede transferir sus datos localmente.

I'm going to guess that the Drobo disks may have some errors? I like your idea of only mounting the remote share when it is needed and then unmounting it when you are done. You can mount and unmount remote shares in a script using rc.unassigned. Go to the UD webpage and enable 'Help', then scroll down the page to see the rc.unassigned commands for mounting a remote share. You can do the same to unmount it.

Post your diagnostics.

If you have the UD plugin installed, that is what is causing that log error. Post diagnostics so we can provide better help.

Don't add anything to the smb-extras.conf. You may create more problems than you solve. Samba configurations can be very touchy, plus UD manages the UD devices configurations for you. Be sure to post diagnostics the next time you post.

Wow, I don't remember ext4 ever being a format option, but you're right. I stand corrected. Regardless, yes UD can auto mount an ext4 disk,

It has never been an option to format ext4 disks, but UD can mount them. Reiserfs was removed some time ago as a format option because it is deprecated.

I'm out of ideas.