Seeing the dreaded "ZFS: i/o error - all block copies unavailable" on 9.0-CURRENT

Chris behrnetworks at gmail.com
Wed Feb 17 18:45:49 UTC 2010


Pegasus,

Thanks for the tip. I'll give it a shot. If it is the case, then the
RootOnZFS wiki guides need to be updated to account for that. They all
currently say to use vfs.root.mountfrom="zfs:zroot" in loader.conf

Thanks,
Chris

On Wed, Feb 17, 2010 at 1: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.
>
> 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
>


More information about the freebsd-current mailing list