From owner-freebsd-questions@FreeBSD.ORG Mon Apr 3 13:56:36 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 59A5716A420 for ; Mon, 3 Apr 2006 13:56:36 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id F105E43D4C for ; Mon, 3 Apr 2006 13:56:35 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 2677 invoked from network); 3 Apr 2006 23:56:35 +1000 Received: from 210-84-32-140.dyn.iinet.net.au (HELO localhost) (210.84.32.140) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 3 Apr 2006 23:56:35 +1000 Date: Mon, 3 Apr 2006 23:56:31 +1000 From: Norberto Meijome To: freebsd-questions@freebsd.org Message-ID: <20060403235631.6357c20c@localhost> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.16; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Help understanding SMART log info 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: Mon, 03 Apr 2006 13:56:36 -0000 Hi there, brand new thinkpad z60m , 100GB Sata drive. Wednesday night, it started doing this little tsttt....tsttt..tstt... like it was trying to re-spin or something like this. laptop crashed - HARD. FS were a complete mess, drive VERY slow to use, most of the time doing the noise. this lasted for 3 days. Before returning it under warranty, i decided to wipe whatever data was there, so I left the drive running outside the laptop over the weekend on an USB-SATA adapter - the noise was still there, and pushing about ... 20 Kbps only. This morning the drive is working just fine and I can access ALL the data just fine (was using an OS-X box and must have made a mistake on my dd line , not sure why, BUT it didnt wipe a thing). ANYWAY, smartctl shows this: [....] Error 65535 occurred at disk power-on lifetime: 214 hours (8 days + 22 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 08 50 11 00 e0 Error: IDNF 8 sectors at LBA = 0x00001150 = 4432 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 03 08 50 11 00 e0 00 2d+21:25:42.300 WRITE DMA EXT 35 03 08 48 11 00 e0 00 2d+21:25:42.200 WRITE DMA EXT 35 03 08 40 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 38 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 30 11 00 e0 00 2d+21:25:42.000 WRITE DMA EXT Error 65534 occurred at disk power-on lifetime: 214 hours (8 days + 22 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 08 48 11 00 e0 Error: IDNF 8 sectors at LBA = 0x00001148 = 4424 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 03 08 48 11 00 e0 00 2d+21:25:42.200 WRITE DMA EXT 35 03 08 40 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 38 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 30 11 00 e0 00 2d+21:25:42.000 WRITE DMA EXT 35 03 08 28 11 00 e0 00 2d+21:25:42.000 WRITE DMA EXT [....] (about 6 times, different LBA ranges, always 8 sectors, always WRITE DMA EXT) HOW bad is the drive damaged? I run the selftests and it didnt report any issues, but I'm sure if I had run them on Friday, they would have all failed. thanks for any advice / comment, Beto