From: Adam Talbot <talbotx@comcast.net>
To: Nix <nix@esperi.org.uk>
Cc: Gordon Henderson <gordon@drogon.net>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-raid@vger.kernel.org
Subject: Disks keep failing durning testing
Date: Wed, 14 Jun 2006 13:38:05 -0700 [thread overview]
Message-ID: <449073AD.3000809@comcast.net> (raw)
In-Reply-To: <87zmgfn562.fsf@hades.wkstn.nix>
You guys are going to love this one... I have ripped most of my hair
out because of this bug and can not track down the problem!
When ever I build my new array I looses a disk in slot N. So, a bad
disk? Move that disk to a different slot in my drive cage, rebuilds
just fine. New disk in slot N fails... Bad cable? Replace the cable
to slot N... Drive in slot N still fails. Get mad at drive cage. Get
new drive cage... Same slot "N" in new drive cage fails... Bad
controller card? New controller card. So I have now replace the drive,
drive cage, cable, controller card... I am going mad. My mother board
has 4 onboard SATA ports, I have never had a drive fail on any of those
4 ports... Concept test. Took 4 "Failed" drives and installed them
in the 4 slots the connected to the onboard SATA's... build array. The
array built in record time, and built at 50MB/sec! 4 disk array works
fine? Ok, try test 9 more times, just to be sure. Never once did the
array fail during building or testing in the 4 drive/onboard state.
What is wrong with my controller cards! I can connect them to any one of
the drives in my array, to any slot in the cage and watch that drive
fail... The drive(s) never fails at the same stop.
All disks now have over 1000 error in the SMART Logs !@#$. All the
exact same error:
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
35 00 f8 08 08 00 e0 00 00:06:26.949 WRITE DMA EXT
35 00 f8 08 08 00 e0 00 00:06:26.907 WRITE DMA EXT
35 00 f8 08 08 00 e0 00 00:06:26.866 WRITE DMA EXT
35 00 f8 08 08 00 e0 00 00:06:26.824 WRITE DMA EXT
35 00 f8 08 08 00 e0 00 00:06:26.782 WRITE DMA EXT
My NAS's hardware.
AMD Athlon 64 3000
1024MB DDR400
Foxconn 6150K8MA-8EKRS Motherboard
Off brand 6X SATA drive cage
6X MaxLine 300GB SATAII 7200RPM Hard drive.
Promise SATA300 TX2plus controller card
Silicon Image, Inc. SiI 3112 controller card
Any ideas?
-Adam
next prev parent reply other threads:[~2006-06-14 20:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 0:37 to understand the logic of raid0_make_request liu yang
2006-06-13 0:49 ` Neil Brown
2006-06-13 1:18 ` RAID tuning? Adam Talbot
2006-06-13 10:19 ` Gordon Henderson
2006-06-13 10:21 ` Justin Piszcz
2006-06-13 10:23 ` Justin Piszcz
2006-06-13 10:32 ` Gordon Henderson
2006-06-13 17:57 ` Adam Talbot
2006-06-13 21:38 ` Gordon Henderson
2006-06-14 15:11 ` Nix
2006-06-14 15:35 ` Molle Bestefich
2006-06-14 20:38 ` Adam Talbot [this message]
2006-06-14 21:45 ` Disks keep failing durning testing PFC
2006-06-14 23:23 ` Adam Talbot
2006-06-15 12:12 ` Leo Kliger
2006-06-13 18:45 ` to understand the logic of raid0_make_request Bill Davidsen
2006-06-16 2:53 ` liu yang
2006-06-16 4:32 ` Neil Brown
2006-06-16 5:14 ` RAID on the root partition / Adam Talbot
2006-06-16 6:13 ` Neil Brown
2006-06-16 6:55 ` Gordon Henderson
2006-06-16 13:41 ` to understand the logic of raid0_make_request liu yang
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=449073AD.3000809@comcast.net \
--to=talbotx@comcast.net \
--cc=gordon@drogon.net \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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).