From: "David Flynn" <Dave@keston.u-net.com>
To: "linux kernel mailinglist" <linux-kernel@vger.kernel.org>
Subject: Via KT133 and 2.4.8 and a hard disk problem ?
Date: Sun, 28 Oct 2001 11:57:46 -0000 [thread overview]
Message-ID: <045301c15fa7$c2809b70$1901a8c0@node0.idium.eu.org> (raw)
All;
What is the status of the problems with the old KT133 and kernel 2.4.8 ?
I have a system here which looks to me as if its beginning to suffer from
HDD failure, just do anything with the disk for a while and you get disk {
busy } errors (and there is an 0x0d error code there somewhere) ... (oh, and
the HDD light reports no activity) normally, i would view this as a good
time to pull all the data off the drive and replace it.
However, i have noticed that the chipset used is the Via KT133, and am now
wondering if this is actually a HDD problem (i still am siding with this) or
a chipset problem.
You can guarantee the problem by just running badblocks -sv /dev/hda
and it will happen at some point, (not always the same place)
Can anyone offer any advice on this ?
Thanks,
Dave
next reply other threads:[~2001-10-28 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 11:57 David Flynn [this message]
2001-10-28 12:34 ` Via KT133 and 2.4.8 and a hard disk problem ? Martin Eriksson
2001-10-28 20:46 ` David Grant
2001-10-28 22:03 ` Martin Eriksson
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='045301c15fa7$c2809b70$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