Date: Thu, 26 Jun 2025 16:43:30 +0100 From: void <void@f-m.fm> To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: device in raidz2 array only partially recognised by the OS Message-ID: <aF1ohYXl53oVlj7k@int21h> In-Reply-To: <1542499005.232121.1750950766794@localhost> References: <aF1UtxMn6v03JC9w@int21h> <1542499005.232121.1750950766794@localhost>
index | next in thread | previous in thread | raw e-mail
On Thu, Jun 26, 2025 at 05:12:46PM +0200, Ronald Klop wrote: >I don't dare to say. but... did you try to turn it off and on again? > >Like again full power off and power on. Or replug the cable. Yeah, it's been cold-booted and unplugged. It's in a slotted array and connected to a HP P440 card in HBA (JBOD) mode, so not much in the way of cables. What *is* unusual is this disk is SAS the others are SATA. Although in *theory* these can be mixed, I'm unsure of whether they can be mixed on the *same card* without encountering "unexpected behaviour". Like smartmontools seeing the drive but not the cam subsystem. It worked well for a time, then the power outage happened, then the UPS was exhausted, then on cold boot the disk dropped out of the array. Now it doesn't work for zfs/cam but it does for smartmontools. next thing to try is see if da7 is seen when booting the latest snapshot. If not, try booting to a different os --home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aF1ohYXl53oVlj7k>