GingerSnaps35

Ty!

I am getting a CRC error on my 2nd cache disk. The 1st spot never gets one. No matter what SSD disk is there, I get an error. I've had my 250GB Samsung Evo 860 there, currently a 500GB Evo 860, and a 500GB Evo 850. I followed another thread that said to unload all data from the cache array which I did and swap the cables, and then reload them/format if necessary. I actually took that opportunity to make a RAID 0 cache array with the two 500GB drives, and then returned the "Prefer" option back on for those shares that had it. I am at a loss and I don't know what to do anymore. It isn't SATA cables or the drives (both Evo 860 drives are brand new, 2 weeks apart from each other). Please help. Also, up until I added the 2nd 500GB drive today, the server had been error free since I completely reloaded the array and started over a week ago. federation-diagnostics-20200921-2133.zip

I chose to do unRaid because I had read that several people had my same setup and were running it as a Plex server and pfSense firewall which is what my intentions were. I guess I need to buy my AMD EPYC 7351P SOC board and build my server so I get proper Hw pass through.

So I did that Saturday and both ways it restarted, so I reinstalled the unRaid on the ISB drive Saturday afternoon, did the full setup again, and this time I just set up pfSense As a VM with the Quad Port NIC being pass-thru. Ever since then, it has been running without any issues or restarts. I did have to restart the system after the VM was made so that it saw the NIC, but once I did, it was smooth as butter and no issues. Fortunately I’m only holding less than 2TB so I can offload data and rebuild if I need to.

yes. Memtest came back good. I ran pfsense on this box for a year before installing unraid a week ago. I just went through an entire process to narrow down what could be wrong: *Deleted Plex docker and vdisk; Same with pfSense VM *Disabled VM's and Docker *Ran Mover *Restarted unraid *Started array *ran mover again *enabled VM/Docker *re-installed pfSense (had to do it three times to get it to recognize the quad port Intel NIC on passthrough) Finally am on the interwebs. This Diag is after pfSense was installed correctly and up and running just now. federation-diagnostics-20200912-0410.zip

Ok, so right after I made the previous comment, I turned off the Plex docker and the entire server restarted. federation-diagnostics-20200912-0304.zip

This time it did a pfsense VM restart only. federation-diagnostics-20200912-0259.zip

I think, and I could be COMPLETELY wrong, that transcoding enabled was doing some of the restarts. At least the last two I had were as someone started a stream from my plex docker. I turned off transcoding and it is still running. Earlier today it happened a couple of times but no one was streaming my plex server.

So my shares stay visible now. Now I am running into a random restart issue that I made a new post about just now.

I'm getting random restarts on the server. Can anyone please help me figure out what it is, because the logs don't make sense to me. =( federation-diagnostics-20200912-0228.zip

also, thank you for that info. It was very very helpful in understanding that!

ok, so i have the shares marked as Cache:Yes, so mover should be moving it when idle?

It appears now that the cache is working, as it is holding a bluray movie, but How do I get it to offload that to the array? I would have thought that was automatic. Again, I am very new to this so please bear with the stupidity of my questions.

Here is the updated diag file. federation-diagnostics-20200908-1324.zip

When I set up the array, I formatted the drive and attached it to the cache spot. It registers as btrfs file system and I currently have 231 reads on it and I just restarted the system 7 minutes ago.