public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Cc: Andre Costa <costa@tecgraf.puc-rio.br>, ballen@gravity.phys.uwm.edu
Subject: Re: 2.4.26: IDE drives become unavailable randomly
Date: Thu, 01 Jul 2004 19:43:58 +0100	[thread overview]
Message-ID: <40E4697E.28752.15EB61B8@localhost> (raw)
In-Reply-To: <20040701074933.722e40e4.costa@tecgraf.puc-rio.br>

> (please cc me on any replies, I am not subscribed to this list)
> 
> On Thu, 1 Jul 2004 04:48:30 -0500 (CDT)
> Bruce Allen <ballen@gravity.phys.uwm.edu> wrote:
> 
> > > I was getting this problem, and advice from smartmontools people was
> > > to clean out the box and reseat all cables etc.  Seemed to work for 
> > > me on the box at work with this DMA timeout issue - BTW, always 
> > > happened at idle, like 2:15am in the middle of the night etc.
> > > 
> > > Reference: 
> > > http://sourceforge.net/mailarchive/message.php?msg_id=8660397
> > > http://sourceforge.net/mailarchive/forum.php?thread_id=4908273&forum_i
> > > d=12495
> > 
> > An additional reference. See the entry that starts 'System freezes
> > under heavy load" in:
> > http://cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/WARNINGS?view=markup
> > 
> > Cheers,
> > 	Bruce
> 
> 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.

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.

Regards,

Nick

-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 15:18 2.4.26: IDE drives become unavailable randomly Nick Warne
2004-07-01  9:48 ` Bruce Allen
2004-07-01 10:49   ` Andre Costa
2004-07-01 18:43     ` Nick Warne [this message]
2004-07-01 19:03       ` Andre Costa
  -- 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=40E4697E.28752.15EB61B8@localhost \
    --to=nick@ukfsn.org \
    --cc=ballen@gravity.phys.uwm.edu \
    --cc=costa@tecgraf.puc-rio.br \
    --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