trurl

To enable viewing of sigs on this forum (disabled by default) click on your user name at top right on any forum page and select Account Settings. There you will be able to enable viewing of sigs and setup your own sig.

If it offers to format anything, DON'T

As suspected you have issues with Flash. Are you booting from a USB2 port? (recommended) Do you have a current backup of your flash drive? Shutdown, put flash in your PC and let it checkdisk. While there make a backup of flash. If you ever need to you can always put the config folder from your flash backup on a new install and everything will be back. For future reference, you can download a backup of flash from Main - Boot Device - Flash - Flash Backup. You should get a new backup anytime you make significant changes in the webUI. This is especially important if you make any changes to disk assignments.

Since there is no striping, read performance is at the speed of the single disk that contains the file. Write performance is somewhat slower due to realtime parity updates. Depends on how you want your VMs to work. Many VMs can just run with VNC as the virtual display, but if you need more graphics performance then you would want a graphics card for it. Note that not all CPUs and motherboards support hardware passthrough. Solid state storage is good for the cache pool, and you can have multiple disks in the cache pool for redundancy. Cache can be used for dockers, VMs, and as temporary storage to speed up writes to the server. Not required. Some recommend it. I don't have it. There are containers for cloud backup. Looks like there are currently 684 dockers and plugins listed on the Apps page. Plugins are typically enhancements to the Unraid webUI or other things that add functionality to Unraid itself. Docker containers are standalone VM environments designed to run a specific application. VMs and containers will not endanger the underlying host OS. You will probably give many of them read and/or write access to some of the data store depending on what you need them to do.

Unraid is a custom version of slackware linux.

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

Where did you see these errors if you didn't do a memtest? There should never be any memory errors. Everything goes through memory. Your data, the executable code, everything.

appdata doesn't have anything to do with VMs normally so I don't know what you have done there. The only things plex stores are its library, which can get somewhat large but nothing like what you have. Transcodes are also stored as a subdirectory of that library by default but that can be changed. Other than that plex doesn't really write anything, except possibly DVR, which should be on another share. And any media you want plex to play should be on other shares and not appdata. Looking again at your diagnostics it seems you don't actually have any shares except appdata, domains, isos and system. These shares are not intended for any of your media, downloads, or any other files you may want to write to your server. appdata is strictly for the working storage of your containers. By working storage, I mean anything it might need to keep track of what it is doing. Plex, for example, has a database that it keeps track of where all of your media is stored and other information about that media. The media itself does not belong in appdata. domains is strictly for your VMs. This is where the OS for each of your VMs goes. The VMs will typically access storage from other shares on your Unraid server. isos is where the installation files for your VMs go. This will be where you save downloaded distributions of whatever OS you want to install as a VM. system is where your docker image and libvirt images go. The docker image actually contains the downloaded executable code for each of your docker containers. You should not be storing anything in these shares. They are for the system to use to manage your dockers and VMs. Sounds like you need to rework almost everything. Do you have backups that would allow you to just start over?

Do you have any actual symptoms? Have you done memtest?

No it won't fix your problem, but the fact that you set things up this way may have something to do with the cause of your problems. Which dockers do you normally run? Apps - Previous Apps will let you reinstall your dockers just as they were, but just as they were doesn't seem like the correct way.

Why would your appdata have several TB? Do you have your container applications configured to write downloads into appdata or something? appdata should only contain the "working storage" of your containers. Downloads and other things the applications write should go to other shares. appdata, domains, and system shares should be on cache because cache will give your applications and VMs better performance if their working storage is not impacted by the slower parity writes. And they should be on cache so they won't keep array disks spinning, since the files in these shares are in constant use. Those shares are cache-prefer by default for those reasons. I don't know what you have done but it is not the way people normally do it.

Go to Settings - Docker and disable Docker service. Go to Settings - VM Manager and disable VM service. Set appdata, domains, and system shares to cache-prefer (this is their default so you did this to yourself). Run Mover. When it completes post new diagnostics.

Why are your appdata, domains, and system shares set to cache-yes? They have files on the array instead of all on cache where they belong.

Click on the SMART warning on the Dashboard.

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post

Since this your first post to our forum and you don't mention it, which docker are you using? Or are you even using this on Unraid? (the purpose of our forum). Probably most of these questions on this thread are better suited for the Sonarr website.

Also means each data disk can be read all by itself, regardless of what happens to all the other disks. If for some reason you have more than parity can recover, you still haven't lost everything.

We seldom want just syslog. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Diagnostics includes syslog and many other useful things.

We get all kinds with first posts. Many people don't know that Unraid is not RAID. What else do you already know about Unraid then maybe we can fill in the gaps. The fact that Unraid is not RAID, and allows you to mix different sized disks in the parity array and add disks to the array without rebuilding.

That is just showing there were read errors and suggested checking the SMART. Did you? If so what was the exact SMART issue reported? Some are more serious than others and would be better dealt with by replacing the disk. So no recommendation without more information.

Why did you post your question to the Unraid forum? Just following a random google search? I don't know if that Synology you are thinking about can be converted to Unraid or not. Unraid is a NAS operating system. Many people use it on computers they have built for that purpose, some use it on prebuilt computers. But the main thing is it is an Operating System and would have to replace whatever OS is already on that Synology

Since you also posted about this in the Community Applications support thread I recommend everyone that might be interested in responding take that discussion there so our responses can be coordinated.

This is likely. The connector must sit squarely on the connection with plenty of slack so it stays squarely on the connection.

Unraid IS NOT RAID. It does allow 1 or 2 parity, but data is not striped. Each data disk is an independent filesystem and each file is completely on a single disk. Folders can span disks (user shares). Unraid (or any RAID) is not a substitute for backups.