Server rebooting when using plex and copying files

[stuartsjg]

Hello,

I've setup a NAS, some background can be found at my previous post here: https://forums.freenas.org/index.php?threads/hardare-raid-5-or-zfs.30204/

My media is all sorted into folders under my folder structure which ive used for years and is mapped as:
"D" = \\freenas\server\
(i.e. such that a folder below appears in the address bar as "D:\04 Multimedia\02 Music\00 MP3" )

I've installed Plex and setup two file jails so far:

Source: ..server/04 Media/02 Music/00 MP3 mapped to ..server/media/music
Source: ..server/04 Media/03 Movies/ mapped to ..server/media/movies

I've set Plex to scan these folders which it has done, and i can stream music to browser on my PC, Laptop, Ipad and Androd phone all at the same time with no issues. Even playing 4 1080p movie sources to each at the same time is handled with no issue.

Where i am seeing a problem is with the server rebooting.

If i am using (i.e. playing from) Plex on even one device and copy files into the windows map as above (or the movies one), the server will appear to freeze then reboot. During this, the monitor attached to the server rapidly scrolls with text. https://www.youtube.com/watch?v=Nb6QZ4nBS90

If i copy files into any folder on the NAS, this problem doesn't show - only if i copy files into one of the two folders linked to the jail.

I've never used jails before so am perhaps doing something wrong. It may be a hardware compatibility issue or the likes, perhaps RAM shortage - not sure.

Any help would be useful.

 

[SweetAndLow]

I have enjoyed reading your threads up until this one. You need to read the hardware suggestions and meet the minimum system requirements if you want to use Freenas. You also need to flash your raid card to IT mode or make sure you can access S.M.A.R.T data with it.

from reading your other posts i didn't think you were actually going to use your hardware for freenas but it turns out you are. :(

 

[pirateghost]

Sounds like a classic example of why we suggest you don't use piss poor hardware.

A. Your issue sounds just like a lack of RAM, considering you are running on less than half the minimum JUST FOR FREENAS, not to take into account any plugins.....

B. I won't touch your choice of RAID0 drives on a RAID controller.....you have been warned a few times before in your other posts.

 

[Joshua Parker Ruehlig]

just to stoke this fire more. i think your processor is AMD. my cousins AMD freenas server (CPU+mobo we got for free) regularly reboots at 3AM during freenas' normal nightly tasks.

 

[gpsguy]

My guess, is that the problems are related to the issues that pirateghost pointed out, especially running on too little RAM.

While I respect Joshua Parker Ruehlig, I doubt the problem is due to your AMD Opteron (server class) CPU. There might be a reason he got the CPU+mobo for free - did the former owner knew it was bad?

 

[Joshua Parker Ruehlig]

My guess, is that the problems are related to the issues that pirateghost pointed out, especially running on too little RAM.

While I respect Joshua Parker Ruehlig, I doubt the problem is due to your AMD Opteron (server class) CPU. There might be a reason he got the CPU+mobo for free - did the former owner knew it was bad?

we got it from an AMD fan day. I thinks it's a gaming motherboard, terrible for BSD...

I used to have another AMD board (e-350) chipset that worked fine with freenas so I guess not all AMDs aren't terrible.

 

[marbus90]

You have now seen for yourself why you should not use 4GB RAM. Especially not with Plugins.

Do not ask for help with that system, do not expect a stable system, do not expect ZFS to keep your data safe (it doesn't with HW raid in between and kernel panics with low RAM).

 

[stuartsjg]

After taking the video, i tried again and got a photo and was able to make out various things related to overflows, buffers etc, so i think the ram is without a doubt the issue which doesn't surprise me. CPU usage was low during these tasks so i dont think the CPUs are being taxed in the task.

Just to be sure, can i confirm that i should (given no hardware restrictions) be able still use the media source folders via windows whilst its also the source of the media jail into Plex?

Without plex, the server has been running stably (it certainly hasn't exploded) and ive setup permissions etc without any issues so in that regards im happy enough to invest in new hardware provided thats the issue with Plex and not my software configuration.

With regards to data on it, nothing is going on it currently other than test files. Ill need to be 100% happy before it becomes the main day-t0-day data store. Too many times in the past ive been cought out doing things half arsed or on the cheap, which is partly why i wanted to test with what i knew worked in the past (probably when freenas was happy with 4Gb RAM and i didnt use any plugins) before seeing what i needed to spend to improve.

Whilst im here, on the subject of reflashing the raid card (i wouldn't be using this 3Ware one going forward owing to the PCI-X), the hardware fine suggests to avoid MegaRaid units however im looking at a motherboard (SuperMicro X8DA3) with an SAS1068E controller onboard however i see this can be reflashed to IT mode. I dont see the controller listed in the HCL and in a few posts i see people moving away from it so perhaps its not such a good idea...?

Cheers for the input.

 

[mjws00]

The 1068e is limited to 2TB drives. Thus the move away from it. It will do IT mode.

 

[SweetAndLow]

Too many times in the past ive been cought out doing things half arsed or on the cheap

This is funny because you are doing it now. Your current build and the x8 build would be unacceptable and cheap.

 

[marbus90]

The X8 Intel mobos are actually quite well. Only problem is the onboard SAS controller, but that can be avoided via adding a modern LSI SAS HBA card.

 

[stuartsjg]

OK, so been doing more testing - didn't buy that board in the end for avoidance of the inbuilt LSI controller. Did buy an X8STi thought and its working very well.

I've some separate queries at this post here to avoid repetition but suffice to say, as expected and discussed here, with more (namely) 12Gb RAM and a faster CPU, ive not seen this error come back on a new build based on the experiences of this one. The new post may or may not address some of the comments raised in here too.

Thanks again for the input.