From owner-freebsd-bugs@freebsd.org Mon Aug 17 20:33:43 2020 Return-Path: Delivered-To: freebsd-bugs@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 9323A3BBAAD for ; Mon, 17 Aug 2020 20:33:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4BVm3C3Q8sz4FYk for ; Mon, 17 Aug 2020 20:33:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 7373B3BB8ED; Mon, 17 Aug 2020 20:33:43 +0000 (UTC) Delivered-To: bugs@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 721F53BBAAC for ; Mon, 17 Aug 2020 20:33:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BVm3C2PfZz4FmM for ; Mon, 17 Aug 2020 20:33:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 371182627A for ; Mon, 17 Aug 2020 20:33:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 07HKXhp8099896 for ; Mon, 17 Aug 2020 20:33:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 07HKXhOt099895 for bugs@FreeBSD.org; Mon, 17 Aug 2020 20:33:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 248630] sesutil does not report all drives in an MSA60, locate LED is off by +1 Date: Mon, 17 Aug 2020 20:33:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mike@biesele.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2020 20:33:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248630 --- Comment #4 from Mike Biesele --- Unfortunately, I have other MSA60s that are on the latest firmware (2.28, according to https://support.hpe.com/hpsc/swd/public/detail?swItemId=3Dco_119008_1#tab-h= istory ) that exhibit this same behavior. I think they are past EOL/EOS so a firm= ware update is not possible. I assume this enclosure falls under the category described at http://sg.danny.cz/sg/sg_ses.html :=20 "Prior to the EIIOE bit's introduction in ses3r06 several arrays acted as if this bit was present and set. If 'force' is given the Additional Element St= atus page's element index field is treated as if EIIOE=3D1. If 'auto' is given a heuristic is used to decide whether to set EIIOE or not." It looks like ses3r06 was introduced in August 2013, and the 2.28 firmware = for this enclosure was released in May 2013.=20=20 I think the heuristic described in the sg_ses documentation is documented i= n a large comment in sg_ses.c in sg3_utils : /* Join array has four "element index"ing stategies: * [1] based on all descriptors in the Enclosure Status (ES) dpage * [2] based on the non-overall descriptors in the ES dpage * [3] based on the non-overall descriptors of these element types * in the ES dpage: DEVICE_ETC, ARRAY_DEV_ETC, SAS_EXPANDER_ETC, * SCSI_IPORT_ETC, SCSI_TPORT_ETC and ENC_SCELECTR_ETC. * [4] based on the non-overall descriptors of the SAS_CONNECTOR_ETC * element type * * The indexes are all origin 0 with the maximum index being one less then * the number of status descriptors in the ES dpage. Table of supported * permutations follows: * * =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D * Algorithm | Indexes | Notes * |Element|Connector element|Other element| * =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D * [A] | [2] | [4] | [3] | SES-2, OR * [A] | [2] | [4] | [3] | SES-3,EIIOE=3D0 * ----------|-------|-----------------|-------------|--------------------= --- * [B] | [1] | [1] | [1] | SES-3, EIIOE=3D1 * ----------|-------|-----------------|-------------|--------------------= --- * [C] | [2] | [2] | [2] | SES-3, EIIOE=3D2 * ----------|-------|-----------------|-------------|--------------------= --- * [D] | [2] | [1] | [1] | SES-3, EIIOE=3D3 * ----------|-------|-----------------|-------------|--------------------= --- * [E] | [1] | [4] | [3] | EIIOE=3D0 and * | | | | --eiioe=3Dforce, OR * [E] | [1] | [4] | [3] | {HP JBOD} EIIOE=3D0= and * | | | | --eiioe=3Dauto and * | | | | AES[desc_0].ei=3D= =3D1 . * ----------|-------|-----------------|-------------|--------------------= --- * [F] | [2->3]| [4] | [3] | "broken_ei" when any * | | | | of AES[*].ei invalid * | | | | using strategy [2] * ----------|-------|-----------------|-------------|--------------------= --- * [Z] | - | [4] | [3] | EIP=3D0, implicit * | | | | element index of [3] * =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D * * */ Which does look pretty cumbersome, and appears to call out some HP gear for specific treatment as well. Ugh. Would a sysctl tunable be plausible to implement? Something like dev.mps.ses.X.eiioe=3D1 to mimic the --eiioe=3Dforce behavior from ses_util= and allow working around the broken behavior? I realize it may not be worth it= at this point, of course. --=20 You are receiving this mail because: You are the assignee for the bug.=