I just had a 2TB WD disk red ball, so I swapped it out with another 2TB WD disk that had just finished preclearing for another system. The rebuild process kicked off without a hitch, but now that it's processing, it's going at a whopping 1.6MB/sec. Syslog and screenshot attached. I've already replaced the SATA cable connected to Disk5, getting the same results. Any advice is appreciated.

syslog.txt

System specs?

Here's another posting of a slow rebuild: http://lime-technology.com/forum/index.php?topic=27411.0 it's been marked as SOLVED and you might get some tips from it. What I get out of it is to boot without plug-ins, stop mover script, stop cache_dirs (if running) and maybe even disable cache drive. Essentially get back to a stock system.

In this case there was a additional drive that was causing troubles. The smaller drives you have may also be slowing down the rebuild.

The smaller drives you have may also be slowing down the rebuild.

 

I think this may be my issue... I have an Asus P7P55D-E Pro mobo with a core i3 processor, 10GB ram. I have eight hard drives (2TB and 3TB) connected directly to the mobo, and an additional five 250GB hard drives in a 5-in-3 cage on a Dell PERC H310 raid controller.

 

I kicked off the check before I went to church this morning, and now that I'm back, it seems to be working as I expected (see screenshot). I'll have to do some further testing, but it looks like the rebuild is dog slow for the first 250GB.

 

Thanks for the advice, I'll definitely check out that other thread you posted.

There is also a debate about large levels of system memory. In some systems it seems to cause problems and so one proposed solution is to set memory limits to 4095 mb. It's good to hear it's not a problem with another drive!