[Bug 192184] [uefi] fresh install of 2014-07-14 11.0-CURRENT amd64 snapshot doesn't boot

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184

--- Comment #15 from Dave Cottlehuber <dch at skunkwerks.at> ---
@pablo I'm successfully booting direct from ZFS, here's what I learned:

1. it must be a UEFI-enabled boot image (10.1 pre-releases are good)

2. zfs must have a dataset with mountpoint=/ and your usual /boot/* stuff in
here. Note this is not actually where the kernel will be loaded from, but it's
where I keep the master copy so it's safely versioned on zfs.

3. the zpool* must have property bootfs set to point to that dataset, for
example my default bootfs is:

    bootfs=zroot/ROOT/default

4. you must have a FAT-style EFI partition, with the kernel modules & all boot
loader stuff in it. I am not exactly sure if there's a way to trim this down
and have a smaller set. You *must* copy this across from within FreeBSD, I was
unable to boot FreeBSD if I used either a linux system to transfer, or OSX --
the FAT 8.3 path mangling screwed things up.

I keep the master of /boot in ZFS but rsync it across to the EFI partition.  My
/boot/loader.conf is:

# cat /efi/boot/loader.conf

# master in zfs:/boot/loader.conf but
# actually loaded from /EFI FAT partition
# remember to keep settings mirrored
# mkdir -m 0700 /efi
# mount -f msdosfs /dev/diskid/DISK-Z1F21XGNp1 /efi
# rsync -harv /boot /efi/boot --exclude=\*.symbols --del --partial --inplace
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
kern.vty="vt"
zfs_load="YES"
vfs.root.mountfrom="zfs:zroot/ROOT/default"

my EFI partition is (directories only):

# tree -qcd
.
├── boot
│   ├── defaults
│   ├── kernel
│   ├── modules
│   ├── zfs
│   └── firmware
└── EFI
    ├── APPLE
    │   ├── EXTENSIONS
    │   ├── FIRMWARE
    │   └── CACHES
    │       └── CAFEBEEF
    └── refind
        ├── icons
        ├── drivers_x64
        └── tools_x64


As this is still a mac there is apple cruft in here. Working on getting rid of
that. This might be better discussed on one of the mailing lists BTW rather
than in a resolved ticket ;-).

-- 
You are receiving this mail because:
You are the assignee for the bug.