<br><br><div><span class="gmail_quote">On 4/17/06, <b class="gmail_sendername">Alan McKinnon</b> <<a href="mailto:alan@linuxholdings.co.za">alan@linuxholdings.co.za</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Monday 17 April 2006 00:22, Yorvik wrote:<br>> Gary W. Swearingen wrote:<br>> > I'll propagate a rumor I heard: Use of "badblocks" has been<br>> > obsolete since drives started to remap their own bad blocks many
<br>> > years ago. You won't find bad blocks until after your drive has<br>> > found so many that it's better used as a doorstop.<br>> ><br>> > I beg to be corrected by someone with real knowledge.
<br>><br>> I was told a couple of years back, that if you can find bad blocks<br>> with 'normal user software' the drive has had it and may as well be<br>> chucked.<br><br>That's not true. There's many urban myths surrounding disks, and this
<br>is one of them.<br><br>> Personally, I can remember when harddisks had labels on them<br>> listing the bad blocks.<br><br>Those were MFM drives. Drive manufacturers soon got fed up with the<br>support calls from users as to why they shipped faulty disks - ALL
<br>drives have errors. Solution - disguise the errors. Modern drives<br>keep a small percentage of space free for bad blocks and as the<br>firmware picks up failing sectors, it remaps their location into this<br>unused space. The whole cyclinder/sector scheme is a pure abstraction
<br>anyway, so this works well.<br><br>When you run badblocks and pick up a few errors, all you are doing is<br>beating the drive firmware to the same job. When you find it with<br>user software, it means that the firmware has given up trying.
<br>Reading and writing to a disk is a tricky job (almost but not quite<br>entirely unlike reading and writing to RAM), and the firmware is<br>limited in what it can get the heads to do. The end result is that it<br>gives up easily, which opens up a nice market for third party
<br>software. This is most of what disk data recovery is about. Spinrite<br>is a good example and <a href="http://www.grc.com">http://www.grc.com</a> explains it all nicely as<br>long as you can read past Steve Gibson's hyped opinions.
<br><br>What you should be worried about is the *rate* at which bad sectors<br>are being produced. Once this passes a certain well-defined amount,<br>then the drive is becoming statistically more likely to fail. This is<br>
what SMART is all about.<br><br>So while what you were told is not completely wrong, it's over<br>simplified by a very big margin<br><br></blockquote></div><br>
so does this mean I shouldn't bother in testing my hard disks for its already taken care of?<br>