Dear misc@, The standard way to install crypto is to go with the "(S)hell" option at boot.
In the MBR days it would be "fdisk -i sd0", now should be with the GPT option on so "fdisk -ig sd0". Doing this, importantly, no "EFI Sys" partition is created. Am I supposed to know how to add that one, or is there some magic argument to fdisk, or some system tool, that I missed, that would do that for me? Then, disklabel -E sd0 to add a RAID, bioctl it going, and proceed with /install . In my installation, sd0 is the physical harddrive, sd1 is the installation media, and sd2 is the softraid. In the installation, I instruct the installer script that I want to install on sd2 . Its first question is how I want its non-BSD partitioning to be - that is "(M)BR, (G)PT or (E)dit". (E)dit takes you into fdisk , pointless. (G)PT seems to be the right thing, but.. it creates an "EFI Sys" partition *within the logical softraid disk* and not on the root partition - obviously. Therefore I naturally remove the EFI Sys partition (offset 64, size 960, fstype MSDOS), which got BSD disklabel designation "i". I find this behavior of how (G)PT works quirky, though maybe the softraid-disklabel logics and the GPT partitioning logics are so deeply intertwined, that it still makes sense to run the ordinary GPT initialization also on softraids, and then just let the user remove the redundant EFI Sys partition that is created within the softraid. Or? Quirky anyhow. Did I understand this right? At the end of the installer, the installer tells me there is no boot partition so therefore couldn't install boot code so therefore boot will fail. And boot does fail. Your instruction for how to get this going would be much appreciated. Thanks! Tinker
