From: "whc86 (sent by Nabble.com)" <lists@nabble.com>
To: linux-raid@vger.kernel.org
Subject: troubleshooting PNY S-cure
Date: Mon, 17 Jul 2006 12:49:52 -0700 (PDT) [thread overview]
Message-ID: <5367261.post@talk.nabble.com> (raw)
I am setting up a mythtv backend server on fedora 5 using 5x Seagate 300gb
drives and PNY S-cure Raid 3. the bulk of the 1.2 TB is a jfs partition
while there is a 100 mb /boot partition in ext2 also. the OS runs from /
partition and /swap partition on a WD raptor on a different controller.
My raid array keeps losing drives. Its usually drive 3 but sometiems drive
4, but they usually rebuild and then thigns are reported as 'all is well'
again. No interruption to functionality during these drive failures for the
past 2 weeks (added the raid and drives to my comptuer 2 weeks ago)
Yesterday, i think drives 3 and 4 failed together-- after a reboot pny bios
said 3 and 4 not attached-- after anotehr reboot, it 'array rebuilding',
showing drive 3 as failed but 4 as fine. However, unlike the past failures,
this time i only get to a grub> prompt and dont know how to/if i can boot
the system
I have rma'd the card and two drives, but am curious about other reasons
this might be failing. How much power should i need? at first, all ran
from a single 400w fanless psu.
Athlon 2600, Asus A7v8x, gig of DDR333, raptor 74, 5x Seagate 7200 Sata, 2
optical drives, 2 PCI cards plus raid card
after first failure, took 400 w psu from the closet and shorted the 'on'
lead to the ground so it would run, then tied the ground from the closet psu
to the psu in my system. I put all hard drives on the closet psu and
resumed using the system. Things seemed to work better for a while but i
had another couple harmless failures and then the major one...
any help would be great!
thanks,
will
--
View this message in context: http://www.nabble.com/troubleshooting-PNY-S-cure-tf1956814.html#a5367261
Sent from the linux-raid forum at Nabble.com.
reply other threads:[~2006-07-17 19:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5367261.post@talk.nabble.com \
--to=lists@nabble.com \
--cc=linux-raid@vger.kernel.org \
--cc=willconstable@gmail.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).