I'll start by saying I have 2 other unraid boxes that are working perfectly fine but on my new server I'm having some issues. Whenever I try to copy data to the array it crashes the server. I've tried tailing syslog on the box while doing this but nothing pops in. I've tried both a local copy from an external hard drive and a copy over the network and both resulted in the same crash. Sometimes the box comes back up (with the array not mounted) and sometimes I have to shut off the machine manually and restart it to be able to ping it again. I'm not sure what else I can do. I've attached the diagnostic log.

 

Unraid version: 6.2.4

Array: 1 5TB hard drive, no cache, no parity.

tower-diagnostics-20170101-0914.zip

Hook up a monitor to the server.  Then do the procedure that causes the crash.  Hopefully, you will have a something on the screen.  You will probably have to take a photo of that screen.  Check to see that your picture is in focus and the flash( if needed) reflection does not obscure any information.

I looked through your syslog and another files, and didn't see anything out of the ordinary.

 

Is this a new build?  Have you run a memtst (It is an option on the boot menu) on the RAM?  Twenty-four hours is considered t be the the appropriate testing time to use.  (A copy operation will usually use all of the unused available memory as a cache during the write operation.  Hence, it is a RAM tester in its own way...) 

Frank1940,

 

I will try the memtst, I had some issues with my mobo. I got a mobo and i5 for $10 from a sale at work but the mobo wasn't ATX so I bought an ATX one off ebay (odd/old socket for ATX) and it wouldn't support (it would get past post) my 2x4GB memory (even though the mobo is rated to for up to 8GB) so I only have 1 stick in it right now.

Well I didn't need 24 hours.... I didn't need 5 minutes, it crashed almost right after the memtest started... I'm not sure where the issue is, the mobo was used and the memory is new. I wonder if the issue is I'm only using 1 of my ram sticks? Also the ram is 1600 but it's running at 1333. Ugh, this is what happens when I don't build from scratch I guess.

Try the other stick.  And be sure to download the MB manual. check for BIOS updates that might address your issue. And google for that Mb model and see if there were any memory compatibility issues with it. 

 

If that other MB that you got with the i5 purchase has at least two SATA ports on it, you could try that one too.  At least, you have enough components to quickly isolate the problem. 

 

OH, and double check that you did a good job of cleaning the i5 and cooling fan/heatsink so that a hot cpu is not the issue. 

Frank,

 

First off I should have said this earlier: Thank you for your help and quick responses!

 

I will try the other stick now, I did a good job of cleaning the CPU and applying thermal paste and the fan is seated well (I checked the temps and they are all good). If that has the same problems I will try to other mobo.

Well the other stick had the same issue.

 

I ended up stealing 2 2GB sticks from an old build and those worked with new build (I think the speed of the ram was the reason they both wouldn't work with the mobo and the fact that the 2 sticks needed to be used the cause of the crashing). My old build got an unplanned upgrade from 6 to to 10 GB and my new build went from a planned 8 to 4 but it's just a fileserver so it will be fine. Thanks again for all the help and pinpointing the memory issue, I was at a loss and didn't even think to check that.

Glad you got it working.  Just mark the thread as 'Solved'.