Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
Sorry to bump such an old thread, but I have exactly the same issue (that is, using PE2950 with SAS 6/ir). The drives I'm using, is Seagate Barracuda 2TB (ST2000DM001).
I managed to get a drive online in bay 2, however, this only worked if I pulled out the other drives in bay0-1+3-5.
OP; did...
So, 6x2TB installed, using Dell SAS 6/iR (yes, it supports pass-through of devices not in any array).
Partitions on all 6 drives;
6x1MB: bios_grub
6x100MB: use as physical RAID
6x25GB: use as physical RAID
6x~2TB: use as physical RAID
mdraid using the above partitions (except bios_grup);
md0...
Okay, so I've bought a Dell SAS 6/iR. It has pass-through support of devices not in any array.
I'll stick with the WD2002FAEX, I think. I bought 2 more, and I'm going for 6x2TB in RAID6 using md-raid.
Thanks for all the help and inputs in this thread! (-:
Well, thats the core of the problem; this is a PERC 5/i, not a SAS 5/i. Hence, it's not a MPT-card.
In order for me to use this controller with md-raid, I have to set up the 6 drives as 6 individual RAID0's. This is what I'm concerned about, since the controller would be doing RAID against 6...
Would that be even if the drives is single RAID0 disks on the controller? I mean; the issue with TLER is between the drive and the controller, right? Or does mdraid actually figure these things out, even if the drive is running RAID0?
Maybe I'm asking stupid questions here, now, but...
Auch.
I haven't really decided what to do yet.
Currently I have 4x2TB WD2002FAEX, and 2x1TB Seagate ST1000DM003.
The original plan was to use 2x1TB in RAID1 as system-disks. Then put the 4x2TB as RAID5 for storage.
However, with this TLER-thing, it seems I'm stuck with two...
So, I got my storage-disks today; 4x 2TB WD2002FAEX.
I initialized two of them as RAID1, and did some tests on it;
Using 2.6-kernel;
jocke@noshut:~$ ./ddtest.sh
Testing 128k bs
time sh -c "dd if=/dev/zero of=ddfile1 bs=128k count=262144 && sync"
262144+0 records in
262144+0...
Ah, I see. I was kinda confused with the 10k vs 15k RPM, yes. (-:
'Write Back' and 'Adaptive Read Ahead' is enabled, so I think so. I'm not sure if there are any other "cache" settings that needs to be set?
So I would actually be better off with buying some newer drives? Could I expect the "lockups" during high IO to go away as well? Or is the latter more related to the controller, than the disks?
So, without any IO at all;
jocke@noshut:~$ time ls -alh /var | grep lolol
real 0m1.275s
user 0m0.000s
sys 0m0.000s
It's not consistent; i.e. it doesn't happen every time, but often enough.
This couldn't be caused by badly aligned partitions or something? Or just bad drives?
So, tried with new kernel (from backports, though, not sure if that has any effect?);
root@noshut:~# uname -a
Linux noshut 3.2.0-0.bpo.1-amd64 #1 SMP Sat Feb 11 08:41:32 UTC 2012 x86_64 GNU/Linux
root@noshut:~# cat /proc/version
Linux version 3.2.0-0.bpo.1-amd64 (Debian 3.2.4-1~bpo60+1)...
Phew. Good. Then I know that there is a problem. Started to wonder if I where trying to solve a problem that didn't exist (-:
Yes, "ancient" kernel (running Debian Squeeze).
root@noshut:~# uname -a
Linux noshut 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux...
Hi,
It seems like I'm having some performance-issues with my PERC 5/i card.
I have a Dell PE 2950, with a PERC 5/i installed. I have 2x 300GB Seagate Cheetah T10 15K RPM (ST3300555SS) in a RAID1-setup.
While copying stuff, or when doing dd-tests, the system is almost unusable...