I have a system that I have moved a ZEVO-created mirror into, and subsequently boot that system with various USB flash installs of FreeNAS 8.3.x (tried current RELEASE, two nightly builds and a beta on two different 8GB flash drives) inducing a kernel panic right after it launches all available CPU cores and sees the disk geometry. Anecdotally the "geometry does not match label" message before the fatal trap may or may not be indicative of the root cause, my searching for similar KPs has lead to postings that this isn't a fatal condition or shouldn't be in and of itself.
I get the GEOM error about the label, and then a couple of new lines and then Fatal trap 12 while in kernel mode, a newline, and "Trying to mount root from ufs://dev/ufs/FreeNASs1a".
More recently the current process was `firmware taskq`, but other attempts usually reference `g_event`. It stops in to the debugger and I'm not competent enough to read a trace correctly.
If I pull the disks, the system will boot. If I plug them back in, it KPs. I'm inclined to think that FreeBSD/FreeNAS are not able to handle the GUID -> EFI -> ZFS layout. Honestly I don't even know what FreeBSD's ZFS disks look like or if they have a disklabel like UFS disks or what.
This isn't a show-stopper or anything for me, it's really more of a curiosity at this point. If I want to continue with testing FreeNAS on that hardware I'll just get new disks, right? But it did make me wonder if I would be able to move a ZFS volume back from FreeNAS to OS X and ZEVO if I needed to, or if OS X would balk at the disks FreeBSD's ZFS tools make.
If this isn't an appropriate question, no hard feelings for nuking it or whatever. I'll stick to my core competency of cluttering up grahamperrin's posts like I do elsewhere
