FN Reboots when copying certain files???

[BlackPoodle]

Hello,
first i have to apologise for my bad english...
Im a really noob in Freenas altough i got some Linux experiences, bash etc..

I have problems when transfering much files ~300gb for example, from one drive to another using my windows 8 Pro client. For the first half minute it looks very good with 50 MB Down and Upstream, then ALOT of messages appear on the server, i cant figure out what it is because there displaying too fast. then the server reboots. When i transfer files from client to nas there isnt any problem and the speed is ~90 MB tried with 900GB, works fine.

Here some details:
FreeNAS 9.1.2.3 64 Bits
dualcore athlon @2.6 ghz
Realtek NIC (shouldnt be that problem right?)
4Gigs of NON ECC RAM

HDD Config:
1. Western digital 3TB
2. Western digital 2TB
3.Samsung 1,5 TB
Using UFS and CIFS

Would be very nice if someone could help me : )

 

[Yatti420]

Have you done memory testing / hdd checkes etc? What kind of WD drives? Realtek NIC could be the problem.. Random reboots are a big problem.. 4gb is 2 little for ZFS as you know..

 

[BlackPoodle]

Thank you for the Reply,
I bought and installed a new intel 1000GBase NIC but its still the same.

It seems that this issue is depends only to the Samsung Hard Drives(I have two of them), when I copy files from client to the WD Drives everything is well.

The copied data contains many big files as many little files as well, when it copies the big files it works just fine but then it copies the little files, the transfer speed decreases to some mb/s (normal behaviour it think). Then it decreases more and more finally to zero… this is the moment when the errors appear on the shell.

But theres more, every time after booting I get this “Freenas smbd[4850]: matchname failed on 192.168.2.2” where this ip address is the win 8 client. Additionaly I sometimes get this “unknown tag name 64” error.

I tried to disable the smart via bios but this hasn’t any effect.

Maybe Freenas isn’t compatible with this hard drive or my chipset, or maybe could it be a bug???


Additional Information:
Chipset is Nvidia Nforce 8200
Samsung HD154UI
NAS configured with static ip


Thanks for the Help : )

PS: I dont think its an cable defect, i replaced it and theres no effect.

 

[cyberjock]

Well, 2 possible problems that I think have a high degree of being your problems.. not enough RAM and the choice of CPU/motherboard.

AMD based systems seem to not be as reliable or work as well as Intel. Not sure exactly what the problem, just an observation.

4GB of RAM can cause all sorts of random problems with FreeNAS. Generally I just ignore threads outright when people claim less than 8GB. If the manual didn't convince them to upgrade I'm not sure why me telling them would matter. And technically, it would be me telling them twice because I told them to in the manual!

 

[BlackPoodle]

Hello, cyberjock thanks for the reply,

aaah damn what a stupid problem : (
but isnt that UFS minimum specification is 2Gigs of Ram??
i tried it with 6 Gigs of Ram it is still the same....
Should i make a bug ticket for this??
Maybe the combination of the Samsung hdd and the chipset is incompatible with FreeNAS : (

 

[cyberjock]

You are welcome to put a ticket in. But if history is any indicator I wouldn't expect a fix anytime soon, if ever, unless you can point a finger at exactly what driver or hardware and what in particular is broken.

That's why we tell people to just avoid AMD. It goes bad so often and we don't usually have access to the designs for the hardware so troubleshooting is basically impossible.