From nobody Thu Jun 26 16:25:13 2025 X-Original-To: freebsd-current@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 4bSkYn0bx1z60kcP; Thu, 26 Jun 2025 16:25:17 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh-a1-smtp.messagingengine.com (fhigh-a1-smtp.messagingengine.com [103.168.172.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4bSkYl6P4Dz3mGl; Thu, 26 Jun 2025 16:25:15 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b="XI/eZO7M"; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=NgA+zUIG; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.152 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id 5A9B51400086; Thu, 26 Jun 2025 12:25:15 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Thu, 26 Jun 2025 12:25:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1750955115; x=1751041515; bh=1gGAZ96s3N 5wenHIhyJdls0eE8sx8xzowFmv7wJrh/o=; b=XI/eZO7MqYKtnpvfcMLDFBdDEZ FwIhlXwKDJ1lRVM9PKoCz5aDHL9UiLM/o3AuF8Z7KbkIR0GgVkMEz5WJEpJX+IA8 X3yfzPYWoJKVawZstwEuKzLkkrKuYTNaw2zZ0yG2AFF2t2Db3PUMPh0HP2LYclLx 1G2/1qXwheZ4KE7Dw5RxPOv0UjsB8vhpP5QBzDYkF4yzcFxkrk9dWx9nkidt2GwW Rtb56sd7f9FkAs3FtHo4ZILp61l/rJyodfnUuCPT4c7w7cOWgn1/jr8lCQyFJd7R 9li0ZGoj5RdLm0SUKtiTyWMMExLjPKMuRazF4gObhmNu2DSGO3uDgYELzKWg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1750955115; x=1751041515; bh=1gGAZ96s3N5wenHIhyJdls0eE8sx8xzowFm v7wJrh/o=; b=NgA+zUIGl/QWoN4NnyCXn53ZAxgM4Z2CEQ6CVcSRwIhfY0MNZc1 BNdZDEgEp7ppSDuk5Ij0lZq4dbHowkg5Ck0Ie8V0LxVv9lDIHOXxXIBHM+szrAwg o/ZpOeZ0Q/qmC8lyqLYGOf2sXwapt0bZ/bGSW9bfmb9OgqblG1K4kn+kbyM905+e cS5iZSZkCixCoHGUTD6Dh6Licwpsn/2dpGmXlACPoPvoPsMTdJJU/zVhlHPwTd6U a7VBxPpBusF2a6omPl8QVEnpT3sbSvhklCdLgH7hFuINMHgWpFpel8p/l5D6abOR f6kvpmKF9+DRnjox/tEkFAmnJnnVAzwA9dw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdeihecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegrihhl ohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvne cuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrghtthgvrhhn peekleduvdelhfeileefgffghfffkedtheellefgudfgvdegkeejjedutdehhefgueenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiuges fhdqmhdrfhhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprhgtph htthhopehfrhgvvggsshguqdhfshesfhhrvggvsghsugdrohhrghdprhgtphhtthhopehf rhgvvggsshguqdgtuhhrrhgvnhhtsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 26 Jun 2025 12:25:14 -0400 (EDT) Date: Thu, 26 Jun 2025 17:25:13 +0100 From: void To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: device in raidz2 array only partially recognised by the OS Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org References: <1542499005.232121.1750950766794@localhost> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [0.46 / 15.00]; NEURAL_SPAM_LONG(0.84)[0.842]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; NEURAL_SPAM_MEDIUM(0.29)[0.294]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27:c]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.152:from]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.08)[-0.075]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-fs@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:151847, ipnet:103.168.172.0/24, country:AU]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_LAST(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4bSkYl6P4Dz3mGl X-Spamd-Bar: / On Thu, Jun 26, 2025 at 11:58:28AM -0400, Alexander Motin wrote: >Your card is a RAID at its heart, even if you say it pretends to be >HBA to some degree. You should start from logging into its >configuration interface and checking what it thinks about the drive. >I guess the card may consider the drive faulty, or it may forget that >it is a JBOD, or decide it is a part of some RAID array. In either of >those cases it may wish hide the drive from OS. smartmontools, the >way you call it, accesses the drive via card's pass-through interface, >designed to monitor health of drives hidden from OS as being a part of >RAID array. In iLo (the machine is a hp proliant gen8) in storage information in the physical view (where all the individual disks can be seen) the status of the disk is 'ok' (all green) and drive configuration is 'unconfigured' for all disks. There's a hp tool I need to run if I need to set HPA mode again. I won't do that just yet though because there's data I'd need to back up as the mode changing process erases all data. But as you say, this one disk might be in smart array mode, given as you, I think mean that all the other disks are seen as raw devices and it's just this one that can only be seen with the cciss,7 in smartmontools. I don't understand why it was working before though, unless uncontrolled power outage upset the card, or disk, or both. --