c::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 "R12" (not verified))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4frtM626cRz3Dr4
	for <bugs@FreeBSD.org>; Thu, 09 Apr 2026 08:26:42 +0000 (UTC)
	(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: bugs@FreeBSD.org
Subject: [Bug 294353] mfiutil(4)/mrsasutil(4): Information on enclosures is
 ambiguous and poorly documented
Date: Thu, 09 Apr 2026 08:26:42 +0000
Message-ID: <bug-294353-227@https.bugs.freebsd.org/bugzilla/>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Auto-Submitted: auto-generated
Sender: owner-freebsd-bugs@FreeBSD.org
MIME-Version: 1.0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D294353

            Bug ID: 294353
           Summary: mfiutil(4)/mrsasutil(4): Information on enclosures is
                    ambiguous and poorly documented
           Product: Base System
           Version: 14.4-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: michaelo@FreeBSD.org

On: reeBSD deblndw014x.innomotics.net 14.4-STABLE FreeBSD 14.4-STABLE c5e1d=
de24
GENERIC amd64

Consider this output:
> # mrsasutil show drives
> /dev/mrsas0 Physical Drives:
>  4 (  279G) JBOD <SEAGATE ST9300653SS 5301 serial=3D6XN1LGJJ\000\000??@> =
SAS E1:S13
>  5 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2W2A9> SAS E1:S0
>  6 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2W2CT> SAS E1:S1
>  7 (  279G) JBOD <SEAGATE ST9300605SS 5101 serial=3D6XP3F4YH\000\000??@> =
SAS E1:S14
>  8 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2W25E> SAS E1:S2
>  9 (  279G) JBOD <SEAGATE ST9300653SS 5301 serial=3D6XN1LGL7\000\000??@> =
SAS E1:S12
> 10 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2SR8E> SAS E1:S3
> 11 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2W3D2> SAS E1:S7
> 12 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2W2PJ> SAS E1:S4
> 13 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2W3W3> SAS E1:S5
> 14 (  838G) JBOD <SEAGATE ST9900805SS 5101 serial=3D6XS2W2HG> SAS E1:S6
> 15 (  279G) JBOD <SEAGATE ST9300605SS 5101 serial=3D6XP3F6GJ\000\000??@> =
SAS E1:S15

Let's query the same from storcli by Broadcom:
> # ./storcli64 /c0 show all
> Generating detailed summary of the adapter, it may take a while to comple=
te.
>=20
> CLI Version =3D 007.3603.0000.0000 Oct 30, 2025
> Operating system =3D FreeBSD 14.4-STABLE
> Controller =3D 0
> Status =3D Success
> Description =3D None
> ...
> PD LIST :
> =3D=3D=3D=3D=3D=3D=3D
>=20
> -------------------------------------------------------------------------=
-----
> EID:Slt DID State DG       Size Intf Med SED PI SeSz Model            Sp =
Type
> -------------------------------------------------------------------------=
-----
> 16:0      5 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:1      6 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:2      8 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:3     10 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:4     12 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:5     13 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:6     14 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:7     11 JBOD  -  838.363 GB SAS  HDD N   N  512B ST9900805SS      U  -
> 16:12     9 JBOD  -  279.396 GB SAS  HDD N   N  512B ST9300653SS      U  -
> 16:13     4 JBOD  -  279.396 GB SAS  HDD N   N  512B ST9300653SS      U  -
> 16:14     7 JBOD  -  279.396 GB SAS  HDD N   N  512B ST9300605SS      U  -
> 16:15    15 JBOD  -  279.396 GB SAS  HDD N   N  512B ST9300605SS      U  -
> -------------------------------------------------------------------------=
-----
>=20
> EID=3DEnclosure Device ID|Slt=3DSlot No|DID=3DDevice ID|DG=3DDriveGroup
> DHS=3DDedicated Hot Spare|UGood=3DUnconfigured Good|GHS=3DGlobal Hotspare
> UBad=3DUnconfigured Bad|Sntze=3DSanitize|Onln=3DOnline|Offln=3DOffline|In=
tf=3DInterface
> Med=3DMedia Type|SED=3DSelf Encryptive Drive|PI=3DPI Eligible
> SeSz=3DSector Size|Sp=3DSpun|U=3DUp|D=3DDown|T=3DTransition|F=3DForeign
> UGUnsp=3DUGood Unsupported|UGShld=3DUGood shielded|HSPShld=3DHotspare shi=
elded
> CFShld=3DConfigured shielded|Cpybck=3DCopyBack|CBShld=3DCopyback Shielded
> UBUnsp=3DUBad Unsupported|Rbld=3DRebuild

The E value does not match. How so?
> # ./storcli64 /c0/e16 show all
> CLI Version =3D 007.3603.0000.0000 Oct 30, 2025
> Operating system =3D FreeBSD 14.4-STABLE
> Controller =3D 0
> Status =3D Success
> Description =3D None
>=20
>=20
> Enclosure /c0/e16  :
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Information :
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Device ID =3D 16
> Position =3D 1
> Connector Name =3D Port 0 - 3 & Port 4 - 7 x8
> Enclosure Type =3D SES
> Status =3D OK
> FRU Part Number =3D N/A
> Enclosure Serial Number =3D
> Enclosure Zoning Mode =3D N/A
> Partner Device ID =3D Unavailable
> Device Type =3D Enclosure
> EnclLogicalID =3D 0x0000000000000000
>=20
>=20
> Inquiry Data :
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Vendor Identification =3D FTS CORP
> Product Identification =3D SAS20BP_12_25HD
> Product Revision Level =3D 0700
>=20
>=20
> EnclSasAddress :
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> -------------------------
> Index SAS address
> -------------------------
>     0 0x500605B0000272BD
> -------------------------
>=20
>=20
> Properties :
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> -------------------------------------------------------------------------=
-------------------------
> EID State Slots PD PS Fans TSs Alms SIM Port#                      ProdID=
          VendorSpecific
> -------------------------------------------------------------------------=
-------------------------
>  16 OK       16 12  0    0   3    0   0 Port 0 - 3 & Port 4 - 7 x8 SAS20B=
P_12_25HD x36-254.7.0.0
> -------------------------------------------------------------------------=
-------------------------
>=20
>=20
> EID=3DEnclosure Device ID | PD=3DPhysical drive count | PS=3DPower Supply=
 count
> TSs=3DTemperature sensor count | Alms=3DAlarm count | SIM=3DSIM Count | P=
rodID=3DProduct ID

As it turns out all Broadcom/AVAGO/LSI utils use always the enclosure id. T=
he
value matching seems to be the "enclosure position", but wait there is an i=
ndex
as well: 0. To make it even worse mfi(4) or mrsas(4) expose the position as
"unit8_t encl_index" in C.

This causes confusion because although it refers to the same item, but with
different numbering schemes. There are two ways to solve it:
* Align with Broadcom utils and use the enclosure id only since the manpage
just talks about "enclosure" w/o any specs (thus an implementation detail).
* Explicitly document as enclosure *position*, even better change from
encl_index to encl_pos in source code to make it unambiguous and add CAVEAT=
S to
the manpage.

I'd prefer the first option for consistency.

--=20
You are receiving this mail because:
You are the assignee for the bug.=