dlandon

Hiding dot files is controlled by the Settings->SMB setting. It applies to all SMB shares - Unraid and UD shares.

The log will show a deleted file right away, but it can take up to 5 minutes to show in the Recycle Bin shares tab.

Only files deleted through SMB (network shares) are recycled. Files deleted using the File Manager, Krusader (or similar), or cli commands do NOT get recycled.

@cloudyhome Nice writeup! One suggestion. Don't use the 'devX' designation from the 'Disk Name' field. UD defaults this to the 'devX' designation Unraid assigns to unassigned disks and it can change. Assign a unique name to the 'Disk Name' field as an alias and use that in your script.

USB is not generally robust enough to do reliable preclears.

Use UD Preclear plugin. It has a disk erase mode.

Did you intend to report this as a UD issue?

Ok, it seems a change was made in Unraid 6.13 to address an issue with saving script files after a UD change. It has been fixed in 6.13, but 6.11 and 6.12 will have an issue. I will update UD once I come up with a way to make a proper fix.

You need to unmount the disk in UD and mark it as passed through so UD will prevent any operations while the VM is using the disk.

That can't be used as a file name because it is a folder. The name you want is '/boot/config/plugins/unassigned.devices/some file name'.

I'm not having any trouble with scripts. Is your disk or remote share mounted? The script buttons act differently if the device is mounted. If the script is running, you are even more limited in what you can do. The only button that applies changes is 'Apply'. There's an off chance you are running into a php warning or error. Check the Tools->PHP Settings and see if anythjing is logged.

Currently Unraid's value is 'smbd max xattr size = 65536'. You can try setting this value higher in the smb-extras, but I don't think this is your problem. smbd max xattr size = <new value> I think @Frank1940 may have the answer - see above.

How about you change your strategy and mount and unmount the shares as needed for your backup. You could also add some code to check that the backup server is online by pinging it before auto mounting and either waiting for it to come on line or fail the backup. In pseudo code: Ping remote server and see if it is on line. If not, wait for it to come on line, or fail the backup script. rc.unassigned mount <backup remote share>. Perform the backup... rc.unassigned umount <backup remote share>. I wouldn't have dockers running depending on the remote mount to be available if it is turned off. Coordinate the use of the mount points with when the backup server is on line.

Sounds like you might be getting stale file handles. Post diagnostics.

Look in /flash/preclear_reports/.

A few things to try: You are using tailscale. Check your setup and be sure the 'SARAH' server is seen. Try pinging it from the server that is not showing it as mountable. Ping both the name and IP address. Try using the IP address of 'SARAH' in UD instead of the name. The issue may be name lookup.

Post diagnostics from the server that is failing.

You have to enter the correct credentials in order to list the shares. As a test, when you get to the part where yoiu enter a share, enter a share manually. Then mount the share and let's see if an error shows.

Your best bet is to upgrade to 6.11. The other option is to copy the /boot/config/plugins/ folder from a backup and reboot.

1. Probably not because I don'rt think there is enough room to fit it in. 2. The appdata, syslog, and system shares are excluded from file activity and won't show any activity.

This might be affected by the excluded files in the recycle bin. As I mentioned already, this is a very bizare get around and I don't expect it to work in all cases. It's going to end up being up to the samba development team to find the final solution.

I've done some testing and found out Samba is crashing: [2024/03/14 09:07:19.329402, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) [2024/03/14 09:07:19.329435, 0] ../../lib/util/fault.c:178(smb_panic_log) =============================================================== [2024/03/14 09:07:19.329442, 0] ../../lib/util/fault.c:179(smb_panic_log) INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in smbd (smbd[192.168.1.) (client [192.168.1.188]) pid 22564 (4.19.5) [2024/03/14 09:07:19.329447, 0] ../../lib/util/fault.c:186(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2024/03/14 09:07:19.329451, 0] ../../lib/util/fault.c:191(smb_panic_log) =============================================================== [2024/03/14 09:07:19.329464, 0] ../../lib/util/fault.c:192(smb_panic_log) PANIC (pid 22564): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.19.5 [2024/03/14 09:07:19.329708, 0] ../../lib/util/fault.c:303(log_stack_trace) This is with samba 4.19. I seem to have found a get around, but I'm baffled right now about why this works. Install the recycle bin plugin and be sure it is running. In my testing it looks like file deletes work. Deleting directories works but an error is displayed and the Android app does not show the directory as being deleted until closed and re-opened. The directory delete also crashes samba. Since the recycle bin plugin is for deleted files through SMB, there is something the recycle bin vfs is doing that prevents the file deletes from failing in this situation. Because samba is crashing it looks to be an issue that the samba team needs to fix. At this time, I don't see any way through samba settings we will be able to fix this on the Unraid side. It could also be an issue with the Android app, but I doubt it. In doing some research, there is a samba bug here that might solve the issue.

Are you using the recycle bin plugin?

What Android app are you using? I'd like to do some testing.

Update UD and see if it is fixed.