Re: ZFS i/o error in recent 12.0

2018-03-21 Thread KIRIYAMA Kazuhiko
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 unavail

Re: ZFS i/o error in recent 12.0

2018-03-21 Thread Markus Wild
Hello Thomas, > > I had faced the exact same issue on a HP Microserver G8 with 8TB disks and > > a 16TB zpool on FreeBSD 11 about a year > > ago. > I will ask you the same question as I asked the OP: > > Has this pool had new vdevs addded to it since the server was installed? No. This is a mi

Re: ZFS i/o error in recent 12.0

2018-03-21 Thread Thomas Steen Rasmussen
On 03/20/2018 08:50 AM, Markus Wild wrote: > > I had faced the exact same issue on a HP Microserver G8 with 8TB disks and a > 16TB zpool on FreeBSD 11 about a year ago. Hello, I will ask you the same question as I asked the OP: Has this pool had new vdevs addded to it since the server was instal

Re: ZFS i/o error in recent 12.0

2018-03-21 Thread Thomas Steen Rasmussen
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

Re: ZFS i/o error in recent 12.0

2018-03-20 Thread Allan Jude
On 2018-03-20 10:29, Andriy Gapon wrote: > On 20/03/2018 09:09, Trond Endrestøl wrote: >> This step has been big no-no in the past. Never leave your >> bootpool/rootpool in an exported state if you intend to boot from it. >> For all I know, this advice might be superstition for the present >> ve

Re: ZFS i/o error in recent 12.0

2018-03-20 Thread Andriy Gapon
On 20/03/2018 09:09, Trond Endrestøl wrote: > This step has been big no-no in the past. Never leave your > bootpool/rootpool in an exported state if you intend to boot from it. > For all I know, this advice might be superstition for the present > versions of FreeBSD. Yes, it is. That does not

Re: ZFS i/o error in recent 12.0

2018-03-20 Thread Toomas Soome
> On 20 Mar 2018, at 09:50, Markus Wild wrote: > > Hi there, > >> 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

Re: ZFS i/o error in recent 12.0

2018-03-20 Thread Markus Wild
Hi there, > 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 > > 268847104 30978715648

Re: ZFS i/o error in recent 12.0

2018-03-20 Thread Trond Endrestøl
On Tue, 20 Mar 2018 08:00+0900, 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 d

Re: ZFS i/o error in recent 12.0

2018-03-19 Thread Allan Jude
On 2018-03-19 19:00, 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

ZFS i/o error in recent 12.0

2018-03-19 Thread KIRIYAMA Kazuhiko
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 unav