Date: Fri, 15 May 2009 19:07:30 -0500 (CDT) From: "Jonathan Noack" <noackjr@alumni.rice.edu> To: "Doug Rabson" <dfr@rabson.org> Cc: freebsd-fs@freebsd.org Subject: Re: Booting from ZFS raidz Message-ID: <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> In-Reply-To: <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 14, 2009 10:25, Doug Rabson wrote: > I fixed a bug in the patch. Try this version: > http://people.freebsd.org/~dfr/raidzboot-14052009.diff I know the bug fix was for booting from degraded pools, but I can at least give you a "no regression" report. I just set up a new amd64 box and was able to boot from a raidz1 pool using your latest patch. Getting this working from scratch was tedious but not too complicated. I followed lulf's instructions (http://blogs.freebsdish.org/lulf/2008/12/16/setting-up-a-zfs-only-system/) using the May snapshot fixit CD. Only differences were that I set up all 4 disks with gpart (identically), created a raidz1 pool, and used a patched gptzfsboot that I cross-compiled on my 7.2 i386 box for the bootcode (applied to all 4 disks). If only I had remembered to patch my /usr/src tree before rebuilding world and rebooting... *sigh* Once more unto the fixit breach... :) -Jon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9cc826f0720e1624489dd6e6d384babc.squirrel>