HAMANY

I'm not familiar with sonarr and radarr, but this should work: - Edit the docker - "Add another Path, Port, Variable, Label or Device" - The SMB share will be under this path "/mnt/remotes/<SMB Share Name>/" Then the docker will have access to the SMB share similar to the array

Are your apps installed as dockers in UnRaid? Add the paths of the SMB shares and UD moints to the dockers, then add them as a new source.

Not sure if Symlink / soft links will work, but why you don't just map multiple drives in your main PC? You can add different sources to your Plex (Array, SMB shares, unassigned drives, etc.)

Have you tried plugins like "File Activity" or "Open Files" to see what files/processes are currently being active?

As far as I know, SMB and NFS shares cannot be added to the array, as they are not viewed as a "Drive" to other unRaid server.

You're right, this was the issue. Reduced it to 100GB and everything works fine now. Thanks a lot @trurl and @JorgeB

The one I've tried is "Media"

Hi all, When switching the Share "Primary storage" from "Cache" to "Array", dockers like rtorrent and FileZilla can't write new files, even in SMB shares. Switching back to "Cache" then everything works fine. I've seen the below thread, but I don't understand why the using (/mnt/user/) path doesn't work with the "Array"? I remember it was working fine in older updates. Appreciate your help. Thanks. tower-diagnostics-20240227-1735.zip

I've restored the backup in a new USB stick. Every thing looks stable now. Thank you @trurl

Yes I do. Should I do full data restore? Or just for the corrupted files? Thanks

Thank you! The array is back online again, however, there are some issues. - Some dockers and plugins got corrupted. The Community App tab disappeared. - Loading the docker icons in the dashboard page is very slow. The server is overall slower than before. - Many disks have UDMA CRC error. Although recently, I've changed the power and Sata cables - Every time I restart the server, the Cache drive goes to unassigned. Appreciate your suggestion tower-diagnostics-20230217-1030.zip

Attached. Disk 6 is rebuilding now. tower-diagnostics-20230209-0746.zip

Disk 6 the drive that got disabled Cache (nvme0n1) the cache ssd that is shown as unassigned Is there any risk of losing the pool data (cache)? It has all the dockers, I've a backup for it.

Hi all, Few days ago, one of my drives had read errors and got disabled (Disk 6). I stopped the array, remove the disk from the array, started the array again, saw the disk in unassigned but I wasn't able to select it in the array (No disk). So I shutdown the server, changed the disabled disk cables, started the server again, then the surprise. The cache (NVME) was shown under the unassigned devices, when I add it to the pool, it says it's a new device. Also there were many disks with UDMA CRC errors. I've attached the diags before the first restart and after the restart. Appreciate your help. Thank you. tower-diagnostics-20230209-0626 (After Restart).zip tower-diagnostics-20230206-2321 (Before Restart).zip

Thanks. True, I misunderstood the when I saw the options under "Preserve current assignments". I thought if I select "all", the emulated data + disk data will both be restored to my drives. Anyways, I've done what @JorgeB mentioned and everything worked as expected, the parity sync is in progress. Thank you all @JorgeB, @trurl, @itimpi. I will mark this issue as resolved. Lessons learned: - Avoid SATA power splitters - Avoid motherboard SATA ports and get SAS HBA