trurl

👍 Please upgrade

I'll leave out the part of your question about "when the system powers off" because I can't make any sense of it. There is a process called Mover that runs on a schedule. Daily in the middle of the night is the default but you can change that. Mover is intended to run during idle time. Each user share has a Use cache setting which controls how that user share uses cache. Mover uses these settings to decide whether to move the share from cache to array, from array to cache, or to just skip that share. There is Help in the webUI. You can toggle Help for the whole webUI using Help (?) in the main menu. You can also toggle help for a specific setting by clicking on its label. Rather than explaining all the details of how Unraid uses cache, I will give you some links and you can ask more questions after reading them. https://wiki.unraid.net/UnRAID_6/Overview#Cache https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-537383

Don't know how I've missed that

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post. Diagnostics contains syslog and many other things that give us a more complete understanding of your situation.

You probably need to setup an app password in gmail for your server to use.

Most plugins I assume would be sending a notice, warning, or alert notification, so those should be covered by your settings. And any scripts that call notify would have to choose one of those types also. Do you have any scripts that call ssmtp directly?

Other things besides those on the Notifications page can send emails, such as scripts or plugins.

By this I assume you are not using this on Unraid. You should always read the first post in any support thread.

Set Minimum Free for cache in Global Share Settings to larger than the largest file you expect to write to cache. If a user share is set to cache-yes or cache-prefer, then if cache has less than Minimum Free, it will choose the array (overflow) to begin writing the file. Once it has chosen a disk to begin writing a file it won't change and will just give an error if it runs out of space. There is a similar Minimum Free settings for each user share. If an array disk has less than minimum free unraid will choose another.

VMs on the parity array will be impacted by the slower parity writes, and they may keep parity and array disks spinning. Another approach would be to use Unassigned Devices for an SSD outside the array or cache pool.

Yes And in the more general case where you have more disks, you can always assign them all as data and none as parity. The only danger is accidentally assigning a data disk to the parity slot so it gets overwritten by parity. What we usually say is assign all disks as data and none as parity, and parity should be the only unmountable disk because it doesn't have a filesystem. That is how you can identify parity. Unless you have a corrupt filesystem on any data disks, then there might be more than just parity unmountable.

A formatted disk is not a clear disk. A clear disk is all zeros and has no effect on parity. An empty formatted disk contains the filesystem metadata that represents an empty top level folder ready to receive new folders and files. Format is a write operation and all write operations update parity, so parity would have been changed if you had formatted the disk.

Since your diagnostics say the share in question has default settings, there probably isn't a .cfg file for it. You must have a folder at the root of one of your disks with an invalid character in the name.

None of those. Before doing anything you should

The hard resets on ata4 in those original diagnostics were referring to disk5. I don't know what connections you have now. Post new diagnostics.

Your VMs can use VNC as a virtual display from the Unraid boot GUI or from another computer on the LAN.

Mounting a disk on another system will invalidate parity. And unless you are using linux, you won't be able to mount the disk anyway. I don't know what your understanding of parity is, but parity is very common in computing and communications. It is just an extra bit that allows a missing bit to be calculated from parity and all the other bits. Parity doesn't contain any of your data, but with a single data disk parity is identical to that data disk just because of the way the parity calculation works. Here is the wiki on parity. If you work through the calculation for the case of a single data disk you will see what I mean. https://wiki.unraid.net/UnRAID_6/Overview#Parity-Protected_Array

The SHOW button next to the text "SMART self-test history"

Read errors reset when you reboot.

The usual advice is to not install any disk to the parity slot and you won't have any risk of getting your data overwritten by parity. In your case, if you only have a single parity disk and a single data disk then they are essentially mirrors of each other just because of the way parity works.

What GPU? Explained in the first post in this thread. You should always read at least the first post in the support thread.

Log into the server command line and copy them to the folder. As the root user you have full permissions. Or use Krusader docker if you have that setup.

In addition to the mapping, you need to tell the Plex application itself where to store its transcodes in the Plex Settings.

So are you stuck in the BIOS, or are you stuck at the Unraid Boot Menu?

From this same page on this thread: