From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 72A6E15800A for ; Sun, 02 Mar 2025 21:59:37 +0000 (UTC) Received: from lists.gentoo.org (bobolink.gentoo.org [140.211.166.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 5AE15343105 for ; Sun, 02 Mar 2025 21:59:37 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 92A15110472; Sun, 02 Mar 2025 21:58:31 +0000 (UTC) Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bobolink.gentoo.org (Postfix) with ESMTPS id 759811102D0 for ; Sun, 02 Mar 2025 21:58:30 +0000 (UTC) Received: by mail-pj1-x102d.google.com with SMTP id 98e67ed59e1d1-2fe96dd93b4so6982502a91.0 for ; Sun, 02 Mar 2025 13:58:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740952709; x=1741557509; darn=lists.gentoo.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=TglMpBwdkbYj6vph1ceknspdKGkUqBYdrsThEaoJFt8=; b=i5kME2n909AApFod4Wd7CWl0TPV8iBo68Jf6bg4t75tqbVerNPugEriS2VToccq5UX N9pFkzIvJL8iApXpqURJMoBn0nlV9apdE4JE+gPEgI8/Lwe/wGhUaPKM6DsVCzbsytsa j01CtcnRGMyjg0QK4Ke5Ae2ATy9ut6eZo/pW6wsHciITUR3VLq8PgKzWQeN8b4HjdWA6 M6z4w+KDo+rz47yQqjjTnnHNm6sFCC9227idHC842QOCcGfsog5h0+GoiMsRNdFKwNFP oFCP9xAjUaqgT/7SNPTUGv+CPANEv5mO7EREeya9JEp79f4/D5PSZScVB+sELeO0+7/J pcSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740952709; x=1741557509; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=TglMpBwdkbYj6vph1ceknspdKGkUqBYdrsThEaoJFt8=; b=uyO6xLeAiJfmR0txzOKaRGGOm+Vt6wmNoDL8p6ws7hTyrvq77zcZEwdN4WLLyndcEL R+79Bnce/thwzuNrMaatPoaO+cJHhh9Af4J0N1MA8L5X4uqCMbiy67Z8R5NTEEtGKLnT 9h9Cs/zbVqhkf7DODxvwXliPMYc5XC9JVTCE6uODEH+8eS/+KvQQdgUdZC6Le8KKwwlS p0GoIvybfopuDiyUvg2OlS4jCPrDtKKwULePHEknjM3huSuIH1sG2GwWaDOVQAbLgIY+ sVNgs407E8M2pXHFe1FokzutP8Zrmjdla4se/KHYaJ2umXvQKU5W/5qS1f3a6NHDuxfz 8qQg== X-Gm-Message-State: AOJu0Yz4zCsZLgnz4if6d7hI2rBhMsz18eaYHM5UpWK06+nJQYcfpcTp EZvoqePM64kCMYPrvw0XvaNr8G9PpUFszG6u299e7Q7Jhbu6iq7XwMSCafWv9AiK2xh/LrcgrjP FjW40DkdSQ3I3NNvK0qkxf7MMbmZ9c9RygOs= X-Gm-Gg: ASbGncu8IN9LJF8pOPAGFzFxX66Gcna61fCr0gHgXbkQDPd3ThKay9ZsKYlLhiRmpZZ ZUVlFHleWjTes8jus+SdtGVnQ53+587TRoAWCIQuItRZhrIWa6J+nW+V/L4x3IcJ7W5+ZJtm5tf KtafCvocojEXd/PS7Dv4J/Cvo8jO7s X-Google-Smtp-Source: AGHT+IFuEP0sQLbJBxEHZnVNcHc+a5IJzO00sJPtfJhC7BkFyG/jIzElh+Rc1M28cQ+Wp+hTH6Yurlfz/VdreX4j7Ls= X-Received: by 2002:a17:90b:3cc6:b0:2fa:9c9:20a3 with SMTP id 98e67ed59e1d1-2feb9ac1836mr18533111a91.0.1740952709400; Sun, 02 Mar 2025 13:58:29 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <3335789.aeNJFYEL58@rogueboard> <83da23d6-4320-4858-af1d-9f1e7fd38ef7@youngman.org.uk> In-Reply-To: <83da23d6-4320-4858-af1d-9f1e7fd38ef7@youngman.org.uk> From: gevisz Date: Sun, 2 Mar 2025 23:58:15 +0200 X-Gm-Features: AQ5f1JrwMBLPnYXE4__j8YDPBizyNVligAdMZZ08gQ_0YTh5lDbxZaCmrmDGW9E Message-ID: Subject: Re: [gentoo-user] Problem with detecting ZFS HDD To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 2f3a5ed6-9c8b-40e5-beb6-fd875ad6606a X-Archives-Hash: 6b37ac49a15f3c62eb7ae4051c01df1f =D0=B2=D1=81, 16 =D1=84=D0=B5=D0=B2=D1=80. 2025=E2=80=AF=D0=B3. =D0=B2 18:5= 1, Wols Lists : > > 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 p= ort. > > 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 p= ort. 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...