After PVE Update kernel trap 12

[Theflu]

I have (had) FreeNAS running on Proxmox VE. I upated PVE and after the reboot I am getting a fatal trap 12 non of the hardware has changed and all other VMs run fine. I am lost here I have terabytes of data on this NAS for my VMs and want to get it back online ASAP.

Any Ideas?

I know virtualization of a NAS isn't ideal but I only have one server and I have a lot going on with it.


Thanks,
Flu

 

[Theflu]

Or at least a way to pull my config from the broken drive and use it on the a fresh build and import my raid z.

 

[gpsguy]

The config file resides here /data/freenas-v1.db on your boot device.

Or at least a way to pull my config from the broken drive and use it on the a fresh build and import my raid z.

 

[Theflu]

So if I do a fresh install and replace the db file and import my raid z it should be back to normal?

 

[William Grzybowski]

He has no idea what he is talking about.

Impossible to say without you posting the panic photo.

 

[Theflu]

Here is the crash data.

 

[William Grzybowski]

Ok, that is a bug with FreeBSD supporting this hypervisor.

You'll have to downgrade to the same version you were using before.

 

[cyberjock]

I have (had) FreeNAS running on Proxmox VE. I upated PVE and after the reboot I am getting a fatal trap 12 non of the hardware has changed and all other VMs run fine. I am lost here I have terabytes of data on this NAS for my VMs and want to get it back online ASAP.

Any Ideas?

I know virtualization of a NAS isn't ideal but I only have one server and I have a lot going on with it.


Thanks,
Flu

There's many reasons why FreeNAS should not be used on a VM if you value your data. Many people have had zero problems and then suddenly *bam* no more data(not that I think you are in that position). Sometimes it isn't even clear why they lost their data. But this looks like one of those reasons why my noobie presentation says its great for experimenting but shouldn't be used in a production environment.

Quite honestly, if you aren't keeping religious backups of all of the data on your FreeNAS VM, you are crazy. I wouldn't even consider trusting one with DVD/Blu-Ray Rips that are easily replaceable.

 

[Theflu]

Thanks for the quick reply.

I edited grub to use the kernel before the update and I am getting the same error.

- - - Updated - - -

I have everything backed up, it syncs to another physical server offsite.

 

[William Grzybowski]

Grub? what kind of Frankenstein setup you got there? Reinstall the old version

 

[Theflu]

This worked for me. Link

tom
Proxmox Staff Member

Re: Error pfsense freebsd

we just uploaded a fix (new seabios) for the issue to our pvetest repository. if you do not want to switch to pvetest, you can download the package manually and install it with:

Code:
wget http://download.proxmox.com/debian/dists/squeeze/pvetest/binary-amd64/pve-qemu-kvm_1.4-7_amd64.deb

dpkg -i pve-qemu-kvm_1.4-7_amd64.deb
pls test and give feedback.
Best regards,
Tom