big file transfer over SMB makes nas4free reboot

[gifo]

Hello everyone,
i'm expecting some problems transferring "big data" from my mac to my nas4free box.
the hardware is super limited 2gb ram on dual atom 1,6ghz + 2tb drive
i'm not expecting to get things solved at 100% but i'm trying to understand why this happens to trying avoid some behaviors.
any idea?
i've tried to check the log but as soon as i see that the system restarted i only found new boot infos.
thanks

ok well:
a-n4f version: 9.2.0.1 - Shigawire (revision 972) x86-full
b- CPU: Atom 230 1,6 ghz MB: IPXLP-MB RAM: 1x 2gb ddr2 800mhz 2xseagate barracuda 1000gb 7200 rpm 64mb
c-DGE-528T Copper Gigabit PCI Card

i've had this problem with softraid setup and even with normal setup
disks are OK no smart problems and no bad sectors.

[raulfg3]

more info is needed, please read forum rules to see what info is requested.

[racmar]

Hello gifo,

I had this problem.
Maybe you have the same.
See:
viewtopic.php?f=68&t=6563&p=42296#p42296
Check your ram with memtest
http://www.memtest.org/
Download the precompiled bootable ISO file, burn to CD then boot your NAS computer with it.

Seems like copying big files is using more memory so you may reach a bad memory chip which you don't reach usually.
While copying, keep an eye on the memory usage in the system information page. You will see it going up.

Good luck.

[alexey123]

Maybe one harddisk have problem, Run fsck for all disks, or check smart logs for error ( I was have some behavior when one from my disk was pre-lost )

[gifo]

i'll check my ram asap...added details about config on top. changed the drives from a 2x1tb raid to a 1x2tb and transfered about 1.8 tb in one shot without any restart....maybe system was overloading...

[chrisf4lc0n]

Overheating could also be the problem... Even though Atoms do not heat up that much they can force the OS to restart if too hot, same with RAM.

[id2test]

I had the exact same issue, and no solution I tried worked.
But after upgrading to 9.3.0.2 - Nayla (revision 1190), which includes Samba 4.1.13, the problem no longer reproduces.