On 01/02/2025 00:13, gevisz wrote:
The problem is that after booting with an additional HDD,
one of these ZFS HDDs does not report any of its disk id:
nor wwn neighter in the form ata-WDC_WD5000*.
The situation remained the same even after swapping the
undetected 500GB WD HDD with the one.
And now, this makes me think that the problem is indeed with the SATA port.
I know I'm very late to the party but ...
As linux boots, it will allocate an sd* address to all the drives it
sees. So if you've got three drives, but only sda and sdb, then one of
them hasn't been detected.
Seeing as /dev/disk/by-id is only a symlink to /dev/sda, /dev/sdb etc,
from what you say I suspect you won't see the relevant sdx entry in /dev
That to me seems the obvious way to do things - linux assigns a "random"
name to the device, so it can read the device, and then symlinks the
device name to whatever random code got assigned initially.
As to why, do you have a manual for your mobo? It's an unfortunate fact
(and I don't know when it started) that a lot of SATA ports nowadays
don't work a lot of the time. When I was looking for a mobo, there was a
lot of "if you stick an NVMe in, it will disable SATA4" or whatever.
Likewise, if you used an external graphics card, depending on what PCIe
it was, it might disable certain SATA ports. Given that I wanted about
six *working* sata ports, that was a pain in the proverbial!
Basically, a lot of things nowadays run over the PCIe bus, and it's very
common for (a) lanes to be shared between different devices, and (b)
there's a pecking order - if multiple devices share a lane, only the
highest up the pecking order will work.
So of course, sods law probably says you can't even get a SATA expansion
board, because that will require the hijacked lane and won't work ...
Cheers,
Wol
