Corrupted disk

[Ov10fac]

Ok,

I have a 4 drive sata raid configured. I am running the 32 bit version of FreeNAS and it has been running fine for several years. I have used zfs file system on the raid, and I have FreeNAS running on VirtualBox. Yes I know I shouldn't do that, so I was in the process of building a stand alone version.

During the rsync process the server with FreeNAS loaded powered down. As a result there seems to be a problem with the drive. I can't load FreeNAS any longer. I keep getting a "panic: kmen_malloc(16384): kmen_map too small: 326960800 total allocated
cpuid - 0
KDB: enter: panic

I installed a new VM using the old system image on VirtualBox but without the data drive and it seemed to run fine. But when I added the raid drive got the same error.

So now I need to know what can be done to get things back on line? I am considering downloading the 64 bit version and installing a new VM, then adding the drive. I am hoping that will solve the problem. But I would like to know if there is another way to boot FreeNas to correct the file system, or maybe to do something from the panic screen.

Thanks for any help.

 

[cyberjock]

Well, I'd try 8GB of RAM and the 64bit version of FreeNAS first. Then go from there based on what happens. But I will warn you that most people that have your error and virtualize rarely get their pool to mount to recover their data. Do you have backups?

 

[Ov10fac]

Since it was running inside VirtualBox, I added a 64bit version. I got that up and running then added the data disk from the original and, surprise of surprises it was all there. So then I shut the 64 bit version down and re started the 32 bit version and it too functioned .

So I'm back to normal ops.

Yes I do have backups of the files and the vid file created by VirtualBox.

 

[cyberjock]

You should get rid of FreeNAS in a VM. ZFS can't do its normal detect and repair from a VM in the configuration you are using. So all those cool ZFS benefits you want, they aren't really there.