Date: Wed, 23 Nov 2005 10:33:17 +0700 (ICT) From: Olivier Nicole <on@cs.ait.ac.th> To: freebsd-scsi@freebsd.org Subject: Re: KDying disk Message-ID: <200511230333.jAN3XH61008638@banyan.cs.ait.ac.th> In-Reply-To: <4383D128.1080505@samsco.org> (message from Scott Long on Tue, 22 Nov 2005 19:17:12 -0700) References: <200511230205.jAN2526j007750@banyan.cs.ait.ac.th> <4383D128.1080505@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Nov 22 17:42:50 ufo kernel: Copied 18 bytes of sense data offset 12: 0xf1 0x0 0x3 0x0 0x51 0x3b 0x9f 0xa 0x0 0x0 0x0 0x0 0xc 0x0 0xd3 0x80 0x0 0x18 > > Nov 22 17:42:50 ufo kernel: (da0:ahd1:0:0:0): WRITE(10). CDB: 2a 0 0 51 ac 7f 0 0 4 0 > > Nov 22 17:42:50 ufo kernel: (da0:ahd1:0:0:0): CAM Status: SCSI Status Error > > Nov 22 17:42:50 ufo kernel: (da0:ahd1:0:0:0): SCSI Status: Check Condition > > Nov 22 17:42:50 ufo kernel: (da0:ahd1:0:0:0): Deferred Error: MEDIUM ERROR info:513b9f asc:c,0 > > Nov 22 17:42:50 ufo kernel: (da0:ahd1:0:0:0): Write error field replaceable unit: d3 actual retry count: 24 > > Nov 22 17:42:50 ufo kernel: (da0:ahd1:0:0:0): Retrying Command (per Sense Data) > > N > > This means that you're starting to get failing sectors. The disk can > automatically remap them if you are writing to them, but can't do Is there a way to tell what sector(s) is bad/what partition is concerned? I did a physical disk verify (from Adaptec BIOS at reboot) that detected nothing bad. I am afraid that the error message will not be an evidence good enought to claim for waranty :( Thanks, olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511230333.jAN3XH61008638>