Kernel with crypto and geli won't mount /

[Christian Baer]

oxy wrote:

> in your dmesg i don't see the mirrors..
> did you compiled it in the kernel too?
> (or just load the module)
> after you load gmirror, geli will work too

No, I did not compile gmirror into the kernel. Normally, the gmirrors 
are started by

gmirror load

In case this wasn't clear:
There are two gmirrors on the drives and on top of these are two 
encrypted providers (so basicly, the mirrors are encrypted). Neither are 
needed at boot time! Here is my fstab:

# Device	Mountpoint	FStype	Options  Dump	Pass#
/dev/da0b	none		swap	sw	  0	0
/dev/da0a	/		ufs	rw,sync	  1	1
/dev/da0h	/tmp		ufs	rw,async  2	2
/dev/da1f	/usr		ufs	rw	  2	2
/dev/da0f	/usr/obj	ufs	rw,async  2	2
/dev/da0g	/var		ufs	rw	  2	2
/dev/cd0	/cdrom		cd9660	ro,noauto 0	0

The mirrors *are* on these two physical drives but only contain data (as 
in blueprints, letters, project photos, contracts etc.).

So basicly, the mirrors and geli aren't needed for FreeBSD itself but 
only to access the data stored on the system. And my problem is that 
FreeBSD won't even boot when I compile geli and crypto into the kernel - 
although neither are needed at boot time. So either there is a code 
problem somewhere or I need to change something that I couldn't find 
documented anywhere so far.

Regards
Chris