Thread (8 messages) 8 messages, 6 authors, 2009-05-30

Re: Raid and badblocks

From: John Robinson <hidden>
Date: 2009-05-30 13:29:59

On 30/05/2009 11:13, hank peng wrote:
2009/5/26 Andrew Burgess [off-list ref]:
quoted
On Tue, 2009-05-26 at 13:59 +0100, Jeremy Sanders wrote:
quoted
Strangely, the Reallocated_Sector_Ct is still zero on the drive even though
Current_Pending_Sector is now zero. This is a Samsung HD103UJ by the way.
That can be ok. It probably tried writing and then rereading and when
that worked it decided the sector didn't really have a 'hard' error
(like a physical defect on the platter) and thus didn't need to be
reallocated to a spare sector. You could generate an unreadable sector
during a write by the power failing or with excessive vibration.
I have a question, in this situation, if I do as Jeremy did, write
zero to bad block to make drive think it is not bad any more, then
what about old data? Isn't it lost?
In Jeremy's case, the bad block was past the end of the data in the 
array, so no, data wasn't lost. If the bad block had been within the 
array data, the repair operation he ran earlier would have found it, 
reconstructed the correct data from the other drives, and rewritten it, 
again avoiding any data loss.

Cheers,

John.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help