DaWord2011

Sorry I forgot to update, found the issue is with the SATA controller on my motherboard (sad it is such a nice board). Moving the cache drives to the other SATA controller resolved the issues. After that I simply bought a second LSI card, flashed it, and dropped it in. After balancing and scrubbing the cache array I haven't had a single error! thank you for the brainstorming.

My thoughts exactly, all 3 of the SSD's look like they are having issues. I have started to wonder if this is an issue associated with possibly my case or mobo. These 3 SSD's are in their own 4 drive caddy but each of them are going to the motherboard SATA instead of my SAS 9211-8i card I have all of my HDD's hooked into. Manually ran a quick SMART test on all 3 SSD's and didn't have any new errors I could see. I am starting to suspect a SATA controller or possibly an issue with that 4 drive bay itself. Attached logs from last night, mover successfully ran last night, and the cache is back to it's "empty" state (always appdata in there). These logs should include short SMART tests for the three SSD's as well, and I noticed some errors late at night, however, they do not seem to be as prominent as the other logs. I have notifications set up, however, it is not out of the realm of possibility that they are set up incorrectly. The notifications were what lead me to the unclean shutdown investigation that led me to replace the power supply. I am wondering if the unclean shutdowns may have lead to the BTRFS becoming corrupt. I will first attempt the easy stuff of replacing SATA cables. Then I will attempt to move a SSD's out of the caddy and run them hooked directly in with a cable. If that fails I will move to other board's SATA controller or my SAS card and see if it is related to the mobo controllers. tower-diagnostics-20180824-0746.zip

I have been recently experiencing issues with the mover. When invoking the mover, manually or scheduled, sometimes (about half the time) the mover will lock up part way through and act like it has completed. After analyzing the cache array's capacity I will notice that it has not completed the move, and restarting will change nothing. When I notice this mover issue, if I try and access my array I can navigate through it, however, I cannot read or write to any of it, instead, I get a permissions error. If I attempt to use any of my apps (all installed on my cache array) they will not function properly. Plex, for instance, will load but none of the content will be available. If I reboot the server all of the data is retained and the array will come back up and work properly. If I simply stop and start the array again, it will state that the cache array cannot be added and there is no filesystem. At this time, a separate SSD that I have as a VM drive (unassigned) will also halt working. Although not all at once, the VM contained on it will simply BSOD and reboot, and when it comes back up it will go into the default bios screen and not show any boot options. I am a little stumped, I have recently been dealing with random power downs and found that the PSU was the cause of the issue. After replacing the original unit with a new Seagate option, the power issues have been resolved. Any ideas? Attached are some anonymized logs that I grabbed on two separate occasions after noticing the issue. Diag-anon.zip Diag-r&r-anon0817.zip Server Specs are as follows: 2x Xeon E5-2630 V2 ASRock EP2C602 Motherboard 4 x 8GB Samsung ECC RAM Seasonic Focus Gold 850w PSU 6 x 4TB Seagate HDD's 1 x 2TB WD Red HDD 2 x 256GB SSD's (Cache) 1 x 128GB (VM's)

Exact same logs as this ^. Teamspeak starts but does not run successfully.

Great, that answers my question. Thank you.

I just made the transition to UnRaid from FreeNAS (used for 6 years). My setup currently consists of 2x Xeon E5-2630V2 processors, 32GB of ECC memory and 6 x 4TB drives. I am in the process of adding a cache drive and will install my apps and VM's on there eventually, however, I am wanting to test out the VM capabilities of my server first. When I go to assign CPU's to the VM the cores do not seem to line up in the same fashion I would see in FreeNAS. The method I am used to seeing is cores 0-11 as CPU 1 and cores 12-23 as CPU 2, however, it appears that the core counts may not be assigned that way according to the "thread pairs" info under System Devices. I did a lot of searching and did not find anything that seemed to answer my question. When it shows "thread pairings" is that the two threads for a single core, or simply the corresponding threads on each CPU (ex. core 1, thread 1 for CPU 1 & 2)? For instance, in the second attached image, it shows Pair 1 as CPU 0 / CPU 12. Does this imply that the first CPU core consists of threads 0 & 12? Or does this simply indicate that threads 0 & 12 are the first thread of each processor? The reason I ask is typically it is best practice to assign the threads under the same core so that you divvy up the resources a little more evenly, and avoid simply using one thread from multiple cores.

Do we know what the cause of this is? I have recently upgraded my entire server and wanted to try UnRaid over FreeNAS that I have been using for years, however, this issue is really frustrating me. I have tried 3 different USB drives I have lying around and none of them have seemed to work. Unfortunately, I am attempting to boot for the first time so I do not have any way of getting a config file of any sort. I am also running an ASRock 602 mobo.