dlandon

Your log only goes to Feb 26th, so it is not up to today. I see this in your log that I don't understand: Feb 16 17:51:20 unRAID nginx: 2022/02/16 17:51:20 [alert] 10670#10670: worker process 32187 exited on signal 6 Feb 16 17:51:22 unRAID nginx: 2022/02/16 17:51:22 [alert] 10670#10670: worker process 32232 exited on signal 6 Feb 16 17:51:24 unRAID nginx: 2022/02/16 17:51:24 [alert] 10670#10670: worker process 32369 exited on signal 6 Feb 16 17:51:26 unRAID nginx: 2022/02/16 17:51:26 [alert] 10670#10670: worker process 32439 exited on signal 6 Feb 16 17:51:28 unRAID nginx: 2022/02/16 17:51:28 [alert] 10670#10670: worker process 32498 exited on signal 6 Feb 16 17:51:30 unRAID nginx: 2022/02/16 17:51:30 [alert] 10670#10670: worker process 32556 exited on signal 6 Feb 16 17:51:32 unRAID nginx: 2022/02/16 17:51:32 [alert] 10670#10670: worker process 32615 exited on signal 6 Feb 16 17:51:34 unRAID nginx: 2022/02/16 17:51:34 [alert] 10670#10670: worker process 32687 exited on signal 6 Feb 16 17:51:36 unRAID nginx: 2022/02/16 17:51:36 [alert] 10670#10670: worker process 32726 exited on signal 6 Feb 16 17:51:38 unRAID nginx: 2022/02/16 17:51:38 [alert] 10670#10670: worker process 324 exited on signal 6 Feb 16 17:51:40 unRAID nginx: 2022/02/16 17:51:40 [alert] 10670#10670: worker process 397 exited on signal 6 Feb 16 17:51:42 unRAID nginx: 2022/02/16 17:51:42 [alert] 10670#10670: worker process 453 exited on signal 6 Feb 16 17:51:44 unRAID nginx: 2022/02/16 17:51:44 [alert] 10670#10670: worker process 513 exited on signal 6 Feb 16 17:51:46 unRAID nginx: 2022/02/16 17:51:46 [alert] 10670#10670: worker process 585 exited on signal 6 Feb 16 17:51:46 unRAID nginx: 2022/02/16 17:51:46 [alert] 10670#10670: worker process 643 exited on signal 6 Feb 16 17:51:48 unRAID nginx: 2022/02/16 17:51:48 [alert] 10670#10670: worker process 644 exited on signal 6 Feb 16 17:51:50 unRAID nginx: 2022/02/16 17:51:50 [alert] 10670#10670: worker process 704 exited on signal 6 Feb 16 17:51:52 unRAID nginx: 2022/02/16 17:51:52 [alert] 10670#10670: worker process 748 exited on signal 6 Feb 16 17:51:54 unRAID nginx: 2022/02/16 17:51:54 [alert] 10670#10670: worker process 899 exited on signal 6 Feb 16 17:51:56 unRAID nginx: 2022/02/16 17:51:56 [alert] 10670#10670: worker process 958 exited on signal 6 Feb 16 17:51:58 unRAID nginx: 2022/02/16 17:51:58 [alert] 10670#10670: worker process 1023 exited on signal 6 Feb 16 17:52:00 unRAID nginx: 2022/02/16 17:52:00 [alert] 10670#10670: worker process 1094 exited on signal 6 Feb 16 17:52:02 unRAID nginx: 2022/02/16 17:52:02 [alert] 10670#10670: worker process 1160 exited on signal 6 Feb 16 17:52:04 unRAID nginx: 2022/02/16 17:52:04 [alert] 10670#10670: worker process 1336 exited on signal 6 Feb 16 17:52:06 unRAID nginx: 2022/02/16 17:52:06 [alert] 10670#10670: worker process 1509 exited on signal 6 Feb 16 17:52:08 unRAID nginx: 2022/02/16 17:52:08 [alert] 10670#10670: worker process 1584 exited on signal 6 Feb 16 17:52:10 unRAID nginx: 2022/02/16 17:52:10 [alert] 10670#10670: worker process 1665 exited on signal 6 Feb 16 17:52:12 unRAID nginx: 2022/02/16 17:52:12 [alert] 10670#10670: worker process 1721 exited on signal 6 Feb 16 17:52:14 unRAID nginx: 2022/02/16 17:52:14 [alert] 10670#10670: worker process 1781 exited on signal 6 Feb 16 17:52:16 unRAID nginx: 2022/02/16 17:52:16 [alert] 10670#10670: worker process 1849 exited on signal 6 Feb 16 17:52:18 unRAID nginx: 2022/02/16 17:52:18 [alert] 10670#10670: worker process 1908 exited on signal 6 Feb 16 17:52:19 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token ### [PREVIOUS LINE REPEATED 1 TIMES] ### Your 'cache' disk has a lot of issues in the SMART rport. This is an example: Error 122 [1] occurred at disk power-on lifetime: 41127 hours (1713 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 84 -- 51 00 00 00 00 00 00 00 01 a0 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- ec 00 00 00 00 00 00 00 00 00 00 a0 08 42d+08:12:53.709 IDENTIFY DEVICE You probably need to replace that disk. The 'cache2' disk also seens to be having issues.

Can you also show me your SMB security settings on the share?

Is your flash drive offline or read only?

I've been asked to look at your situation again since you haven't been able to resolve it. Let's reset and come at it again. Do the following: Upgrade to 6.9 if you're not already on 6.9. Update all your plugins. Create the issue where the ownership of the files gets lost. Post your diagnostics. While you are doing that, I'll set up a pool device as a btrfs encrypted device and see if I can recreate your issue, The problem I may have is that I am currently on 6.10, so I may not be able to reproduce the issue. If I can't, I'll have roll back to 6.9.

Yes.

Because the recycle bin plugin is unaware of the share defined in the smb-extra.conf, it cannot configure the recycle bin for that share. I have suggested adding the 'rootshare' feature into Unraid and then the recycle bin plugin would configure the 'rootshare' properly. It can't be manually done because there are too many configurable parameters to the recycle bin.

Post on the support forum for the specific docker container.

Like this:

The UD Preclear won't allow preclearing just any unassigned disk. This was done for safety and yes you have to remove the partitions before a disk can be precleared.

UD is not just about preclearing disks. The reason for the destructive mode is that most of the time a user would not be removing partitions, clearing disks, or formatting disks and this is a protection to prevent accidental data loss. The way it currently stands is a good user experience, and It is not appropriate to enable clearing a disk when the destructive mode is disabled just so a preclear user doesn't have to install UD+.

This looks like an issue with Unraid assignments. Post a new issue on the appropriate forum and include your diagnostics. Whether or not the disk is precleared, Unraid should accept the disk and do what it needs to do to include it in the array.

UD used to show open files on the Gui, but I removed it because UD is already doing a lot of querying for this kind of information and it gets to the point where UD is slowing things down just to collect information. The log entry is very clear about open files. It states that the device is busy and can't be unmounted. I like the general idea, but haven't exactly come up with a slick way to show a user the problem(s). There are a lot of reasons for a failed unmount and UD would have to try to sort through that and show a user what's happening (or not happening as it were).

Thanks for the feedback. I assume you used the 'Enhanced' script? That script is great for notifications on the progress of a preclear. I had to do a lot of rewrite to the background task being used before that was called 'rc.diskinfo'. I had several instances where a preclear would hang. There was a lot of stuff duplicated by the Preclear Disk plugin that was already being handled by UD. That's why it is an add on to UD. It uses some UD functionality. Most of the work other than that was Gui stuff, and I felt it very important to only present disks that were actual candidates for a preclear, rather than all unassigned disks. I think in general you'll find this version a lot smoother.

We can't always assume that a disk being cleared is a precleared disk. I've added a shortened version of this in the clear disk dialog just to give a heads up if the disk is precleared. This would be the first step required before formating a precleared disk and would remove the signature at this point. Edit: This message only shows if the preclear plugin is installed.

After you do a full preclear, you need to clear the stats on the preclear status line before the 'Format' button is enabled. It shows up as 'Stop Preclear', but it removes the stats file once the preclear is finished. You still need to do that step before you can format a disk.

This is not needed for adding a disk to the array. Once a disk is preclered, it can be added to the array without formatting. This is in fact the preferred method for adding a new disk. I fixed it because there are users that might want to remove the preclear signature and format a disk for use in UD or on another system. It needed to be fixed for that. You shouldn't need to go through several steps to clear the disk.

Some Best Practices: Use the 'Enhanced' preclear script. Preclears will be paused if the array is shutdown or rebooted preventing hang-ups and unclean shutdowns. Once a preclear is completed, just add the disk to the array. You don't need to format the disk first. It is not recommended to run multiple cycles on a disk. One cycle will normally be enough to find a premature failure of a disk. UD Preclear has a max limit of three cycles. There is no reason to do more than that unless you want to kill your new disk. If you used the binhex Docker Container to preclear a disk and you want to then clear the disk so you can format it, do a 'Clear Signature' operation on the binhex docker and then clear the disk in UD. UD doesn't remove a binhex docker generated signature.

