mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Costa <costa@tecgraf.puc-rio.br>
To: "Nick Warne" <nick@ukfsn.org>
Cc: linux-kernel@vger.kernel.org, ballen@gravity.phys.uwm.edu
Subject: Re: 2.4.26: IDE drives become unavailable randomly
Date: Thu, 1 Jul 2004 16:03:42 -0300	[thread overview]
Message-ID: <20040701160342.26c557b0.costa@tecgraf.puc-rio.br> (raw)
In-Reply-To: <40E4697E.28752.15EB61B8@localhost>

(please cc me on any replies, I am not subscribed to this list)

Hi Nick,

On Thu, 01 Jul 2004 19:43:58 +0100
"Nick Warne" <nick@ukfsn.org> wrote:

[snip]
> > Thks, folks, I wouldn't really suspect of bad cables/PSU, this was
> > an eye-opener. I have just opened the box and reseated the 80-wire
> > IDE cable to my hda device, and I will consider replacing it, just
> > in case. The PSU is brand new, 450W -- although it could be bad
> > quality, I will try to check this out.
> > 
> > BTW: Nick, I missed your msg because you didn't cc me. My hda also
> > usually gets disconnected at early hours in the morning, as you
> > pointed out. I arrived today to work and it had happened again =/
> > Last entry on/var/log/messages was around 1:30am, and it was about a
> > NFS mount that had expired.
> > 
> > Best,
> > 
> > Andre
> 
> Hi Andre,
> 
> Sorry, I too am not subscribed to the list, and I read (and reply to) 
> from:
> 
> http://marc.theaimsgroup.com/?l=linux-kernel
> 
> I totally overlooked CC'ing you.

No worries. I have to remind myself over and over again to put the
"please cc me" header on every msg =)

> Anyway, new IDE cable did fix the box at work for me.  Also I only 
> used smartd AFTER the problem arose, not before, so it was not smartd 
> that caused it.

Thks, this is definitely valuable info. I will surely go after some new
cables to see if it improves my situation (I hope it does, otherwise I
will have to move services away from this box and relocate them to other
servers, which will be a PITA...)

On a side note, I browsed 2.4.27rc2 changelogs today, and there is some
interesting stuff there about interruptions, ACPI etc. Looking forward
to trying it out.

Thks again,

Andre

-- 
Andre Oliveira da Costa
(costa@tecgraf.puc-rio.br)

  reply	other threads:[~2004-07-01 19:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 15:18 Nick Warne
2004-07-01  9:48 ` Bruce Allen
2004-07-01 10:49   ` Andre Costa
2004-07-01 18:43     ` Nick Warne
2004-07-01 19:03       ` Andre Costa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30 11:41 Andre Costa
2004-06-30 13:59 ` tom st denis
2004-06-30 14:51   ` Andre Costa

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=20040701160342.26c557b0.costa@tecgraf.puc-rio.br \
    --to=costa@tecgraf.puc-rio.br \
    --cc=ballen@gravity.phys.uwm.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@ukfsn.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

all inboxes | Powered by JetHome®