trurl

I used to use that one myself, but there is a popup window into the command line builtin now on the main menu bar.

This is it:

Sorry, that's what I meant. Corrected in my post above.

root definitely doesn't survive a reboot on stock Unraid. What plugins do you have?

The biggest boost in writing to the array is Turbo (reconstruct) write. See this thread for an explanation of the 2 different methods for updating parity and their tradeoffs: https://forums.unraid.net/topic/50397-turbo-write/ There is a plugin that enhances this somewhat by automating that setting. Search the Apps page for turbo. And, you should make sure your dockers and VMS are running on SSD cache instead of the array. You do this by making sure that appdata, domains, and system shares are all on cache with nothing on the array, and configured to stay on cache (cache-prefer or only). You can see which disks each user share is using by going to User Shares and clicking Compute... for the share. What commonly happens is people will enable dockers and VMs before actually installing cache, so they get created on the array and get stuck there because open files can't be moved.

Interesting. So USB drives and no parity? That might work for some limited uses.

Here is the way unclean shutdown actually works, down in the details. When Unraid boots up, it checks whether or not the array was stopped previously by reading that start/stop status from config/super.dat on flash. When Unraid stops or starts the array, it updates that status on flash. If for some reason Unraid shuts down without updating that status, you get a parity check since the last status shows the array was already started (not stopped). One thing that can cause that status to not get updated is if it actually powers off before it can update the status. That is what happens if you "hard" shutdown. Another thing that can happen is the flash drive is not mounted or not otherwise writable for some reason. This often happens when people are having problems with flash and it gets dropped. This seems to be more common for USB3 ports. And, Unraid will eventually timeout after a few minutes and shutdown anyway even if it can't stop the array.

I doubt you are running Unraid on Atomic Pi. Did you just find this thread on google? Or are you actually using Unraid, the purpose of our forum?

And this basic difference is the tradeoff between the 2 systems. RAID5 is always going to be faster. It is all about the disk I/O, not about the processor. But RAID5 disks cannot be used by themselves. If you lose more than parity can recover from, you lose it all. An individual RAID5 disk has no usable data. Each disk in Unraid can be used by itself. If you lose more than parity can recover from, you haven't lost it all. Each data disk in the Unraid parity array has complete files that can be easily accessed on any Linux. Also unlike RAID5, Unraid allows you to mix disks of different sizes in the array, and allows you to easily replace or add a disk without rebuilding the whole array.

Got nothing at all to do with the CPU. RAID5 stripes data across disks so it read/writes multiple disks in parallel to access the data. Unraid read/writes a single disk if accessing the array, possibly uses multiple disks in the cache pool depending on how that is configured (which you don't specifically mention). According to the specs you listed, one of them has and the other has so not at all the same with regard to the very thing you say you were testing. A cache-yes share writes all data to cache if cache has sufficient capacity. Then it just stays there until the next time Mover runs. The default Mover schedule is once per day in the middle of the night. I suspect this caching model is very different than QNAPs

👍

You will have to use a different flash drive. Probably that one doesn't have a real GUID is the reason it is blacklisted. The Globally Unique Identifier is required for the Unraid license. I recommend a USB2 flash drive of a well-known brand, larger in size than that one so it won't overheat, but you don't really need more than 4GB capacity. And I recommend booting from a USB2 port. There is no benefit to faster larger boot flash for Unraid since it is mostly only accessed at boot time to load the OS into RAM.

Post your docker run command as explained at the very first link in the Docker FAQ

That looks like the screenshot from your Windows client instead of from the server. I just opened mine and it looks like you can do it from there but I always just use the webUI to manage plex. On the left, it is showing your pinned content. So far you only have the builtin web content (I actually unpin most of that). Click on MORE > That will show all of your content, and at the top will be your servername. There will be a + next to it (mouseover if you don't see it). Click that and it will bring up the Add Library wizard. Just work through that, using the container paths from your docker mappings to find your media. In your case you just have the one mapping, which gives your video share at /media inside plex.

That looks very similar to mine. Go ahead and Apply.

Not having used Drobo, I'm not entirely clear on your scenario. How does Drobo "attach directly"?

Have you read any of this thread you have posted to? Lots of other posts about this. Here is one from just the previous page: https://forums.unraid.net/topic/38582-plug-in-community-applications/?do=findComment&comment=795789

On mobile now so can't look at Diagnostics. Don't do anything without further advice.

Not sure I understand. Have you ever used Plex? Did you try to add any of your media? Adding media in Plex is something you do from within the Plex application, regardless of how you have mapped it in the docker. Maybe a screenshot of what you are seeing in Plex would help me better understand.

It's working for me. Did you actually read that first popup? It explains what the problem may be and suggests possible fixes. Here is just those portions of that message:

I must admit I don't know much about QNAP, and you haven't told me enough about your testing to make much sense of it. How is cache even involved? If this is strictly a transfer test involving only cache, why didn't you make that clear? If it isn't only about cache, then what does cache actually have to do with the testing? Is the QNAP using RAID of some kind? Do you know that Unraid is NOT RAID? Do you know how caching in Unraid works? Speed isn't the primary design criteria with Unraid.

yes, then click the Add button and post another screenshot of the Add Container page.

Diagnostics?

If you select Shutdown from the webUI then Unraid will stop the array before shutting down. If by shutdown you just mean holding the power button that is going to result in a parity check on next boot due to unclean shutdown.

Possibly your work network won't allow it.