Date: Wed, 17 Feb 2010 18:40:41 +0000 From: Pegasus Mc Cleaft <ken@mthelicon.com> To: freebsd-current@freebsd.org Cc: Chris <behrnetworks@gmail.com>, Scot Hetzel <swhetzel@gmail.com> Subject: Re: Seeing the dreaded "ZFS: i/o error - all block copies unavailable" on 9.0-CURRENT Message-ID: <201002171840.41088.ken@mthelicon.com> In-Reply-To: <64aa03031002161849s7b66b9e3l727aafd2afd3d596@mail.gmail.com> References: <64aa03031002161803h667734cal4d668b9eb9c0a1a8@mail.gmail.com> <790a9fff1002161842g17de8ecfvf2cfa8c77f03c32@mail.gmail.com> <64aa03031002161849s7b66b9e3l727aafd2afd3d596@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Chris, Scott & Current I use gptzfsboot on my AMD64 (current) machine all the time and also on my laptop. I am not sure if this will cause the problem you are seeing but I know I ran into a lot of trouble depending on what type of pool I was creating. I believe this is correct, and if I am not than I apologise in advance, but.... If you are trying to boot off a linear type pool (A single disk or a mirror) your bootable filing system has to be a zfs filing system beneath the root pool (IE: zroot/boot). If you are trying to boot off a zraid pool, your bootable filing system must be the root filing system of the pool (IE: zroot) You must also include the appropriate declaration in the /boot/loader.conf file: (for a zraid pool) zfs_load="YES" vfs.root.mountfrom="zfs:zpool" (for a linear type) zfs_load="YES" vfs.root.mountfrom="zfs:zpool/root" If I try any other method, zboot explodes in a myriad of different ways. I hope this helps Peg On Wednesday 17 February 2010 02:49:56 Chris wrote: > Scot, > > I did, as part of step 7 in section 1: > > 7. Create ZFS Pool zroot > > Fixit# mkdir /boot/zfs > Fixit# zpool create zroot /dev/gpt/disk0 > Fixit# zpool set bootfs=zroot zroot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201002171840.41088.ken>