Date: Thu, 22 Mar 2018 15:26:09 +0900 From: KIRIYAMA Kazuhiko <kiri@kx.openedu.org> To: Thomas Steen Rasmussen <thomas@gibfest.dk> Cc: KIRIYAMA Kazuhiko <kiri@kx.openedu.org>, freebsd-current@freebsd.org Subject: Re: ZFS i/o error in recent 12.0 Message-ID: <201803220626.w2M6Q9KE061507@kx.openedu.org> In-Reply-To: <2deff4f0-6b97-7ccd-2763-8c812e871c78@gibfest.dk> References: <201803192300.w2JN04fx007127@kx.openedu.org> <2deff4f0-6b97-7ccd-2763-8c812e871c78@gibfest.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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@t1:~ # zpool import -fR /mnt zroot
root@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@t1:~ #
[1] http://ds.truefc.org/~kiri/freebsd/current/zfs/dmesg.boot
>
> /Thomas
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
---
KIRIYAMA Kazuhiko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201803220626.w2M6Q9KE061507>