Date: Wed, 17 Feb 2010 22:49:37 -0500 From: Chris <behrnetworks@gmail.com> To: Scot Hetzel <swhetzel@gmail.com> Cc: Pegasus Mc Cleaft <ken@mthelicon.com>, freebsd-current@freebsd.org Subject: Re: Seeing the dreaded "ZFS: i/o error - all block copies unavailable" on 9.0-CURRENT Message-ID: <64aa03031002171949gdfbd99ci8eab7f29399cc011@mail.gmail.com> In-Reply-To: <64aa03031002171416s128ff196y92a5be5a6abadeb@mail.gmail.com> References: <64aa03031002161803h667734cal4d668b9eb9c0a1a8@mail.gmail.com> <790a9fff1002161842g17de8ecfvf2cfa8c77f03c32@mail.gmail.com> <64aa03031002161849s7b66b9e3l727aafd2afd3d596@mail.gmail.com> <201002171840.41088.ken@mthelicon.com> <790a9fff1002171303u4b40a90cr626ef856efee473b@mail.gmail.com> <64aa03031002171416s128ff196y92a5be5a6abadeb@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As a follow-up to this, I rebuilt world and kernel and updated my system to the latest 8.0-STABLE. I'm still seeing the problem and I can still get around it by choosing my hard drive from the F12 boot menu. I did notice that the bootloader now says it's ZFS enabled whereas it didn't while on 8.0-RELEASE. I also updated the bootcode with: "gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 adX" after installing world. No help there. It seems to me that there's a difference in the way the ZFS-enabled bootloader sees the drives that the BIOS reports as opposed to the non-ZFS-enabled bootloader. Anyone have any ideas on that? I checked for any BIOS updates but it looks like I'm current. It sure would be nice to not have to select my hard drive each time. Thanks, Chris On Wed, Feb 17, 2010 at 5:16 PM, Chris <behrnetworks@gmail.com> wrote: > How's this for bizarre? If I hit F12 to bring up the boot menu and > select my hard drive, it boots just fine! If I don't do that, with > 8.0-STABLE installed, I get the same lba error 1 <some number> errors > as well as the "ZFS: i/o error - all block copies unavailable" error. > Time to call in an exorcist... > > > > On Wed, Feb 17, 2010 at 4:03 PM, Scot Hetzel <swhetzel@gmail.com> wrote: >> On Wed, Feb 17, 2010 at 12:40 PM, Pegasus Mc Cleaft <ken@mthelicon.com> = wrote: >>> Hello Chris, Scott & Current >>> >>> =A0 =A0 =A0 =A0I use gptzfsboot on my AMD64 (current) machine all the t= ime 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. >>> >>> =A0 =A0 =A0 =A0I believe this is correct, and if I am not than I apolog= ise in advance, >>> but.... >>> >>> =A0 =A0 =A0 =A0If you are trying to boot off a linear type pool (A sing= le disk or a >>> mirror) your bootable filing system has to be a zfs filing system benea= th 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) >>> >>> =A0 =A0 =A0 =A0You must also include the appropriate declaration in the >>> /boot/loader.conf file: >>> >>> (for a zraid pool) >>> zfs_load=3D"YES" >>> vfs.root.mountfrom=3D"zfs:zpool" >>> >>> (for a linear type) >>> zfs_load=3D"YES" >>> vfs.root.mountfrom=3D"zfs:zpool/root" >>> >>> =A0 =A0 =A0 =A0If I try any other method, zboot explodes in a myriad of= different ways. >>> >> >> Not sure why your zboot explodes, but I use a single disk and only use >> the following in /boot/loader.conf: >> >> zfs_load=3D"YES" >> vfs.root.mountfrom=3D"zfs:zpool" >> >> it should work with either zfs:zpool or zfs:zpool/root. >> >> Scot >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64aa03031002171949gdfbd99ci8eab7f29399cc011>