System freezing and not responding

[biggyk]

Built my system and set it up. Was going pretty well for a while but a few times now il be moving around within the gui and then il get no response. Il get an error in chrome saying the website took to long to respond. Went downstairs and checked the console and it had all these errors.

i3-6100
Kingston ECC 16gb ram
ASRock Rack C236 WSI motherboard
2x 4tb WD Red Drives

 

[Ericloewe]

Please do not use external image hosts. Post images directly on the forum.

 

[biggyk]

Please do not use external image hosts. Post images directly on the forum.

Tried that first, it was too big to upload.

Sent from my ONEPLUS A3000 using Tapatalk

 

[biggyk]

Ok iv reuploaded the picture. Anyone have an Idea? I have switched my USB to 2.0 ports from 3 and it worked a while bug crashed once yesterday.

I have no does a mem test or stress test yet but thinking I should.

Sent from my ONEPLUS A3000 using Tapatalk

 

[Ericloewe]

What were you doing, exactly? That stack trace doesn't have any obvious (to me) clues.

 

[biggyk]

What were you doing, exactly? That stack trace doesn't have any obvious (to me) clues.

If I remember one time I was just navigating through the freenas gui and the other time I was loading my plex library. I have watched a couple movies with no problem through plex and straight to kodi.

Sent from my ONEPLUS A3000 using Tapatalk

 

[biggyk]

I ran memtest for the afternoon today and no errors. Mind you it only did 4 passes. So may run it overnight. Trying to find a bootable usb cpu stress test to run.

 

[Robert Trevellyan]

Trying to find a bootable usb cpu stress test to run.

Ultimate Boot CD has a few options.

 

[biggyk]

Ultimate Boot CD has a few options.

Thanks Il check it out

I left memtest running this morning before I left for work. Then Il try cpu. Really have no clue why it randomly crashes.

Sent from my ONEPLUS A3000 using Tapatalk

 

[biggyk]

This time it was when I deleted the Syncthing plugin.

Sent from my ONEPLUS A3000 using Tapatalk

 

[biggyk]

Why would it say cpu reset? Is that normal? I didn't tweak any thing in uefi settings.

Sent from my ONEPLUS A3000 using Tapatalk

 

[joeschmuck]

What version of FreeNAS are you running? Also, if you installed using UEFI, you may need to try the BIOS setup instead.

So you didn't get a traceback on the GUI? I'm assuming you are using the GUI. A traceback typically means that you should be reporting this as a bug.

 

[biggyk]

What version of FreeNAS are you running? Also, if you installed using UEFI, you may need to try the BIOS setup instead.

So you didn't get a traceback on the GUI? I'm assuming you are using the GUI. A traceback typically means that you should be reporting this as a bug.

I'm still fairly new to freenas. I guess I could try a bios install. I'm guessing either or does provide benefit over the other?

I didn't know about traceback. Should I be reporting this then?

Sent from my ONEPLUS A3000 using Tapatalk

 

[joeschmuck]

I would report it and let the developers weed out if this is a real bug.

The BIOS setup tends to be more successful than UEFI. The goal is for UEFI to work as well as the BIOS version.

 

[biggyk]

I would report it and let the developers weed out if this is a real bug.

The BIOS setup tends to be more successful than UEFI. The goal is for UEFI to work as well as the BIOS version.

I also have csm enabled. I just left all default. Would that ok as well?

Sent from my ONEPLUS A3000 using Tapatalk

 

[joeschmuck]

I also have csm enabled. I just left all default. Would that ok as well?

Sent from my ONEPLUS A3000 using Tapatalk

Not sure but your testing will let you know.

Since you are new to FreeNAS, you should take the time to play with it. Create and Destroy the datasets, pool, plugins, jails, etc... Do not commit data to it until after you feel like you have some control or understanding what you are doing. Also pretend to swap out a failed hard drive, everyone hates to learn this when a drive fails and to be familiar with it will ease your mind a bit. Follow the user manual for this operation, it's well written.

 

[biggyk]

Not sure but your testing will let you know.

Since you are new to FreeNAS, you should take the time to play with it. Create and Destroy the datasets, pool, plugins, jails, etc... Do not commit data to it until after you feel like you have some control or understanding what you are doing. Also pretend to swap out a failed hard drive, everyone hates to learn this when a drive fails and to be familiar with it will ease your mind a bit. Follow the user manual for this operation, it's well written.

Yeah thats a good idea. I did reinstall and restore my config, im using bios now. So far so good, no crashes. I am starting to read the manual regarding snapshots and jails ect.

 

[joeschmuck]

Beware of snapshots. While they can be good, if not setup properly they can also use up all your storage very quickley so read that section very well.

 

[Huib]

Beware of snapshots. While they can be good, if not setup properly they can also use up all your storage very quickley so read that section very well.

Isn't that mostly the case when you modify a lot of files frequently? If he is running plex he is most probably a home user and just adding big files to his lib. Not deleting or modifying them all the time.

I'm saying this since I'm running freenas at work and I'm making TONS of snapshots and even replicating them to my home without any problems.... What's the big danger for a home user?

I'm not an expert. I'm just trying to learn the edge cases I do not know yet.

 

[joeschmuck]

What's the big danger for a home user?

Hanging on to snapshots too long.

If he is running plex he is most probably a home user and just adding big files to his lib. Not deleting or modifying them all the time.

That is a big assumption to make. I assume nothing but the worst case. This user has two 4TB drives, I don't know if this is a mirror or stripe but lets assume mirror, this makes for a small pool and snapshots could eat it up quickly. I assume that with FreeNAS 11 and the addition of VMs, there could be a lot of data change going on. Setting up snapshots may be done poorly and again just eat up the storage.

I'm saying this since I'm running freenas at work and I'm making TONS of snapshots and even replicating them to my home without any problems....

I suspect that you understand what you are doing or you got lucky and set it up properly.

My warning is there to ensure the user reads about snapshots before they leap. There are a lot of theads here on the forum with the same problem of people running out of storage and it all started and ended with snapshots not being setup properly, not that you can't use snapshots.