From nobody Fri Jan 06 19:17:30 2023 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NpY5l4PKSz2pFYr for ; Fri, 6 Jan 2023 19:18:19 +0000 (UTC) (envelope-from bsdlists@jld3.net) Received: from mail.jld3.net (mail.jld3.net [45.55.236.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4NpY5l3w74z3hB6 for ; Fri, 6 Jan 2023 19:18:19 +0000 (UTC) (envelope-from bsdlists@jld3.net) Authentication-Results: mx1.freebsd.org; none Received: from localhost (localhost [127.0.0.1]) by mail.jld3.net (Postfix) with ESMTP id 4A69741654; Fri, 6 Jan 2023 12:18:19 -0700 (MST) X-Virus-Scanned: amavisd-new at jld3.net Received: from mail.jld3.net ([127.0.0.1]) by localhost (mail.jld3.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id N24vN7NLoDsU; Fri, 6 Jan 2023 12:18:18 -0700 (MST) Received: from [172.21.35.229] (c-24-9-144-115.hsd1.co.comcast.net [24.9.144.115]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jld) by mail.jld3.net (Postfix) with ESMTPSA id 66D9E40615; Fri, 6 Jan 2023 12:18:18 -0700 (MST) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.jld3.net 66D9E40615 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.jld3.net 66D9E40615 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jld3.net; s=8d052f02dde2; t=1673032698; bh=wQ1ECJ3nsBpi/gx4499fw4sLcMFuixWBn5Di/69AEZg=; h=From:To:Subject:Date:Message-ID:MIME-Version:From; b=zqT8yt9BSgsccwwSDZ5ZFc4zozzonp4KJyH4oIfI0St9FA6CeLZo8okXCe6OLZKNA GaH2DJc7AmdWzExKy3aFjRhjbU8sIvjufPfoTu/sVgWqoh+0xXzyi92uXArRAgELui XwQvbP0TGVnyFZar0EIVH5h67kLGkWNFcLhxUQX8= From: "John Doherty" To: "mike tancsa" Cc: freebsd-fs Subject: Re: ZFS: i/o error - all block copies unavailable Date: Fri, 06 Jan 2023 12:17:30 -0700 X-Mailer: MailMate (1.13.2r5673) Message-ID: <867AADBE-60F8-4B54-BBE8-875D381DA296@jld3.net> In-Reply-To: <48b9848c-2e47-0d4b-f8b0-6a8ef7a7c982@sentex.net> References: <9DDC68E1-4321-45D9-831E-A73F70C66191@jld3.net> <48b9848c-2e47-0d4b-f8b0-6a8ef7a7c982@sentex.net> List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4NpY5l3w74z3hB6 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:14061, ipnet:45.55.192.0/18, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Thanks for your response, that's a good idea. The HDDs are connected to a Supermicro AOC-S3008L-L8e, which has a Broadcom 3008 SAS controller supported by mpt(4). I have to take a break now but will try getting into the BIOS next. On Fri 2023-01-06 12:13 PM MST -0700, wrote: > On 1/6/2023 2:08 PM, John Doherty wrote: > >> Posting this to freebsd-fs because the problem appears to be related >> to ZFS. >> >> I have a system running FreeBSD 12.3-RELEASE to which I have only >> remote access (about 3,300 miles from where I am). >> >> This morning I ran "freebsd-update fetch" and "freebsd-update >> install" on it. This was to get it up to date with 12.3 in >> preparation for a further update to 13.1-RELEASE. >> >> I rebooted the machine after "freebsd-update install" and it doesn't >> boot all the way. I connected to its IPMI and by recording the screen >> while trying to boot it, I was able to capture error messages that >> went by too fast to read otherwise: >> >> ZFS: i/o error - all block copies unavailable >> ZFS: can't read MOS of pool zp0 >> > > Is the disk controller's driver being loaded by the kernel ? What is > the driver ?  Is it possible that the disk order has been messed up > and its trying to boot not from the boot pool, but from disks in zp0 > and not trying zroot ? If you have ipmi, try and go into the BIOS and > make sure the disk its trying to boot from first is indeed part of > zroot