dlandon

You're saying UD mounted your disk? I'm releasing an update today that doesn't allow mounting an array disk. Is your disk a USB connected disk? Be sure the "Auto Mount USB Devices" is set to "No" in UD Settings.

No, if the new drive is not zeroed (either by a preclear or Unraid clear), then parity will be incorrect and have to be updated which can take a long time and involve all data disks. Unraid clearing a disk is done in the background and won't affect normal array operation.

Working for me: The script to do the preclear itself has not changed in a long time. You might try the preclear docker and see if you get different results.

You can only specify a single sub-directory for a share. Look at the Help: List of directories to exclude from the Recycle Bin separated by commas. To specify a particular share directory, use 'share/directory'. You can specify up to one sub-directory. Unassigned Devices are specified the same way using 'mountpoint/directory'. Wild cards '*' and '?' are allowed in the directory name. So you specify 'pool/Backups' for the complete 'Backups' directory. If you are lookiing to exclude only the 'pool/Backups/Portables', specify it like 'pool/Portables'. I see an issue with specifying multiple share folders. I think this should work 'pool/Backups,pool/Portables', but it looks like only 'Portables' is excluded. I think the Recycle Bin should exclude both 'Backups' and 'Portables' when specified this way.

I did a little research and to my surprise, UD will try to auto mount a disk that drops out of the array if it is marked "Automount". Click on the device settings (three gears) and be sure the "Automount" switch is off. If the disk is in the array, delete the history for that disk.

There can be many reasons for a network issue. Try rebooting all the network equipment - router, switches, and servers. You need to take a look at how you are managing your downloads. Work on stopping the mover issues.

Can you show a screen shot of your Recycle Bin settings?

When UD detects a disk has dropped out of the array, it is marked "Array" on the mount button. UD will not mount a disk in this condition. If your drive has gotten corrupted, it would not be from UD. Disk 19 is not staying connected.

You have several problems. The first is a mover issue: Jan 3 12:06:37 9900K move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Media/Usenet/IncompleteSab/Rodney.King.2017.2160p.WEB-DL.DD5.1.HEVC-PLAYREADY Jan 3 12:13:56 9900K move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Media/TV Shows/Recordings/The View (1997)/Season 26/The View (1997) - S26E72 - The View.log Jan 3 12:13:56 9900K move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Media/TV Shows/Recordings/The View (1997)/Season 26/The View (1997) - S26E72 - The View.txt Jan 3 12:13:56 9900K move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/Media/TV Shows/Recordings/The View (1997)/Season 26/The View (1997) - S26E72 - The View.logo.txt Review where you are downloading your media and how it is handled. Networking issues? Dec 28 12:01:32 9900K unassigned.devices: Warning: shell_exec(/bin/df '/mnt/remotes/NAS1_user-pool.nas1megashare' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10s! ### [PREVIOUS LINE REPEATED 7 TIMES] ### Dec 28 12:18:55 9900K kernel: NFS: server NAS1 error: fileid changed Dec 28 12:18:55 9900K kernel: fsid 0:81: expected fileid 0x90300038c16f49c, got 0x35000001901735 Dec 28 12:18:55 9900K kernel: NFS: server NAS1 error: fileid changed Dec 28 12:18:55 9900K kernel: fsid 0:81: expected fileid 0x901000007a287b3, got 0x35000001901733 Dec 28 12:19:03 9900K kernel: NFS: server NAS1 error: fileid changed Dec 28 12:19:03 9900K kernel: fsid 0:81: expected fileid 0x901000100000088, got 0x35000001901726 Dec 28 12:27:00 9900K unassigned.devices: Warning: shell_exec(/bin/df '/mnt/remotes/NAS1_user-pool.nas1megashare' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10s! ### [PREVIOUS LINE REPEATED 14 TIMES] ### Dec 28 12:43:52 9900K kernel: NFS: server NAS1 error: fileid changed Dec 28 12:43:52 9900K kernel: fsid 0:81: expected fileid 0x9070001aa8dabc6, got 0x3500000190184f Dec 28 13:02:55 9900K unassigned.devices: Warning: shell_exec(/bin/df '/mnt/remotes/NAS1_user-pool.nas1megashare' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10s! ### [PREVIOUS LINE REPEATED 1 TIMES] ### Dec 28 13:08:15 9900K kernel: NFS: server NAS1 error: fileid changed Dec 28 13:08:15 9900K kernel: fsid 0:81: expected fileid 0x902000113194415, got 0x3500000190185e Dec 28 13:08:17 9900K kernel: NFS: server NAS1 error: fileid changed Dec 28 13:08:17 9900K kernel: fsid 0:81: expected fileid 0x90d0000000000bf, got 0x35000001901863 Dec 28 13:11:21 9900K kernel: NFS: server NAS1 error: fileid changed Dec 28 13:11:21 9900K kernel: fsid 0:81: expected fileid 0x3500000190166e, got 0x90d000406b01385

You need to do the following: Remove "statistics.sender.plg". It's part of the old preclear. It is no longer needed and is not compatible with 6.11. Remove "modprobe i915" from the go.txt file, Unraid takes care of that in 6.11. Remove all the stuff in the smb-extra.conf file and install UD to create a rootshare. Put "[global]" and "logging = 0" in the smb-extra.conf. Reboot.

I'm not seeing a reason for your remote shares to fail. Why are you logging so much in your smb-extra.conf? It makes the log very hard to read. log level = 3 logging = syslog Try the following: Turn off SMB Multichannel. Turn off macOs Interoperability. Turn off NetBIOS. It doesn't look like you need it. If none of that fixes your issue, turn off the excessive SMB logging and post another diagnostics so I stand a chance of being able to read your log.

Start by going to Settings->Unassigned Devices and set the Debug Log Level to 'None'. The log is full of debug messages and it is impossible to find any relevant log messages. Rebooot to clear up the log, then post diagnostics again once you have the problem.

'share' refers to your share name. I doubt you have a share named 'share'. Don't use quotes on the Excluded Shares.

I am very confused. How did you start the array if the start array button is not visible? Your array is not running in the screen shot either. And, you said yo see the same thing when you boot in the safe mode with UD installed? What about in safe mode without UD being installed?

Your array is started. Post a screen shot of what you are seeing.

Remove the settings in the smb-extra.conf file. Install UD and post another diagnostics.

Show a screen shot when you are trying to install the open files plugin. I don't see anything in the log that helps.

Post diagnostics.

Post diagnostics.

Update to 6.11.5 and see if the issue continues. If it does, post new diagnostics.

Post diagnostics.

Can you click on the green orb next to the drive and spin the drive down manually? If not, the drive probably won't spin down.

That would indicate your password is wrong. Be sure you set it for the right disk. Also stay away from special characters.

It doesn't touch anything.

Delete the one marked 'none' in Historical Devices.