jamis
Full Member
Posts: 109
|
Post by jamis on Oct 8, 2006 2:36:32 GMT 7
Using Firmware 1.00.03
5x Western Digital WD4000YR 400GB disks (RAID5)
WAN is configured with a static IP.
100Mbps network.
I have been able to copy about 30 gigs of files to the N5200 from all of my computers. The problem arises when I try to copy larger files (larger than 150-300MB) over samba/cifs as well as FTP.
Quite consistantly, the N5200 will lock up and need to be powered off and brought back up. The logs show nothing useful and I'm pretty sure this isnt the DHCP lease issue I've seen others having. I can still ping the machine thats about it.
The wierd thing is this only seems to happen from my WinXP desktop. I was able to successfully copy large (600+MB) files just fine over samba/cifs from my linux box.
Any thoughts?
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 8, 2006 9:25:30 GMT 7
Update:
Using a second ethernet card in the WinXP machine and the LAN port on the N5200, I am still seeing the same lockups and aborted transfers with large files.
I also reproduced the problem on a second WinXP machine.
The transfer aborts 100% of the time and the N5200 locks up about 80% of the time.
|
|
kevin
New Member
Posts: 1
|
Post by kevin on Oct 9, 2006 18:17:12 GMT 7
Do you have use snapshot function ? Update: Using a second ethernet card in the WinXP machine and the LAN port on the N5200, I am still seeing the same lockups and aborted transfers with large files. I also reproduced the problem on a second WinXP machine. The transfer aborts 100% of the time and the N5200 locks up about 80% of the time.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 9, 2006 19:12:34 GMT 7
Yes, snapshot is enabled...
Ill try disabling it.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 9, 2006 19:24:13 GMT 7
I think that may have been it...
I disabled th scheduled snapshots and deleted the the one that was there (100% full). I'm not sure if it was a snapshot thing in general or a full snapshot that caused the issue, but everything seems to be working now.
Thanks!
|
|
|
Post by nextlevel on Oct 18, 2006 4:52:00 GMT 7
I've got right the same problem now while copying large video files. The N5200 still gives answer to a ping, but no response from the web interface and unable to connect true smb.
Even a controlled power of doesn't work. I have to hold the power button to force it.
I cannot accept the "disable snapshot" story. I do not want to disable it. So what is the problem about large files? What size should the space for snapshots be?
Any experiences?
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 18, 2006 6:00:41 GMT 7
No clue as to why its a large file thing.. but since snapshots in general don't seem to be accessable yet, its silly to even have them enabled/configured especially when it causes crashes. I'll wait til they fix it before I re-enable the snapshots, though I'll leave the space I alloacted in place for that day.
I left 1% (76GB) for snapshot use. Not sure what the optimal size is.
|
|
|
Post by cyberwolf42 on Oct 18, 2006 21:51:55 GMT 7
Seems related to my problem posted here: thecususergroup.proboards106.com/index.cgi?board=n5200installations&action=display&thread=1158535190Scroll down to reply #5 where I describe the lock-up that results in teh N5200 falling off of the network when copying data to it from a WinXP system, resulting in the "Cannot copy <filename>: Specified Network Name is No Longer Available" error message. Pay particular attention to the links I posted where MANY people have this problem in general between WinXP and SMB but nobody seems to have a working solution to it. Most people tried a ton of things and the one common thread I've seen is that DHCP lease renewal causes the issue, although I do not think it is that in my case as I have DHCP turned off on most of my devices, and on my router the lease time is set to 24 hours and the problem occurs randomly, sometimes every few minutes, sometimes every few hours. YMMV... but I thought this info might help. Quite frustrating.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 18, 2006 22:30:20 GMT 7
I saw your stuff about DHCP and that was the first thing I tried to avoid by assigning a static IP. It was only after I disabled and deleted my snapshots that the NAS stopped dropping off the network.
|
|
|
Post by cyberwolf42 on Oct 18, 2006 22:37:15 GMT 7
I believe mine is already disabled. How did you delete the snapshots? (where are they stored, etc?)
Thanks!
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 18, 2006 22:40:19 GMT 7
In the web UI under the snapshots section there should be a 'del' button next to each snapshot.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 18, 2006 22:41:35 GMT 7
Funny thing is... i supposedly have them disabled, but there are now two small shapshots in place... interesting. Looks like another small bug.
|
|
|
Post by cyberwolf42 on Oct 18, 2006 22:43:42 GMT 7
I wonder if that is one of the issues fixed by the beta firmware that Thecus support mentioned (but never sent me a link to).
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 18, 2006 22:48:42 GMT 7
I'm running 1.00.03 I'm thinking my issue might have been an issue of lockups with a full snapshot.. I've apparently had at least one snapshot (9% full) for 2 weeks and I've had no problems. I think the problem arose when I enabled snapshots BEFORE copying data to the NAS. All the new files registered as 'changes' and thus were copied to the snapshot. Now, since I deleted the 100% full snapshot, only 'changed' and new files since have been copied. The 'dropped network connection' during copy was actually the system locking up in my case.
|
|
jamis
Full Member
Posts: 109
|
Post by jamis on Oct 18, 2006 22:58:09 GMT 7
I wonder if that is one of the issues fixed by the beta firmware that Thecus support mentioned (but never sent me a link to). Check the firmware forum... i just noticed that they put up the firmware in the beta directory that disables snapshots/scheduling...
|
|