Re: Trouble finding bad block on WDC WD1600SB-01KBA0

mathog <[email protected]> Tue, 10 Jan 2017 17:15:16 -0800
Newsgroups gmane.linux.utilities.smartmontools
Message-ID <[email protected]>
On 10-Jan-2017 02:07, Carlos E. R. wrote:
> On 2017-01-10 02:12, mathog wrote:
>> Hi,
>> 
>> One system has a WDC WD1600SB-01KBA0 which shows
>> 
>> 197 Current_Pending_Sector  0x0012   200   200   000    Old_age   
>> Always
>>        -       1
>> 198 Offline_Uncorrectable   0x0012   200   200   000    Old_age   
>> Always
>>        -       0
>> 199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age   
>> Always
>>        -       1
> 
>> Is there some other trick to find the thing?
> 
> I run "badblocks" with the intention of locating them, and they
> disappeared...

Rebooted that node into PLD Rescue CD over the network, ssh'd into it
and ran

    badblocks -nvs /dev/sda >/tmp/bb.log 2>&1 &

somewhere along the line the pending sector cleared, but there was no 
message
giving the block number, and it said there were no errors.  The 
UDMA_CRC_ERROR_COUNT is still 1.

So that worked.

Now, for the next time, is there a command one can use
while the OS is running and the disk mounted that can do something 
similar?
badblocks -n isn't happy running on mounted disks, and that badblocks
command took ~4.5 hours.

Thanks,

David Mathog
[email protected]
Manager, Sequence Analysis Facility, Biology Division, Caltech

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi