Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi
I stumbled upon a problem with my new and shiny DNS-323.
I'm not able to copy files larger than 2GB. Every time I try to copy large files the process will stop at some random size ex: for the same file once I'm able to load 4 GB of it, while the next time it will stop at 80% and 7 GB. After a failed copy the DNS-323 stalls for couple minutes.
This behavior only manifests itself while I copy using SMB, as in case of the FTP the drive is able to receive even 9GB files with no problem.
Has anyone came across such a behaviour?
If there is any advice you can give please do.
what helped a little bit:
turning the drive from SATA1 compatibility mode to SATA2 improved some things. For example after a failed copy the drive stalls for only a second instead of couple minutes.
about my setup:
I'm using a D-link approved (Seagate barracuda 500GB series 35000...) drive in JBOD configuration.
Since it arrived with 1.03 bios i upgraded it to 1.05. Also since then I'm not able to get successfully through formating (94% curse).
I tried swaping the drive to the second bay, reformating it (with cleaning the drive on a computer and reseting the firmware, always the format failed). But with no luck.
I will try to follow the advices to get a 100% format and maybe that helps, cuz since the transfer is failing in all sorts of diffrent sizes it might a problem with alocating space on a badly formatted drive.
if that does not work, im gonna load telnet onto the box and see what syslog is spitting out.
Offline
Early versions of the firmware - I believe pre 1.02 would not allow files greater than 2GB to be transferred from certain versions of Windows - you would get an "insufficient space" message whenever a transfer was attempted and not the "partial transfer" that you describe.
With all later versions this problem has been resolved, the largest file I've transferred is somewhere in the region of 65GB - an Acronis image.
One more thing - I'm using a D-link approved (Seagate barracuda 500GB series 35000...) drive in JBOD configuration.
On this device JBOD requires two disks, you only mention one.
Last edited by fordem (2008-07-11 01:50:08)
Offline
Hi
Yes, thats what I also thought after reading the wiki.
About the JBOD, yes you're right. I use the standard configuration for one drive only not JBOD.
Anyway, to get the HDD formated I had to go all the way back to 1.03. Now I'll try to upgrade to 1.05 and do some heavy testing.
The large Acronis image that you mentioned, you've uploaded that using SMB, right?
Offline
more reasearch:
- When coping through SMB (windows) I get the "The path is too deep" error
- When coping through Total commander I get the "disk is full" error
- on ftp, well it stops from time to time with a pretty reason
Does anybody have any idea on how to fix this?
Offline
even more research:
- tried changing the network cables. did not help
- tried changing the HDD (different model but still a seagate barracuda 400GB). did not help
- tried turning on jumbo frames. did not help
- tried turning off "oplocks". did not help
- tried turning off "map archive". did not help
- tried firmware 1.03, 1.04, 1.05. did not help
- tried coping from another machine (also windows xp based). it even has a diffrent network card than my normal PC. Well I'm getting a different error after couple minutes of coping this time about not being able to find the DNS-323. did not help
- tried uploading all sorts of fancy stuff (top,...). did not help
- looked for any messages in dmesg. nothing.
- tried testing the HDD from the DNS-323 on a linux box with e2fsck. no errors
- tried FE and GE speeds if DNS-323 network card. did not help
- tried grepping the network traffic with etherreal(wireshark according to newest nomenclature). it seems that the DNS-323 just dies couple minutes into each coping process.
whats interesting is that although it seemed like it stops in random points this does not seem to be the case. if a file transfer fails and I will retry the same file next time it will fail at the exact same byte. this was noticed on couple files. sometimes the byte at which this fails is the first byte of a file. this points me to the fact that this is a bug.
after every failed copy the DNS-323 goes into a little bit of coma. sometimes it lasts a second, sometimes 2 minutes does not help and I have to kick in dlink bottom with a hard-reset to make it work.
in this coma the DNS-323 does not respond to ping requests but interestingly does not close telnet session. If it manages to come back to the world of living my telnet session is still working and showing a uptime like nothing bad just happened. again nothing in the logs.
My hardware is B1.
My last attempts will be to try to turn on samba logging to see if i can pinpoint the problem. next if I manage to convince myself not through this wortless piece of crap with a d-link logo through a window I will take it to the shop and ask them to fix it.
does anybody have any idea?
Last edited by krystian (2008-07-14 22:28:11)
Offline
Have you tried searching the forum?
Have you seen other users complaining of the same or similar problems?
Doesn't that suggest that the problem is not the DNS-323 itself, but rather something in your environment?
Start by looking at your network infrastructure - does wireshark give you details on network errors?
Offline
I've found it!
Well apparently I had some other network equipment on the same IP in the LAN (it was not responding to pings as it has firewall).
Changing DNS-323 to diffrent IP solved everything.
Offline
Updated FW 1.05B
I have Hardware Version B1
I tried copying a DVD rip folder ( contains *.vob files ) to the 323 but got the error:
Path Too Deep
Ive manually assigned the DNS-323 IP to 192.168.1.150 and the rest of my network devices is DHCP assigned to the lower end of the 192.168.1.x so definately not a IP conflict.
WindowsXP
DNS-323 connected to my Asus WL-600G router.
Raid0 1 x 500Gb Samsung and 1 x 500Gb Western Digital
Offline
Path too deep generally refers to being in a path that is inside of too many subdirectories.
Offline
bq041 wrote:
Path too deep generally refers to being in a path that is inside of too many subdirectories.
I would normally tend to agree with you there, however this is a normal dvd rip folder from dvd decrypter so its not deep at all.
Offline
AwdFun, How are you copying the files?
Offline
ok i am having the exact same problem as the threadstarter.
winxp + sp3
siemens gigaset 100mbit router
1 harddrive western digital 250GB
firmware 1.04, 1.05
i am trying to copy a 30GB file to the nas.
via ftp it works (10MB/sec)
the problem is samba i think.
i tried the firmware samba and the samba version from ffp.
the result is the same, after some time it says disk is full.
i also already tried to change the ip adress but still get the same result: disk is full.
anyone with new ideas?
Offline
ok i tried both gbit lan ports on my gigabyte x38-dq6, problem persists.
i added an old 100mbit and ... it works. i successfully transferred 30gb (~1h) without any problems.
since i already upgraded the drivers it seems to be a general nic problem and/or the fact, that i am running 100mbit over the gbit nics.
Offline
mastervol - if you can transfer files at 100 mbps but not at gigabit speeds then the problem MAY be the network cables themselves.
Offline
i tried quite some cables (5) now .. 2m, 1m, 3m .. all bought in the store and certified ..
no problems with GBit nic and nas connected directly.
i guess i have to look for an new router gbit jumbo frame style ;-)
Offline
I am using the DLINK DIR-655 router and few DGS-2208 switches for my Gbit portions of my network and they run great. I get 17-20 MB/s sustained and 22 MB/s burst on it with no jumbo frames.
Offline
I had problems with my EVGA 680i gigabit ports combined with my 8 port Netgear gigabit switch. Worked fine connected straight to the DNS-323. I changed the gigabit switch for a TP-Link version and it works fine again. Some chipsets in gigabit switches seem to work better than others on certain LAN ports.
Offline