trurl

Parity check is not something that would be improved by changing filesystems, since parity operations deal only with the bits and not the files.

Unless it appears as a SATA or IDE device I don't think unRAID will use it for cache. You might see if Unassigned Devices will allow it to be mounted outside the array.

Do you think this is caused by one of the Dynamix plugins in the first post of this thread?

I'll try this in a couple of days when I do my monthly offsite backup. Worked OK last month. Just finished my montly backup with this, and it worked. It is a little different than I remember from last time though. There is no checkbox for running the script in the background, I assume because it always runs in the background now. Also, when I push the Mount button, it does mount and run the script, but the Mount button just sits there "spinning" until the script completes. Not sure that is expected behavior or not, or whether I would even consider it a bug, but it might be a little disconcerting if you aren't aware of what's happening. Once the script completes, the button does show the drive is mounted. My script doesn't take any action on the unmount, so that happens quickly. Don't know if it would also "spin" if the script did anything or not.

+1 All the other plugins on the forum are just WIP too.

Good plan on the new drive. Then you can try to clear the pending sectors on the other drive by preclearing it.

Screen also requires utempter, so find that one too. Put them in the extra folder on your flash drive and unRAID will automatically installpkg them when it boots. Or see here

Multiple cache drives are only supported as btrfs raid, so they cannot be used separately for different purposes.

I'll try this in a couple of days when I do my monthly offsite backup. Worked OK last month.

Have you tried scrub?

Was the disk disabled, showing a red X next to it? If so, then what you did was copy the data from the emulated drive. unRAID will not let you format a disabled disk.

docker exec -it docker-name bash will give you a bash command line inside a docker.

I'll get 3tb of data onto a drive and add it to the array and let you know. That will tell us more. (converting from rfs to xfs and the formatting was a pain prior to today) I'm converting the last 2 drives from RFS to XFS. Precleared 2 disks and using the newly available format command in unassigned devices, I made them XFS. I now had 2 3tb drives formatted XFS with Unassigned Devices and I rsynced data onto them filling them up without issue. Now I just needed to get them into the array and pull the RFS disks out. I then swapped them with the 2 RFS drives that were in the array and restarted the array with these 2 new drives. Now unRaid complains about these 2 being unmountable disks. Unassigned devices works with them fine, but they aren't quite kosher for unRaid array devices. Some minor format difference?? Did you do New Config? That is the only way you are going to get unRAID to accept these new disks as part of the array.

Detect requires perl be installed. Search this thread.

See post #21 in this thread

What version of unRAID do you have?

Set appdata to be a cache-only share.

Right. I don't manage files usually from the disk share, but I was just testing it based on the text from your earlier post: Haven't tried it, but in theory if the folder is created at the root of the drive, it will automatically become a user share. Probably a hidden share. I'm not sure exactly how this would work. I may fire up the test server and play with it. I thought I'd test it and report back to save you from having to fire up a test system. I did take a minute to give it a go. Yes a hidden share is created. Any folder at the array disk level will end up being collected into a shared folder mounted at /mnt/user/.Recycled.Bin. This is what unRAID does. What everyone needs to keep in mind is that with the latest changes I've made, every share - user shares, disk shares, flash, and devices mounted with unassigned devices will all be smb shares and each will have its own .Recycled.Bin folder. Those on the array disk devices will be collected into a hidden .Recycled.Bin share mounted at /mnt/user/.Recycled.Bin. All share .Recycled.Bin folders will be browseable in their respective shares and not collected into a hidden share. The .Recycled.Bin folders in the shares will be treated like any other folder on the share with respect to user access and cache operations (cache only, etc). The webgui only browses the /mnt/user/*/.Recycled.Bins. These are the files of most interest. OK, I can't help myself drilling down on this some more. What happens if a file is deleted from the .Recycled.Bin share? Does it get saved to a .Recycled.Bin folder within the .Recycled.Bin share? So, /mnt/user/.Recycled.Bin/.Recycled.Bin/ ?

You need to install perl to detect. It was removed from stock unRAID. Search this thread for perl.

Yes commas to separate users. I'll fix the help text to explain that better. You would access the recycle bin in Windows explorer by using //Tower/.Recycle.Bin Actually, you access the recycle bin in Windows explorer by using \\Tower\RecycleBin

NTFS

OK, that looks like it is indeed your parity disk. It was the emulated part that was throwing us off, since there is no data to emulate on parity. The legend is not really correct in the case of a disabled parity disk.

Yes, definitely post a screenshot. Your description doesn't seem right and we need to be very clear before taking any action or you could lose data.

See the example script in the first post of the thread. You supply your own code for the "events". In my case, I use the 'ADD' event to start an rsync script I have.

Appears to be working for me. One oddity I noticed though. When I delete a file from my flash share, it creates the directory structure for it, but no file. Deleting from my normal user shares works as expected. Maybe something to do with the /boot path vs the /mnt path. Not worth worrying about if you don't see an obvious fix.