mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: "Wahlman, Petter" <Petter.Wahlman@compaq.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Marking sectors on IDE drives as bad
Date: Tue, 23 Jan 2001 08:28:37 -0700 (MST)	[thread overview]
Message-ID: <200101231528.f0NFSbb30649@webber.adilger.net> (raw)
In-Reply-To: <E7D21F6C2128D41199B600508BCF8D54A9AD67@nosexc01.nwo.cpqcorp.net> "from Wahlman, Petter at Jan 23, 2001 11:34:11 am"

You write:
> I'm experiencing some fscking problems due to a defective IDE drive.
> 
> exerpt from /var/log/messages:
> Jan 22 09:31:29 evil kernel: hda: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Jan 22 09:31:29 evil kernel: hda: read_intr: error=0x01 { AddrMarkNotFound
> }, LBAsect=10262250, sector=1311147
> Jan 22 09:31:29 evil kernel: ide0: reset: success
> Jan 22 09:31:29 evil kernel: hda: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Jan 22 09:31:29 evil kernel: hda: read_intr: error=0x40 { UncorrectableError
> }, LBAsect=10262250, sector=1311147
> Jan 22 09:31:29 evil kernel: end_request: I/O error, dev 03:05 (hda), sector
> 1311147
> 
> Is it possible to somehow mark the above sector as bad (in ll_rw_block.c or
> similar) to circumvent the problem?

Chances are, you should replace the drive, because this sort of problem
usually gets worse as time goes on.

That said, it is possible for ext2 to mark the sectors bad (assuming you
use ext2 and not reiserfs), and then they will never be used.  You can
use the "badblocks" program in conjunction with e2fsck or mke2fs to mark
the blocks bad in the filesystem.

I would suggest keeping good backups after that.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-23 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23 11:34 Wahlman, Petter
2001-01-23 15:28 ` Andreas Dilger [this message]
2001-01-26 10:36 Wahlman, Petter
2001-01-26 10:49 ` Andrzej Krzysztofowicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200101231528.f0NFSbb30649@webber.adilger.net \
    --to=adilger@turbolinux.com \
    --cc=Petter.Wahlman@compaq.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®