Date: Thu, 14 May 2009 16:25:02 +0100 From: Doug Rabson <dfr@rabson.org> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: freebsd-fs@freebsd.org Subject: Re: Booting from ZFS raidz Message-ID: <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> In-Reply-To: <20090201072432.GA25276@server.vk2pj.dyndns.org> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 1 Feb 2009 18:24:32 +1100, Peter Jeremy <peterjeremy@optushome.com.au> wrote: > On 2008-Dec-17 18:25:51 +0000, Doug Rabson <dfr@rabson.org> wrote: >>I've been working on adding raidz and raidz2 support to the boot code >>and I have a patch which could use some testing if anyone here is >>interested. This http://people.freebsd.org/~dfr/ >>raidzboot-17122008.diff adds support for raidz and raidz2. The easiest >>way to prepare a bootable pool is to put a GPT boot partition on each >>disk that will make up the raidz pool and install gptzfsboot on the >>boot partition of every drive. > > This sounds great so I thought I'd try it. Unfortunately, it didn't > work on my degraded pool [ZFS managed to kill a disk and I thought I'd > experiment]. When I tried to boot, I got: > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS > ZFS: unexpected object set type lld > > FreeBSD/i386 boot > Default: tank:/boot/loader > boot: > > The boot loader is up-to-date and was built with 'LOADER_ZFS_SUPPORT'. > Any ideas? I fixed a bug in the patch. Try this version: http://people.freebsd.org/~dfr/raidzboot-14052009.diff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?246ecf0c87f944d70c5562eeed4165c9>