From owner-freebsd-questions@FreeBSD.ORG Tue Jan 16 21:13:53 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFB7D16A412 for ; Tue, 16 Jan 2007 21:13:53 +0000 (UTC) (envelope-from ceo@l-i-e.com) Received: from o2.hostbaby.com (o2.hostbaby.com [67.139.134.202]) by mx1.freebsd.org (Postfix) with SMTP id 8C31913C457 for ; Tue, 16 Jan 2007 21:13:53 +0000 (UTC) (envelope-from ceo@l-i-e.com) Received: (qmail 80761 invoked by uid 98); 16 Jan 2007 21:13:56 -0000 Received: from 127.0.0.1 by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-1.25 (clamdscan: 0.88.7/2456. Clear:RC:1(127.0.0.1):. Processed in 0.14389 secs); 16 Jan 2007 21:13:56 -0000 X-Qmail-Scanner-Mail-From: ceo@l-i-e.com via o2.hostbaby.com X-Qmail-Scanner: 1.25 (Clear:RC:1(127.0.0.1):. Processed in 0.14389 secs) Received: from localhost (HELO l-i-e.com) (127.0.0.1) by localhost with SMTP; 16 Jan 2007 21:13:56 -0000 Received: from 216.230.84.67 (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Tue, 16 Jan 2007 15:13:56 -0600 (CST) Message-ID: <1398.216.230.84.67.1168982036.squirrel@www.l-i-e.com> Date: Tue, 16 Jan 2007 15:13:56 -0600 (CST) From: "Richard Lynch" To: freebsd-questions@freebsd.org User-Agent: Hostbaby Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: READ_DMA48 error interpretation X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ceo@l-i-e.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2007 21:13:53 -0000 I know the messages below mean the hard drive or IDE cards are having problems. But is this like RED ALERT or more like YELLOW or what? And what do I do about it? umount and fsck everything a lot? swap cards/drives around until it stops? Ignore it and pray? All the content is already copied to a second box, plus on CD, and none of it is crucial data, so if I lose a LITTLE data by ignoring this, I'm okay. If the whole thing wipes out, that would be bad. These drives are often spun down, as they are not accessed very often -- it's the roll-over fall-back audio server in a cobbled-together system I won't describe, as you'll just laugh at me. :-) Is it possible that these are just from the drives spinning up too slowly? +ad1: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=404955007 +ad1: FAILURE - READ_DMA48 status=51 error=10 LBA=404955007 +g_vfs_done():ad1s1[READ(offset=207336931328, length=16384)]error = 5 +ad1: TIMEOUT - READ_DMA retrying (1 retry left) LBA=106507715 +ad1: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=324791875 +ad1: FAILURE - READ_DMA48 status=51 error=10 LBA=324791875 +g_vfs_done():ad1s1[READ(offset=166293407744, length=2048)]error = 5 +ad1: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=325168415 +ad1: FAILURE - READ_DMA48 status=51 error=10 LBA=325168415 +g_vfs_done():ad1s1[READ(offset=166486196224, length=16384)]error = 5 +ad1: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=400062279 +ad1: FAILURE - READ_DMA48 status=51 error=10 LBA=400062279 +g_vfs_done():ad1s1[READ(offset=204831854592, length=4096)]error = 5 +ad1: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=387991903 +ad1: FAILURE - READ_DMA48 status=51 error=10 LBA=387991903 +g_vfs_done():ad1s1[READ(offset=198651822080, length=16384)]error = 5 +ad3: TIMEOUT - READ_DMA retrying (1 retry left) LBA=287 -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?