From nobody Sun Nov 27 22:14:27 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 4NL2w25xbZz4j027 for ; Sun, 27 Nov 2022 22:14:58 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4NL2w21P41z3hMg for ; Sun, 27 Nov 2022 22:14:58 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Authentication-Results: mx1.freebsd.org; none Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 2ARMERI3009735; Sun, 27 Nov 2022 14:14:27 -0800 (PST) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 2ARMERSR009734; Sun, 27 Nov 2022 14:14:27 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202211272214.2ARMERSR009734@gndrsh.dnsmgr.net> Subject: Re: CAM: extract HDD informations about failure/to fail? In-Reply-To: To: Warner Losh Date: Sun, 27 Nov 2022 14:14:27 -0800 (PST) CC: FreeBSD User , FreeBSD CURRENT X-Mailer: ELM [version 2.4ME+ PL121h (25)] 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 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4NL2w21P41z3hMg X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > 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 What about using camcontrol standby, that should spin the drive down. It probably takes a camcontrol reset to spin it back up. camcontrol standby ada0 camcontrol reset ada0 -- Rod Grimes rgrimes@freebsd.org