trurl

I have split your post into its own thread, since it isn't about the FCP plugin itself. From first post of the FCP thread: Attach Diagnostics ZIP to your NEXT post in this thread.

Does latest Unraid version still mount ReiserFS?

Attach Diagnostics ZIP to your NEXT post in this thread.

If you want the data from the old disk to be on the new disk, then the Unassigned Device method is a way to do that. The New Config would be done first to assign the new disk to the array as disk1, then format it, then copy the data from the old disk as Unassigned Device. Or you could assign the new disk as disk3, format it, copy the data from disk1 to disk3, then New Config to remove the old disk1 and reassign disk3 as disk1.

Unraid IS NOT RAID. If you had parity you could just replace the drive and rebuild. Since you don't you will have to copy the data from it. You will have to New Config to make the new assignments. You could do the new assignments before copying the data if you make the old drive an Unassigned Device. Also your appdata should be on cache.

Tell us more about this. What is it? How is it attached? How is it powered?

You will have to New Config after emptying the drive.

Do you have an attached monitor and keyboard?

No need to head anywhere yes

contact support

If they are duplicates it should already be using the system files on cache. Do they have the most recent timestamp? domains share has files on disk1 also. VMs will perform better if those are on pool such as cache, if your vDisks aren't too large to put there.

Check filesystem on emulated disk11 from the webUI and post the output.

Not sure about how Unbalanced implements that, but Highwater allocation for an Unraid User Share would not have put anything on the smaller drive until the larger drive had gone through half full (500G), then half again (250G), then half again, before it would switch to the smaller drive.

All disks mounted, including now disabled/emulated disk11. But syslog indicates some corruption on disk11. Did you check any of your connections before rebooting?

You can remove each container from the webUI. Same with plugins. Don't know what else you would want to reset if you are keeping your data.

This is a little unclear. I assume you mean you are getting parity check due to unclean shutdown, not that you are running these parity checks intentionally. Setup syslog server.

Not unmounted, disconnected. Different concepts.Those errors have filled syslog, and if disk5 weren't invalid and parity2 weren't already disabled I'm sure disk11 would have been disabled. Since parity2 is disabled and disk5 rebuild hasn't completed I don't see how you can finish disk5 rebuild since you are now missing disk11 from the parity calculation. Stop, shutdown, check connections, reboot and post new diagnostics with the array started in Normal (not Maintenance) mode.

HDDs in XFS array, 1 parity should be fine for that many. SSD as btrfs or zfs cache pool, if you want redundancy add another SSD to the pool. Don't enable docker before installing cache so the docker shares can be created on cache.

I fixed it from command line

I have moved your post to General Support (v5 and older). I haven't seen V5 in many years and it is much more trouble to diagnose than modern versions. I think the screenshot is showing that the emulated drive is mounted so that's good news. You should be able to rebuild to a new drive. See this thread for how to get us more information: https://forums.unraid.net/topic/9277-how-to-report-a-defect-and-capture-syslog-and-smart-reports/ The link for getting SMART report is broken but I assume it required command line, so see if you can get us the SMART report for the drive in addition to syslog. And hopefully you haven't rebooted since the drive became disabled, since syslog won't tell us what happened before reboot. But it can still tell something.

Running New Permissions on an Exclusive share results in subfolders not being browsable, possibly other problems. I think this must be because of symlink. Maybe this is a known problem. Does Docker Safe New Perms work correctly for Exclusive shares? My exclusive shares are on the same pool as appdata so I don't want to run New Permissions on the pool.

Have you done memtest recently?

That drive disconnected as sdc and is now Unassigned Device sdh. Looks like it disconnected after rebuilding for about 9 hours. Emulated disk3 is mounted. SMART for the drive looks OK. Check connections, both ends, data and power, including splitters, maybe try another cable. Each plug must sit squarely and firmly on the connection, with no tension in the cables. Don't bundle data cables.

Actually you don't want to trust parity since you will be removing a disk. Post a screenshot of your disk assignments.

Among other things it seems you have filled docker.img, despite it being about 10x larger than should be needed. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Reboot and post new diagnostics with the array started in normal mode.