Re: Weird result while smart testing a Winchester Digital drive

[email protected]
Newsgroups gmane.linux.utilities.smartmontools
Message-ID <20140727132123.GC16178@solfire>
Hi,

On my Gentoo - Linux I smart tested (offline) my Winchester Digital
drive (SATA)


smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.14.13-RT] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (AF)
Device Model:     WDC WD10EARS-00Y5B1
Serial Number:    WD-WMAV51276611
LU WWN Device Id: 5 0014ee 001f5fb47
Firmware Version: 80.00A80
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sun Jul 27 14:39:58 2014 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled



and got (beside other things) this report:


197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       1
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       1

#14  Extended offline    Completed: read failure       90%     14484         4288352511



(the #14 is there due to my fruitless experiments - see below)

The offline test immediately stops when hitting the bad sector. 90% of
the disk was never tested.

By the way: I started smartctl as 'smartctl -d sat' as recommended by
'smartctl -d test'.

My partitionlayout is:


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x07ec16a2

Device     Boot      Start        End    Blocks  Id System
/dev/sda1  *          2048     104447     51200  83 Linux
/dev/sda2           104448   12687359   6291456  82 Linux swap / Solaris
/dev/sda3         12687360  222402559 104857600  83 Linux
/dev/sda4        222402560 1953525167 865561304   5 Extended
/dev/sda5        222404608  232890367   5242880  83 Linux
/dev/sda6        232892416  442607615 104857600  83 Linux
/dev/sda7        442609664  652324863 104857600  83 Linux
/dev/sda8        652326912  862042111 104857600  83 Linux
/dev/sda9        862044160 1071759359 104857600  83 Linux
/dev/sda10      1071761408 1281476607 104857600  83 Linux
/dev/sda11      1281478656 1491193855 104857600  83 Linux
/dev/sda12      1491195904 1953525167 231164632  83 Linux


With 

4288352511 / 512 = 8375688 I found that the swap (/dev/sda) 
partition has been affected by the bad sector.

I swappoffed the swap (...) and did a 

dd if=/dev/zero of=/dev/sda2 bs=512 conv=notrunc

and it fails with an I/O-error at a certain point.

Another offline test shows my, that the bad sector was still there (no
remapping).

To scan the rest of the disk a entered a selectiv selftest.


(one example of my fruitless experimemts...scanninng the very end of
the disk)
smartctl -t selective,1953525100-1953525167 /dev/sda
smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.14.13-RT] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Selective self-test routine immediately in off-line mode".
SPAN         STARTING_LBA           ENDING_LBA
   0           1953525100           1953525167
Drive command "Execute SMART Selective self-test routine immediately in off-line mode" successful.
Testing has begun.



BUT!: Regardless of what I entered as scan span, it ALWAYS break
with the error that the already found sector cannot be
written/accessed:


SMART Selective self-test log data structure revision number 1
 SPAN     MIN_LBA     MAX_LBA  CURRENT_TEST_STATUS
    1  1953525100  1953525167  Not_testing

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Selective offline   Completed: read failure       90%     14500         4288352511



I am completly irritated...

IF a selftest stops at the first sector, which cannot be read or
written...and the bad sector is right at the beginning of the scan
area...and any selectiv test will first check that bad sector (as it
seems) and fails than also...how can I monitor my hd in a meaningfull
manner?

Any help is very very appreciated!

Best regards,
mcc

PS: uname -a:
Linux solfire 3.14.13-RT #1 SMP PREEMPT Fri Jul 18 15:53:15 CEST 2014 x86_64 AMD Phenom(tm) II X6 1090T Processor AuthenticAMD GNU/Linux







------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.