Re: ZFS i/o error in recent 12.0

From: KIRIYAMA Kazuhiko <kiri_at_kx.openedu.org>
Date: Thu, 22 Mar 2018 15:26:09 +0900
At Wed, 21 Mar 2018 08:01:24 +0100,
Thomas Steen Rasmussen wrote:
> 
> On 03/20/2018 12:00 AM, KIRIYAMA Kazuhiko wrote:
> > Hi,
> >
> > I've been encountered suddenly death in ZFS full volume
> > machine(r330434) about 10 days after installation[1]:
> >
> > ZFS: i/o error - all block copies unavailable
> > ZFS: can't read MOS of pool zroot
> > gptzfsboot: failed to mount default pool zroot
> >
> > FreeBSD/x86 boot
> > ZFS: i/o error - all block copies unavailable
> > ZFS: can't find dataset u
> > Default: zroot/<0x0>:
> > boot: 
> 
> Has this pool had new vdevs addded to it since the server was installed?

No. /dev/mfid0p4 is a RAID60 disk of AVAGO MegaRAID driver[1].

> What does a "zpool status" look like when the pool is imported?

Like below:

root_at_t1:~ # zpool import -fR /mnt zroot
root_at_t1:~ # zpool status
  pool: zroot
 state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        zroot       ONLINE       0     0     0
          mfid0p4   ONLINE       0     0     0

errors: No known data errors
root_at_t1:~ # 

[1] http://ds.truefc.org/~kiri/freebsd/current/zfs/dmesg.boot

> 
> /Thomas
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 

---
KIRIYAMA Kazuhiko
Received on Thu Mar 22 2018 - 05:26:23 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC