Multiple problems copying file

[Toydoll]

Hi. Sorry for the wall of text, you only need to read the bold text though.

I have finally managed to setup my first freenas system to a state which I am pretty happy with. Except for one thing:

The first is probably the most serious, even though I'll manage to work around it:
If I move many files, or rather large files (>30Gb) from my mac to the freenas via afp, then my freenas ≈freezes.
I say "≈freezes" because I really don't know what happens. It seems like everything dies; I can't access it through my browser, plex stops working, transmission stops working etc. etc.
I can however plugin my keyboard and press "14" to shut my computer down (thank you my half descent memory). So it's not completely frozen.

The second one is probably not so serious, but far more annoying:
Whenever I copy a file from one folder to another in the same share (AFP) the pop-up info box tells me ≈"preparing for copy" (or whatever the english translation is) until it dies and says something like ≈"can't copy, an error occurred".
The thing is that the system does copy the file during the "preparing for copy" part and when it dies I am left with an partly copied file. So if I'm copying a file thats, lets say, 13Gb big, then I will end up a file that's about 8Gb big. Sometimes 8,3, other times, 8,7 and so on.

So my main questions are (quite obviously):
Are there any solutions for these problems?


Bonus questions:
How do I reboot my headless system without LAN access?
What number do I have to press (13?) and do I have to press "y" or "yes" after that? Something else I have to do?



I did some search on the forum about this problem and it seemed to happen a lot a couple of years ago, but none of them where exactly like mine (what I could find).


And while I'm writing a short novel here I can take the time to thank all you guys that have taken your time to help people here in the forum. 3-4 days ago I knew nothing about handling a freenas system, I had barely even touched the terminal on my mac. Thanks to you I now have a system that can do so much more than I imagined before I even bought my NAS.


My setup:
FreeNAS-9.3-STABLE-20150902215
i3-4130T CPU @ 2.90GHz
Gigabyte GA-H97N-WIFI
8Gb RAM
6x3Tb WD red RAIDZ2

(I know, no ECC ram... But I got the MB and CPU pretty much for free so I thought that I start with that and advance if I like freenas, which I do. And I don't have any critical data stored there, if you exclude the hours put down setting it up.)

Sincerely
The non-native english guy who might had a few to many beers this evening (that's my smooth excuse for any grammatical errors and such ;))

 

[joeschmuck]

First I'd think it has to do with your AFP and you possibly may need to do some tweaking. Also, did you do any stability testing of your FreeNAS system?

You need to put a head on your system so you can read the screen to see what is failing, and any log data. Good luck.

 

[Toydoll]

First I'd think it has to do with your AFP and you possibly may need to do some tweaking. Also, did you do any stability testing of your FreeNAS system?

You need to put a head on your system so you can read the screen to see what is failing, and any log data. Good luck.

More tweaking, yeah! As I said, I'm totally new at this, don't even know where to start.

Stability testing? I run SMART and have tested som of the "Command Line Utilities" mentioned in the document. Guessing that aint what you mean? Tried to search for "stability testing" and similar, didn't find anything useful.

I will probably have to add a large amount of files in the next few days, can hook it up to my TV (the only screen I have) then. It's just such a pain in the ass to do.

 

[anodos]

I use SSH and IPMI to manage headless systems.

 

[joeschmuck]

I use SSH and IPMI to manage headless systems.

His MB doesn't support IPMI, it's just a generic MB, no ECC RAM support, etc...

Stability testing?

Testing which will push your system components to ensure they are stable such as MemTest86+, Prime95, etc...

When running MemTest86+, run it for at least 3 complete passes but I'd recommend running it for 2 days for your system given the low amount of RAM. Any CPU tester which maxes out the cores should not run longer than 30 minutes in my opinion, any longer is useless as your CPU should be up to it's maximum temp well before 30 minutes. Whatever you do, do not run it longer than a few hours and always keep an eye on it.

Also, you have two LAN connections and a WiFi connection on this MB. Use the Intel LAN port #1 (right side as looking at the connections, refer to your user manual pages 7 & 8), not the Atheros LAN port#2. If you have to move the LAN connection then you will need to setup the NIC interface before you do that or just reset to factory defaults.