From: Brandon Evans <maillists@hosttuls.com>
To: Pau Montero Pares <pau@imente.com>
Cc: Linux Admin <linux-admin@vger.kernel.org>
Subject: Re: Drive Ready seek errors
Date: Mon, 07 Jun 2004 10:45:23 -0700 [thread overview]
Message-ID: <40C4A9B3.7050007@hosttuls.com> (raw)
In-Reply-To: <40C04A41.5070207@imente.com>
Pau Montero Pares wrote:
> Brandon Evans wrote:
>
>>> Could it be a power suply problem affecting several machines?
>>
>>
>> That's interesting because we recently had a power issue at our data
>> center.
>
>
> Can you verify if the hard disk armageddon happened just after this
> power issue?
>
I don't think it was the power issue. After talking with a co-worker I
found out
The power problem was due to a miscommunication. he thought we had X
amount of
amps, but had less. So when the last server got pluged in, the fuse went.
plus, the raq with the power problem was on a separate circuit then the raq
that has the servers with the hard drive problems.
--
Thanks,
Brandon E.
next prev parent reply other threads:[~2004-06-07 17:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 5:02 Drive Ready seek errors Brandon Evans
2004-06-03 9:54 ` Toby Fisher
2004-06-03 9:59 ` Pau Montero Pares
[not found] ` <40BF9824.4090002@hosttuls.com>
2004-06-04 10:09 ` Pau Montero Pares
2004-06-04 13:04 ` Chris DiTrani
2004-06-07 17:45 ` Brandon Evans [this message]
2004-06-03 21:24 ` Brandon Evans
2004-06-08 23:29 ` Toby Fisher
2004-06-08 23:30 ` Toby Fisher
2004-06-03 12:30 ` terry white
2004-06-03 21:30 ` Brandon Evans
2004-06-04 10:14 ` Alexander Economou
2004-06-05 10:15 ` a Maxtor story (was: Drive Ready seek errors) markus reichelt
2004-06-05 16:10 ` a Maxtor story Ben Potter
2004-06-05 16:32 ` DragonK
2004-06-05 16:33 ` Ben Potter
2004-06-07 13:46 ` Yu Chen
2004-06-05 18:26 ` Scott Taylor
2004-06-03 13:04 ` Drive Ready seek errors Miguel González Castaños
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=40C4A9B3.7050007@hosttuls.com \
--to=maillists@hosttuls.com \
--cc=linux-admin@vger.kernel.org \
--cc=pau@imente.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;
as well as URLs for NNTP newsgroup(s).