From nobody Sun Nov 27 18:10:41 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NKxVR0Hclz4jPqb for ; Sun, 27 Nov 2022 18:10:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NKxVQ45Msz464r for ; Sun, 27 Nov 2022 18:10:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id n21so20874137ejb.9 for ; Sun, 27 Nov 2022 10:10:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=C10tD6KblrWwq6MsJXng9H3OM0kUckUtk7EWxrS5iT0=; b=79ll7z7P8oDL4zxYuN56Vim3oOwzlglXpqLxC8GZVw+NwJVLFgQApqE6tu1SP51lkw HSQKhK6tK/vXaFzYOK9ITYWLOv/+AMztFgfgKzY2ebz9kDn/98i5o7EfNfqJcA55RXi5 p4Kg4sxM/EzlQy641weliNs5Q66zm4QGAxP+vIou70NX1Rswo4lgcMx0hg3ruJE9Stok I8tNchN+qB2u77KF36jz+2YO3ElO4F/JHwcUG/mypBxWCqxkJml8Fr96mXQ5fQZDrAij 3SpLzxcZw4uTJsZvE7eXIO+C2oPwYQiQUsa7beP+jEWVAWeOHd4TdgTNm7wdbC2nkji2 CyQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc: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=C10tD6KblrWwq6MsJXng9H3OM0kUckUtk7EWxrS5iT0=; b=kSjK+EHP4Hf+4wD8UsZv5EFdg6GiLSogjgIhpuTbjfpDBmc4Exda+lFmKioFzmyfHK jd9oFGvJoU3hIbXLXhRPSFMAre00FTCHcsvt3JrstOHjVCWkgxW294bkM2ip3z5Ti5K0 bHG1jxOHETflKSGNKlK+9A+jDAuFRkJb9PVD5UPeNpSKYQlUfVE22JfIiQ2onIvdWTld m8+Kru9L0ee1lN1A8NGICfuUdkfa3BEtxNcAqsDjkUQob362O+oMkPQ/V1hrl1gsa/4l dHpHJFd+jY/O0bb4ZDIPSjn8W8Vca92k7lxRnStu63QEC0t8FBuFvw+tmNMSLoBJkSbB aYdQ== X-Gm-Message-State: ANoB5pmEghbphD5he+BlYp06cR0TsHkXPsMSGW7UlDXKAwAIPtIgAZTC ayqQRwD5HmhMdv+l0WemHBQIQhy+Xyuok6NugmEM3U+Mcuo= X-Google-Smtp-Source: AA0mqf5brD3V4y88efN2nfZPiFoyYXh6RZM+r08bZIMnJieJxgDm0evTChvkj0Q5mG1CgvghWUyzNTLs4vOyxrtPZYg= X-Received: by 2002:a17:907:206f:b0:7bb:cc6b:86d6 with SMTP id qp15-20020a170907206f00b007bbcc6b86d6mr13457815ejb.252.1669572652908; Sun, 27 Nov 2022 10:10:52 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Sun, 27 Nov 2022 11:10:41 -0700 Message-ID: Subject: Re: CAM: extract HDD informations about failure/to fail? To: FreeBSD User Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000e758c105ee77ac95" X-Rspamd-Queue-Id: 4NKxVQ45Msz464r X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000e758c105ee77ac95 Content-Type: text/plain; charset="UTF-8" On Sun, Nov 27, 2022 at 8:15 AM FreeBSD User wrote: > Hello, > > well, the aim of my post sounds strange, but I'm serious. > Background: I run at home a 14-CURRENT based server with a ZFS volume > (RAIDZ) comprised from > 4x 4 TB HDD. A couple of days I had to exchange the HGST NAS drives since > one got a permanent > SMART error. So all HDDs have been replaced by now with four times Seagte > IronWolfe Pro 4TB > drives. So far, so good. > Now I face a weird sound sourcing at one of the new HDDs. The box is > supposed to be a heavy > duty poudriere build facility, so the drives are up 24/7. It seems that > one (or even more) > drives emitt a weird sound like the spindle motor is loosing for a > fraction of a second power > and spiining up the the drive again. Searching the net reveals that at > least one Seagate > customer did have the same issue and he provided an audio file of that > very weird sound, to be > found here: > > Post at reddit: > > https://www.reddit.com/r/techsupport/comments/sca6al/seagate_ironwolf_pro_making_weird_noise/ > > and herin the post of the audio file: > > https://www.mediafire.com/file/x3le816qsakiff9/Hdd.mp4/file > > I checked S.M.A.R.T for any unusual data, but everything is fine. The > values for > > Power_Cycle_Count > Power-Off_Retract_Count > Start_Stop_Count > > seem all within a reasonable range compared to the life time in hours (did > some simple > statistsics ), nothing looks unusual. > > Also, the advanced view onto each drive via > > smartctl -x > > doesn't give me any hint of a power failure as a source for the noise. > > So, big question here is: the drives are attached to a HBA, LSI3008 based > SAS9300-8i. Is it > possible to retrieve via CAM more health paramteres than those gathered by > SMART/smartmontools > and if the answer is yes, how can this be achieved? > >From SATA drives? No. smartctl with enough flags retrieves everything available. Seagate is mainstream enough that there's unlikely to be other data.... at least that Seagate documents. > It close to impossible to isolate the drive making the noise. My guts tell > me to RMA the > supposed to be faulty drive and not to wait until it dies from "spindle > motor desease" or > something that is the source for the noises. > The only way you can do this is to just apply power to the drives one at a time, which in most setups requires pulling cables. Warner --000000000000e758c105ee77ac95 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Nov 27, 2022 at 8:15 AM FreeB= SD User <freebsd@walstatt-de.d= e> wrote:
Hello,

