trurl

FYI since you seem to not know how it became invalid. Since you told Unraid to forget about your parity drive it assumed any disk you put in the parity slot later did not have valid parity. And since you had started the array while nothing was assigned to parity, that assumption was correct.

All user shares are at the same mount, /mnt/user. mv is the linux command for both rename and move. When you mv a file from one path on a mount to another path on the same mount, nothing is changed except the path as it is referenced by the file system. The actual file data goes nowhere, it is only the path of the file that is changed.

32GB is the maximum size for FAT32. I've never use the USB Creator having set up many years before it was available. I recommend booting Unraid with that sandisk, but from a USB2 port. USB2 is more reliable, and USB3 speeds aren't needed since the OS is unpacked into RAM from the archives on flash at boot and Unraid OS runs completely in RAM. The flash drive is actually little used, mostly just for storing configuration changes you make in the webUI.

Looks good. Now you have appdata, domains, and system all on cache, and all other shares on the array. Since your cache is small, I recommend setting all shares except those to cache-no. Then go to Settings - Docker and enable dockers again. Later you can decide if it makes sense to use cache for anything else, but keep it limited.

^This However, if you enable dockers/VMs before installing cache, then the shares related to dockers/VMs (appdata, domains, system) will get created on the array where your docker/VM performance will be affected by the slower array, and docker/VMs will keep array disks spinning. And it takes a few steps to get those shares moved to cache later.

That's what I do. Here is a link in that thread to a post that is a good starting point to getting this setup like I have it. Just read from there to the end of the page and all the things you need to do is explained:

Have you tried hitting enter on the attached keyboard?

You can go directly to the correct support thread for any of your dockers by simply clicking on its icon on the Dashboard or Docker page and selecting Support.

I only use a few of those, and I'm not likely to do the research required to figure out how to use the others and what if anything might be misconfigured in them. Maybe someone else will contribute. Plex is one I do use, and it doesn't write as much as for example some downloading application. Other than its library (appdata) the only things it is likely to write are DVR and transcodes. Do you use plex DVR? You don't have a mapping for transcodes. What does the application itself use for the transcode directory? If you go to Settings - Docker and disable docker altogether, do you still get crashes?

To me this suggests a problem with one or more path settings within one or more applications you have running as a docker container. I have 15 dockers installed and they are only using 44% of 20G, and they are stable at that amount of usage. That plex screenshot isn't nearly as useful as the docker run command that results from it. See this very first link in the Docker FAQ for instructions on how to get that docker run command and post it: What other dockers do you run?

On mobile so haven't looked at diagnostics yet. If you get your connection or other hardware issue resolved you have to rebuild those parity drives since they are out of sync now.

A new install isn't enough to be the backup you need. Actually all you really need is a copy of the config folder from flash so you can put it on a new install. You can download a zipped backup of your flash drive from Main - Boot Device - Flash - Flash Backup. Or you can schedule an automatic backup of flash with the CA Backup plugin. However you make the backup, you should get a new backup any time you make any configuration change you don't want to lose. It is especially important to use a backup with the correct disk assignments. Have you tried the usb flash creator with a USB2 port? USB2 ports are more reliable and especially recommended for booting Unraid.

Not related to crash, but something to be aware of so you can clean it up. Your syslog is being spammed with these: May 24 10:47:22 HomeServer root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token May 24 10:47:24 HomeServer root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Here is the FAQ on that: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=545988 Also probably unrelated to your crashes, but your docker/VM related shares are not configured ideally, and your docker image is much larger than should be needed. 20G is my usual recommendation and should be more than enough unless you have something misconfigured. Have you had problems filling docker image? How is that configured? Misconfigured dockers can fill docker image, or they can fill RAM. Any mapped host path that is not an actual disk or user share is in RAM just like the rest of the OS, and anything that writes to the container path of that mapping is writing to RAM. Any application path that does not correspond exactly to a container path, including upper/lower case and including the leading '/', isn't a mapped path, so if the application writes to that path it is writing into the docker image.

You should move the rest of appdata back to cache now that you have room. Go to Settings - Docker and disable. This will make sure all docker related files are closed so they can be moved. Change the appdata share to cache-prefer, run Mover, wait for it to complete. Post new diagnostics.

If copying/moving from cache or array disk, you can't allow the destination to be a share, and if copying/moving from a share, you can't allow cache or array disk to be the destination. See my previous post about this here:

plex does often take a lot of space in appdata, but that seems excessive. Mine is only taking 11G, but my media collection is perhaps modest by some standards. Where do you have plex transcoding? By default transcoding goes to a subdirectory in the plex appdata. There are other ways to set that up.

Sometimes it can take a while for computer names to propagate on the LAN. If you plan to run your server 24/7, install Dynamix Local Master plugin so your server will keep track of computer names on your network. Have you done memtest?

As it says, domains is where VMs are saved, and people usually keep that on cache. And domains is all on cache according to your Diagnostics. Up to you whether you want to recover that small amount of space. Still unclear what is using up all that cache space though. Are you sure you don't have any files at the top level of cache, not inside any folder, perhaps accidentally created? Go to Shares - User Shares and click the Compute All button. You will probably have to wait a few minutes for the result. If it hasn't displayed the results after several minutes refresh the page. Then post a screenshot. Also, go to Main - Cache Devices and click on the folder icon at the far right under View. Post a screenshot.

Unraid doesn't move files except for moving cache-yes shares from cache to array and cache-prefer shares from array to cache.

Try a shorter name for your server.

Why? And how? Your diagnostics said no parity was assigned, it didn't say it was missing. OK, I think your syslog is saying you did New Config without parity. Why? So you indeed have no parity, and whatever might be on the disk you previously had assigned as parity is likely invalid now.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

OP did post diagnostics, and it seems there isn't a parity drive, so no drives can be emulated or rebuilt. I think putting them back in that enclosure is probably going to be the best bet for getting the data off the drives before you can make any changes to the hardware configuration. Parity should be a top priority.

If you mean the sdX designation, there is no guarantee what disk that will refer to after booting regardless of what you do. It is usually not important to even know that designation.