dlandon

Don't think so. Did you hot plug this into a sata port? Maybe static electircity got it? If it's a backup, don't you have the original files still?

Just released a new version of UD. You can now create a rootshare in UD and name it like you want. It will also work with the Recycle Bin plugin. You need to be sure to turn on the 'Enable on Unassigned Devices?' in the Recycle Bin plugin so the recycle bin is enabled on the rootshare. This functionality replaces the modifications to the smb-extra.conf to make a rootshare.

You're getting a duplicate device ID on /dev/sdb. Try going to the UD settings and change the UUID on that disk. It's towards the bottom of the page.

There is a new file manager plugin that replaces the built in file browser and has a lot more functionality. It makes recovering files from the recycle bin a lot smoother. Go to CA and search for "File Manager'. Install the Dynamix File Manager. Once you've done that, you can click on the browse icon in the recycle bin plugin shares page and you'll see what you can do.

It's not in RC3, but I am adding the rootshare capability to UD and it will work with the recycle bin.

Some work was done in RC3. Give it a try.

It comes from the devX designation not being consistent. Unraid changes the devX at times and because the disk tracking is by devX and not serial number, Unraid re-reports the error thinking it's a change on a new disk. I've put this on the list of bugs in Unraid.

Remove the partition and you can then format the disk. Go to the UD settings and enable destructive mode and then you can remove the partition.

That disk doesn't have a file system. 'FS' is blank.

Worked for me with two. Did you select all the disks? Hold the Shift key and highlight each one to the precleared. Shift key and down arrow to highlight them. Or mouse click the ones to preclear while holding the Shift key.

Could this have something to do with this issue? Mar 6 19:59:21 tdm emhttpd: shcmd (83): xfs_growfs /mnt/disk1 Mar 6 19:59:21 tdm kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Mar 6 19:59:21 tdm root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device Mar 6 19:59:21 tdm root: meta-data=/dev/md1 isize=512 agcount=32, agsize=137330687 blks Mar 6 19:59:21 tdm root: = sectsz=512 attr=2, projid32bit=1 Mar 6 19:59:21 tdm root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 6 19:59:21 tdm root: = reflink=1 bigtime=0 inobtcount=0 Mar 6 19:59:21 tdm root: data = bsize=4096 blocks=4394581984, imaxpct=5 Mar 6 19:59:21 tdm root: = sunit=1 swidth=32 blks Mar 6 19:59:21 tdm root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 6 19:59:21 tdm root: log =internal log bsize=4096 blocks=521728, version=2 Mar 6 19:59:21 tdm root: = sectsz=512 sunit=1 blks, lazy-count=1 Mar 6 19:59:21 tdm root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 6 19:59:21 tdm emhttpd: shcmd (83): exit status: 1 Mar 6 19:59:21 tdm emhttpd: shcmd (84): mkdir -p /mnt/disk2 Mar 6 19:59:21 tdm kernel: XFS (md1): EXPERIMENTAL online shrink feature in use. Use at your own risk! It seems when the xfs_growfs doesn't have enough space on the disk, the shrink feature kicks in.

I've just applied a fix for the dd_output_complete file error. If you are running a preclear, stop it, apply the UD Preclear update, then resume the preclear.

If there are issues with the UD Preclear, post there so it can be looked at and fixed. It has not come up there yet, but I'll have a look and see if there is a problem. If the binhex docker container is installed and running, it is an option in UD Preclear for preclearing disks. I don't recommend the cli as it is too prone to errors.

I'm not sure what your issue is, but it works fine for me on 6.10-rc.

Updated version available.

Does the status in the upper right hand corner of the file activity show 'Running'?

What's a general share, and how were you opening them? Did you try my test to see if it would log that?

I don't see anything in your diagnostics that would be an issue, You are creating file activity that would be logged? Try creating a file on one of your shares and then save it. Does it log that file activity?

You're doing a post read. I didn't catch that one because I only concentrated on the write. I'll get a fix out today.

The error message is related to notifications and does not affect the disk preclear. Note: You can stop the preclear at any time, update the plugin, and then start a preclear and select resume. It will pick back up where it left off.

It's not normal. I'll get a fix released soon.

From what I remember there is no way.

Yes.

This has been sorted out in the post link mentioned in the original post here. It turns out to be a hardware problem.

Scroll down the SMART report and you'll see the disk errors I'm talking about. Here's the complete report: WDC_WD2003FZEX-00SRLA0_WD-WMC6N0H9MZL6-20220221-0901 cache (sdk).txt