trurl

Unimportant. When you start the array Unraid looks for your license .key file. An annoying side effect of Apple ecosystems is putting a bunch of hidden (.) files everywhere. I don't know why. The message is because Unraid finds ._Pro.key, decides it is no good and then it finds the actual Pro.key file. Not sure what memory message you were seeing, but it does suggest the question. Have you done a memtest recently? I don't see any mention of I/O errors in syslog. As you may have noticed if you were looking at syslog, sometimes hours go by with nothing to report. Do you see anything in the errors column on Main? I notice your disk1 is 100% full. Don't know if there might be any performance issues associated with that or not.

Assuming you haven't actually attempted to rebuild a data disk while you had incorrect parity then your data should be fine. Each of your disks is independent, and bad parity doesn't have any effect on the data on those disks. But, when you need to rebuild a data disk, parity must be correct, and every bit of parity plus every bit of ALL other disks must be reliably read in order to reliably rebuild a disk. This is why we are always concerned with the health of EVERY disk in the array, regardless of how important its data is. Every disk is required for rebuilding any disk. yes The only correct answer is zero, and you need to get it to zero somehow. If another correcting parity check still doesn't fix it then you need to get to the bottom of the problem.

What squid said. Don't ever try that again! And please, please, when you have something new to say, don't edit an old post and expect us to find it. If you have something new to add to the thread put it in a new post.

no You really should have been trying to get to the bottom of this before now. The only successful parity check is one that has exactly zero errors. If you lose a data disk you won't be able to reliably rebuild it if parity isn't completely correct. Have you done a memtest recently?

Of course the whole purpose of SAB is downloading, which is not only reading but also writing. Is it writing to the same disk plex is streaming from? I don't know if that plex log will be useful to someone on this forum or not. We are mostly just plex users here. Even the plex docker authors are just packaging software someone else wrote. The reason I said was because of the details of what other processes were doing with which disks on which sectors and so on. Literally more than we will know. I suppose its also possible that you have some disk I/O problem you haven't mentioned or even noticed. That might show up in your Unraid Diagnostics.

The assignment for each disk is clearly specified as part of the SMART filename for each disk in recent versions of diagnostics.

Parity rebuild and 2 streams going at the same time? Not only is that going to slow down reading by plex, it is going to slow down your parity rebuild. You do know that rebuilding parity must read all the disks don't you? And in the meantime, 2 different plex streams is asking for data on different sectors than those the parity rebuild is asking for (and even each other if they are on the same disk), causing the disks to thrash as it tries to move the heads all over the place and wait for the platters to spin around to the correct place. Which specific stream (including parity rebuild) gets the most noticeable performance degradation may not be predictable without a lot more information than we will know.

Well I haven't seen anything suspicious in anything you have given us so far. As for plex, you might try this:

He double-posted. The screenshots did make it into the first copy just above that one.

Since you don't have cache, where is your system share? Go to Shares page and click Compute...

Are you talking about the latest changes to this plugin, or did you just now discover this plugin which has existed for 2 years? It will allow you to set a custom schedule but I just use the daily setting which should be enough for anybody.

Not really. Did notice some wrong csrf tokens in the syslog. This typically means you left a browser open somewhere when you rebooted. Doesn't look like you have cache. Is this true?

A photo from the monitor might also help when it happens again. Yes, diagnostics aren't saved except in Troubleshooting mode, and all logs etc are lost on reboot since all the OS files are in RAM.

Yes, I have taken to spelling it out like this so we don't get links (sometimes to unknown filesharing sites) or lots of separate files from the zip or an attachment by unexpected edits of the first post: I also asked for this:

Nothing obvious. You might try Troubleshooting Mode in Fix Common Problems to capture logs closer to the crash.

Go to Tools - Diagnostics and attach the complete zip file to your next post.

No effect on cache use except Turbo would improve mover performance.

First link in the Docker FAQ:

Sounds like you have a network problem. In the Unraid webUI, on the Dashboard page, at lower left there is System Status section. At the bottom of that section it shows your network statistics. What does it show for your speed?

OK, read it again and it seems you are not actually rebooting, just starting the array. If Unraid thinks parity is invalid it is always going to do a parity sync when you start the array, so maybe that is what is happening. In addition to Diagnostics post a screenshot of Main - Array Devices and Main - Array Operations.

Likely you have flash corruption or flash has disconnected, and that is preventing the start/stopped status from being written to flash. So every time you reboot it is doing a parity check due to unclean shutdown. That is, of course, assuming you are actually doing a clean shutdown and not just shutting it off. Diagnostics will give us a better idea.

Maybe. In a way. Those are actually mount points for vdisks used by Docker and VM Services. Cache is the default location for those vdisks assuming everything else involved is set to defaults. It depends on the paths you have specified in Docker Settings and VM Manager Settings. It also depends on what the settings for those paths are if they are on user shares, and also whether or not cache was available when they were created. In any case, unrelated to the discussion of this thread.

First link in the Docker FAQ:

Unraid is based on slackware linux, but it isn't a full linux installation and isn't intended to be a general purpose linux system. Plugins, dockers, and VMs are the preferred way to add additional functionality. Have you installed the Community Applications plugin? It is the best way to find and install dockers and additional plugins. Perhaps Nerd Pack plugin and Dev Tools plugin might have something for you also. You can find them on the Apps page after installing Community Applications. Looks like git is included in Nerd Pack.

Is it really "the exact same"? You are using Unraid 6.6.1 just the same?