From owner-freebsd-questions@freebsd.org Fri Feb 28 19:04:45 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E0367242403 for ; Fri, 28 Feb 2020 19:04:45 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "holgerdanske.com", Issuer "holgerdanske.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48Tf9S3bqPz4PTv for ; Fri, 28 Feb 2020 19:04:44 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from 99.100.19.101 ([99.100.19.101]) by holgerdanske.com with ESMTPSA (ECDHE-RSA-AES128-GCM-SHA256:TLSv1.2:Kx=ECDH:Au=RSA:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Fri, 28 Feb 2020 11:04:39 -0800 Subject: Re: ZFS i/o error on boot unable to start system To: freebsd-questions@freebsd.org References: From: David Christensen Message-ID: Date: Fri, 28 Feb 2020 11:04:38 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 48Tf9S3bqPz4PTv X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of dpchrist@holgerdanske.com has no SPF policy when checking 184.105.128.27) smtp.mailfrom=dpchrist@holgerdanske.com X-Spamd-Result: default: False [-1.56 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.858,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-0.60)[ipnet: 184.104.0.0/15(0.65), asn: 6939(-3.58), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[holgerdanske.com]; RCVD_IN_DNSWL_NONE(0.00)[27.128.105.184.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:184.104.0.0/15, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2020 19:04:45 -0000 On 2020-02-28 05:51, James B. Byrne via freebsd-questions wrote: > I have reported this on the forums as well. > > FreeBSD-12.1p2 > raidz2 on 4x8TB HDD (reds) > root on zfs > > We did a hot restart of this host this morning and received the following on > the console: > > ZFS: i/o error - all block copies unavailable > ZFS: failed to read pool zroot directory object > qptzfsboot: failed to mount default pool zroot > > FreeBSD/x86 boot > ZFS: i/o error - all block copies unavailable > ZFS: can't fild dataset 0 > Default: zroot/<0x0> > boot: > > What has happened? How do I get this system back up and online? > > My first thought is that in modifying rc.conf to change some ip4 address > assignments that I may have done something else inadvertently which has caused > this. I cannot think of any other changes made since the system was last > restarted a noon yesterday. > > ​This is an urgent matter. Any help is gratefully welcomed. So, you have a desktop computer with four Western Digital Red 8 TB SATA hard disk drives. You installed FreeBSD-12.1-RELEASE-amd64 and ended up with one ZFS RAIDZ2 pool with everything in it -- boot, root, usr, var, tmp, home, whatever. You have since upgraded to 12.1-p2. Yesterday, you edited /etc/rc.conf and now the system will not boot. The most likely explanation is that you broke rc.conf. One possible solution would be too boot a rescue shell or live system, import the RAIDZ2 pool, and fix rc.conf. Be sure to export the pool each time you are done editing and before attempting to boot it. Let us know how it works out. David