From nobody Mon Jul 10 13:17:35 2023 X-Original-To: freebsd-hackers@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 4R04LN2grHz2tv7h for ; Mon, 10 Jul 2023 13:17:48 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f53.google.com (mail-vs1-f53.google.com [209.85.217.53]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R04LN12SYz464v for ; Mon, 10 Jul 2023 13:17:48 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-f53.google.com with SMTP id ada2fe7eead31-440bb9bad3cso1169542137.0 for ; Mon, 10 Jul 2023 06:17:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688995066; x=1691587066; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=15olOHyzD9vB/Npwl/D8Z7TcqfWSNxmJsMnOBVc72z4=; b=CWmZ1cabO3ON4P4qbAeDMkK8WXO1OIymZnl8lzP5Rmbn8qYVGV5cDTBGrY9GINLavx tgoRSPRQtExBVwlsqElnlZjUgXJxtNErgN46+esWrPecd8jkxQ5+zILt6u8yJxD/DcmG 636Ai1NXeD7355YuODYnpAwXKb/y/uUod2T01qL7gUa1TLhjnvUOSKLUN2GYHR86ri/G hYBGf79fsVPPzKYdnPA6iwBAQRScH9Wp8Ku1FOxdQQx/VoG3NJ2RMJGEbRRZ0frIHoB5 Fs+kFKMhnDqHs1lSBkO7XnmGO1Rg/U1naSFFWhoAAGIvxEpNZ+5yfWWyjfMCs0f69RVa EA+Q== X-Gm-Message-State: ABy/qLZTL5xAkiAhp4ZsvFqQn5gXm/82A01N7LaxC1iN9qZpG+fApT5N V6KLc1FSKPgJeHkN9oQuKdExHBY9I3Z21ZRlH7BL0r9I71Q= X-Google-Smtp-Source: APBJJlF+77AI4bB9pwIDJ6xW2tao289jt7dQx8kbZaDaGKBHD7PmywiHZU823wSA6ymHhrPWmxhH6jwEYWz4zKQu3Gg= X-Received: by 2002:a67:e903:0:b0:444:bf8f:a939 with SMTP id c3-20020a67e903000000b00444bf8fa939mr4649338vso.12.1688995066687; Mon, 10 Jul 2023 06:17:46 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <6A5954CF-E4B4-4CFD-BCB3-652B89F2475A@bsd4all.org> In-Reply-To: <6A5954CF-E4B4-4CFD-BCB3-652B89F2475A@bsd4all.org> From: Alan Somers Date: Mon, 10 Jul 2023 06:17:35 -0700 Message-ID: Subject: Re: ZFS Solaris: Cannot find the pool label To: pblok@bsd4all.org Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4R04LN12SYz464v X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Mon, Jul 10, 2023 at 1:18=E2=80=AFAM Peter Blok wrot= e: > > Hi, > > I have a small sized NAS with an on-board LSI SAS2308 controller in IR mo= de, but with drives presented directly. Due to space constraints I=E2=80=99= m booting of those drives, which host a RAID-Z pool. A known problem with t= he on-board controller is that it is getting to hot and over time it dies s= lowly with lots of controller resets. This happened before, but I had a spa= re MB. > > Over the weekend this started to happen with my last spare MB. I still ha= d a PCIe version of SAS2308 and plugged that with the drives into a newer m= achine, because it doesn=E2=80=99t fit in the existing case. > > The boot loader is started but it stops with Solaris: Cannot find the boo= t label for zroot > > When I add an extra drive on a SATA port and install FreeBSD ( same versi= on 13-stable of a couple of days ago ) I can import the pool ok and scrub i= t. No errors found, but booting stil fails the same way even when I physica= lly disconnect the extra drive. > > There are differences: > > - PCIe controller runs in IT mode. Reported drive size in blocks is ident= ical. Firmware is 17.0. based when the on-board had 20.0 (latest) and ran I= R in pass-thru. > - hardware is different > > Before I start upgrading firmware, I would like to investigate a bit more= . (This is my last controller and I don=E2=80=99t want to brick it with new= er firmware) > > Which label is ZFS complaining about and where is it located? > > Peter At any point did you do `zpool upgrade` or `zpool set`? Maybe you activated a zpool feature that is too new for the bootloader to understand. You could try reinstalling the boot loader. -Alan