From owner-freebsd-fs@FreeBSD.ORG Sun Jan 27 14:56:19 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 250C1A41; Sun, 27 Jan 2013 14:56:19 +0000 (UTC) (envelope-from prvs=1739a0aae4=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 976F1382; Sun, 27 Jan 2013 14:56:18 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001878220.msg; Sun, 27 Jan 2013 14:56:16 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 27 Jan 2013 14:56:16 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1739a0aae4=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> From: "Steven Hartland" To: "Vladislav Prodan" References: <13391.1359029978.3957795939058384896@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> <93308.1359297551.14145052969567453184@ffe15.ukr.net> Subject: Re: Re[2]: AHCI timeout when using ZFS + AIO + NCQ Date: Sun, 27 Jan 2013 14:56:52 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1251"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 14:56:19 -0000 ----- Original Message ----- From: "Vladislav Prodan" >> Is it always the same disk, of so replace it SMART helps identify issues >> but doesn't tell you 100% there's no problem. > > > Now it has fallen off a different HDD - ada0. > I'm 99% sure that MHDD will not find problems in HDD - ada0 and ada2. > I still have three servers with similar chipsets that have similar problems > with blade ahci times out. I notice your disks are connecting at SATA 3.x, which rings bells. We had a very similar issue on a new Supermicro machine here and after much testing we proved to our satisfaction that the problem was the HW. Essentially the combination of SATA 3 speeds the midplane / backplane degraded the connection between the MB and HDD enough to cause the disks to randomly drop when under load. If we connected the disks directly to the MB with SATA cables the problem went away. In the end we had midplanes changed from an AHCI pass-through to active LSI controller. So if you have any sort of midplane / backplane connecting your disks try connecting them direct to the MB / controller via known SATA 3.x compliant cables and see if that stops the drops. Another test you can do is to force the disks to connect at SATA 2.x this also fixed it in our case, but wasn't something we wanted to put into production hence the controller swap. To force SATA 2 speeds you can use the following in /boot/loader.conf where 'X' is disk identifier e.g. for ada0 X = 0:- hint.ahcich.X.sata_rev=2 Hope this helps. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.