xMaverickx Posted February 24, 2020 Share Posted February 24, 2020 Hi All, Sorry if this is stupid or obvious, but I'm having some trouble figuring it out. I'm pretty new to unRAID. I've had a series of issues, but the main current issue is that my parity build is going really slowly. Hardware: Recently changed from an old 2013 Revo Aspire PC connected to an 8 bay Orico drive with a USB-C to USB-A cable to an 8th gen Intel NUC i5 with USB-C to USB-C cable hoping to make everything run a bit snappier since the CPU was always maxed out. (I know external enclosures are not recommended, but that's what I had). I had a set of drives including 1x 10Tb parity, and 2x 10Tb, 2x 4Tb and 3x 2Tb data drives. With the NUC I bought a 480Gb SSD to use as cache, was cacheless before that. Initially things were fine, then the enclosure was unplugged during a data write and a 10Tb drive was disabled. I was reasonably convinced that it wasn't damaged, so I unassigned it and reassigned it for a rebuild. This was taking forever. It seemed the total read speed of the array stays constant at about 30-35Mb/s, so each drive will read at about 6Mb/s and the data drive would write at 6Mb/s. Once the 2Tbs are out of the way the remaining drives go up to 8-9Mb/s and once the 4Tbs are done the 10Tbs go at 18-19Mb/s. It got to 99.6% complete and my son threw a toy behind the TV and it unplugged again Hence why external enclosures aren't recommended. I then tried to do a SMART test on the drive, but even though the drives are active and working, none of the drives in the Orico enclosure appear spun up so they won't test. I think because they all get listed as JMicron Generic 0-7 instead of their actual model WD__ etc. So I copied the emulated data off disk3 (10Tb disabled drive) and did a new config and am now rebuilding the parity, thinking that maybe that drive was faulty and slowing things down, but am getting the same thing. Currently, the rebuild has been active for 16 hours, is 3.7% complete and has about 16 days to go. Oddly on the old Revo with the same drives, I would build parity in around 22 hours or so, which seemed normal. Why would the new system be slower? It's all a bit of a mess. Can anyone help clarify where the bottleneck in this system is? I've attached my diagnostics file. I'm sure I've left out some crucial information, so just let me know what I can do to help. Thanks! blackbox-diagnostics-20200224-2248.zip Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.