trurl

But note that simply moving the data to other disks is not all that is required. When you remove a disk, even if it is empty, you have to New Config and rebuild parity.

So just powering down doesn't work? Is that a full power down or just a reboot? Sounds like something with the hardware isn't getting reset.

A Docker container is small virtual machine dedicated to specific App. Not sure where you got the idea there was a Plex App that wasn't a docker. Years ago before dockers on Unraid there was a plugin for plex but apps are not done that way anymore. There are literally hundreds of Docker apps available. Even if you don't care about caching User Share writes, cache is the usual place for Docker / VMs to be setup. This allows better performance for these and also allows array disks to spin down since these will always have open files.

How much RAM do you have?

I doubt it. The important reason was already explained soon after that post you quoted.

What browser?

Then get us Diagnostics before it gets to that point

Now you have me wondering about how you have appdata, domains, and system shares already configured. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Are you really running nextcloud in a VM and not as a docker? Are you asking about the cache setting for the user share, or about which user share needs backup? Do you mean you don't want the cloud data to stay on cache?

That does make more sense.

According to diagnostics disk1 is the invalid and emulated disk now so if you restart the rebuild that is the one it should begin rebuilding. And in fact, syslog says it had already begun rebuilding disk1 but looks like you cancelled it. It will start over from the beginning. Syslog isnt showing an unclean shutdown though. Is your server on an UPS? SMART for disk2 looks OK. If you want you can try checking the filesystem on disk2 before restarting the rebuild, or you can do that after. https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

Do you mean replace the Unassigned HDDs with 2xSSD raid1 cache pool? That would work. You would set the User Share to cache-prefer . You still need a separate backup for anything important of course

If you mean it fails in some way that makes it have less capacity of course it must be replaced and can't imagine why you would consider using it again for anything

You can edit the title of the first post. Might be helpful to others to know the solution

Post new Diagnostics

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

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

I wanted you to check there to make sure none of system share was still on the array.

I have always had a small case and like it that way. All my capacity increases have been replacement with larger drives. I currently have 8TB parity with 6TB data disks so I am ready for my next replacement when needed. And the older smaller disks find other uses as backups or other builds for friends, etc. And as I often say each additional disk is an additional point of failure.

As long as they have the same identifier, which is the disk serial number unless you have RAID controller or some USB enclosure for those.

I think you have to boot in legacy instead of UEFI for memtest on the Unraid boot menu to work. Or or you can make a bootable memtest flash drive.

Maybe not so much on Linux:

Many including me have done this. The license goes with the flash drive to the new hardware, Unraid doesn't care as long as the flash GUID is the same. If your current system is using RAID controller (shouldn't be) or your new system is using RAID controller (shouldn't be) then there is definitely a possibility of drives not getting recognized. If you are passing hardware to any VMs then of course you may need to work through that on new hardware. Other than that it should all just boot up and work as before. Not sure how to interpret this. Are there some drives that are not among the "remaining drives"?

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