trurl

Why? If all you are trying to accomplish is a virtual host there are probably simpler solutions than unRAID.

Is your sig correct? unRAID 6.1.6 If your version is that old, and your plugins aren't all up-to-date, then possibly that is the problem. There was some jockeying for position between Stats, Apps, and Users with various versions of unRAID and plugins. Personally, I take Users and Stats both off the Header since they aren't used that often.

I overlooked the subject of the thread and was just responding to kizer's single post. Duh!

root@unSERVER:/usr# which inotifywait /usr/bin/inotifywait root@unSERVER:/usr# which inotifywatch /usr/bin/inotifywatch root@unSERVER:/usr#

inotify is built-in now.

Yes. Be sure to read it all before starting the upgrade and ask if you have any questions.

It's in Tools. You can move it to its own tab in its settings.

Plex does

They shouldn't, but some make mistakes, and some don't really understand volume mapping.

Misconfigured dockers.

Why do you care how fast your backup runs? Isn't it unattended? I don't cache much because most of my new data is either from downloads that are unattended, or from scheduled backups that are unattended. Much of it happens in the middle of the night and the data has parity-protection immediately.

Display of sigs is optional on this new forum platform. If you want to see them (recommended) click the down-arrow at upper right then Account Settings - Signature - View Signatures.

I don't know if a previous version is available for download. If you have a backup of an old version of the .plg file you could just put it in your config/plugins folder. And of course, there are preclear script(s) you can use like we used to do before we had the plugin.

Make a backup plan soon. You don't have to backup everything, but you must have another copy of any important, irreplaceable files on another system.

Is it really /mnt/cache/appdata, and not /mnt/cache/appdata/transmission? Each docker should have its own separate folder within appdata.

Delete the orphan and use Community Applications to add plex from you Previous Apps.

Update unRAID

You are posting in the wrong thread. There is a thread specifically for each docker. You can get to the transmission support thread by clicking on its link in Community Applications.

The faster method as outlined leaves you without parity protection until after the data is consolidated. Do you have backups? One thing the wiki doesn't mention is formatting the new large disk. unRAID will give you the option to format that disk after adding it when you start the array. Since that method doesn't involve rebuilding any disk, you can format that disk to any filesystem you want. You could also do the "safer method". I mentioned Turbo write earlier in the thread, but I'm not sure how much advantage that would give since there would be reads of the source data mixed in with reads of all disks to calculate parity writes. Of course, since you would be rebuilding this first large disk, it would be the same filesystem as the original disk, so you would eventually have to empty it and reformat.

All New Config does is let you change disk assignments and rebuild parity. Why would you need to do that?

And this method has the advantage of write speed, at the expense of having no protection until parity is rebuilt at the end. Turbo (reconstruct) write would get you some of the speed back while keeping parity.

This is exactly correct. Format is a write operation. It writes an empty filesystem to the disk. unRAID treats this write exactly as it does any other, but updating parity from the written data. So after the format, a rebuild would result in an empty filesystem.

You can make a large pool out of small SSDs.

I think he does have a point here. If you move the data to cache as I was thinking, then the data is unprotected while on cache. Parity would rebuild an empty disk. Maybe I'm not understanding what you have in mind.

Have you done a memtest?