similar to: HW experience

I have 15x SAS drives in a Dell MD1000 enclosure, attached to an LSI 9200-16e. This has been working well. The system is boothing off of internal drives, on a Dell SAS 6ir. I just tried to add a second storage enclosure, with 15 more SAS drives, and I got a lockup during Loading Kernel. I got the same results, whether I daisy chained the enclosures, or plugged them both directly into the LSI

Hi, We bought a new Dell PowerEdge 2950III with Perc 6/i and have the disk geometry problem using 6.3 final or 7.0 RC1. Seems that we are not alone at least one guy has similar problem reported earlier: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-01/msg00506.html I was reading the mailing list and found that some of the people are happily using this hardware with the latest

we have several DELL R900 with PERC 6/E adapter in it. R900 using Redhat Linux. Each R900 have two PERC 6/E adapter and at least two MD1000 connect to it. Configuration 1: PERC 6/E -- two MD1000 PERC 6/E -- empty Configuration 2: PERC 6/E -- MD1000 PERC 6/E -- MD1000 Normally first MD1000 for database and second MD1000 for nightly backup. My

We have DELL R900 server with PERC6/i and PERC 6/E in it. O.S. is CENTOS 5.3. I download latest PERC 6 driver from DELL site and tried to installed it. I have error messages said : Module version 00.00.03.21 for megaraid_sas.ko is not newer than what is already found in kernel 2.6.18-128.1.10.el5 (00.00.04.01-RH1). Does CENTOS 5.3 come with PERC6 driver? I knew in CENTOS 4.X PERC 5 or PERC6

I have a Dell R710 which has been flaky for some time. It crashes about once per week. I have literally replaced every piece of hardware in it, and reinstalled Sol 10u9 fresh and clean. I am wondering if other people out there are using Dell hardware, with what degree of success, and in what configuration? The failure seems to be related to the perc 6i. For some period around the time

I need to replace a slow HP MSA20 that's a bottleneck right now (We are an HP shop). HP's only option with 3.5" SATA drives is stuck at SATA I behind a SAS controller. Dell makes an MD1000 that claims SATA II speeds behind a SAS Perc 5/E (Don't know anything about dell). Anyone got any real world info they can share? I need 3.5" SATA II at least 12 drives behind SAS, I am

Hello everyone. I'm wondering what other people's experiences are WRT systems becoming unresponsive (unable to ssh in, etc) for brief periods of time when a large amount of IO is being performed. It's really starting to cause a problem for us. We're on Dell PowerEdge 1955 blades - but this same issue has caused us problems on PE1950, PE1850, PE1750 servers. We're running

We have DELL server with MD1000 Disk array in it. O.S. is CENTOS 5.5. Recently every time MD1000 "patrol read" start I will get "media error" messages on /var/log/message file. I use MD1000 "slow initialize" to initialize "bad disk" and NO error. After "slow initialize" finish, I manually "startup patrol read". I continue get

I have a perc5i (and perc5e) raid controller in my poweredge 2970 running centos 5.5. The RAID controller config is set for write-back policy, which I can confirm by checking in OpenManage. I also called Dell and ran their reporting application and had them double check to make sure everything looks OK hardware wise and they confirm that it does Yet when CentOS boots is appears to use the

we have DELL server (CENTOS 4.X) with MD1000 connect on it. One of Raid5 (internal 4 disks) has hard disk bad and I replace it. I saw /var/log/messages have following entry: ======================================= Aug 18 15:33:20 host1 Server Administrator: Storage Service EventID: 2049 Array disk removed: Array Disk 0:11 Controller 1, Connector 0 Aug 18 15:34:09 host1 Server Administrator:

Is anybody here monitoring Dell SAS6/iR RAID health? I have a mix of CentOS 5.9 and 6.3 installs on the PE1950s. I'm finding drivers and Megaraid Storage Manager downloads via LSI's site, but I'd prefer not to install a bunch of crapware. All I need is the proper LSI daemon which exports info via SNMP. I've used check_sasraid_megaraid Nagios script [0] in the past for PERC5i and

we have DELL R900 with CENTOS 5.3 in it. This DELL R900 come with one integrate PERC6/I and two PERC6/E card. DELL 6/I control 5 internal disks. The original disk sequence are: /dev/sda1 /boot /dev/sda2 / /dev/sdb1 swap ... after I configured PERC6/E disks and reboot, /dev/sda change to RAID disk and original /boot and / change to /dev/sde1 and /dev/sde2. My modprobe.conf is: alias

Hi, we are currently working on getting windows working on your xen servers. but we are facing a severe problem where dom0 and all domus hang for 1-5 seconds from time to time. we think it is probably because of disk i/o, because top sometimes says 100% wa (waiting on io) during the hang. dom0 has cpu 0 for exclusive use and the windows vms use cpu 1 to 7. should we give dom0 more than once

While thinking about ZFS as the next generation filesystem without limits I am wondering if the real world is ready for this kind of incredible technology ... I''m actually speaking of hardware :) ZFS can handle a lot of devices. Once in the import bug (http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6761786) is fixed it should be able to handle a lot of disks. I want to

we have DELL server with Centos 5.3 X86_64 bits version on it. This server also have couple MD1000 connect to it. We configured MD1000 as one hardware Volume size 2990GB. I tried to use "fdisk" to partition this 2990Gb volume and "fdisk" can only see 2000GB. does 64 bits O.S. still have 2TB limitation on File system? Does there has other tool can partition disk size large

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

We have several DELL servers with MD1000 connect to it. Server will install CENTOS 5.x X86_64 version. My questions are: 1. Which configuration have better performance RAID5, RAID50 or RAID60? 2. how much performance difference? ___________________________________________________ ??????? ? ???????????????? http://messenger.yahoo.com.tw/

Hi, I've installed CentOS 5 on a Dell pe1950 with 2 dual port NICS. One of the NIC is an Intel and use the e1000 module. The problem is when the server is rebooted it does no asign the ethx name to the NICs, instead the so assign something like _dev377362... so i dont have networking on the server. Any ideas what is happening and how to solve it? Thanks. -------------- next part

On 6/17/20 9:59 AM, Deventer-2, M.S.J. van wrote: > Hi, > > the first thing that comes to mind, did you set ip_forward to enable in > /etc/sysctl.conf ? > net.ipv4.ip_forward = 1 > > Should explain why you IP on the bridge works but not on the vms. > First, thanks for the reply and excellent suggestion.? Yeah, I thought about that, and while it's not specifically