ctblackm

I just wanted to throw a huge thanks out for this. I just updated from 5.0.6 this morning with no issues whatsoever. Thanks for the perfect instructions!

I am new to unRaid, so please bear with me. I recently built a new unRaid server with 3 EARS (2TB) drives, 1 EADS (2TB) drive and 1 Hitachi (1TB) drive. My motherboard is a SUPERMICRO MBD-C2SEA-O. One of the EARS is the parity and all other disks are data. The trouble that I am having is that the write speeds to these EARS drives is < 4.0 MB/sec. I have tried copying files directly to the Hitachi and the EADS drive and I get anywhere from 35 - 45 MB/sec, so I think my network, mobo, etc can be ruled out. While the file is copying, the data drive has a solid activity light and the parity will blink occasionally. Here are some things I have tried (all to no avail): 1. I removed one of the EARS drives, restarted the array and attempted to let it rebuild the disk from parity. - The write speed for the rebuild was < 4.0 MB/sec and I canceled it and gave up 2. I then read the posts all over the forum about the jumpers and then attempted on this same disk to set the jumper and rebuild the disk from parity. - This resulted in a much better rebuild speed of ~20.0 MB/sec. But, once the disk was completely rebuilt, the write speed was the same as before. (I don't understand why rebuild would be able to write data to the disk faster than a normal write, but this is what happened) 3. I was running the beta 9 release and thought maybe I would try to just start over from scratch with no jumpers and just make sure that I had everything setup on 4.7 with these disks the way this post suggests. But, with the jumper removed from the disk mentioned in parts 1 and 2, the disk would simply hang with the activity light solid for 30 - 45 seconds before the OS would start completely. So, I figured that this disk must be bad. So, I removed it and replaced it with another 1TB Hitachi, and moved my EADS drive to be the parity. All started up perfectly, the data from my remaining disks was still there (cool) and the parity built at ~50MB/sec on the EADS disk. So, I thought that all was solved. However, now I go to write data to the two remaining EARS disks and I again get < 4.0 MB/sec write speeds. I attempt to write data to either of the Hitachi drives and I get > 40MB/sec. I have no idea what I am doing wrong here. These drives seem to show performance that is reasonable for the parity sync and rebuild operations (~20MB/sec), but any other sort of write to these disks is incredibly slow. I have run this command: fdisk -lu /dev/sda on all drives with the following results similar for all disks: root@Tower:~# fdisk -lu /dev/sda Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. If I am reading this right, it appears that I am aligned on 64 with no jumper. Which if I have read this post correctly, I have this setup right. Other than get on Newegg and pony up another $300 for disks that actually work, I don't know what else I can do. Any help or suggestions would be appreciated. ** Additional info ** The EARS drive I removed from my unRaid machine works perfectly in my Windows computer. -- Chris syslog.txt