From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <linux-kernel@vger.kernel.org>
Subject: Why are bad disk sectors numbered strangely, and what happens to them?
Date: Sat, 11 Oct 2003 18:00:31 +0900 [thread overview]
Message-ID: <227d01c38fd6$2e4764f0$5cee4ca5@DIAMONDLX60> (raw)
My first question is why the bad disk sectors are numbered strangely, and
second is what does Linux do with them after detecting them?
I repartitioned and reformatted two Reiser partitions before installing SuSE
8.2 and then compiling kernels 2.6.0-test5, test6, and test7. My feeling is
that the following errors "should" have been detected during writes, so the
damage "should" not be too bad. The correct data "should" get written to
replacement sectors. But my understanding of modern ATA drives is that the
firmware "should" have detected the errors during writes and "should" have
finished the work without the OS knowing about it.
If the following errors occured during reads then I have some pretty angry
questions about why they didn't get detected during writes, especially when
the writes occured minutes or milliseconds prior to the reads. (I'll copy
this message to some Toshiba employees. Maybe the next time they visit,
certain persons should get cat food instead of my wife's cooking _^o^_
MK4018GAP, about 2 years old.)
Hmm, I guess I also need to ask how to figure out if these occured during
writes or reads.
Meanwhile, it seems really strange to see separate numbers for LBAsect and
sector, and to see that the two numbers are sometimes related but sometimes
apparently unrelated, and to see LBAsect remain constant while sector
changes with each error. What is really going on here?
Also kernel 2.6.0-test7 no longer says whether hda was on 03:08 or 03:00
when the errors were detected.
Sep 27 16:49:41 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 27 16:49:41 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=852296
Sep 27 16:49:41 diamondpana kernel: end_request: I/O error,
dev 03:08 (hda), sector 852296
Sep 27 16:49:41 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 27 16:49:41 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=852304
Sep 27 16:49:41 diamondpana kernel: end_request: I/O error,
dev 03:08 (hda), sector 852304
[comment: no more that day]
Sep 28 15:20:20 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:20 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021784
Sep 28 15:20:20 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021784
Sep 28 15:20:20 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:20 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021786
Sep 28 15:20:20 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021786
[... every even-numbered sector in this range ...]
Sep 28 15:20:21 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:21 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021880
Sep 28 15:20:21 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021880
Sep 28 15:20:21 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:21 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021882
Sep 28 15:20:21 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021882
[comment: after hitting equality, it soon repeated from the middle]
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021832
Sep 28 15:20:26 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021832
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021834
Sep 28 15:20:26 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021834
[... every even-numbered sector in this range ...]
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021880
Sep 28 15:20:26 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021880
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 28 15:20:26 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021882
Sep 28 15:20:26 diamondpana kernel: end_request: I/O error,
dev 03:00 (hda), sector 19021882
[comment: after hitting equality again, no more that day]
Sep 29 01:24:09 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 29 01:24:09 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=852296
Sep 29 01:24:09 diamondpana kernel: end_request: I/O error,
dev 03:08 (hda), sector 852296
Sep 29 01:24:09 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 29 01:24:09 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=852304
Sep 29 01:24:09 diamondpana kernel: end_request: I/O error,
dev 03:08 (hda), sector 852304
[comment: same sectors as on Sep 27]
Oct 10 18:29:29 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Oct 10 18:29:29 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021842
Oct 10 18:29:29 diamondpana kernel: end_request: I/O error,
dev hda, sector 19021842
Oct 10 18:29:29 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Oct 10 18:29:29 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021850
Oct 10 18:29:29 diamondpana kernel: end_request: I/O error,
dev hda, sector 19021850
[... every 8th sector in this range, congruent to 2 modulo 8 ...]
Oct 10 18:29:30 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Oct 10 18:29:30 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021874
Oct 10 18:29:30 diamondpana kernel: end_request: I/O error,
dev hda, sector 19021874
Oct 10 18:29:30 diamondpana kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Oct 10 18:29:30 diamondpana kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=19021882, sector=19021882
Oct 10 18:29:30 diamondpana kernel: end_request: I/O error,
dev hda, sector 19021882
[comment: some of the same sectors as on Sep 28]
next reply other threads:[~2003-10-11 9:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 9:00 Norman Diamond [this message]
2003-10-11 9:39 ` Why are bad disk sectors numbered strangely, and what happens to them? Andreas Jellinghaus
-- strict thread matches above, loose matches on Subject: below --
2003-10-12 8:25 Norman Diamond
2003-10-13 9:31 Norman Diamond
[not found] ` <200310131014.h9DAEwY3000241@81-2-122-30.bradfords.org.uk>
2003-10-13 10:24 ` Norman Diamond
2003-10-13 10:33 ` John Bradford
2003-10-13 11:30 ` Norman Diamond
2003-10-13 11:58 ` Maciej Zenczykowski
2003-10-15 10:22 ` Norman Diamond
2003-10-13 12:02 ` John Bradford
2003-10-15 10:23 ` Norman Diamond
2003-10-15 18:56 ` Pavel Machek
2003-10-14 6:54 ` Rogier Wolff
2003-10-13 14:24 ` Chuck Campbell
2003-10-13 14:54 ` Maciej Zenczykowski
2003-10-13 16:29 ` Roger Larsson
2003-10-14 6:49 ` Rogier Wolff
2003-10-14 7:05 ` Wes Janzen
2003-10-14 7:21 ` John Bradford
2003-10-14 7:40 ` Rogier Wolff
2003-10-14 8:11 ` John Bradford
2003-10-14 8:45 ` Hans Reiser
2003-10-14 9:46 ` Rogier Wolff
2003-10-14 9:57 ` Hans Reiser
2003-10-14 10:10 ` Rogier Wolff
2003-10-14 10:31 ` Hans Reiser
2003-10-14 10:19 ` John Bradford
[not found] ` <200310140800.h9E80BT9000815@81-2-122-30.bradfords.org.uk>
[not found] ` <20031014081110.GA14418@bitwizard.nl>
2003-10-14 8:55 ` Wes Janzen
2003-10-14 10:05 ` Rogier Wolff
2003-10-14 7:24 ` Rogier Wolff
2003-10-14 9:04 ` Hans Reiser
2003-10-15 10:23 ` Norman Diamond
2003-10-15 10:39 ` Hans Reiser
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='227d01c38fd6$2e4764f0$5cee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--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;
as well as URLs for NNTP newsgroup(s).