From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 84A2213877A for ; Wed, 25 Jun 2014 07:26:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 95D41E088C; Wed, 25 Jun 2014 07:26:48 +0000 (UTC) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) by pigeon.gentoo.org (Postfix) with ESMTP id 90280E0818 for ; Wed, 25 Jun 2014 07:26:47 +0000 (UTC) Received: from [212.54.42.134] (helo=smtp3.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1WzhbS-0000oh-Kt for gentoo-user@lists.gentoo.org; Wed, 25 Jun 2014 09:26:46 +0200 Received: from 53579160.cm-6-8c.dynamic.ziggo.nl ([83.87.145.96] helo=data.antarean.org) by smtp3.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1WzhbS-0005qJ-52 for gentoo-user@lists.gentoo.org; Wed, 25 Jun 2014 09:26:46 +0200 Received: from [192.168.45.104] (53579160.cm-6-8c.dynamic.ziggo.nl [83.87.145.96]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id 0B5044C for ; Wed, 25 Jun 2014 09:25:34 +0200 (CEST) User-Agent: K-9 Mail for Android In-Reply-To: <53AA587F.8090300@gmail.com> References: <53AA050F.4070907@gmail.com> <49620f42-d9c3-43b1-9f01-1250e52eb950@email.android.com> <53AA587F.8090300@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Subject: Re: [gentoo-user] smartctrl drive error @60% From: "J. Roeleveld" Date: Wed, 25 Jun 2014 09:26:44 +0200 To: gentoo-user@lists.gentoo.org Message-ID: <8657ca17-4c68-4b96-af12-479417fec6f5@email.android.com> Content-Transfer-Encoding: quoted-printable X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.8 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9,DOS_RCVD_IP_TWICE_B=0.001,PROLO_TRUST_RDNS=-3,RDNS_DYNAMIC=0.982,TW_HD=0.077 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: 318b89c3-c5f7-43c7-bcef-7771315c00f1 X-Archives-Hash: 7fb312bc102e2240181d015d373cc348 On 25 June 2014 07:05:03 CEST, Dale wrote: >J. Roeleveld wrote: >> On 25 June 2014 01:09:03 CEST, Dale wrote: >>> Howdy, >>> >>> I run this test every once in a while. How bad is this: >>> >>> root@fireball / # smartctl -l selftest /dev/sdc >>> smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.14.0-gentoo] (local >>> build) >>> Copyright (C) 2002-13, Bruce Allen, Christian Franke, >>> www.smartmontools.org >>> >>> =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D >>> SMART Self-test log structure revision number 1 >>> Num Test_Description Status Remaining=20 >>> LifeTime(hours) LBA_of_first_error >>> # 1 Extended offline Completed: read failure 60% =20 >>> 16365 2905482560 >>> # 2 Extended offline Completed: read failure 60% =20 >>> 16352 2905482560 >>> # 3 Extended offline Completed without error 00% =20 >>> 8044 - >>> # 4 Extended offline Completed without error 00% =20 >>> 3121 - >>> >>> And better yet, is there any way to tell it to not use that part and >>> finish the test? It seems it stopped when it got to that, or I >think >>> it >>> did.=20 >>> >>> Thoughts?=20 >>> >>> Dale >>> >>> :-) :-)=20 >> Dale, >> >> Not sure how to get it to go past. Think that is in the firmware of >the disk. >> >> I would start with making a backup first. >> >> -- >> Joost > >That's a 3TB drive. I don't have anything big enough to back it up to. > >Is there anyway to find out if this error is really serious or just a >run of the mill type error? I would think that if it was a run of the >mill error the drive would handle the error itself and I wouldn't even >see it. Something like marking the area as bad and just not trying to >use it anymore, even for the test.=20 > >Thanks. Any advice is appreciated. I need a hard drive guru. ;-) > >Here is additional info: > >root@fireball / # hdparm -i /dev/sdc > >/dev/sdc: > > Model=3DST3000DM001-9YN166, FwRev=3DCC4C, SerialNo=3DZ1F0PKT5 > Config=3D{ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } > RawCHS=3D16383/16/63, TrkSize=3D0, SectSize=3D0, ECCbytes=3D4 > BuffType=3Dunknown, BuffSize=3Dunknown, MaxMultSect=3D16, MultSect=3D16 > CurCHS=3D16383/16/63, CurSects=3D16514064, LBA=3Dyes, LBAsects=3D586053= 3168 > IORDY=3Don/off, tPIO=3D{min:120,w/IORDY:120}, tDMA=3D{min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4 > DMA modes: mdma0 mdma1 mdma2 > UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 > AdvancedPM=3Dyes: unknown setting WriteCache=3Denabled > Drive conforms to: unknown: ATA/ATAPI-4,5,6,7 > > * signifies the current active mode > >root@fireball / # > > > >Dale > >:-) :-)=20 There are some options with smartctl you could try to force the drive to = swap that bad sector with a spare one. A full disk read could also force that. Eg. Try ' dd if=3D/dev/sdc of=3D/= dev/null '. But, I usually order a replacement when Smart tests start throwing errors= . I know 3TB is a lot for you to have to backup, but it's also a lot of dat= a to loose... -- Joost --=20 Sent from my Android device with K-9 Mail. Please excuse my brevity.