(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version



Best of the Newsgroups: bad blocks on disk


What is this stuff?

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):



From: Bela Lubkin <belal@sco.com>
Subject: Re: opensever cmd=0x000000C8 on fixed disk
Date: Tue, 14 Oct 2003 18:09:24 GMT
References: <563ac914.0310140728.32e6d772@posting.google.com> 

tully wrote:

> i keep getting errors on this 80 gig drive, the blocks are usually
> different and badtrk does not seem to find anything.  What does the
> cmd C8 used for?  do we need a new one here?
> 
> example below:
> wd0: Error on fixed disk dev 1/42, block=8049847, cmd=0x000000C8
> status=0x00000040, LBA sector=16792639...



C8 is the "READ using DMA" command.  These are read errors on the disk.

When you say the blocks are "usually" different, what do you mean?  Have
you actually seen some where the block numbers were the same?

Modern drives do auto-sparing; that is, if they find a bad sector, they
replace it for you without having to bother the operating system (most
of the time).  There are a few different scenarios:

- Bad sector detected on a write: the drive can silently spare it out,
OS never needs to know a thing.

- Bad sector detected on a read: the drive will attempt many times to
read the data, seeking from different sides, trying different head
current strengths, whatever the particular drive is designed to do.  If
it eventually reads successfully, it can assign a spare sector, write
the data there, pass it back to the OS without informing it about the
problem.

- Bad sector detected on a read, and data was unrecoverable: then the
drive _has_ to tell the OS about the problem.  It will probably also
replace that sector with a spare (but the spare will contain garbage, or
[hopefully] all 0's or some other such intentional "blank" pattern).



You're seeing this problem on reads, which makes sense.  The fact that
it's actually coming through to the OS means that the sectors it's
finding are totally unreadable.

If a `badtrk` scan finds nothing, either there are no other bad sectors
at the time, or (if there are any) the drive is retrying and eventually
getting a good read.

And then if you get more bad sectors later, whatever is wrong is an
ongoing deterioration; as if, for instance, something has come loose
inside the drive and is bouncing around in there, scratching more and
more places on the media.

There's one thing to check before replacing the drive.  It's using Ultra
DMA.  Make sure that you have it attached with a proper 80-pin UDMA IDE
cable.  IDE connectors are 40 pins wide.  UDMA drives require an 80-pin
cable where the separating pins are ground lines.  Operating a UDMA
drive with a 40-pin cable can cause all sorts of bizarre behavior.

If that isn't the problem, you need to replace the drive.  Do not
overwrite your last few backups.  Make a new full backup.  Replace the
drive, restore onto it.  The older backups are important because you may
later notice that some files are corrupt; you will want several backups
from various time ranges to have the best possible chance of being able
to find a good copy.

>Bela<




Click here to add your comments



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



ad

/Bofcusm/2358.html copyright 1997-2004 (various authors) All Rights Reserved

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.



More:
       - OSR5
       - Bofcusm
       - Bela


Unix/Linux Consultants

Skills Tests

Guest Post Here











My Favorites

Change Congress