From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id ECB3115808B for ; Tue, 12 Apr 2022 14:57:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 05165E08BF; Tue, 12 Apr 2022 14:57:22 +0000 (UTC) Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) (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 pigeon.gentoo.org (Postfix) with ESMTPS id 72E03E0896 for ; Tue, 12 Apr 2022 14:57:20 +0000 (UTC) Received: by mail-pj1-f44.google.com with SMTP id md4so10437852pjb.4 for ; Tue, 12 Apr 2022 07:57:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=fbx2Ch89ajPDO0ElR0oIUWzvgfoTJVsktqqLQidunSc=; b=ThGI4KxzoQqbmeIPGCvWyMw9YfavKyooHESQXeGG3B5J8epOZmQZy7jarw35bk77YC ZwVh/YHVFr+ew+xVN+HkxF1ldjPXc8XTUjxh7hRai8Q+FGaKWjWimN40gqaiTAyAV6hj ZP4TcLa6e/EGBVO2PR4qoDGmtL0NMxPy/n9vtTU9SLwI8bYeBY+TPwhS329wNNsKicoY o07vohvLKhVxH08bRShidbWJrdW2z/T/HZoVGpoGx35IlsNOd0V/8rtBedkqqMRm8Uej nkdBfL98S/NmTIZQCQh2+7/bgvf8yKxVP7rL7h/JjzT/EKPxGwV91QG57AnGwsA/Q+yp MdkA== X-Gm-Message-State: AOAM533dAbjjzOIXlY77EaOJ/Ebtn6WDrtlGipR+Z3ZtzsHv2j4IIDJh 2o6wjIXZ+qaV417XqCREtewLfSQE53gOEtcOPP5EvjrX X-Google-Smtp-Source: ABdhPJxKXFu9mG6qNWKqDk3drF1jZqfRYs18KtKDItg1Jwo5VVPGQXSYzIFpdZCHw6W5CrekNrUVXoW6/Yf2ud/FZac= X-Received: by 2002:a17:902:c94b:b0:158:7729:97c3 with SMTP id i11-20020a170902c94b00b00158772997c3mr7267462pla.167.1649775438140; Tue, 12 Apr 2022 07:57:18 -0700 (PDT) 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: <13443afe-5879-3108-a19a-9457c0b054d1@gmail.com> In-Reply-To: <13443afe-5879-3108-a19a-9457c0b054d1@gmail.com> From: Rich Freeman Date: Tue, 12 Apr 2022 10:57:08 -0400 Message-ID: Subject: Re: [gentoo-user] Hard drive error from SMART To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 753aca9b-c5fa-4830-a521-5e15ea16c26f X-Archives-Hash: 84c1c266f23a2d5722fac10c8ef041d9 On Mon, Apr 11, 2022 at 9:27 PM Dale wrote: > > Thoughts. Replace as soon as drive arrives or wait and see? > So, first of all just about all my hard drives are in a RAID at this point, so I have a higher tolerance for issues. If a drive is under warranty I'll usually try to see if they will RMA it. More often than not they will, and in that case there is really no reason not to. I'll do advance shipping and replace the drive before sending the old one back so that I mostly have redundancy the whole time. If it isn't under warranty then I'll scrub it and see what happens. I'll of course do SMART self-tests, but usually an error like this won't actually clear until you overwrite the offline sector so that the drive can reallocate it. A RAID scrub/resilver/etc will overwrite the sector with the correct contents which will allow this to happen. (Otherwise there is no way for the drive to recover - if it knew what was stored there it wouldn't have an error in the first place.) If an error comes back then I'll replace the drive. My drives are pretty large at this point so I don't like keeping unreliable drives around. It just increases the risk of double failures, given that a large hard drive can take more than a day to replace. Write speeds just don't keep pace with capacities. I do have offline backups but I shudder at the thought of how long one of those would take to restore. -- Rich