Seeing the dreaded "ZFS: i/o error - all block copies
unavailable" on 9.0-CURRENT
Chris
behrnetworks at gmail.com
Wed Feb 17 22:16:24 UTC 2010
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 at gmail.com> wrote:
> On Wed, Feb 17, 2010 at 12:40 PM, Pegasus Mc Cleaft <ken at mthelicon.com> wrote:
>> 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.
>>
>
> Not sure why your zboot explodes, but I use a single disk and only use
> the following in /boot/loader.conf:
>
> zfs_load="YES"
> vfs.root.mountfrom="zfs:zpool"
>
> it should work with either zfs:zpool or zfs:zpool/root.
>
> Scot
>
More information about the freebsd-current
mailing list