| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 28 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 46:55:26 |
| Calls: | 422 |
| Files: | 1,024 |
| Messages: | 90,384 |
I should have used /dev/disk/by-id/ata-WDC_WD5000* notations instead!
Unfortunately, I have not found the way to change these notations
other than deleting the whole zpool and re-creating it anew with
the notations /dev/disk/by-id/ata-WDC_WD5000*, which took quite
a lot of time.
Thank you for your reply.
I will look into the link but, as far as I understand,
it does not answer the question why one of my ZFS disks does not
appear in /dev/disk/by-id/ directory when I boot my computer with
additional disk connected to it.
After setting up one of them as a ZFS mirror, I immediately
got the problem that if I boot my system with additional HDD
connected to my computer, one of these ZFS mirror disks
is not detected and the corresponding zpool appears to be degraded.
I have realized that it was my fault to use /dev/sdb and /dev/sdc
notations when setting up the ZFS mirror because with more disks
at the boot time these notations may change.
I should have used /dev/disk/by-id/ata-WDC_WD5000* notations instead!
Unfortunately, I have not found the way to change these notations
other than deleting the whole zpool and re-creating it anew with
the notations /dev/disk/by-id/ata-WDC_WD5000*, which took quite
a lot of time.
Presumably, the problem with detecting my ZFS mirror HDDs
should have disappeared after that because now the disks were
referred to by their ids but unfortunately it was not the case.
When I boot my computer with an additional external HDD
attached to the computer via USB, one of my ZFS mirror HDDs
is not detected by the system and the corresponding zpool again
appears to be degraded until I restart my computer in the usual
setup, that is, without any additional HDD attached to it.
I have looked into my /dev/disk/by-id/ directory and found out
that this happens because one of these ZFS mirror HDDs
does not appear in this directory at all!
The situation remained the same even after swapping the
undetected 500GB WD HDD with the one.
So, I wonder if it is a fault of
1) refurbished WD HDDs
2) my almost 20 years old Ultra-Durable Gigabyte motherboard
3) the Linux system itself.
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*.
And now, this makes me think that the problem is indeed with the SATA port.The situation remained the same even after swapping the
undetected 500GB WD HDD with the one.
вс, 16 февр. 2025 г. в 18:51, Wols Lists <antlists@youngman.org.uk>:
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 ...
Thank you for your insight.
Probably, after using my Gigabyte GA-MA790FXT-UD5P
motherboard for almost 20 years, I indeed should read its manual. :)
After all, "if nothing else helps, try to read the manual." :)
Will do it in the nearest future, but I doubt that it says something
about this issue.
However, I think that you are right and the problem lies in the motherboard.
By the way, for years, I have had another issue with it that confirms your point of view: if I start my computer with a Logitech USB video camera plugged in, I randomly do not have a sound out. By "randomly" I mean
that sometimes the sound out may be present and sometimes not.
I have tried everything and even started a thread about it here, but
nothing helped.
Finally, I used to start my computer without my USB video camera
plugged in, and it guarantees the presence of an audio after booting.
Additional information: I have AMD/ATI RV740 PRO [Radeon HD 4770]
video card plugged into PCIEX16_1 slot and (never used) "brackets",
one of which is connected to F_AUDIO and the other is connected to a SATA port.
The manual also says that my motherboard has 6 SATA ports working
via South Bridge and 4 SATA ports working via another Gigabyte SATA chip.
Maybe, I have to experiment with connecting my hard drives to SATA
ports in different order...