well, the aim of my post sounds strange, but I'm serious.
Background: I run at home a 14-CURRENT based server with a ZFS volume (RAID= Z) comprised from
4x 4 TB HDD. A couple of days I had to exchange the HGST NAS drives since o= ne got a permanent
SMART error. So all HDDs have been replaced by now with four times Seagte I= ronWolfe Pro 4TB
drives. So far, so good.
Now I face a weird sound sourcing at one of the new HDDs. The box is suppos= ed to be a heavy
duty poudriere build facility, so the drives are up 24/7. It seems that one= (or even more)
drives emitt a weird sound like the spindle motor is loosing for a fraction= of a second power
and spiining up the the drive again. Searching the net reveals that at leas= t one Seagate
customer did have the same issue and he provided an audio file of that very= weird sound, to be
found here:

Post at reddit:
=C2=A0h= ttps://www.reddit.com/r/techsupport/comments/sca6al/seagate_ironwolf_pro_ma= king_weird_noise/

and herin the post of the audio file:

=C2=A0https://www.mediafire.com/file/x3le= 816qsakiff9/Hdd.mp4/file

I checked S.M.A.R.T for any unusual data, but everything is fine. The value= s for

Power_Cycle_Count
Power-Off_Retract_Count
Start_Stop_Count

seem all within a reasonable range compared to the life time in hours (did = some simple
statistsics ), nothing looks unusual.

Also, the advanced view onto each drive via

smartctl -x

doesn't give me any hint of a power failure as a source for the noise.<= br>
So, big question here is: the drives are attached to a HBA, LSI3008 based S= AS9300-8i. Is it
possible to retrieve via CAM more health paramteres than those gathered by = SMART/smartmontools
and if the answer is yes, how can this be achieved?
From SATA drives? No. smartctl with enough flags retrieves eve= rything available. Seagate is mainstream enough that there's unlikely t= o be other data.... at least that Seagate documents.
=C2=A0
=
It close to impossible to isolate the drive making the noise. My guts tell = me to RMA the
supposed to be faulty drive and not to wait until it dies from "spindl= e motor desease" or
something that is the source for the noises.

The only way you can do this is to just apply power to the drives one= at a time, which in most setups requires pulling cables.

Warner=C2=A0
--000000000000e758c105ee77ac95--