Miles-

This solved the real problem. No more errors. Thank you all so much!

Like I wrote, the rest of the shares is set to NO. Correct. Yes, still full of chache full errors. Rebooted, let it run an bit, diagnosis in the attachments. nasa-diagnostics-20180225-2030.zip

Sorry for the late reply. Share - Cache - Settings: appdata -> prefer domains -> prefer isos -> yes media -> yes miles -> yes system -> prefer rest is set to NO nasa-diagnostics-20180221-1909.zip

I set the system share. You are right. The Cache disk error disappeared, because Mover is not working at all. This is the error log I'm getting: But on the cache disk are 360GB free space.

@tdallen , @trurl: You were both right. I changed the Share settings from "YES" to "Prefere". The problem still occured. I manualy copied the file that was causing the error. The error dissapeared. Thank you for your help. SOLVED

Ifter some testing it has to have something to do with mover. When I started it by hand, I got the same problems. So after looking into the log i found this: I set the prferences to use the chache disks for the system share, but the libvirt folder on the cache disk is empty. In disk 2 there is the libvirt.img. Shouldn't the file be on the cachedrive? Should I move it there?

Since a few weeks the cache pool (JBOD) from my Unraid Server is filling up every day at midnight. After it is completely full it returns to normal and nothing is wrong. I have no idea what is causing the problem. Diagnostics are fetched and can be provided. Thanks in advance. Miles

Thats a solution. Thanks

Same Problem here... @nuhll Have you found the solution? Or anyone?

Thank you

I have just installed System Temp and Fan Auto Control in my Server, running on a Supermicro X11SSM-F motherboard. System Temp works without installing perl. Problem is I don't see any PWM controller in Fan Auto Control. I read through most of the thread but can't find any solution. Please help.

Ok, I started parity rebuild right now. Will come back to you when finished. Thank you very much for your help! I really appreciate it. Miles P.S.: I will flag it as SOLVED after rebuild shows now problems.

Ok, I knew that I would have forgotten something. The two Paritydrives are connected via a 4 * SATA <-> SAS cable to the HBA. Three weeks ago I added two used SSD cache drives and these are also connected over the same SATA <-> SAS cable. Might this have caused the problem? I now disconnected one of the SSD (wich I didnt use anyway) and connectet the failed Paritydrive via SATA directly to the motherboard. So on the SATA <-> SAS cable remain the SSD Cache Drive and the Parity 2.

Hello guys, OS: Unraid 6.3.5 Plugins [Version]: (CA Auto Update Applications [2017.06.09], CA backup / Restore Appdata [2017.06.04], CA Cleanup Appdata [2017.01.28], Community Applications [2017.06.10], Dynamix Active Streams [2017.04.24a], Dynamix Auto Fan Control [2016.12.15], Dynamix File Integrity [2017.02.17], Dynamix S3 Sleep [2017.05.12a], Dynamix Stystem Temperature [2016.08.26], Dynamix webGui [2017.05.26], Nerd Tools [2017.02.06], Preckear Disks [2017.06.15a], Unassigned Devices [2017.06.10] MB: Supermicro X7SPE-HF-D525 CPU: Intel® Atom™ CPU D525 @ 1.80GHz RAM: 4GB HBI: Dell Perc H310 (flashed to IT-Mode) Yesterday my NAS (called NASA) suddenly sent me an Alert about Parity Disk 1 beeing in error State. Ich checked Parity three days before with 0 Errors. I downloaded the Diagnostics and startet a big SMART-Test after that. The Paritydisk is only a few month old and the whole system is normaly shut down when not in use. Do you need any more information then the above? Dont know what to do next. Hope you can help. Thanks Miles nasa-diagnostics-20170618-1927.zip nasa-smart-20170619-1625.zip