From owner-freebsd-questions@FreeBSD.ORG Sat Jul 8 16:05:43 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 636F416A4DF for ; Sat, 8 Jul 2006 16:05:43 +0000 (UTC) (envelope-from hakmi@rogers.com) Received: from smtp108.rog.mail.re2.yahoo.com (smtp108.rog.mail.re2.yahoo.com [68.142.225.206]) by mx1.FreeBSD.org (Postfix) with SMTP id D8EA743D45 for ; Sat, 8 Jul 2006 16:05:42 +0000 (GMT) (envelope-from hakmi@rogers.com) Received: (qmail 61257 invoked from network); 8 Jul 2006 16:05:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:From:To:Cc:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:In-Reply-To:X-MimeOLE:Thread-Index; b=1m91OiATn2NgA5ep0q0lfsm2DaENJFm1Q9FGQYfuYz0P6lcIx5aXUj/GdQedqQ6JtCsjcLLNwW161+2guP/yGay9k6wwIc9kqNgML7TQ4oDg1R3bJmxEmfIt74xOkb8o6eLzaQm8QEG2Kxj+41oOkqZW7HOdo7JRwrZjBNKXtKA= ; Received: from unknown (HELO tamouh) (hakmi@rogers.com@70.27.160.99 with login) by smtp108.rog.mail.re2.yahoo.com with SMTP; 8 Jul 2006 16:05:41 -0000 From: "Tamouh H." To: "'Robert McIntosh'" Date: Sat, 8 Jul 2006 12:06:04 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <44AFC6C5.1010909@gmail.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: Acainkc3KJN/t9A/QIC2IlJ/csPIbQACc7ow Message-Id: <20060708160542.D8EA743D45@mx1.FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: RE: HD Errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 16:05:43 -0000 =20 >=20 > Tamouh H. wrote: > >> Hi, > >> > >> I'm seeing the following messages in /var/log/messages and am=20 > >> concerned about the integrity of the hard drive: > >> > >>> ad0: WRITE command timeout tag=3D0 serv=3D0 - resetting > >>> cd9660: RockRidge Extension > >>> ad0: READ command timeout tag=3D0 serv=3D0 - resetting > >>> ad0: READ command timeout tag=3D0 serv=3D0 - resetting > >>> ad0: READ command timeout tag=3D0 serv=3D0 - resetting > >>> cd9660: RockRidge Extension > >>> ad0: READ command timeout tag=3D0 serv=3D0 - resetting > >>> cd9660: RockRidge Extension > >>> ad0: WRITE command timeout tag=3D0 serv=3D0 - resetting > >>> ad0: READ command timeout tag=3D0 serv=3D0 - resetting > >>> ata0: resetting devices .. done > >>> ad0: READ command timeout tag=3D0 serv=3D0 - resetting > >>> ata0: resetting devices .. done > >>> swap_pager: indefinite wait buffer: device: #ad/0x20001, > >> blkno: 5488, > >>> size: 4096 > >>> ad0: WRITE command timeout tag=3D0 serv=3D0 - resetting > >> Are the ad0 messages showing the hard drive is having hardware=20 > >> problems? > >> > >> Many thanks, > >> Robert > >=20 > > Very likely, backup your important date, grab a HD=20 > manufacturer disk and test out the drive then post results=20 > here with the hard drive manufacture name/model. > >=20 > > Tamouh > >=20 > >=20 >=20 > OK, >=20 > It's a Maxtor DiamondMax Plus 9 120GB ATA/133 hard drive=20 > (EIDE). It's in a Dell Dimension P133v. I also have a Dell=20 > Optiplex GX1 which only supports a hard drive of 80 GB max. =20 > This machine is at least as old as the optiplex, so it's=20 > likely to support at most 80 GB as well, not 120 GB. >=20 > I ran Maxtor's HD Diagnostic tools on the drive and the test,=20 > with the exception of the long, full test, came back as=20 > "passed". So, I have reasonable confidence that the problem=20 > isn't the drive. >=20 > FreeBSD says during drive formatting that there may be weird=20 > errors for drives misreporting size. Are the errors that I'm=20 > seeing likely reflective of this? What should my concern level be? >=20 > Thanks again, > Robert Robert, I've seen bad drives passing the quick test but fail the long = test. Do a long test , it could be couple of bad sectors on the drive = failing, and this usually causes the short test to Pass. Also, take Gayn suggestions, check the cables...etc. Try another good = drive, if that gives the same problem then most likely something = incomatible with the ATA controller!=20