From nobody Mon Jul 10 13:54:46 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 4R059H3bK5z3cRs3 for ; Mon, 10 Jul 2023 13:54:59 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (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 4R059G34ykz4GRJ for ; Mon, 10 Jul 2023 13:54:58 +0000 (UTC) (envelope-from nonesuch@longcount.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=longcount.org header.s=google header.b=Q2J7XIwn; spf=pass (mx1.freebsd.org: domain of nonesuch@longcount.org designates 2607:f8b0:4864:20::a2e as permitted sender) smtp.mailfrom=nonesuch@longcount.org; dmarc=none Received: by mail-vk1-xa2e.google.com with SMTP id 71dfb90a1353d-47e8934d3easo1151312e0c.1 for ; Mon, 10 Jul 2023 06:54:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount.org; s=google; t=1688997297; x=1691589297; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=wimCFP9eNccnjcdShSBUcSlJYo6l1D8qLXO+TnEvTOc=; b=Q2J7XIwny1n3+Z143PvxzQhjJXJfdAwtA1fwJL57r3Tkmx5DewWXngrbZzP5SSzpF7 j2MsSt8u5JkG0YPrSnblcvnPhMr4uf2zQ8VxdnpGmhQ1RbRd8N+GbylterpMKeF5ws3+ FFltfVQ7H9Pe/NraklLP3Jmo2Tbp09wc504EDS+MFwjiOfTzTcddP9RCopUbmaD9PXiQ j1uMKmplu6MeluQ51VNFISGVidgFGg7d+3hK1S7WZIvcqa2uAAqkYqj3rBlDdR6m9oFf fkA8ZLe8siduyef9RyGqlgHYNXhYLcuLWjMSVgkj+YqSQJojyejrLYWtdT7nqJ2Eh+ta 3CDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688997297; x=1691589297; h=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=wimCFP9eNccnjcdShSBUcSlJYo6l1D8qLXO+TnEvTOc=; b=cFAK7yPKC3vwDF7CUz8vhnnQk1MNA7xloJ0nkAf8waj/CLiMMSLPjirdpd56Vmb65B jGAsZAWGwH3q3K7a4GPI9riC2NN8T7N2gFziSmv01ddB+2INeTV/8i3GcOOl+FbASH49 TqMNbl5mXxEj7MAo33tRSMZAt3uiIQRDvJ7o5DJ5iPeGR11NWqonjIThzZtt3Y2zxoUn AlEonWiWfwHtO/R6GQ9qniODEODKg9L4qm/RxDCcw0B7Jm3UZRLJAh+ajU3XtERd8DVQ jb+eKi73drhC1n7gzpJPmr2uRr/mt43qPicBdXFAG4QdHk817VV/uXwUOyl9dhtAXLtz zY1Q== X-Gm-Message-State: ABy/qLZj4IhBiY1IfTrrk14qWApXwmqAeWjZFM4IZJPxcUstdfE9hgEA wMcfiHmOQvvq2TDN66YfbO97HTj3qlG0V2YYi07mgbYzA+/nD3RtL/NPKw== X-Google-Smtp-Source: APBJJlGDPFIoxhyQdUFdKY+fBIyhrBwWj4EKTkf9/bgr9vs2JafLEp+Gpn/8bWIBwZXVxtqJHi5ODV5hW/lVkZXkqAU= X-Received: by 2002:a1f:5c42:0:b0:47e:22fd:7b65 with SMTP id q63-20020a1f5c42000000b0047e22fd7b65mr3613131vkb.14.1688997297364; Mon, 10 Jul 2023 06:54:57 -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: From: Mark Saad Date: Mon, 10 Jul 2023 09:54:46 -0400 Message-ID: Subject: Re: ZFS Solaris: Cannot find the pool label To: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="000000000000efb85f06002253a0" X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[longcount.org:s=google]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::a2e:from]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[longcount.org:+]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[longcount.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4R059G34ykz4GRJ X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000efb85f06002253a0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable pblock I have added case exhaust fans in the past to help deal with overheating cards. Not sure if this will help, but it's inexpensive . https://www.startech.com/en-us/computer-parts/fancase On Mon, Jul 10, 2023 at 9:18=E2=80=AFAM Alan Somers w= rote: > On Mon, Jul 10, 2023 at 1:18=E2=80=AFAM Peter Blok wr= ote: > > > > Hi, > > > > I have a small sized NAS with an on-board LSI SAS2308 controller in IR > mode, but with drives presented directly. Due to space constraints I=E2= =80=99m > 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 > slowly with lots of controller resets. This happened before, but I had a > spare MB. > > > > Over the weekend this started to happen with my last spare MB. I still > had a PCIe version of SAS2308 and plugged that with the drives into a new= er > machine, because it doesn=E2=80=99t fit in the existing case. > > > > The boot loader is started but it stops with Solaris: Cannot find the > boot label for zroot > > > > When I add an extra drive on a SATA port and install FreeBSD ( same > version 13-stable of a couple of days ago ) I can import the pool ok and > scrub it. No errors found, but booting stil fails the same way even when = I > physically disconnect the extra drive. > > > > There are differences: > > > > - PCIe controller runs in IT mode. Reported drive size in blocks is > identical. Firmware is 17.0. based when the on-board had 20.0 (latest) an= d > ran IR 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 wi= th newer > 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 > > --=20 mark saad | nonesuch@longcount.org --000000000000efb85f06002253a0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
pblock
=C2=A0=C2=A0 I have added case exhau= st fans in the past to help deal with overheating cards. Not sure if this w= ill help, but it's inexpensive . https://www.startech.com/en-us/computer-parts/f= ancase

On Mon, Jul 10, 2023 at 9:18=E2=80=AFAM Alan Somers <asomers@freebsd.org> wrote:
<= /div>
On Mon, Jul 10, 2023= at 1:18=E2=80=AFAM Peter Blok <pblok@bsd4all.org> wrote:
>
> Hi,
>
> I have a small sized NAS with an on-board LSI SAS2308 controller in IR= mode, but with drives presented directly. Due to space constraints I=E2=80= =99m booting of those drives, which host a RAID-Z pool. A known problem wit= h the on-board controller is that it is getting to hot and over time it die= s slowly with lots of controller resets. This happened before, but I had a = spare MB.
>
> Over the weekend this started to happen with my last spare MB. I still= had a PCIe version of SAS2308 and plugged that with the drives into a newe= r machine, because it doesn=E2=80=99t fit in the existing case.
>
> The boot loader is started but it stops with Solaris: Cannot find the = boot label for zroot
>
> When I add an extra drive on a SATA port and install FreeBSD ( same ve= rsion 13-stable of a couple of days ago ) I can import the pool ok and scru= b it. No errors found, but booting stil fails the same way even when I phys= ically disconnect the extra drive.
>
> There are differences:
>
> - PCIe controller runs in IT mode. Reported drive size in blocks is id= entical. Firmware is 17.0. based when the on-board had 20.0 (latest) and ra= n IR in pass-thru.
> - hardware is different
>
> Before I start upgrading firmware, I would like to investigate a bit m= ore. (This is my last controller and I don=E2=80=99t want to brick it with = newer firmware)
>
> Which label is ZFS complaining about and where is it located?
>
> Peter

At any point did you do `zpool upgrade` or `zpool set`?=C2=A0 Maybe you
activated a zpool feature that is too new for the bootloader to
understand.=C2=A0 You could try reinstalling the boot loader.
-Alan



--
mark saad | <= a href=3D"mailto:nonesuch@longcount.org" target=3D"_blank">nonesuch@longcou= nt.org
--000000000000efb85f06002253a0--