'll allow you to get further through the boot process and perhaps
> even start your ZFS pool correctly.
>
>
>
> On Feb 19, 2013, at 12:52 PM, Konstantin Kuklin
> wrote:
>
>> you understand me right, but my problem not in dead device... raid1
>> must work correctly
0x0> adress?
2013/2/18 Fleuriot Damien :
> Reassure me here, you've replaced your failed vdev before trying to resilver
> right ?
>
> Your zpool status suggests otherwise, so I only want to make sure this is a
> status from before replacing your drive.
>
>
> On Feb 18,
d
> enough to check their ML subscription.
>
>
> On Feb 17, 2013, at 3:46 PM, Konstantin Kuklin
> wrote:
>
>> hi, i have raid1 on zfs with 2 device on pool
>> first device died and boot from second not working...
>>
>> i try to get http://mfsbsd.vx
hi, i have raid1 on zfs with 2 device on pool
first device died and boot from second not working...
i try to get http://mfsbsd.vx.sk/ flash and load from it with zpool import
http://puu.sh/2402E
when i load zfs.ko and opensolaris.ko i see this message:
Solaris: WARNING: Can't open objset for zro
So, I install FreeBSD 8.2 with ZFS patch v28 and have this error message
with full freeze zfs system:
Solaris: Warning: can`t open object for zroot/var/crash
log_sysevent: type19 is not emplement
log_sysevent: type19 is not emplement
log_sysevent: type19 is not emplement
log_sysevent: type19 is not
Good morning, I have a problem with ZFS:
ZFS filesystem version 4
ZFS storage pool version 15
Yesterday my comp with Freebsd 8.2 releng shutdown with ad4 error
detached,when I copy a big file...
and after reboot in 2 wd green 1tb say me goodbye. One of them die and other
with zfs errors:
Apr 2
