D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: evaniam on August 07, 2011, 12:43:56 PM
-
I've had my DNS-320 for two weeks now and it use to get on average 20MB/s write and 30MB/s read in Raid-1 on my 1Gbps network. Now I am only receiving 1MB/s read and write.
I tried restarting and resetting the device with no luck...
-
This may seem pretty basic, but did you try power cycling your router and the PC accessing the DNS-320?
-
Yeah I tried that a few times with no luck.
I actually had to restart my my entire network (modem, router, switches) and now my read/write speeds are back to normal.
Very strange... ::)
-
Pretty obvious something is hogging your network traffic, perhaps due to virus/malware or some P2P program running in the background.
-
Yeah I tried that a few times with no luck.
I actually had to restart my my entire network (modem, router, switches) and now my read/write speeds are back to normal.
Very strange... ::)
I experience a vaguely similar issue with my DNS-343 where the read/write throughput is only impacted by one particular PC on the network. Apparently, the DNS-343 isn't compatible with some Windows 7 installations (the root cause is unknown), and every now and then I have to reboot the Windows 7 box to restore normal read/write throughput between the DNS-343 and Windows 7 PC. All other PCs on the network behave normally.
You're issue could have been anything from a hanging process from a particular client or network device or any number of things. So, oddly enough, I'm not surprised that rebooting your network fixed things. I've seen stranger things happen.
-
I also faced the same problem. Bought the DNS-320 last Thurs and it worked well till sat. Took me 20 min to moved a 300mb file from 1 folder in the NAS to another folder in the same NAS.
I've had my DNS-320 for two weeks now and it use to get on average 20MB/s write and 30MB/s read in Raid-1 on my 1Gbps network. Now I am only receiving 1MB/s read and write.
I tried restarting and resetting the device with no luck...