From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <aj@dungeon.inka.de>, <linux-kernel@vger.kernel.org>
Subject: Re: Why are bad disk sectors numbered strangely, and what happens to them?
Date: Sun, 12 Oct 2003 17:25:00 +0900 [thread overview]
Message-ID: <2bf201c3909a$98215330$5cee4ca5@DIAMONDLX60> (raw)
Andreas Jellinghaus replied to me with useful advice. But he didn't really
answer my questions. Please, if anyone knows the answers to my questions,
please kindly say.
(Why the sectors were numbered so strangely,
what does Linux do with them after detecting them,
and how to know if the errors occured during writes or during reads.)
Anyway,
> try the smartmontools package, it has "smartctl" that will
> show you the discs S.M.A.R.T. details
Good idea, thank you.
> doing a backup couldn't hurt.
It's essentially my crash box at the moment. But I didn't expect visible
errors on a 2-year-old disk. (Of course the magnetic layer always has
errors but I didn't expect things to get beyond the firmware's automatic
assignment and writing of replacement sectors.)
And my reason for posting is that the error logs didn't look the way I would
have expected, regarding the sector numbers and the repetitions.
> btw: are you sure cables are ok?
1. There are none.
2. If the connector on the motherboard were coming loose from the
motherboard, or if the motherboard had a crack causing intermittent failures
in some of its connections, surely the I/O errors would be far more numerous
and far more random than the strange occurences I observed.
next reply other threads:[~2003-10-12 8:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 8:25 Norman Diamond [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-13 9:31 Why are bad disk sectors numbered strangely, and what happens to them? 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
2003-10-11 9:00 Norman Diamond
2003-10-11 9:39 ` Andreas Jellinghaus
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='2bf201c3909a$98215330$5cee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=aj@dungeon.inka.de \
--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