[FreeNAS-9.2.0-RELEASE-x86] Crash / GPF after creating UFS vol

Status
Not open for further replies.

Barry

Dabbler
Joined
Dec 23, 2013
Messages
25
Hi,

I'm running 9.2 x86 in VMWare ESXi 5.5, with a 4GB VMDK and a 2.3TB VMDK.
(I know I won't get SMART monitoring, etc. in this config, and all the data is redundant.)

After creating the VM with 640MB RAM, I did the following:
1. changed the web admin server to listen on BOTH http & https, ports 80 & 443, and only listen on the admin IP instead of 0.0.0.0

2. created a UFS volume on the 2.3TB vmdk.
I watched it initializing for a few minutes and then I went to bed (last night).

This morning, my web browser had an error, and I could not reconnect, so I checked the VM console and found FreeNAS had crashed with a Fatal Trap / GPF.
I guess that it might be low on RAM, so I increased RAM to 1GB and rebooted.
It crashed again, and now I see that it's an AES-NI error.
(please see attached screenshot)

The CPU is a Xeon E3-1265L V2, which does have the AES-NI instructions, and I have not modified any of the "FreeBSD 32-bit" defaults in the VM.

Let me know if there's any tests I should try, or if I should file a bug report, or if more information is needed.

I had previously tested 9.0 or 9.1 with ZFS on the same system, so I don't currently suspect a hardware problem.

Thank you,
Barry
 

Attachments

  • FreeNAS-gpf.png
    FreeNAS-gpf.png
    97.1 KB · Views: 350

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Well, you're supposed to have 2GB of RAM minimum for UFS and 8GB of RAM minimum for ZFS. So how about you check out the minimum system requirements. :)
 

Barry

Dabbler
Joined
Dec 23, 2013
Messages
25
I've now deleted the VM and started from (virtual) scratch: created a new VM with 2.5GB RAM.

I had some problems when enabling HTTPS access, including a crash/reboot of FreeNAS, so I turned HTTPS back off.

When I tried to create the UFS volume again (2.3TB), it rebooted itself and now is getting the GPF errors again.

The ESXi server has been stable all along, but I will try to do some more testing to rule out a hardware fault.

Let me know if I can try anything else.

Thanks,
Barry
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
I don't know what else to try. It works fine for me. It could be related to you using a hardware RAID. I don't know.
 
Status
Not open for further replies.
Top