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 62E2713877A for ; Sun, 27 Jul 2014 16:51:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D9A3FE0D34; Sun, 27 Jul 2014 16:50:53 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A75CAE0D1D for ; Sun, 27 Jul 2014 16:50:52 +0000 (UTC) Received: from localhost ([84.133.128.119]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LkxLZ-1Wb0JT2Isv-00ajMG for ; Sun, 27 Jul 2014 18:50:51 +0200 Date: Sun, 27 Jul 2014 18:50:49 +0200 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Contradictionary behaviour of SMART on hds ?!? Message-ID: <20140727165049.GD16178@solfire> References: <20140727101247.GA3817@solfire> <20140727131958.GB16178@solfire> <53D50741.3070007@gmail.com> <201407271534.18932.michaelkintzios@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 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <201407271534.18932.michaelkintzios@gmail.com> User-Agent: mutt-ng/devel-r804 (Linux) X-Provags-ID: V03:K0:dq3FYfmsAaCav6UFQ8Va9ai3w93lPnDDZ6blUjFovQ3Yby5+CnF oD9kp5IUF3WOHEfKDnyIWXWIr/BKu2tG7fftnOY60MD2Y524PXbnWg8FFTyatKa/CPGTlc2 KqWUrTm1G6NBWn9SVc/p9WfLwKykxjNir7HQNszQc0H5JNvL3PBRFPTpuvuGKH/ce7H4eUs lx9YfjJFGuuMRLLDl7Bvw== X-Archives-Salt: 7f5478dd-0bbe-475d-9881-0b262715a7da X-Archives-Hash: 114a0dadc3fcbfb57e56059fb3860fea Mick [14-07-27 16:36]: > On Sunday 27 Jul 2014 15:05:53 Dale wrote: > > meino.cramer@gmx.de wrote: > > > Dale [14-07-27 14:36]: > > >> meino.cramer@gmx.de wrote: > > >>> Back to the initial problem: How can I offline test the rest of the > > >>> disk if the first bad sector (10%) of the surface breaks the test w= ith > > >>> an error? Best regards, mcc > > >>=20 > > >> I never got mine to go past the first failure until I used dd to era= se > > >> the drive. As mentioned before, I may could have done that without > > >> moving my data but that was to complicated and risky for me at the > > >> time. From my understanding tho, until that data is moved off the b= ad > > >> spot so that the drive knows it can do what it needs to, that spot is > > >> still going to show up. I don't know of a way to make it test beyond > > >> the bad spot either. > > >>=20 > > >> If you have a drive that you can move that data over to so that you = can > > >> play with the bad drive, that's what I would do. Once you get it mo= ved, > > >> then dd the whole drive, run the test and then see what results you > > >> get. I looked at a howto that someone posted or I found and doing it > > >> with the data on there just made me nervous. > > >>=20 > > >> I'm running out of info here. Anyone else provide more help than me? > > >>=20 > > >> Dale > > >>=20 > > >> :-) :-) > > >=20 > > > Hi Dale, > > >=20 > > > thanks for the info... > > >=20 > > > I already did this. PLEASE read my previous posting completly. > > >=20 > > > dd failed with an I/O error at that spot. > >=20 > > Hmmmm. I'd be getting my data off there or some sort of backup and then > > try erasing the whole drive. If that fails as well, then it seems like > > you need a box and some shipping to get a replacement if it is under > > warranty. If the dd fails, that sounds like maybe it has a error it > > can't correct for some reason. I think dd does its thing on a basic > > level and I have never had it give me a error except for running out of > > space when it is done. I'm sure if the command you used was wrong, Neil > > would have picked up on it and said something. So, I don't think you > > are doing anything wrong, I just think your drive may have even more > > serious issues than mine had. > >=20 > > Unless someone else comes on with a idea on something else to try, I'd > > be looking for somewhere to put my data and a different drive. If after > > that you can get it working, well, you got a spare. If not, it was > > broke anyway. > >=20 > > I hope someone else has more ideas. >=20 > Does it still error out if you run the commands in this sequence? >=20 > mkswap -L swap -f -c /dev/sda2 > dd if=3D/dev/zero of=3D/dev/sda2 bs=3D512 conv=3Dnotrunc >=20 > Also, did you try the 'hdparm --write-sector' option that Volker mentione= d? >=20 > --=20 > Regards, > Mick Hi Mick, thanks for your reply on the topic. I executed the mkswap/dd combo a several times today. Since I have no logs I repeated again. Here are the results: solfire:/home/user>mkswap -L swap -f -c /dev/sda2 1 bad page mkswap: /dev/sda2: warning: wiping old swap signature. Setting up swapspace version 1, size =3D 6291448 KiB LABEL=3Dswap, UUID=3De742c0a6-862c-41e9-be4b-698b33c5a236 solfire:/home/user>dd if=3D/dev/zero of=3D/dev/sda2 bs=3D512 conv=3Dnotrunc dd: error writing =E2=80=98/dev/sda2=E2=80=99: Input/output error 1669369+0 records in 1669368+0 records out 854716416 bytes (855 MB) copied, 28.4799 s, 30.0 MB/s [1] 24047 exit 1 dd if=3D/dev/zero of=3D/dev/sda2 bs=3D512 conv=3Dno= trunc solfire:/home/user> I am a little anxious about the hdparm command... For me it is unclear what sector is meant: smartclt says: Num Test_Description Status Remaining LifeTime(hours)= LBA_of_first_error # 1 Selective offline Completed: read failure 90% 14500 = 4288352511 =46rom a previous posting I learned that "LBA" in this case is the byte counter. The sector is therefore 4288352511/512=3D8375688 However as a result of the dd command above I found this in the dmesg log: [48588.471905] end_request: I/O error, dev sda, sector 1773816 Now...what sector count fits what sector count ... ? I will not fire zeroes towards my hd this way before I know exactly to what I am shooting at... ;) Any light in all this shadow is heartly appreciated... Best regards, mcc