public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Flynn" <Dave@keston.u-net.com>
To: "David Flynn" <Dave@keston.u-net.com>,
	"linux kernel mailinglist" <linux-kernel@vger.kernel.org>
Subject: Re: [slightly OT] IDE problems ? or just a dead disk ?
Date: Sun, 17 Jun 2001 19:42:33 +0100	[thread overview]
Message-ID: <017601c0f75d$454c6e70$1901a8c0@node0.idium.eu.org> (raw)
In-Reply-To: <00f501c0f74e$defac4e0$1901a8c0@node0.idium.eu.org>


> hi guys,
>         Since its relativley quiet at the moment, please excuse me for
> asking for some advice about the following problem.
>

i dont usually like following up my own sensless ramblings, but here is an
interesting twist (probabally caused by my ill understanding of the issues
involved)

ive done the badblock test, and compiled a list of 2302 bad blocks on this
disk ... however, when running mke2fs -l badblocfile /dev/hdc1

i got this interesting errormessage for every one of the bad blocks :

Bad block 1006290 out of range; ignored.

mke2fs said my disk was my disk would be 132480 inodes, 264592 blocks in
size ...

some bits in proc (well this capacity one i dont know what it measures)

root:/root# cat /proc/ide/hdc/capacity
2116800

root:/root# cat /proc/ide/hdc/geometry
physical     2100/16/63
logical      525/64/63

is there a geometry problem ? whats causing bad blocks to give apparently
excessivly large bad blocks ...?

any ideas ?

Thanks,

Dave

> for a while now ive had a disk that causes errors to occur during reads,
> however, ive finally got round to doing a
>
> # badblocks -c 32 -o mybadblocks  -w -v -s /dev/hdc
>
> so after one part of the test its found 2048 bad blocks, and dumped alot
of
> error messages, which look like this:
>
> kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604,
> sector=2116604
> kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604,
> sector=2116604
> kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604,
> sector=2116604
> kernel: ide1: reset: success
> kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604,
> sector=2116604
> kernel: end_request: I/O error, dev 16:00 (hdc), sector 2116604
> kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> kernel: hdc: read_intr: error=0x40 { UncorrectableError },
LBAsect=2116607,
> sector=2116607
> kernel: end_request: I/O error, dev 16:00 (hdc), sector 2116607
> kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> kernel: hdc: read_intr: error=0x40 { UncorrectableError },
LBAsect=2116608,
> sector=2116608
> kernel: end_request: I/O error, dev 16:00 (hdc), sector 2116608
> kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> kernel: hdc: read_intr: error=0x40 { UncorrectableError },
LBAsect=2116610,
> sector=2116610
>
> i have tried the disk in 2 systems, one Socket7 pentium and a PII /w a BX
> chipset ... the only thing i can think this is is either a geometry
problem
> ?? or a hard disk failiure ...
>
> anyone got any ideas ?
>
> Thanks.
>
> Dave
>



  reply	other threads:[~2001-06-17 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17 16:59 [slightly OT] IDE problems ? or just a dead disk ? David Flynn
2001-06-17 18:42 ` David Flynn [this message]
2001-06-17 20:00   ` Guest section DW
2001-06-21 20:51   ` John Fremlin

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='017601c0f75d$454c6e70$1901a8c0@node0.idium.eu.org' \
    --to=dave@keston.u-net.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