dlandon

No. The Recycle Bin handles that for you.

Anyone having SMB issues and using the Recycle Bin plugin is encouraged to update to the latest version (2022.10.18a). The previous few versions may have caused SMB issues from some changes to remove the Recycle BIn information from the smb-extra.conf file. The global settings in the Recycle Bin were placed after user and UD shares. Global settings are supposed to go before the share settings. The settings have been reverted back to the smb-extra.conf file to solve this. If you update and see no difference, stop the Recycle BIn and see if it makes a difference. Report back if you find the Recycle Bin causes issues,

Read the post just above yours. It's empty. Don't put fruit settings in smb-extra.conf. Earlier posts describe how to move the /etc/samba/smb-fruit.conf file to the flash and make changes there.

For anyone having this issue, try adding the following to the smb-extra.conf file: log level = 0 If that doesn't work, try adding this: logging = 0 I'm working with the recycle bin plugin and the latest version of Samba seems to have a lot of changes to logging. I'm thinking the log message you are seeing is a debug message and shouldn't be showing up in the syslog.

UD is the best method.

What kind of shares are you asking about? Remote server shares?

In the next release.

It does.

I agree with you, but doing that is not consistent with the rest of Unraid. I would suggest you submit an UnraId feature request to have the buttons moved to the top on all log pages.

That shouldn't be necessary any longer beginning with 6.10. You can adjust it here:

This is the log message choking your log: Oct 12 01:09:12 Tower kernel: vfio-pci 0000:11:00.0: BAR 0: can't reserve [mem 0xd0000000-0xdfffffff 64bit pref] ### [PREVIOUS LINE REPEATED 23893 TIMES] ### You might want to see if this will help:

Possibly, but nothing like this has been reported as a UD or Preclear disk issue yet.

What is that client? Try another computer?

Your log is filled with this message: Oct 12 06:58:39 zaBOX nginx: 2022/10/12 06:58:39 [error] 11969#11969: *370706 connect() to unix:/var/run/php5-fpm.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.0.103, server: , request: "GET /Main HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "zabox.local", referrer: "https://zabox.local/Dashboard" Oct 12 06:58:39 zaBOX nginx: 2022/10/12 06:58:39 [error] 11969#11969: *370706 auth request unexpected status: 502 while sending to client, client: 192.168.0.103, server: , request: "GET /Main HTTP/2.0", host: "zabox.local", referrer: "https://zabox.local/Dashboard" What is the client 192.168.0.103?

Please close it.

Looking at your diagnostics I see an issue with one server: Oct 10 08:56:15 Halcyon unassigned.devices: Warning: shell_exec(/bin/df '/mnt/remotes/AURORA_tdownloaded' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! This is generally indicative of network or remote server connection issues. That server is having a tough time with a CIFS mount: Oct 9 06:46:29 Halcyon unassigned.devices: Mount SMB share '//AURORA/tdownloaded' using SMB 3.1.1 protocol. Oct 9 06:46:29 Halcyon unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_tdownloaded' '//AURORA/tdownloaded' '/mnt/remotes/AURORA_tdownloaded' Oct 9 06:46:29 Halcyon kernel: CIFS: Attempting to mount \\AURORA\tdownloaded Oct 9 06:46:29 Halcyon kernel: CIFS: VFS: Error connecting to socket. Aborting operation. Oct 9 06:46:29 Halcyon kernel: CIFS: VFS: cifs_mount failed w/return code = -111 Oct 9 06:46:29 Halcyon unassigned.devices: SMB 3.1.1 mount failed: 'mount error(111): could not connect to 192.168.1.70Unable to find suitable address. '. What is that server? I would not mount that server share with UD and see if it stops your SMB issues.

Set "Security" to "Private" and click "Apply". You'll then see a "Rule" line.

That's because Linux/Unraid doesn't understand the formatting of the disk. How was it originally formatted? If UD doesn't understand the format, you can't mount it manually. Post your diagnostics.

Remove the following lines from your go file. Unraid is now handling this for you. modprobe i915 chmod -R 777 /dev/dri Reboot.

With the Tips and Tweaks plugun unstalled, you can use the following command to change the CPU governor: /usr/local/sbin/rc.tweaks set_governor 'governor'

I understand about not booting to 6.11. The diagnostics you gave me was fine. You need to remove NerdPack, reboot, and then try to update. NerdPack is deprecated for 6.11. The NerdPack packages may be out of date and not compatible. There is a replacement called NerdTools.

Post diagnostics file.

Remove NerdPack and reboot.

By removing it or using the "Detach" button?

That shouldn't happen. UD never comments out the include line. Maybe you did a manual edit and commented it out while testing. Uncomment it or your UD shares won't work.