From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id CAEBD1384B4 for ; Sat, 2 Jan 2016 07:20:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 852EE21C01A; Sat, 2 Jan 2016 07:20:23 +0000 (UTC) Received: from asav21.altibox.net (asav21.altibox.net [109.247.116.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 64E3A21C002 for ; Sat, 2 Jan 2016 07:20:21 +0000 (UTC) Received: from postfix-relay.alstadheim.priv.no (148-252-112.87.3p.ntebredband.no [148.252.112.87]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: hakon.alstadheim@ntebb.no) by asav21.altibox.net (Postfix) with ESMTPSA id 4C5D0800EA for ; Sat, 2 Jan 2016 08:20:19 +0100 (CET) X-Finnesikke-B-A-I-T: finnesikke@alstadheim.priv.no Received: from smtps.alstadheim.priv.no (localhost [127.0.0.1]) by postfix-relay.alstadheim.priv.no (Postfix) with ESMTP id 75BE2362FC3 for ; Sat, 2 Jan 2016 08:20:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=alstadheim.priv.no; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=smtp; bh= 82GuZfSozOr2dmgEI60ivcE5sSs=; b=W727DELWsrgLAdOugPEOp800XV3/LeLO 75/MsZ8RszSX9iYwswIeqHpJHYmrbnj72q1XqDwGT+5BpI9YtabYHVBgUfbPZcd2 uHyyo70YozkNucjqsY0Ks4opvSDN9k0VFr7nqP3J+ZyWgPrzrnhyK47zQ5nUEOKA 6dkJyp3g6wc= Received: from [192.168.2.4] (unknown [192.168.2.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: hakon) by smtps.alstadheim.priv.no (Postfix) with ESMTPSA id 545A4341389 for ; Sat, 2 Jan 2016 08:20:18 +0100 (CET) Subject: Re: [gentoo-user] Hard drive noise To: gentoo-user@lists.gentoo.org References: <56749E6B.1020800@gmail.com> From: =?UTF-8?Q?H=c3=a5kon_Alstadheim?= X-Enigmail-Draft-Status: N1110 Message-ID: <56877A32.3010407@alstadheim.priv.no> Date: Sat, 2 Jan 2016 08:20:18 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 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 MIME-Version: 1.0 In-Reply-To: <56749E6B.1020800@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=DIgvm35b c=1 sm=1 tr=0 a=Rml61KfIH5gPZ/OzaJf9YA==:117 a=Rml61KfIH5gPZ/OzaJf9YA==:17 a=Git7GJnPAAAA:8 a=IkcTkHD0fZMA:10 a=7aQ_Q-yQQ-AA:10 a=3go8odswAAAA:8 a=XDLOdo3AtcPlRscMr48A:9 a=QEXdDO2ut3YA:10 X-Archives-Salt: d3e95d7e-6fbe-452f-b44b-122139cf9b28 X-Archives-Hash: 3cec6f336b5764fcf3efa2d79df7110b Den 19. des. 2015 01:01, skrev Dale: ... > It sounds like the heads are doing random > reads/writes and the heads are moving but doing so noisily. Thing is, > there is no drive activity according to gkrellm or iotop. All the > drives should be basically idle. ... > Model=ST3000DM001 What kind of file system ? How full ? Raid ? lvm ? What kind of SATA controller? There is lots of stuff about these things I don't know, but I /do/ know all those cause different quirks and telling more specifics would maybe prod someone with experience with your particular type of set-up to chime in. Just as an example, ext4 will delay some of the work on a newly formatted drive. Lots of other system activity can cause background jobs. If this coincides with a bad sector on a drive, you get noise, access latency and system wait. This system wait will not necessarily be counted against any specific process in "top(1)" (depending on how your kernel was compiled) , so you can even get 0%idle and still have no specific process sticking out in "top". Watch your logs and kernel messages for access errors. Difficulties in reading might cause retries without actually timing out. If this is your problem, it will persist until that sector is marked as failing AND SOMETHING IS WRITTEN TO IT. The sector will not be mapped out until something gets written to it. Also, if you are running raid, google around for permutations of "smartctl -T permissive -l scterc,70,70", seeing as this drive is not a server type drive. But, remember, NEVER blindly run something on your system that some random guy sent you by email without understanding what it does. :-D .