From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 24 05:39:11 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D589516A41F for ; Thu, 24 Nov 2005 05:39:11 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4312C43D5A for ; Thu, 24 Nov 2005 05:39:09 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) by mail.cs.ait.ac.th (8.12.11/8.12.11) with ESMTP id jAO5d6nc014418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Nov 2005 12:39:06 +0700 (ICT) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.13.1/8.12.11) id jAO5d4Z0038809; Thu, 24 Nov 2005 12:39:04 +0700 (ICT) Date: Thu, 24 Nov 2005 12:39:04 +0700 (ICT) Message-Id: <200511240539.jAO5d4Z0038809@banyan.cs.ait.ac.th> From: Olivier Nicole To: ken@kdm.org In-reply-to: <20051123041414.GA14542@nargothrond.kdm.org> (ken@kdm.org) References: <200511230205.jAN2526j007750@banyan.cs.ait.ac.th> <4383D128.1080505@samsco.org> <200511230333.jAN3XH61008638@banyan.cs.ait.ac.th> <20051123041414.GA14542@nargothrond.kdm.org> X-Virus-Scanned: on CSIM by amavisd-milter (http://www.amavis.org/) Cc: freebsd-scsi@freebsd.org Subject: Re: KDying disk X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 05:39:11 -0000 Hi and thanks, > You'll probably see this block in the grown defect list. A verify probably > wouldn't find a problem with that sector, since it was remapped. To see > the grown defect list, try this: > > camcontrol defects da0 -f phys -G I did that, the disk does not support the block format of course :( > > I am afraid that the error message will not be an evidence good > > enought to claim for waranty :( > > Some drive manufacturers have a disk verification utility that will > generate pass/fail status for a drive. Sometimes they'll require output I tried the Seagate tool (as the disk is Seagate) 3 times and find no error. > This sort of thing is why I'd recommend some sort of RAID setup for most > machines now. The cost of a disk failure in time, inconvenience and The spare disk is already ordered, it is somewhere in the pipe... I planned to install RAID before I had the problem, but as the machine is new I was not expecting that it was so urgent. Anyway, I installed and run smartclt, and even smartctl gives me some errors from time to time. So I am considering it could be a problem with the onboard SCSI controler rather than with the disk . Does that make any sense? TIA, Olivier ufo: smartctl -S on /dev/da0 smartctl version 5.33 [i386-portbld-freebsd5.4] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ (pass0:ahd1:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (pass0:ahd1:0:0:0): CAM Status: Command timeout Standard Inquiry (36 bytes) failed [Operation not permitted] Retrying with a 64 byte Standard Inquiry (pass0:ahd1:0:0:0): INQUIRY. CDB: 12 0 0 0 40 0 (pass0:ahd1:0:0:0): CAM Status: SCSI Bus Reset Sent/Received Standard Inquiry (64 bytes) failed [Operation not permitted] A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. ufo: smartctl -S on /dev/da0 smartctl version 5.33 [i386-portbld-freebsd5.4] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ ufo: