On 6/26/25 11:43, void wrote:
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
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.
--
Alexander Motin
