Freenas freezing - ata5: FAILURE - out of memory in start

[Rafael]

Good afternoon everyone!

I have problems in my FreeNAS server (FreeNAS-9.2.1.5-RELEASE-x64).

Every day he crashes and repeatedly displays the following warning:

ata5: FAILURE - out of memory in start

After that I can not access the server. I need to reset the server to regain access.

Any suggestions of what can be causing this?

Server configuration:

DellPowerEdge T300
Proc: 1x Intel Xeon X3323 @ 2,50GHz
RAM: 4GBDDR2 ECC
Storage: 5X Seagate SATA 1TB Raid-Z (~3,6TB)
Network: Broadcom BCM5722

Used for NFS sharing with 4 VMware ESXI 5.5.0 servers.

 

[DrKK]

A little bit of research on this says that this error has to do with implementing RAID-like disk arrays.

1) Is the system virtualized? (I assume not)
2) Are there any tunables or sysctl's set or other "optimizations" (lol) that you've done?

 

[Rafael]

Thanks for reply!

1) No its not virtualized (system running in USB stick)
2) after the problem appeared i tried the autotune option without success.

 

[DrKK]

If you used "autotune" (we shoudl really take that out), then you now have sysctls and/or tunables set. I recommend going to those menus, and removing those tunables/sysctls (they may take a while to remove).

Is there is a controller between the motherboard and the hard drives?

 

[gpsguy]

More RAM would probably help. You should have 8Gb at a minimum.


Sent from my phone

 

[Rafael]

If you used "autotune" (we shoudl really take that out), then you now have sysctls and/or tunables set. I recommend going to those menus, and removing those tunables/sysctls (they may take a while to remove).

Is there is a controller between the motherboard and the hard drives?

No, the drives are connected directly to the motherboard.

 

[cyberjock]

I'd say your first step is meeting the minimum requirements of FreeNAS... that means 8GB of RAM. The autotune stuff has to go too. :P

 

[DrKK]

It's odd though. Normally, the system will more or less work with 4GB, but there might be performance issues (it's not like he's doing this with 768MB), and his tone in the OP suggested that everything *WAS* working fine.

He would appear to have something going on, no?

 

[cyberjock]

Oh no. Even at 4GB of RAM people have serious problems. Can't create volumes and other completely unexplainable and unseen errors rear their heads.

 

[Rafael]

Exactly! everything worked fine for a few weeks until this error appears.
The memory is a concern, but was not allowed to buy more memory at the time.

Any ideas on how I can get around this error?

 

[cyberjock]

Aside from trying more RAM, nope. Notice that nobody else on the forum has seen your error before.. that's classic "I don't have enough RAM" problems.

 

[Rafael]

It seems that there is no solution, I'll have to buy more RAM.

Thank you all for answering me so quickly.

Good weekend.

 

[cyberjock]

Keep in mind the problem may not be that you actually need more RAM. But the problem is that there's no easy way to rule that out except to get more RAM. :( So the first step is to rule out the easy/simple stuff.

 

[c32767a]

Good afternoon everyone!

I have problems in my FreeNAS server (FreeNAS-9.2.1.5-RELEASE-x64).

Every day he crashes and repeatedly displays the following warning:

ata5: FAILURE - out of memory in start

After that I can not access the server. I need to reset the server to regain access.

Any suggestions of what can be causing this?

Server configuration:

DellPowerEdge T300
Proc: 1x Intel Xeon X3323 @ 2,50GHz
RAM: 4GBDDR2 ECC
Storage: 5X Seagate SATA 1TB Raid-Z (~3,6TB)
Network: Broadcom BCM5722

Used for NFS sharing with 4 VMware ESXI 5.5.0 servers.

How are your drives connected to the machine? Via the onboard SATA ports or a PERC card?

Have you gone to DELL's web site and confirmed that your BIOS, BMC firmware are up to the most recent version? I believe you can download a liveCD that will check and update if needed.

I've run T300s with 4G of RAM with both FreeNAS and FreeBSD. They work fine, with certain caveats. None fail to boot with that type of error.