From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Simon Turvey <turveysp@ntlworld.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE error on 2.4.17
Date: Tue, 26 Feb 2002 15:48:42 -0500 [thread overview]
Message-ID: <3C7BF4AA.6C31212F@nortelnetworks.com> (raw)
In-Reply-To: <E16fmJt-0001Xi-00@the-village.bc.nu> <006e01c1bef6$6dd78e40$030ba8c0@mistral> <20020226110134.B11982@greenhydrant.com> <009301c1bef9$84dee9a0$030ba8c0@mistral>
Simon Turvey wrote:
>
> It's a dev box anyway - just for tinkering. Even so, it's annoying.
>
> Someone asked what the drive model was: IBM-DTLA-305030.
That's your problem right there. I've had two of the DTLA drives die, a 15GB
and a 45GB. They're notorious. They sent me back a new 120GXP-series 60GB one
to replace the 45 gigger. Hopefully it'll last a bit longer...
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-02-26 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 17:38 IDE error on 2.4.17 Simon Turvey
2002-02-26 17:58 ` André Dahlqvist
2002-02-26 18:20 ` Mohammad A. Haque
2002-02-26 18:27 ` Alan Cox
2002-02-26 18:50 ` Simon Turvey
2002-02-26 19:01 ` David Rees
2002-02-26 19:12 ` Simon Turvey
2002-02-26 20:48 ` Chris Friesen [this message]
2002-02-26 19:10 ` Alan Cox
2002-02-26 19:09 ` Simon Turvey
2002-02-26 20:03 ` Hans-Christian Armingeon
2002-02-26 20:05 ` Skip Ford
2002-02-27 9:47 ` Vojtech Pavlik
2002-02-27 10:25 ` [PATCH] " Erik Andersen
2002-02-27 14:59 ` Alan Cox
2002-02-27 18:47 ` Jan Niehusmann
2002-02-27 18:53 ` Andre Hedrick
2002-02-27 19:26 ` Jan Niehusmann
2002-02-27 19:54 ` Chris Friesen
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 19:11 Costa, Juliano
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=3C7BF4AA.6C31212F@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=turveysp@ntlworld.com \
/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