Unassigned Devices Preclear (UD Preclear) is an add on plugin to UD that allows you to manage preclearing disks either from the UD page or a separate page (Tools->Disk Utilities->Disk Preclear) meant to manage preclearing unassigned disks. This plugin is derived from the Preclear Disk Plugin authored by gfjardim. Disks that are candidates for preclearing will have a preclear icon next to the disk serial number in UD, and will be listed in the 'Tools->Disk Utilities->Settings->Disk Preclear' page. Only presenting unassigned disks that are eligible candidates for a preclear will prevent accidental data loss. You don't want to preclear a disk with data on it. For a disk to be considered a preclear candidate, it must have one of the following attributes: An Unassigned disk with no partitions. An Unassigned disk with a preclear signature and a partition with no file system. There are two methods available for preclearing: 'Enhanced' preclear written by gfjardim that supports pausing and resuming preclears. This is the recommended script to use. 'Docker' preclear is the preclear docker container authored by binhex using the latest version of the legacy preclear script. The advantage to using the docker container is that preclears are isolated to the docker container. This preclear script cannot be paused and resumed, and doesn't support notifications. The binhex preclear docker must be installed and running before this will show as a preclear choice. Both methods write a preclear signature that is accepted by Unraid. When a disk is precleared by UD Preclear, and subsequently installed in the array, Unraid will accept it as a cleared disk and not perform another lengthy clear operation. You do not have to pre-format the disk before adding it to the array. Unraid accepts a pre-cleared disk and will not do a clear when the disk in added if it sees the preclear signature. Preclears are done in the background so you don't have to leave any consoles open. The Tmux package is included so the preclears can run on background consoles. Please do not update the Tmux package through the NerdPack GUI. The latest version of Tmux has a bug and messes up the status display because the terminal size is defaulted to 24x80 and can't be changed. If you want to format the disk for use in UD or as a Pool device, click the red 'X' next to the preclear status line to remove the Preclear Log, then click the red 'X' next to the serial number to remove the preclear signature and all partitions. You'll then be able to format the disk. The choices for preclear operations are: Clear Disk - The disk is cleared and the Unraid signature is written to the disk. This will create an empty partition on the disk. Erase Disk - Erase the entire disk by writing all zeros. The preclear signature is removed. Erase and Clear Disk - random patterns are written to the disk and then zeroes are written. This is a good choice for a disk to be discard to ensure all traces of files are removed. Verify Signature - The disk signature is checked. Verify Disk - The disk signature is checked and the disk is verified to be zeroed. Post-read Verify - Perform a post read verify to check the disk. This is not available in the 'Enhanced' script. Clear Signature - Remove the preclear signature from the disk. This is not available in the 'Enhanced' script. You can follow the status of preclears in UD, on the UD Preclear page, or by hovering your mouse on the preclear icon in the Unraid footer. While preclearing disks is not necessary with the current Unraid versions, users get a sense of confidence with pre-testing their disks. When the original preclear script was written, Unraid would take the array off line while it cleared a disk if it was not precleared. That's why the script is called 'preclear'. In the old days, preclearing a disk would prepare it for the array and Unraid would not take the array offline when a new disk was added. UD Preclear is a direct replacement for the Preclear Disk Plugin. You will have to remove that plugin before the UD Preclear can be installed. UD must be installed before UD Preclear will install. Go to 'Apps' and search for Unassigned Devices Preclear and install it from there. UD+ is not necessary for preclearing, although you'll need it to delete partitions and format disks. Because UD Preclear uses some features in Unraid starting with 6.9, it is not backwards compatible with any Unraid version older than 6.9.

I've put some time into this issue and have it resolved. I am using a different utility now to clear a disk and it does remove the preclear signature and partition created by the binhex preclear docker. The fix will be in the next release.

The timeouts with 'df' are most likely network issues. The 'df' command is used to get the stats on the remote share - size, used and free space. The 'df' command is prone to hanging which is why UD times out the command if it is taking too long. Post your diagnostics zip file for further help.

It looks like you need to go to the Windows computer and share the complete 'D' drive. I didn't have mine shared and that's probably why it didn't work for me. I don't want to share my complete drive, so you'll have to give it a shot.

I'm having the same issue. I'll have to look into it.

You're trying to mount the D drive?

I did a little research into this and the binhex preclear does in fact write a MBR signature that UD can't clear. So what you did was the way to get the partition cleared with UD. I don't think I want UD to get involved with removing the preclear signature before removing the partition. For now the procedure you went through is how to remove the precleared partition with UD.

If you look at the syslog it will tell you why it won't mount. If you don't see anything in the log, post diagnostics.