trurl

The data should already be in user shares if the disks are in user shares, assuming all the files are within a folder. All top level folders on any array or cache disk is automatically a user share. If you didn't create it in the webUI it is still a user share but it has default settings. You should never mix disks and user shares when moving or copying data. Linux doesn't realize the source and destination might be the same file so it will try to overwrite what it is trying to read. That is one of the reasons you shouldn't even use disk shares at all. I recommend you turn off disk shares, or set them to auto, which will not share any disk that is in user shares. That just applies to how they are accessed on the network though. Krusader, for example, depending on how you have it configured, will be able to access the user shares and the disks. Don't mix disks and user shares!

There should always be exactly zero parity errors. If that is not the case you need to consider why. And if you do correct parity errors, you should run another parity check to make sure you have exactly zero parity errors as a result. How can you expect to rebuild a data disk if parity isn't valid? After you get your other problems fixed, be sure to save that original disk in case the rebuild has problems. Nothing obvious in that syslog. Have you done memtest? Have you done these Ryzen tweaks?

Where exactly are you looking? I would expect that relative file path "test.test" to be inside the docker image and not anywhere you could access it from outside the container.

In future, go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post. It includes SMART for all attached disks, syslog, and many other things that give us a more complete understanding of your situation. There was really no need to follow the more complicated parity swap procedure since you had no failed disks. You could have just replaced and rebuilt parity, then added the old parity to a new data slot and let it clear then format it. But, this way will be even faster. Just go to Tools - New Config, assign all disks as you want them, and rebuild parity. It should show only the new data (old parity) as needing formatting. Let us know if any problems or questions.

I assume you mean /mnt/user/Movies, etc. This isn't really about plex and how plex works. It's about how all dockers work. The "volume mappings" are just setting up a correspondence between paths on the host and paths within the "virtual space" of the container. Just as a location on a road map corresponds to a place in the world. The word "map" probably confuses some, but it is often used like this in other contexts such as mathematics. Port mappings are similar. If you understand mappings you are most of the way there to setting up any docker.

User shares are simply the top level folders on all disks. So if those disks are allowed in User shares their top level folders will be user shares named the same as the folder. Normally you will have multiple disks in user shares and their top level folders by the same name will be in the same user share. This is how Unraid allows folders to span disks. I'm not sure how you got it set up so those other disks aren't already in User shares. Go to Settings-Global Share Settings and make sure you don't have any included or excluded. Include means Only, Exclude means Except. If nothing is specified all are included.

Free support is from the community on the forum. Most of the people you will encounter here on the forum are just users like yourself, trying to help each other. If you want you can negotiate paid support with limetech. I don't use VMs since all my needs are taken care of with docker, but I'm sure there are a lot of users successfully using Linux VMs on Unraid.

The plexinc support link just goes to the plex forum. But that is probably the best place to ask this plex question. I'm not sure the "Unsupported App Store" still works with plex but you might be able to put the plugin in manually. I think there is a good chance the plugin won't work even if you do get it installed since it is trying to scrape from Audible, which may be a "moving target" for that purpose.

Did that parity check complete without any errors? You don't want to rebuild a data disk unless your parity was completely valid. If you don't know for sure there were zero parity errors on that last check, you can see by going to Main - Array Operation and click on History. Do you have any SMART warnings on the Dashboard for any of your disks? Syslog is after reboot, of course, so we can't see what happened. Setup Syslog Server so you can get syslog saved somewhere so you can post it if it happens again.

Nobody is going to download each of those individual files you attached. Attach the complete diagnostics zip file to your NEXT post.

If anybody has anything at all to say to this, please DON'T respond to this crosspost. Go to the linked thread instead. In fact, since this is so old I am going to go ahead and lock it. @kennelfort Please don't crosspost. It makes it impossible to coordinate our responses when you have a discussion about the same thing going on multiple threads.

I have split your post into its own topic since it has nothing to do with the (deprecated) limetech docker repository.

Instead of syslog, we usually prefer diagnostics, which contains syslog and many other things that give a more complete understanding of your situation. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Also, if you upgraded from a version before 6.5, then there were a number of things you should have taken care of before doing the upgrade. See here:

Adding disks in the normal way will make Unraid clear them so parity remains valid. You will have to New Config and rebuild parity if you want to add disks that have files on them. As for getting plex to see them, depends on how you have plex set up. If plex was accessing them from tower2 then I assume you had plex mapping a path to an SMB mount from Unassigned Devices. If you change that mapping so it has a different Host path and the same container path, then it should work without doing anything else. Ask more questions if needed.

Not sure what you intended since that link just comes back here. Perhaps you meant this: Reboot and get us your diagnostics before it crashes.

In addition to that Turbo Write topic I linked, here is a wiki link to a good overview for a better idea of how Unraid (IS NOT RAID) actually works: https://wiki.unraid.net/UnRAID_6/Overview

Parity is not even involved in reading data so you can see your expectations have no basis.

I assume this is the write speed you are talking about. See here:

I doubt you would get much improvement in speed, certainly nothing like what you seem to expect. And others in this thread have already explained why this is a bad idea.

Please attach your Diagnostics to your NEXT post instead of linking to unknown external sites. Thanks

I thought it more appropriate to take this in a separate thread and since you had actually made a new thread I got rid of your post in that other thread. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.

You can go back to default network settings by deleting or renaming config/network.cfg on flash and rebooting.

Go to Settings - Disk Settings and disable autostart. Then just use the power button to kill it. Remove that bad disk you have assigned as cache for now. Reboot, and if that seems OK, start the array and post new diagnostics. Probably you will get a parity check for unclean shutdown.

You can edit your own first post in the thread and change the title to show that it is [SOLVED]