On 06/25/2014 06:05 AM, Dale wrote: > J. Roeleveld wrote: >> On 25 June 2014 01:09:03 CEST, Dale <rdalek1...@gmail.com> 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 >>> >>> === START OF READ SMART DATA SECTION === >>> SMART Self-test log structure revision number 1 >>> Num Test_Description Status Remaining >>> LifeTime(hours) LBA_of_first_error >>> # 1 Extended offline Completed: read failure 60% >>> 16365 2905482560 >>> # 2 Extended offline Completed: read failure 60% >>> 16352 2905482560 >>> # 3 Extended offline Completed without error 00% >>> 8044 - >>> # 4 Extended offline Completed without error 00% >>> 3121 - >>>
this is pretty bad. enough to really go and get a replacement asap, and turn that disk off if you can. the self test stops at the first error it comes to and in this case it is LBA#2905482560 for calculation of where the error is check out the smartcl [1] site which will help you to mark the block bad though the data that was in that block is probably lost forever. i'd also suggest you run # smartctl -a /dev/sdc and paste the results here. the crucial rows are 196/197 the reallocated sector counts and pending sector counts. they show how many blocks have been reallocated, and also how many are pending. this will give you a scaling factor, at the moment you are in trouble, if these figures are very high you are in very high trouble, if they are low you are in low trouble. [1] http://smartmontools.sourceforge.net/badblockhowto.html
