From: Guest section DW <dwguest@win.tue.nl>
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 22:00:32 +0200 [thread overview]
Message-ID: <20010617220032.A21156@win.tue.nl> (raw)
In-Reply-To: <00f501c0f74e$defac4e0$1901a8c0@node0.idium.eu.org> <017601c0f75d$454c6e70$1901a8c0@node0.idium.eu.org>
In-Reply-To: <017601c0f75d$454c6e70$1901a8c0@node0.idium.eu.org>; from David Flynn on Sun, Jun 17, 2001 at 07:42:33PM +0100
On Sun, Jun 17, 2001 at 07:42:33PM +0100, David Flynn wrote:
> 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
Your disk has 2116800 sectors of size 512, that is, 1083801600 bytes
(slightly over 1 GB).
> root:/root# cat /proc/ide/hdc/geometry
> physical 2100/16/63
> logical 525/64/63
>
> is there a geometry problem ?
Nothing wrong here.
> whats causing bad blocks to give apparently
> excessivly large bad blocks ...?
2116800 sectors of size 512 is the same as 1058400 blocks of size 1024.
Nothing is wrong with block 1006290 being mentioned.
Note that hdc1 is a partition on hdc, not all of hdc.
> > 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 },
At first sight this is just a rotten disk.
But since this is very close to the end of the disk, you might
investigate some details. (Some ZIP disks can be used as big floppy
and as removable disk, that is, without or with partition table,
and differ a little in size depending on what you do.
Don't know whether something similar could apply in your case.)
Of interest:
(i) the output of dmesg | grep hdc
(ii) the first sector that fails (is it this 2116604?)
Andries
next prev parent reply other threads:[~2001-06-17 20:00 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
2001-06-17 20:00 ` Guest section DW [this message]
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=20010617220032.A21156@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=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