If I'm booting off the pool, the disks need to be partitioned anyway. You still get two references to each partition (the actual partition and the label), but at least they are identical. I generally always GPT partition the disks and use GPT labels. It's completely non-standard, and while it doesn't usually cause an issue, I don't like having /dev/diskpX and /dev/label/labelname, one of which is a sector smaller than the other. Then I will create standalone datasets, such poolname/data or poolname/web, etc, after installation to store actual data depending on the use of the system. I have a single poolname/ROOT/default dataset that contains the base system. I usually follow steps very similar to the 'ZFS madness' howto on here. Might just be me but I really dislike that it seems to create a dozen or so datasets just for the base system.
![mfiutil initialize drive mfiutil initialize drive](https://ahelpme.com/public/media/tutorials/bad-performance-write-through-in-a-lsi-controller-network-statistics-throughput-screenshot-1--710bfbb9db.png)
Just to add, I don't use the installer usually either. It should be possible to hack something with devd(8) but it isn't really needed on a small pool that can have 2 drives fail before losing data. There is probably something you need to tell the installer in order to be able to boot from ZFS, as that is a (relatively) new feature in FreeBSD.ĭon't bother with a spare drive and ZFS autoreplace - it isn't connected to anything in non-Solaris operating systems - it needs an outboard utility to notice that replacement is needed. Zfs set compression=on tankAt this point, you should be able to go back to the installer (a reboot may be needed) and proceed to install, creating needed partitions in the already-existing ZFS pool. # DO NOT USE DEDUP - makes scrubs take forever! Zpool create -f tank raidz2 label/slot0 label/slot1 label/slot2 label/slot33 label/slot4 label/slot5 # Label the drives so we can refer to them with device-independent labels If you are using SATA drives (as opposed to SAS), you will need to add "-d sat" to each entry in /usr/local/etc/nf or it will complain. Mfid12: 1907200MB (3905945600 sectors) RAID volume 'Slot11' is optimalIf you want to run sysutils/smartmontools you will want to load the mfip(4) (no man page, but trust me) driver, which will make the drives appear as /dev/passN devices for smartd. Mfid0: 139392MB (285474816 sectors) RAID volume 'SysDisk' is optimal Mfi0: port 0xfc00-0xfcff mem 0xdf1bc000-0xdf1bffff,0xdf1c0000-0xdf1fffff irq 32 at device 0.0 on pci2
![mfiutil initialize drive mfiutil initialize drive](https://www.insanelymac.com/uploads/monthly_05_2015/post-788634-0-76637400-1432733686.jpg)
When you boot, you'll see messages like this: Most of the PERC controllers you will run into in an R610 will be mfi(4) devices. Exit the utility and do control-alt-delete to reboot (it will remind you). Wait for the "initialization complete" message (it is fast). Arrow down and check Initialize and then arrow to the OK box and press enter. Arrow down to the Advanced Options box and check it.
![mfiutil initialize drive mfiutil initialize drive](https://www.insanelymac.com/uploads/monthly_06_2015/post-52772-0-44541600-1435133143.png)
Enter something that describes the physical location, like "Slot0". Arrow down and select the first drive with the spacebar. Leave the RAID mode at the default, RAID0. If the disks or controller have been used previously, I would select "Clear config" first. You'll normally end up on a teal-colored screen with lots of menus. You'll get a console message like "Press Control-R to enter the configuration utility".