From nobody Tue Nov 29 17:10:03 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 4NM8423X3cz4jJVL for ; Tue, 29 Nov 2022 17:10:42 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp052.goneo.de (smtp5.goneo.de [IPv6:2001:1640:5::8:30]) (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) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4NM84107dYz4WXr for ; Tue, 29 Nov 2022 17:10:40 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=WwR9BELb; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 2001:1640:5::8:30) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub1.goneo.de (hub1.goneo.de [IPv6:2001:1640:5::8:52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by smtp5.goneo.de (Postfix) with ESMTPS id 9CC1D10A1E43; Tue, 29 Nov 2022 18:10:33 +0100 (CET) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id AC3DD10A1E99; Tue, 29 Nov 2022 18:10:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1669741831; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ju3NDDsnwgJIGct6Z+dGm11/ljBFh5SG1xVZ9Um2anI=; b=WwR9BELb42q67hl1XJx/ZxVqPYlVBM1rlkzniW4uE9yV/XG4hhc85g6G202XFFDMPSetSD J+8FrnZEnUDMM8a7OcfFUXSNOPssqa4C2QDvgqoSbUmVaUS0PpPjJ4hQdZ5kTrioDOXBOu 9kYwe13zoRdzh2lqXVIs3v+fN1Tw3CuNHE6EGy2A6aRCVK37UyF/kwqTb12XdQLUvt550o 0lIHWUKNNo4tFFVr0Grn95tBnhujgxxghvGLKlmbCR3lTaWTa94B23pk2/NafGdeqtlTCU 0n/6+ghjRHt5OR6ObfSoqFDYguQrI0yEKJNYkeD7yB2hM10Rwqi7JS+tgeo2Tg== Received: from thor.intern.walstatt.dynvpn.de (dynamic-077-011-002-211.77.11.pool.telefonica.de [77.11.2.211]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 126C910A1E96; Tue, 29 Nov 2022 18:10:31 +0100 (CET) Date: Tue, 29 Nov 2022 18:10:03 +0100 From: FreeBSD User To: "Poul-Henning Kamp" Cc: Warner Losh , FreeBSD CURRENT Subject: Re: CAM: extract HDD informations about failure/to fail? Message-ID: <20221129181030.25299ff0@thor.intern.walstatt.dynvpn.de> In-Reply-To: <202211272112.2ARLCnsk013242@critter.freebsd.dk> References: <20221127161544.7dd1207c@thor.intern.walstatt.dynvpn.de> <202211272112.2ARLCnsk013242@critter.freebsd.dk> Organization: walstatt-de.de 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-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-UID: 59d7b4 X-Rspamd-UID: d68f08 X-Spamd-Result: default: False [-2.40 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[2001:1640:5::8:30:from]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[walstatt-de.de:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; HAS_ORG_HEADER(0.00)[]; DMARC_NA(0.00)[walstatt-de.de]; RCVD_COUNT_THREE(0.00)[4]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4NM84107dYz4WXr X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Am Sun, 27 Nov 2022 21:12:49 +0000 "Poul-Henning Kamp" schrieb: > -------- > Warner Losh writes: > > > It close to impossible to isolate the drive making the noise. > > Use a long thin piece of hard wood as a stethoscope. > > I keep a 30cm length of 6mm beech dowel in my tool-chest, > but in a pinch you can use a pencil or the shaft from an > art-brush. > > Press one end agaist the little piece of cartilage which > can close into your ear, and hold the other end against the suspect > disk-drive, and you hear if there are any mechanical issues. > > It also works for fans, motors, bikes etc. > Awesome! I'll try this nice idea. Thanks and kind regards, Oliver -- O. Hartmann