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 7B9B51580E0 for ; Thu, 30 Jan 2025 16:56:28 +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 679EB343146 for ; Thu, 30 Jan 2025 16:56:28 +0000 (UTC) Received: from bobolink.gentoo.org (localhost [127.0.0.1]) by bobolink.gentoo.org (Postfix) with ESMTP id 60D9211047D; Thu, 30 Jan 2025 16:55:18 +0000 (UTC) Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 28D901103B6 for ; Thu, 30 Jan 2025 16:55:17 +0000 (UTC) Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-2ee74291415so1377070a91.3 for ; Thu, 30 Jan 2025 08:55:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738256116; x=1738860916; darn=lists.gentoo.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=y0EDUOCN+REO48FZrAxNApqXHkqlxtko9tkcN8I6TRM=; b=e+c0VctCMR6+N3ycYaGSInUUs30n4kY/ntA+hRK+nrMo/k35wfTYGIhOWCAG2YUtCa 3vC3pntwgtPrGEF6gGyJC3hGwCPIjRgbFfkzaTMskF9lAFT5XKE4zWg6CNKgIuhuy8Cz UkvhYxZXJrlrdgJhJjMvFQT/CwoebsnbXUJRObTBICj17lYqTEyVonMVCxQwR/HQDAPr jii6r0zJhbHFxkix6rzJyIQSP8U9aVGtWXzYyH3w6fwk/Pj2ojyQpIk/tWk6LrJsY95b r0Etynq2PBsGDSPQaKpKaX6Ocf3KbCL14t5i6T5CqEScRWiyaNrwsyKUVKToevNFGKZ2 MPUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738256116; x=1738860916; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=y0EDUOCN+REO48FZrAxNApqXHkqlxtko9tkcN8I6TRM=; b=OyNUsNfaiydO0AeJBjlk66yYnT3ep2hRjSL5bElcnldMIalA6XSMcEj6mtIgP16d5F gLJXjR1T3VLcbRzu80TgkniHkxo+N8saC7qyyqNuMnn9BGxCppP4M+YpGZN+q/jpqtu5 x7k6IhQh6F1IerMA/kTksZ3QcmlAtlZSxeWyMzOhUyI6SAeE7W8PCKVNLOFmjAx0CO3Z xGZj6HeUVvxCzM4LtKLCDgCH+iSRgV3hRb3asyBf/M1QeTd00UORbisvSnsaWP5/gGHq +dvpcl2Bhgzi7MdWGKj/eEiZQbsBVq1CTkvVzIehTk3wVCybOnKDaHSgme7MJqBwhWyd pJ6Q== X-Gm-Message-State: AOJu0YzYKI4saiB5jt1yLFEZr6zwyaqeCRNKxO6lkcKmA9/krFlHbX63 TCz95Wa61Ddd37Vh0f5/n5sGayHRagz6KUFwga5zfkk0Janzd16wvn8hpyIwczH3FnOvB4er1CK LkCLgAWUzAF1apLrnkiDKczklS03vPQv2 X-Gm-Gg: ASbGncuu+DUX/hFkn3kBE0iCgjMc58l7MtIRe1ZEA5ca8XytY6QQ1kP67U9Vv184pMR bXEV64q+/L4ha2cbh1jt6HJ1mbE7jLmfhzOPQSRPYhbMTQ6VkPIfDto0W4hc+wrw/AnC9fRLBBs w= X-Google-Smtp-Source: AGHT+IFVSKKVsY+wMKTaXLgiCiMf3UmkJwUy3RtYrBEkrLaapBM/alSMyrL3gbRwGRQXE8I9ISthfAN7PorCiqlBRlE= X-Received: by 2002:a17:90b:2748:b0:2f4:465d:5c94 with SMTP id 98e67ed59e1d1-2f83abd9978mr12302413a91.11.1738256116184; Thu, 30 Jan 2025 08:55:16 -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 From: gevisz Date: Thu, 30 Jan 2025 18:55:00 +0200 X-Gm-Features: AWEUYZkTCBV7mI2UErpbiFdFQJCcrOnuz7Gy3f9Ol-wSlapm5F-rI7rmOgr14ks Message-ID: Subject: [gentoo-user] Problem with detecting ZFS HDD To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 061861b8-6ec4-488c-92c8-5f927ceb58bb X-Archives-Hash: c7d2839000937c1d28e560e365194ccf About half a year ago my old 1.5TB SATA Green WD HDD tapped me on the shoulder and said: "Hi, very soon you won't be able to read any data from me." As I have not made my backups regularly, I took this warning seriously and decided to finally realize my old idea of moving from ext4 to ZFS. So, I have bought a 500GB SATA Green WD HDD. Based on its price, I suspected it was refurbished, but I didn't have much choice since the Green WD HDDs were apparently no longer in production, and the 2TB Gold WD HDD was incomparably more expensive. After installing ZFS on it, it turned out that everything works well. So, I decided to buy two other WD HDD of the same model, to set one of them as a ZFS mirror and leave the third WD HDD for the time when one of its twin brothers fails. This time the seller warned me that these WD HDDs are refurbished but assured me that they were refurbished by WD itself. Taking into account that the previous such HDD behaved quite well, I decided to proceed with my purchase. 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.