JorgeB

Looks like you forgot both.

If the pool is now fixed but the GUI is out of sync, you can just reimport it (make sure you unmount it first if it was mounted manually) on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and 2 slots assign the pool devices, leave the filesystem set to auto start the array to import the pool

That suggests a corrupt share cfg file, diags my show the issue.

The pool is currently only using one device; the other is missing. First reimport the pool using only the good device (sdc) on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and 1 slots assign the good pool device, leave the filesystem set to auto start the array to import the pool The pool should be imported degraded, since it's using single profile, you will need to use th CLI to correct it, with the array running type: btrfs dev remove missing /mnt/cache Now reimport the pool once more with the single device, it should now be imported without being degraded. If yes, you can now add one device and then the other one.

Lot's of spam on the syslog, difficult to see anything else, reboot in safe mode, and if the docker still crashes post new diags

No ATA errors during the rebuild, which is good news. It's possible, and I don't remember if I asked before, but if there are any power splitters in use it could also be the problem

Should work; can't comment on the iGPU stuff since I never used it.

Cache device dropped offline; check/repace its cables and post new diags after array start.

Not as far as I know.

It will check the whole pool. With different-sized devices btrfs can now use raid0, but not sure that was supported with the kernel in 7.2, so best to use single, with the array running type btrfs balance start -dconvert=single,soft -mconvert=raid1,soft /mnt/home Any there are any issues during the balance and it aborts, post new diags.

First run the server in safe mode without any plugins to confirm the issue doesn't happen. If it doesn't, then start enabling them, you can start with half, if it still doesn't happen, try the other half, then keep drilling down.

Just to be clear, what ran out of RAM before was just that container, not the server.

-Tools -> New Config -> Preserve current assignments: All -> Apply Then unassign one of the parity drives, if that's what you want; should leave parity1 in use. Start the array to begin parity sync, and you can then also format disk7 at any time.

You can use this board to report any CA template issues: https://product.unraid.net/b/community-apps-submission-support

Hopefully it's resolved, but if it happens again, post new diags.