Date: Thu, 05 Nov 2015 19:11:16 -0500 From: "Michael B. Eichorn" <ike@michaeleichorn.com> To: "Eugene M. Zheganin" <emz@norma.perm.ru>, freebsd-stable@freebsd.org Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable Message-ID: <1446768676.1335.14.camel@michaeleichorn.com> In-Reply-To: <563BAE37.2090205@norma.perm.ru>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, 2015-11-06 at 00:29 +0500, Eugene M. Zheganin wrote: > Hi. > > Today one of my zfs pool disks dies, I was unable to change it on the > fly (video board was blocking it) so I powered off, changed disk (not > in > root pool) and all of a sudden I realized that i cannot boot: > > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot > > It was first reboot since October, 16th, when I installed recent > -STABLE > and upgraded zpool. I was pretty confident that I've installed loaders, > but I tried to reinstall them - no luck. Then I built today's STABLE > and > installed loaders from it - same issue. I've even tried to install less > recent loaders from a server nearby - same issue. > > Two years ago I have encountered similar (if not identical) issue: > https://lists.freebsd.org/pipermail/freebsd-stable/2013-December/076317 > .html > The main difference was it was i386. Now I have an amd64 machine. I > even > updated it's BIOS, and I still cannot boot. Zpool is fine: I'm writing > this message from this exact machine, however, I had to boot it from > today -STABLE from an USB stick. > > I've read about the zfsboottest utility and tried it on my unbootable > pool - after the bried info about it (traated as healthy) it said "OK". > I guess no errors were encountered. > > So... what can I do to restore the ability to boot from my root pool ? > > Thanks. > Eugene I had something similar happen to me in the last month with a the installer zfs setup. Unfortunately it was a critical system so I didn't have time for diagnostics. My pants-on-fire solution was that since the pool was a mirror, swap a disk out with my spare, reinstall, and send/receive the data back. Not pretty, but it was my personal mail/file/web/everything-not-on-the-firewall server. The pool was accessible from the installer shell and on import to the fresh system, it just wouldn't boot. Also in my case it was RELEASE not STABLE, and yes it was consumer grade hardware. TLDR: Not just you. Reinstall? [-- Attachment #2 --] 0 *H 010 `He 0 *H 000]0 *H 010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 150613202446Z 160614003550Z0H10Uike@michaeleichorn.com1%0# *H ike@michaeleichorn.com0"0 *H 0 UՀ,k9D %Z|Y6J<rrK g;&|uNlUE9)V.[ט̊:qS](#vSYDz*CpugYݔ,v<`j(waS#ڒ6n(K5'KVLåErv<J=[}W bLA%gޭnVb| I?M7D:$׃bM_T[,ƃ\ 00 U0 0U0U%0++0Ujj: γ+39啖0U#0Sr풜\|~5NԸQ0!U0ike@michaeleichorn.com0LU C0?0;+70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U/0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U0http://www.startssl.com/0 *H x+ȐF}pw.XvF?rg P]EOp)L˻yA ;hi0u2]m [Sbp$_ gr Xm*YP3#H>mKAǠt)HO|=@}3ӝ'iO81>03 v'h5U "H;ECZtpҗ4rWHu^6+i*kJL8shAV|5;?HMc\ j[j|+000]0 *H 010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 150613202446Z 160614003550Z0H10Uike@michaeleichorn.com1%0# *H ike@michaeleichorn.com0"0 *H 0 UՀ,k9D %Z|Y6J<rrK g;&|uNlUE9)V.[ט̊:qS](#vSYDz*CpugYݔ,v<`j(waS#ڒ6n(K5'KVLåErv<J=[}W bLA%gޭnVb| I?M7D:$׃bM_T[,ƃ\ 00 U0 0U0U%0++0Ujj: γ+39啖0U#0Sr풜\|~5NԸQ0!U0ike@michaeleichorn.com0LU C0?0;+70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U/0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U0http://www.startssl.com/0 *H x+ȐF}pw.XvF?rg P]EOp)L˻yA ;hi0u2]m [Sbp$_ gr Xm*YP3#H>mKAǠt)HO|=@}3ӝ'iO81>03 v'h5U "H;ECZtpҗ4rWHu^6+i*kJL8shAV|5;?HMc\ j[j|+0400 *H 0}10 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0 *H 0 -).2AUGo#G B|NDRpM-B=o-we5JQpa>O.#._<V [~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U00U0USr풜\|~5NԸQ0U#0N@[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[UT0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u+70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0 *H }x,\c^#wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0&
