trurl

Why? Did you read the thread Frank1940 linked? Did you try anything discussed in the thread?

Krusader is a linux file manager, and it probably works fine if you are actually running it on a real linux desktop. I think the problem comes from trying to run a linux desktop inside a docker. I don't know if it can be fixed, but probably the support thread for the Krusader docker in the unRAID forum is the place to ask.

But this is not what wgstarks said he did. He said he used a UD formatted disk to replace/rebuild another disk. How or even whether a disk is formatted before it is used to rebuild another shouldn't matter, should it? You could use UD to format it NTFS and it wouldn't matter because the rebuild is going to have whatever filesystem the original had.

Maybe I'm missing something here, but if a disk is used to replace/rebuild another disk in the array then its history, such as whether or not it was formatted in UD, doesn't matter, does it?

Just to elaborate, anything that is not strictly a read is a write operation. Deleting files is a write operation, and formatting a disk is also a write operation. Anytime you perform a write operation on a disk in the parity array, parity is updated. So when you format a disk that is part of the parity array, parity is updated to remain in sync with that write operation.

When you go to New Config, you will have several options about what assignments to retain. I recommend choosing Retain All. Then you will have everything already assigned just as it is, and you can make changes from that as a starting point. Then after you have everything assigned like you want, start the array and let it build parity.

No. If by the second option you mean: That is done by going to Tools - New Config. There you will be able to keep/change any drive assignments. After New Config, the default is to rebuild parity. So you would NOT check the box saying parity is valid.

No need for GUI mode to run mc. And no point in running it on PC.

mc (Midnight Commander) is a built-in file manager you access from the command prompt. Google it.

Just copy the plugin files to another place on your server, then use mc from the command line to move them into plex.

Probably something to do with the user you are letting windows connect with. See here:

There isn't really a quick way. You either have to zero the disk while it is still part of the array so parity can be kept in sync, or you have to New Config without the disk and rebuild parity.

Logs are in RAM so don't survive a reboot. What device do you think should be constantly written to instead? Fix Common Problems plugin will periodically save logs to flash if a user thinks it is warranted. Whatever the intentions were I think this Plex docker thread needs to move on.

Sorry if this comes off wrong also, and maybe I missed other things that have transpired, but at least part of jonathanm's post wasn't rhetorical. Maybe the anonymizer can be improved, but there are a lot of things in the logs. Some of it seems benign to me and others here, and apparently there are others that disagree.

You have replied to a thread that is nearly 1 year old and is for unRAID 5 and older. What version of unRAID are you using?

Diagnostics?

Linux Screen Video Tutorial

When unRAID rebuilds a disk, it reads parity and all the other disks and uses this data to calculate the data of the missing disk. When you read an emulated disk, it does the exact same thing, calculating the missing data from parity and all the other disks. When you write an emulated disk, it reads parity and all the other disks, calculates the parity change that would happen due to the write, and writes parity. So even writing when a disk is missing or being rebuilt, still results in data that can be calculated by reading parity and all the other disks. Have you seen the wiki about how parity works? It isn't very complicated and unRAID makes a lot more sense if you understand parity. https://wiki.lime-technology.com/UnRAID_6/Overview#Parity-Protected_Array

Extremely unlikely a bad flash would cause reboots. unRAID probably isn't even accessing the flash in the middle of the night, since the OS is loaded into RAM at boot, and after that flash is typically only accessed when you save changes in the GUI. Do you have an UPS?

Restarting the docker will get the latest version unless you have specified another version.

Study this and see if you can adapt

The emulated disk can be read and written just like a real disk. It won't be very efficient since all other drives are used to emulate the disabled disk. Why do you want to do this? Rebuilding the disabled disk is the normal way to keep that data.

2 parity is all that's supported and I personally wouldn't trust more data drives with only 2 parity. Do you really need that many? Drives are pretty large these days and you can get a lot of capacity without using a lot of drives. I always recommend people only add drives as needed. More drives just means more opportunities for problems.

Do you have unRAID Notifications setup? It is very important that unRAID be able to notify you by email or other agent if it detects problems. Many people have allowed themselves to get multiple disks with problems, for example, because they didn't have unRAID configured to notify them. I haven't used this plugin lately, but I assume it uses unRAID's builtin notifications to notify you, which can't happen if you haven't configured unRAID Notifications.