I have noticed, when I seem to run a non-corrective parity check from the unraid menu, my system runs out of memory and starts killing things including emhttp.  This was when I had 2GB of memory, so I upgraded to 4GB and it does the same thing.  Can anyone help explaing why?  Please see syslog-2011-05-03.zip for this.

 

 

Is it normal that smb shares are lost when you are rebuilding drives?  If so, then don' worry about syslog-2011-05-04.zip, otherwise, could someone explain why that happens.  Everytime I rebuild, it seems to kill my shares.  Thanks.

syslog-2011-05-03.zip

syslog-2011-05-04.zip

Neither of the two things you described are normal.

 

Does your RAM pass memtest?  You should run it overnight.

 

Also, try temporarily disabling cache_dirs and then running a parity check.  to disable cache_dirs, type:

 

cache_dirs -q

 

via telnet or at the system console.  Or you can comment out the lines in your go script.

 

Are you running any other add-ons?  I didn't see any in the syslog.

I haven't tired testing the new ram yet, but the old ram passed.  The only other thing I run is crashplan, that's why you will probably notice java running out of memory as well.  Thanks for the tips.