From nobody Tue Nov 29 21:20:13 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 4NMFc92hJhz4jmmd for ; Tue, 29 Nov 2022 21:20:25 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-yb1-f172.google.com (mail-yb1-f172.google.com [209.85.219.172]) (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 4NMFc83gvKz3PpG for ; Tue, 29 Nov 2022 21:20:24 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of sobomax@sippysoft.com designates 209.85.219.172 as permitted sender) smtp.mailfrom=sobomax@sippysoft.com; dmarc=none Received: by mail-yb1-f172.google.com with SMTP id z192so19192984yba.0 for ; Tue, 29 Nov 2022 13:20:24 -0800 (PST) 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=uY8o9set+a3RAQqpgRONuwAX7NLbH7NeY4Qd6vX6iog=; b=qQCLcAfN5I2NH1BRz/qrlaDcLFSZ89ju9vTuyFBLZP0dhPj7TS4mYUM0I7EStFPIku g4f9KLFsZtoupznti1q3dNtNAECg1BN+xCqVVxABRtrEJz05TJk+UH5gv8G0Dk8HJAys 4Ka51m87AAZbmXUVtMn3ylU5+J8Q5IsTehLWrXgNKnDiwxnUD1EeZkelUxyMHJcACpbi PYKZMKCsJdzOJlmrz5PbHf2AtIz3HKzeyXw6Zw084kUi6pTlvVVIPelSkIYdrhHwOb+j zXnfoOd48jxmhwXj7yrJlvhUKDJCwdXvF8dEHG2iusOJh+khzrT7VffRkVVXnM31xzuS eGGA== X-Gm-Message-State: ANoB5pnbgDlVO0wYgNyvMU7+EYgQWexAG+GzOshES/JD7ojt+f/EwdEM F4QuAtomfY6KklWdxx0MtJpUJ2xydpYJ426pEKGzQsVMY6o= X-Google-Smtp-Source: AA0mqf5CB+wkex6iWE4FukNaqIGnBmVmvrqx3Trt4Cja11hLmSymgNbxJqInINZSHu4umbVk0i9x5RGTqameeSMwTgw= X-Received: by 2002:a25:cfd6:0:b0:6f9:1448:d55c with SMTP id f205-20020a25cfd6000000b006f91448d55cmr4279360ybg.257.1669756823406; Tue, 29 Nov 2022 13:20:23 -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: Maxim Sobolev Date: Tue, 29 Nov 2022 13:20:13 -0800 Message-ID: Subject: Re: CAM: extract HDD informations about failure/to fail? To: FreeBSD User Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000521fce05eea28e80" X-Spamd-Result: default: False [0.35 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.994]; NEURAL_SPAM_LONG(0.70)[0.705]; NEURAL_HAM_MEDIUM(-0.36)[-0.357]; FORGED_SENDER(0.30)[sobomax@freebsd.org,sobomax@sippysoft.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.219.172:from]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[sobomax@freebsd.org,sobomax@sippysoft.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[sobomax]; RCVD_IN_DNSWL_NONE(0.00)[209.85.219.172:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DMARC_NA(0.00)[freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4NMFc83gvKz3PpG X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --000000000000521fce05eea28e80 Content-Type: text/plain; charset="UTF-8" Perhaps if you log r/w queue length for all 4 drives with a reasonable interval (say 1 second) under the load using gstat(8) and plot all 4 as function of time on the same graph you should have no problem to visually identify the culprit(s). At least that's how I would do it. -Maksym On Sun, Nov 27, 2022, 7: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? > 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. > > Thanks in advance, > > oh > > > -- > O. Hartmann > > --000000000000521fce05eea28e80 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Perhaps if y= ou log r/w queue length for all 4 drives with a reasonable interval (say 1 = second) under the load using gstat(8) and plot all 4 as function of time on= the same graph you should have no problem to visually identify the culprit= (s). At least that's how I would do it.

-= Maksym

On Sun, Nov 27, 2022, 7:15 AM FreeBSD User <freebsd@walstatt-de.de> 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=A0https://www.reddit.com/r/techsupport/comments/sca6al/seagate_ir= onwolf_pro_making_weird_noise/

and herin the post of the audio file:

=C2=A0https://www.mediafire.co= m/file/x3le816qsakiff9/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?
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.

Thanks in advance,

oh


--
O. Hartmann

--000000000000521fce05eea28e80--