csmith665

Thank you for the recommendation BobPhoenix.

Thank you for the link. The symptoms are almost exactly the same and I suspect it's a fake card more than ever. I'll work on initiating a returned/refund. Does anyone have any recommendations on where to buy a similar card from a reputable seller? Edit: It turns out that I bought the card from the same seller in the link.

Since my original post, I've done a little more digging about the LSI card and think it is ultimately the culprit. It was just purchased from Ebay with IT mode already configured because I was concerned about compatibility of configuration. After removing the card, parity rates well over 100MB/s. I did notice a few things: The card's BIOS calls it a 9211-8e, rather than the 8i, which has me wondering if it's either got the wrong software on it, or is a fake. The card's BIOS date is from 2014, which seems to be outdated. I tried calling LSI to validate the serial number, but an automated message told me to go online due to call volumes. I then tried to re-flash the card into IT mode and update the BIOS, but after an hour of trying to get my machines to boot into the EFI shell, I'm giving up for now. I'll continue to update this thread as I find things out, but if anyone has any insight into the card BIOS saying 9211-8e, rather than 8i, I'd love to hear about it.

Hello everyone, Today I moved UnRAID to new hardware and after the migration, parity synchronization seems to be extremely slow at less than 25MB/s. Previous to the migration, I was getting 88MB/s to 100MB/s. Overall, the system seems to perform OK other than the parity performance. The interface is responsive for the most part (seems to slow down occasionally) and I'm copying data to a new drive over the network. Speeds are between 36 and 50 MB/s. A copy of the syslog is attached Troubleshooting completed: On first boot, the 8tb drive that was implemented into the array today had XFS errors. I believe this was because I started the array, then stopped it a few moments later while parity was calculating for the rebuild. Since I still have the old drive, I opted to reformat in XFS and manually copy the data. It is worth noting that the new drive was pre-cleared for two passes prior to installation today. Restart OS. Move parity off 9211 controller, per documentation. Validate write performance to disk network share is within expected ranges. Re-created the UnRAID USB flash drive, per a post about parity performance following hardware migration. Ran 'Fix Common Problems' plug-in, errors were only related to shares being cache only. Originally, user shares were disabled. When I enabled them, performance on parity seemed to increase from less than 10 MB/s to about 15 MB/s. Prior to this change, I had not see over 10MB/s. Swapped PCI-E ports on TS140. (Bottom x16 port is only wired for x4 performance) Moved all WD Green drives (only WD Reds remaining) off the 9211 controller. Old Hardware: Core2Extreme processor. Don't remember model. On-board SATA with an add-in PCI-E controller 2gb RAM 6 data drives New Hardware TS140 with a e3-1225 (don't remember version, 2 or 3, maybe?) 9211-8i controller 20gb RAM Added an 8tb drive (Drive was pre-cleared on old system before migration. WD Green decommissioned) Power supply from old build was moved to New hardware. Does anyone else have any recommendations? tower-syslog-20170804-1613.zip

Thank you for the recommendations Squid. A Corsair TX750 which has a single 60 amp 12 volt rail has been installed in the server. It is a pretty old power supply so it will likely be replaced soon, but will suffice for now. Additionally, the array has been rebuilt and operating fine, perhaps better, for more than 24 hours. No additional link errors have been found in the syslog.

Thank you for the quick reply. I will look into a replacement power supply.

Hello Everyone, In the last day or so, I have had several issues with my UnRAID server. I rebooted the server to find BIOS reporting a link error on ATA4 (disk1) and re-seated the cable. The error went away, but the red ball was produced. Short SMART test passes, long test is running. Is it safe to re-activate this drive if long SMART passes? Additionally, ATA5 (disk4) reported several errors last night. Dynamix produced notices that SMART errors present, but another notice moments later would state that no errors were found. A short SMART tests passes. To make matters worse, the drive produced a number of errors in syslog and became unresponsive for a short while. The SATA cable was replaced. Fast forward to this morning, the red-ball still exists at boot and ATA5 is no longer producing read/write errors in syslog, but I see several SATA link resets for ATA5 and ATA6 (cache). The cache drive did not mount at boot. Within the last few months I replaced all of my SATA cables due to ATA link resets found in syslog, which temporarily resolved the problem. Does anyone have recommendations on how to move forward here? I'm leaning towards power supply (Antec EA380) or malfunctioning SATA ports on my Asus P5Q. syslog.zip

Thank you Rob. I have removed the openssl packages, ssh, and Dynmix GUI plugin temporarily for testing. It would appear that my issues are relating to other things . After removing Dynamix, the standard UnRAID GUI is also crashing.

Has anyone experienced an inability to access Dynamix, SSH, and Unmenu since upgrading to version 2.2.10? This has happened to me twice since installation of the Dynamix's newest version. Other services such as Sab, NZBDrone, and Plex were still available. It is worth mentioning that I also installed the updates to Email Notify and Plugin Control this afternoon, however, symptoms started before updating those plugins. I've attached a copy of the syslog. On syslog line 2662, you will see that I connected via SSH to the UnRAID server. I was kicked out immediately upon connection. At this point the Dynamix and Unmenu were already inaccessible. syslog.zip