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

On 2017-01-11 18:42, mathog wrote:
> On 11-Jan-2017 07:25, robert@ wrote:
>> I've also seen the UDMA_CRC_ERROR_COUNT caused by a bad SATA cable.
> 
> OK, I will make a note to look at the cable if this unit ever has 
> problems like this again.  (It could have been a gamma ray or something 
> hitting a gate, right?)
> 
> Now I'm trying to understand what happened here.  My best guess is that 
> it went something like this (leaving out a few steps):
> 
> 1.  some issue with cable, connectors, radiation etc. arose.
> 2.  a write to a specific block, presumably with new data, ran
>      into (1) and failed.

If this happens during a write, the sector is reallocated. If it happens
during a read, reallocation is postponed and the sector noted. I don't
know if it creates a list and how to read that list.

Reallocation happens during an attempted write, to another permanent
location.

I don't know what happened during the badblock run, because it is a read
operation.


-- 
Cheers / Saludos,

		Carlos E. R.
		(from 42.2 x86_64 "Malachite" at Telcontar)

------------------------------------------------------------------------------
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

_______________________________________________
Smartmontools-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartmontools-support

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlh2nJYACgkQtTMYHG2NR9W9sACfe0r+R7CeBtVoIhhv3OexX2Z0
28wAn3Y+e1nZBjA6wR1yyzMuqHEW5bfG
=j1yd
-----END PGP SIGNATURE-----