Date: Sun, 1 Feb 2009 18:24:32 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Doug Rabson <dfr@rabson.org> Cc: freebsd-fs@freebsd.org Subject: Re: Booting from ZFS raidz Message-ID: <20090201072432.GA25276@server.vk2pj.dyndns.org> In-Reply-To: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 =20 >and I have a patch which could use some testing if anyone here is =20 >interested. This http://people.freebsd.org/~dfr/=20 >raidzboot-17122008.diff adds support for raidz and raidz2. The easiest =20 >way to prepare a bootable pool is to put a GPT boot partition on each =20 >disk that will make up the raidz pool and install gptzfsboot on the =20 >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? --=20 Peter Jeremy --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmFTjAACgkQ/opHv/APuIfVNgCgwPyiB/cG5TMRKtw1GUSPRUhu lE4AoLy/TiVSXxfdIab+DFKpmeKsMW/s =wsDR -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090201072432.GA25276>