trurl

Sorry, I had forgotten about the Auto Turbo Write plugin. Still recommend you read the linked post to get a better understanding of what turbo write actually is.

Turbo Write isn't a plugin, and your question doesn't really make much sense. Did you bother to read the linked post?

When you setup again, do you also have to rescan your library, or does it remember your media? Are you sure you have your plex appdata mapped to persistent storage?

Dashboard - System Status:General - flash log docker

Radio share include only disk1, problem solved, no need for disk shares.

Lots of other useful posts in that FAQ regarding cache pools.

Often this can be accomplished with a BIOS setting. Whether it is a good idea or not is debatable. I usually prefer to be there when my server boots so I can take a look and make sure everything is working well. Some even go so far as to not have the array autostart on boot until they have checked on it, to make sure all the disks were found, for example. Which reminds me, I need to take care of this myself so my housesitter can watch Plex without complication while I'm on vacation. Seems we often get a power out in this situation.

Have you done a memtest? Maybe something for you in the Ryzen thread.

What version of unRAID are you using? Complete diagnostics zip.

Since shutdown will spin up all drives, checking power during idle times isn't very useful.

Parity check has already been covered by others in the thread, but parity errors by themselves should not cause the other symptoms. It looks like you have told FCP to ignore unclean shutdowns. I guess this is because you currently are having issues that force you to hard powerdown frequently. After you get parity fixed, you might try putting FCP in Troubleshooting mode so we can get better diagnostics if it hangs again.

This forum is only for unRAID support. Linuxserver.io has its own forum for supporting their dockers on other platforms.

I use the one from this support thread we are posting in.

Nobody is suggesting this. How did you come up with that number anyway? There are some deals that have been posted on the forum recently for 8TB drives for $200 or less. One 8TB drive can replace 4 of your 2TB drives. 7 x 8TB could replace all 28 x 2TB. Then you would only have 7 drives to power, 7 drives to troubleshoot, 7 drives that might fail instead of 28. In fact, you could convert one of your parity to data since you would only have 7 data disks, and just buy 6 x 8TB. And as mentioned, there is no need to do it all at once. So, you could do the complete conversion for about 1.2K, and the expenses and troubles of finding cases and power supplies to support so many drives would be gone. You mention using this system for graphics work. Did you know that unRAID doesn't stripe data? There is no performance benefit from multiple drives, since any file is read from only one drive.

You are responding to a post that is nearly a month old. If you still have a question about this, it was asked and answered on Monday in this very thread.

Not really pertinent to this thread or your question, but mapping drives is a security risk itself, and for more than just ransomware. Malware doesn't even have to be network aware to attack mapped drives. Most applications can browse the network these days. I never map drives but can easily open and use files on the network.

But there are some things in your posts that sound like you are possibly on the wrong track. It might be cheaper in the long run to upgrade the disks. 2TB drives aren't very cost effective these days. More drives mean more problems. You already have a problem powering them. More parts just means more things that can fail. Larger drives are cheaper per TB and possibly faster due to data density. Do you know the only reason to have a parity disk larger than any one of your data disks is so you can eventually replace the data disks with larger ones? unRAID allows you to mix disk sizes as you want. There is no need to have all the disks the same size, or to replace all the 2TBs at once. And there is absolutely no reason to have a parity disk that is larger than any data disk you will ever use.

There is Help for most pages in the webUI. The Help button at upper right is a toggle. Here is a more detailed explanation of the Use cache setting:

This should be fine. You should make the appdata share cache-prefer and it will be just like the appdata share created for new installs.

Why is the application referring to a path in /mnt/user? You must have something wrong with the way you have configured the application. Do you have any other working dockers?

Possibly a problem with your flash. Tools - Diagnostics, post complete zip.

See the 2nd page of the thread linked earlier