How did you update the Realtek drivers on the Unraid?

The driver was issued by Realtek and not the 2008 driver included with Windows 7. After rolling back the network card driver (did a fresh install of windows to test with), the network traffic was nice and smooth instead of 10second pulses to 100% traffic which was causing timeouts.

 

Wow has it almost been two months? Here's the update. I rebuilt the Windows7 desktop pc (yay SSD) using the windows nic driver and tested with Unraid 4.6 AIO (previously was 4.5) on a Dell e521/AMD X24200+/2GB RAM and two WD2.0TB EARS drives *jumper4 set*.

 

The solution is working perfect, I'm averaging around 30MB/s in transfer to the Unraid server with no issues at all browsing while copying etc. I've setup TeraCopy on my WHSv1 and migrating all my data disk by disk now over gigabit ~32MB/s.

 

The desktop Realtek Win7 driver was the culprit of all my issues.

I

I have rebooted and tried a to rip a blu ray to the unraid and the same problem occurs.

 

I will preclear some hdds and see if I can resolve the problem by adding more space. It will take about 25 hours to clear the hdds!

 

I put the drives in and the server started responding normally again. Transfers were instantaneously discovered without the long pre-read. I think therefore there is a problem here that Tom may need to have a look at.

Well, I'm still having issues...especially with an attached USB device to the Win 7 machine while copying over the network.  Posted a separate thread here:

 

http://lime-technology.com/forum/index.php?topic=10180.0

 

@binfuser:  I also have a Realtek PCIe GBE Family Controller.  I'm currently using Realtek driver 7.032.1111.2010.  Is yours similar and if so, which driver are you using?

Just wanted to chime in -- I've had the same problem forever -- Win7 copies to UnRaid using TerraCopy time out. I have a EVGA X58 motherboard with the Realtek RTL8168D NIC. Following this thread, I couldn't find an update on Realtek's site to this NIC. But there was a May 2010 update on EVGA's site for the NICs. Installing this update seems to have fixed the problem! Thanks for the advice everyone.

I have the same problem. I copy with drag and drop to my unRaid nfs share and it always fails within a minute. I try a second time and it works. I think it is the disk spinning up.

Try it with the disk spun up already.

Thought I would just check back. 

 

This problem still exists for me. 

 

Upgraded to 4.7

 

Problem now seems worse -taking 2-3 attempts to get the files to copy. Always the first try fails. 

 

Disk being asleep has nothing to do with the problem.  I have tried with them "awake" and even tried with never allowing the disks to sleep.

Thought I would just check back. 

 

This problem still exists for me. 

 

Upgraded to 4.7

 

Problem now seems worse -taking 2-3 attempts to get the files to copy. Always the first try fails. 

 

Disk being asleep has nothing to do with the problem.  I have tried with them "awake" and even tried with never allowing the disks to sleep.

 

How much free space do you have left?

I recently modified the spin down timer in my array from 1 hour to 4 hours.  I did several writes to all the disks in my array yesterday without any transfer issues; however, I noticed VERY high read values (> 20k while other disks were < 100) from 2 of the disks on initial boot up.  SMART reports on the drives do not show any issues.  Any thoughts?

I recently modified the spin down timer in my array from 1 hour to 4 hours.  I did several writes to all the disks in my array yesterday without any transfer issues; however, I noticed VERY high read values (> 20k while other disks were < 100) from 2 of the disks on initial boot up.  SMART reports on the drives do not show any issues.  Any thoughts?

Those disks had journal transactions that needed to be replayed perhaps?

 

Joe L.

Those disks had journal transactions that needed to be replayed perhaps?

 

Joe L.

 

Thanks for the response Joe.  As usual, you've hit the ceiling of my technical expertise.  I did some google searching and think I understand what you mean; however, would this imply that the system was not previously shutdown cleanly?  I didn't notice any errors in the syslog but I did read where the journal keeps a log.  Is there still a way for me to check any logs to know if this was the issue?

Thought I would just check back. 

 

This problem still exists for me. 

 

Upgraded to 4.7

 

Problem now seems worse -taking 2-3 attempts to get the files to copy. Always the first try fails. 

 

Disk being asleep has nothing to do with the problem.  I have tried with them "awake" and even tried with never allowing the disks to sleep.

 

How much free space do you have left?

 

 

I have like 18 1.5TB drives in my array.  Maybe one are two are full - but all the others have between 300GB and 800GB free.  Some are totally free.

 

Whenever I write to a drive - I do sodirectly to the drive - not via the share name.

Thought I would just check back. 

 

This problem still exists for me. 

 

Upgraded to 4.7

 

Problem now seems worse -taking 2-3 attempts to get the files to copy. Always the first try fails. 

 

Disk being asleep has nothing to do with the problem.  I have tried with them "awake" and even tried with never allowing the disks to sleep.

You said the issue was not a disk spin up but have you ever tried navigating to the disk share you are simultaneously trying to copy to (in a separate window) to see if you can access that particular drive?  I've noticed that if my transfer gets stuck on "calculating" that trying to access the drive with a "different" process will sometimes initiate the transfer.  In most cases, I believe this is a disk spinup but I'm not 100% sure.

just wanted to add that I was getting horrible read rates from unraid1 when i was trying to test watching a movie on my WP7 box.  even bought a new intel nic for the unraid box thinking that was the problem (i had not narrowed it down to the WP7 box) and just read this thread.  I updated my realtek driver and now my rates are normal!

 

so thanks for the poster who mentioned the wp7 realtek updated driver.