From nobody Fri Jan 06 21:54:55 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 4Npcb76ZRxz2qq33 for ; Fri, 6 Jan 2023 21:55:31 +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 4Npcb73kmyz3xZ8 for ; Fri, 6 Jan 2023 21:55:31 +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 E9F8D41654; Fri, 6 Jan 2023 14:55:30 -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 BVBv9QYmu3fZ; Fri, 6 Jan 2023 14:55:30 -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 BB6594061A; Fri, 6 Jan 2023 14:55:29 -0700 (MST) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.jld3.net BB6594061A DKIM-Filter: OpenDKIM Filter v2.11.0 mail.jld3.net BB6594061A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jld3.net; s=8d052f02dde2; t=1673042129; bh=B/H2xAsUO7QDuxB/hqP+v5aOrn56YILCXOKbrp15tek=; h=From:To:Subject:Date:Message-ID:MIME-Version:From; b=mZ5fLRhd+pxWlmv7h62dVg9tjBK+4Z8nCcrl/ssgmW2GJp1W1fgZyzIhGEoFom5aq bgLo93E+l6/KXqPOWxz1iMzjEp0WnJtV8gIg9aDOttxE0nerMSlpcO3zOjBIiQHYZA eHBxASMqQPl/SQ2TJlbdKnKkfVe3L2Wol7xa/ncY= From: "John Doherty" To: "mike tancsa" Cc: freebsd-fs Subject: Re: ZFS: i/o error - all block copies unavailable Date: Fri, 06 Jan 2023 14:54:55 -0700 X-Mailer: MailMate (1.13.2r5673) Message-ID: In-Reply-To: <8d73d0b1-a175-79b7-f74d-f19977dca9b1@sentex.net> References: <9DDC68E1-4321-45D9-831E-A73F70C66191@jld3.net> <48b9848c-2e47-0d4b-f8b0-6a8ef7a7c982@sentex.net> <867AADBE-60F8-4B54-BBE8-875D381DA296@jld3.net> <3C4D1747-53D4-4A5A-9153-5777D2D895CE@jld3.net> <8d73d0b1-a175-79b7-f74d-f19977dca9b1@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: 4Npcb73kmyz3xZ8 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 On Fri 2023-01-06 02:15 PM MST -0700, wrote: > On 1/6/2023 4:06 PM, John Doherty wrote: > >> BIOS settings look fine. Boot option #1 is a Micron SSD as it should >> be. It's not clear which of the two installed devices like that it >> is. There's one on SATA port 0 and an identical one on SATA port 1. >> >> Also, occurred to me after my previous message that the machine can't >> be trying to boot from zp0, there's no OS installed there. If I let >> it try to boot normally, it gets far enough that I can ping its >> network interfaces, so it must be trying to boot from the zroot pool. >> >> Now wondering whether there's a problem with one of the two SSDs >> configured as the zroot pool. So far, don't see how to choose whether >> it boots from SATA P0 or SATA P1 but there's got to be a way, I >> think. >> > > Does it mount anything from zp0 like /usr thats required for the OS to > fully boot ?   Can you not use ipmi to bring up the console and log > in via single user mode ?  You can change the boot pref in the BIOS > (on most motherboards anyways) but if its a mirror, beyond the boot > loader I dont think it should make much of a difference or even hit > F11 to bring the boot menu at bios time. But its when you move to > RELENG_13 with the different zfs features you need to be really > careful to update the boot loaders in order to recognize the new > features of the pool. Thanks for your response. No, it doesn't mount anything from zp0 that's required to boot. Figured out how to choose between SATA P0 and P1 as the boot device. Was set to P0, now set to P1, not really making any difference. Cannot get to single-user mode via IPMI. Not sure if the machine is really not booting or if I'm having some problem with IPMI. I'm using SuperMicro IPMIView on a linux machine which seems to work OK. Right now, I have the BIOS set to boot from SATA P1 and when I try to boot to single-user mode from the beastie menu, it gets this far: Loading kernel... /boot/kernel/kernel text=0x1752e24 data=0x140 data=0x7662b0 syms=[0x8+0x188a18+0x8+0x1a5dbc] loading required module 'smbus' /boot/kernel/smbus.ko size 0x2680 at 0x24a7000 loading required module 'opensolaris' /boot/entropy size=0x1000 And then the display stops updating. If I try to boot normally, the IPMI text console display also stops updating after "Loading kernel..." but things seem to proceed farther than that, in that about 15 seconds later, it starts responding to ping. The IPMI display never updates, though. Wishing I could connect to this thing via serial console and ditch IPMI but don't have that available. Getting to IPMI on this thing is sort of roundabout because of some goofiness in the networks involved, might try to simplify that if I can figure out how.